F0 =Trigger 75ms
F1 =Trigger 75ms - Text description reads "Retrigger 2 x 75ms"
F2 = Trigger 2x75ms - Text description reads "Retrigger 3 x 75ms"
It looks like F0 and F1 both output single trigger - and all the retriggers in the More Triggers module are similarly affected.
cheers
b
Argh!!! Just tested and confirming this bevaviour. So why did no one mention this in the last 2 years, since the Trigger16 is out??? I didn't realize this bug at all.
I will update the Trigger16 after the next release (or after that) to get it equal to the local Trigger outputs (eg adding ratcheting, ticks and random etc) anyways so this will be fixed then, too.
hello,
quick question. I just got my Nerdseq yesterday, and after playing around with it, I encountered this problem as well. After diving into the manual and the forum i finally found this thread.
i am currently running firmware V2.02A.
Do I have to renew the firmware of the expander as well? (if so, i did not found the firmware for the Triggers expander)
Because mine says v.1.0 on the boot screen. I tried to update it in the Track menu or Setup menu, but it did not work because the nerdseq didn't find actual firmware on the sd-card
Or is this ticket still open?
Sorry, but I am a little bit confused.
Best regards and thanks for these awesome modules.
V1.0 is the current version and the described updates have not been implemented yet.
Ah, makes sense. In noticed some discrepancies between retrigger settings and result, but thought it was hardware or attack times that couldn't keep up..
I've not always a scope at hand.