Hello - I love my ADDAC case and these quantizers. I did the J9 update, but there is still an accidental gatemode switching that can occur after 60 seconds.
I read through the last comments and made a new update (J_6) to save the CH234 slave to 1 setting in overall memory, so now it should keep your pre-defined setting after startup.
So with that setting off channels 234 will never be listening to channel one, with this long intervals between gates will not be a problem.
all the very best
From the manual (last updated July 2013):
"This Gate in ON/OFF detection is made in software.
After the detection goes On, and if the user removes
the gate in jack it will automatically goes to Off after
60 seconds. If the user want to reset voices before the
60 seconds period Button 6 (Gate L) can be pressed at
the same time as the voice number button (1 to 4).
For example to Reset voice 2 Gate In, the user needs to
press button 2 and 6 at the same time.
This will resume the behavior without regarding the
Gate In until a new jack is plugged in."
OK ---- So, the interval creation and gate detection are different things.
As of the current OS, the "CH234 slave to 1 setting" has only taken care of the accidental mode switching that happens when sending 0V CV to "in" 2, 3, or 4.
The "no-gate-in-patched"-detection is still on a 60 second timer, so "gate detection" issues have not been resolved for anyone who wants their input gates to be spaced wider than 60 seconds.
I did a simple test:
Medium slow LFO into CV "in" (set the speed so you can kind of see it moving up and down on the quantizers LEDs);
make a single trigger pulse happen into "gate in" (start a stopwatch now if you'd like);
This trigger switches the quantizer into triggered operation and stops the quantizing of every step of the lfo and holds the value from the triggered moment;
now wait. . . . . . . . . at 60 seconds the quantizer "goes crazy" (switches back to untriggered mode of operation) . . . .
it stops thinking that I have a cable plugged into "gate in", but the cable is still plugged in.
Doesn't work for slow music (you won't make it past the 15th bar at 60bpm); I think it's why random outputs are sometimes happening for some people; this situation can definitely interrupt any nice long drone note.
It would be very very
helpful to have another "Trig.R." Menu item to declare "I will
be using gates", or "auto detect" (which already works for "I won't
be using gates").
all the very best,