search

AScustomWorks / Paid-Modules-Info

http://www.hakken.com.mx/ascustomworks/
0 stars 0 forks source link

ReStep run signal reset #3

Open WouterSpekkink opened 5 years ago

WouterSpekkink commented 5 years ago

Hi there,

I am using your AS Seqs & Tools modules, which are great. However, I am having an issue with the ReStep sequencer (not sure if it affects other modules as well, but I think I had a similar issue with the ReBeat module), which is that upon restart of VCV, the run signal seems to reset (or perhaps it is just not stored when closing VCV). This means that I often have to disconnect the cable from the clock module run output (I am using the one in your free package) to the ReStep run input, toggle the run button of the clock, and reconnect the cable. It is not the worst nuisance in the world, but a bit of a nuisance nonetheless.

AScustomWorks commented 5 years ago

Hi WouterSpekkink, indeed the ReStep modules don't save the run state as each module can't know whats going on with the rest of the chained modules (also that's the reason to have the ReCon module as a helper). Are you using ReCon module? I assume you are not because of : "...I often have to disconnect the cable from the clock module run output" but not sure. Can you share a patch with your setup to see if I'm understanding the issue right, please? Thanks!

WouterSpekkink commented 5 years ago

Thanks for responding some quickly. I made a quick minimum patch to illustrate the problem. It includes a clock and two sequencers, one of which is the ReStep. The problem only becomes clear if you run the clock, close Rack (don't stop the clock first), and then restart Rack. You will see that the top sequencer is still running, but the bottom sequencer is not, even though the clock is running.

Based on your response, I've played a bit more with the ReStep modules, and also checked what happens if I add a ReCon module to the chain (I did not actually chain ReStep modules that often; I mostly used it as a 4-step sequencer to transpose other sequencers). I see now that the ReCon module works quite different than the run option on your regular clock, because you have a separate pause button, rather than just pausing the sequencers by toggling the run button again. In other words, in your regular clock the run button functions as an on/off switch, whereas in the ReCon module the run button functions as a trigger that always starts the first module it is connected to.

I of course don't know everything that is going on 'behind the panels', but would it not be enough to have a run and a reset button for ReCon as well? Then you would simply start/pause the chain of sequencers by toggling the run button, and you would reset the whole chain to the first step by clicking the reset button (currently, the reset button also seems to switch everything off). Not sure if that makes sense.

Problem_Patch.vcv.zip

Bit-Fiddler commented 1 year ago

Not sure if this is tied to this, but I will post on this one.

Some more input on the ReStep chain:

1) If I hit the reset button on the ReCon module, it resets the current ReStep module to state 1 rather than resetting the entire chain back to the beginning.

2) If I hit the run button on the ReCon module it sends the run command to every module, and thus you have to wait for the cycle to finish on all the modules which are now running in parallel, then it will start back on module 1 and continue the sequence.

Have I missed some patching? Do I need to do something that connects various inputs. to the reset or run buttons?