This (and the subsequent version you posted) works great. Both with internal and external clock. I am still trying to understand exactly how (and why) it works.S0lo wrote:Here is a patch that does what you want it to do:martin_l wrote: Not really. There is an important difference between the behaviour described in the A-155 manual (I don't have the hardware, so I can't test), and the behaviour of your sequencer.
Imagine You send a trigger impulse simultaneously with an clock impulse.
The A-155 jumps back to step one which it plays (!), holds that as long as the reset line is high, but if the line goes low BEFORE the next clock impulse, it continues to play without missing a step. If you do keep the line high, you can keep it on step 1 as long as you want, but you can reset the sequencer to step 1 without a pause.
In your case, if I send a trigger impulse together with a clock impulse (I assume external clocking here), the sequencer goes to the last step, which it does not play (at least the trigger sequencer), and even if the reset line goes low before the next clock pulse, it has generated a pause while being on the (silent) last step.
I don't really mind whether you jump to the first or the last step on a reset pulse, and it is perfectly fine to hold that step while the reset line is high. But I think that it should play that step instead of skipping it. It seems to do that when using the internal clock.
Of course, there is the problem that the trigger pulse will be one sample late. I am not sure how Softube are getting around that. But feeding back a trigger pulse (even through another module) into the reset jack does work exactly, as I would expect. I will have a look whether I can spot any delay of the pulse when recording the signals in the DAW. I am quite curious how they get around that.
Arbitrary number of steps. LFO clocked. no sin wave. (The ADSR on the far right is just for manual reset)
It seems that one sample delay you introduce by the unity mixer is crucial. Even though it seems that the mixer is not doing anything, removing it breaks the patch.
It is surely not what all musicians expect, but I am sure I am not the only one interested in polyrhythmic patterns, which are not of length 4, 8 or 16.SOLo wrote: What you expect it to do is not necessarily what all musicians expect it to do.
Anyway, the patch you posted does the job, even if it seems a bit cumbersome.
Sure, obviously, it is your product. I had the same with my plugin. Some people ask things, which are not in line with your ideas, and it is your call, which things to take on board, and which not.SOLo wrote: What you expect it to do is not necessarily what I intended it to do.
I am glad if my comments have some positive effectSOLo wrote: Yet, I'm actually glad that your venturing into all these details, who knows, I might find problems. I actually just discovered that the mix out of the SB12 doesn't work at all!!, the code was mistakenly commented. Your making me revise things. BTW, I do have the A-155, I could test it some time latter.
Just another small suggestion: would it be possible to "lock" a row in the rack, if it is populated by modules? Right now it is possible to wipe out a complete row, with all it's modules and connections by clicking the "-" button. I know, that button is intended to do exactly that, but it might also happen accidentally. It could be controlled by a switch in the ini file, whether the user is allowed to wipe out entire rows -- a quick way to clean a row -- or whether the user prefers populated rows to be protected.
Cheers,
Martin
