I have ordered the additional parts at reichelt. I put the cable in Trigger Out 1 and then in the Sequencer Trigger In of a JX3P. I tested with an A4 of Elektron and all works fine. I put the jumper on the right two pins which are labeld "STRIG".
you have to set the BPM to '0' for the clock input to work. As with external midi sync. also there is a new trigger settings page to select the prescaler/clock resolution.
shift + Load/save button => takes you to the global setings page now you can select the trigger settings page with the AEG button
Just took my case apart to install my Triggers (built from PCB only) and I find that the 5 jumpers for DAC2 on my batch 1 main board near the rear panel are preventing me from placing the trigger PCB in the correct place.
Are these likely to come in handy in the future or can I remove them to place my board?
how come they are in the way? did you use another kind of jacks that are too high? here it is a tight fit, but the jacks can be placed just below the jumpers.
without the green DAC2 jumpers your first audio output pair won't work. you coukd however remove the green jumpers and clip of a little bit of the pins (not all), then use solder instead of the jumpers to connect the pins. this way you should save some millimeters.
I used the Jacks on the mouser bom (the untested ones!) if the jumpers won't be required in the future I'll remove them and solder in a wire link, I'll never get a socket on them anyway.
I was just thinking that there must be a reason they were jumpers there in the first place, so if they might be needed in the future I'll figure out a way to place the IO board and keep the jumpers
haven't setup my trigger expansion yet but I was wondering if there is an option to change the pulse width of the trigger pulse per track. Would be sick if we could do p locks with pulse width too in the future. Looking to replace my trigger riot with this expansion and that is one thing that is pretty nice about the trigger riot. Trigger riot pulse width changes are pretty sick when pinging various CV ins on the modular.
it is not implemented yet. (or i am not aware of it) i think the pulses are relatively small atm, too. works for triggering stuff like 808/909 modules, but for directly driving AD env module for example, i sometimes wish they would be longer.
+1 for what owensands suggested. it might be connected to the noteoff thing. (might make sense to tie the trigger going low to the note off getting sent - if this will ever be implemented)
at the moment you can't set the length and it are indeed quite short pulses. working fine for my qmmg thiugh
tying them to the note off would be easy, I just wonder if it wouldn't be too long to output gates instead of trigger pulses for a lot of applications?
I could add an option to the trigger config page to select (global) between gates and trigger pulses.
I think the gates option would add a lot of tweaking possibilities for modular users, go for it. Most circuits respond to the rising edge of a pulse, so for users triggering events (AD enveloped, analog drum patches, sequencer resets, etc.. ) there wouldn't be a difference, but for circuits that hold while gate is high (ADSR's for ex) there would be a great use for this.
If you can tie steps of a pattern together to create long "note on" periods on the LXR (?) This would give long analog gates out, very useful in the analog world, especially in conjunction with the short pulse/triggers.
If there is an easy way to implement this functionality anyway at all it would be great. It would make the trigger expansion 2X as useful imo. Not that it isnt already i'm sure! cant wait to set mine up. Kit should be here next week i'm hoping.
to give an example the other night I was rhythmically opening up the the wavefolder gain and FM CV in to two different trigger patterns from the trigger riot while a sequence was playing from the cyclebox II. The patterns had varying pulse widths for different clock divisions for the triggers for the trigger out I was using. So you got this nice varied lengths of the wavefolding and FM happening. and in time! If this was doable with the LXR it would be even better because it has shuffle! trigger riot doesn't but it has micro timing but its really a pain in the ass to program with the encoders. the xoxxox style editing on the LXR for trigger patterns will be killer!
that trigger riot looks like fun. way to expensive for me right now though. i don't even have enough of the very basic modules yet.
adding any kind of gate length to the lxt would be really nice. not sure, if some modules need just a small trigger and won't function with gates, but i think the global menu option is a good idea.
@revok: not without hardware modifications. i don't think the processor pins that are used for the triggers are able to output analog voltages. they probably could be used to talk to an external dac though. other than the dac there would be the need to use some opamps for scaling/buffering.
as an alternative, the pins could probably be used to output voltages using pwm. (in which case modifications would also be needed to filter the pwm signals)
no CV possible with the current hardware setup. It could probably be hacked in. I think there is still an unused 12bit DAC channel free if I did not use it for another purpose by now (would have to check the schematic)
regarding the gate length: how would you suggest to implement it? i just implemented a "gate mode on/off" parameter for the trigger config page. But just tying it to the noteOn/Off MIDI message yields no good results. It ends up giving high triggers all the time, with a short low signal before the next note starts. So you are basically back to setting steps with 0 velocity to define the note off point for the trigger.
I could either make the gate mode On/Off parameter a global gate length parameter, setting all the gate lenghts for the triggers simultaneously (boring) or do something like using step velocity as a gate length for the generated trigger pulses.
i think it would be cool if the length is a modulation destination & destination for the automation sequencer. to archive this, i think it would make sense to use a voice parameter (which can already be a modulation/ automation destination) instead of a step parameter. how about using the amp env decay? (seems logical to me)
edit: thanks julian for implementing this by the way. this will be so much fun...
Comments
I put the cable in Trigger Out 1 and then in the Sequencer Trigger In of a JX3P.
I tested with an A4 of Elektron and all works fine.
I put the jumper on the right two pins which are labeld "STRIG".
*edited to say clock input instead of output.
So no S-Trigger Parts are needed.
you have set notes on the seq track for voice 1? Otherwise no triggers will be generated.
Do you have any other gear that accepts trigger signals? just to rule out that the JX3P isn't responsible.
Now i change the jumper to V-Trig and test the gear again.
I still have to count them.
so probably over the course of the next hour?
Thank you, Julian!
I will initiate the bank transfer this evening.
also there is a new trigger settings page to select the prescaler/clock resolution.
shift + Load/save button => takes you to the global setings page
now you can select the trigger settings page with the AEG button
here it is a tight fit, but the jacks can be placed just below the jumpers.
without the green DAC2 jumpers your first audio output pair won't work.
you coukd however remove the green jumpers and clip of a little bit of the pins (not all), then use solder instead of the jumpers to connect the pins. this way you should save some millimeters.
i think the pulses are relatively small atm, too.
works for triggering stuff like 808/909 modules, but for directly driving AD env module for example, i sometimes wish they would be longer.
+1 for what owensands suggested.
it might be connected to the noteoff thing. (might make sense to tie the trigger going low to the note off getting sent - if this will ever be implemented)
working fine for my qmmg thiugh
tying them to the note off would be easy, I just wonder if it wouldn't be too long to output gates instead of trigger pulses for a lot of applications?
I could add an option to the trigger config page to select (global) between gates and trigger pulses.
way to expensive for me right now though. i don't even have enough of the very basic modules yet.
adding any kind of gate length to the lxt would be really nice. not sure, if some modules need just a small trigger and won't function with gates, but i think the global menu option is a good idea.
i don't think the processor pins that are used for the triggers are able to output analog voltages. they probably could be used to talk to an external dac though. other than the dac there would be the need to use some opamps for scaling/buffering.
as an alternative, the pins could probably be used to output voltages using pwm. (in which case modifications would also be needed to filter the pwm signals)
It could probably be hacked in. I think there is still an unused 12bit DAC channel free if I did not use it for another purpose by now (would have to check the schematic)
regarding the gate length:
how would you suggest to implement it?
i just implemented a "gate mode on/off" parameter for the trigger config page.
But just tying it to the noteOn/Off MIDI message yields no good results.
It ends up giving high triggers all the time, with a short low signal before the next note starts.
So you are basically back to setting steps with 0 velocity to define the note off point for the trigger.
I could either make the gate mode On/Off parameter a global gate length parameter, setting all the gate lenghts for the triggers simultaneously (boring) or do something like using step velocity as a gate length for the generated trigger pulses.
suggestions welcome
to archive this, i think it would make sense to use a voice parameter (which can already be a modulation/ automation destination) instead of a step parameter.
how about using the amp env decay? (seems logical to me)
edit:
thanks julian for implementing this by the way.
this will be so much fun...