I was trying to use midi start (transport) to reset 4ms RCLKD.
but it didn’t appear to be working correctly…
so to test, I just sent midi start → attn → jack
then looked at the signal, and it appears Midi Start is going high then low repeatedly.
I would expect a single pulse / trig when the transport is started.
I verified with a midi monitor on Mac, that the midi device was indeed only sending midi start as expected.
4ms RCLKD
(in gate mode)
reset - does not appear to be working correctly?
after midi start was not working, I tried to move to a knob via attn, and this did not appear to reset it.
leds - after I reloading the patch, all the leds stayed off… (including trig in)
but module was functioning, I was getting output etc.
I had to delete the module, then revert patch to get the leds working again.
btw:
general reloading of patch - does not appear to work , at least as I expected
if I change patch, then load from card - it does not reload patch.
(revert does work)
So far I’m not seeing an issue on the RCD, but maybe there is some way to get it to not work if I fiddle long enough. Any ideas?
Reset functions differently depending on the switches, maybe that’s confusing. When it’s flipped to Down counting all the jacks go ON when you fire a reset. When it’s flipped to Up counting, they all go OFF when you fire a reset. The jack requires > 2V to detect rising edge, and then has to go < 1V to clear the high state. I’m testing it and it’s working per spec, so if you can help me reproduce the error state I can see what’s going on.
Not having the LEDs blink, but the outputs still work sounds like an issue with the light drawing engine mabye. I’ll see if I can reproduce that. Were there lots of other lights in the patch by chance? Or possibly modules with Displays (that weren’t actually drawn since this message is from before firmware v1.3.1)? Because displays and lights overlap in some ways. But if that was the case then it shouldn’t happen on v1.3.1 firmware
I’m testing this out, making a patch and then loading a different one, then loading it again but so far am not able to make it break. Let me know if you can send me a patch or where it happens
This was fixed in v1.3.1
Edit: I’m seeing issues with MIDI start/stop but the signals are clean 10.0V 10ms pulses. Looking into this.
When you were having issues with the RCD, was there always some MIDI connected in the patch? Did you have issue with no MIDI in the patch?
Ok I found a bug that would cause strange behavior. Unmapping a MIDI map (to an input jack, not to a knob) does not actually unmap it. If you happen to map a second signal to the same jack after unmapping a MIDI signal, the MIDI pulse and the new signal will alternate, causing all sorts of weirdness. That’s probably the repeated high/low signal you saw.
If you save the patch and reload/revert it, then it’ll properly forget the MIDI maps that you removed.
I’m pretty sure I know what’s causing this, just out of time today.
I fixed the MIDI bug. It only effected Transport (Start/Stop/Continue) and Retrig pulses. Unmapping these did not actually unmap them until the patch was reloaded from disk.
As for the RCD Reset Input, yeah I can see how it’s looks broken when the RCD is in Gate Mode. But it’s actually working. I tested it against a hardware unit, and it functions the same. And we haven’t touched that firmware in a long time (has it been 10 years??).
In Trig mode it’s obvious how Reset it working. In Gate mode, it actually is doing the exact same thing, it’s just that the on/off state of each jack is not reset – only the internal counter of each jack is reset. So if a jack is high it stays high, or if it’s low it stays low when it gets a reset. But its internal counter gets reset.
indeed this is unexpected/confusing behaviour for me.
but I guess ok, if consistent with hardware
I’ll just use trig mode. (is this the default? perhaps should be if not?!)
led issue
I simply had midi → rcd → out to panel., no other modules.
with midi clock → trig, midi start → reset.
and then some pots mapped to module parameters.
I can’t really remember how I trigged the issue - it was either start/stopping the clock, or when I was re-patching, to see why reset was not working ‘correctly’ e.g. using an attn into reset rather than midi start.
indeed, I assume it was some kind of more general engine issue rather than entirely related to RCD… in fact, I have a feeling Ive seen this before with other modules.