by stefanovic » Fri Aug 26, 2022 7:10 am
Thanks Jim for chiming in.
Do you have reason to think that these parameters are being set per-voice? On a synth such as the Rev 2? I would rather think this changes the parameter for all voices. That’s how it works in the Solaris. I mean, what if it did work per-voice but you wanted to modulate the parameter for all voices how would you tell it to do that?
A guess: it seems to me he only mentions analog synths, which may have voices with unique (non-shared) parameters per voicecard. With a KeyStep mode, the firmware could set the parameters for the next voice to be triggered, without affecting the other voices. With all-digital synths, one could share the parameters between voices, which would make it impossible to change a voice without affecting the others.
That would also mean that VCM in KeyStep mode is impossible on the Solaris? It seems to me that I could definitely tell the difference when I tried it on my unit, but maybe I deceived myself

...
Actually, to implement his original premise, if you do it internally, you don’t need to use the sequencer. You just need to set up each voice’s parameters slightly differently at the start and leave them there. The only reason he’s using the sequencer is for key step mode so he can make the parameter change at each note. If all you need are random changes per note, and if this is all implemented internally then you don’t need the sequencer. We know when notes are played and can make the parameter change without the sequencer. The only reason you’d need a sequencer is for specific, user-controlled changes per-step.
Yes, he is using the seqs in KeyStep mode because without having access to the firmware code, that's the most practical (and maybe the only) means to implement VCM on synths with such seqs. Since you have access to the code, I agree it could be implemented in a more straightforward way. (Still, implementing it with user-defined seqs allows for experimenting, fine-tuning and assessing what works and what doesn't).
So if we completely leave seq aside (and be completely off-topic wrt to ratcheting, sorry), would it be possible for you to extend RndTune to other parameters than "Tune" only? Maybe not in the next OS release, but in a following one? And with values that keep the same for each voice?
Thanks Jim for chiming in.
[quote]Do you have reason to think that these parameters are being set per-voice? On a synth such as the Rev 2? I would rather think this changes the parameter for all voices. That’s how it works in the Solaris. I mean, what if it did work per-voice but you wanted to modulate the parameter for all voices how would you tell it to do that?[/quote]
A guess: it seems to me he only mentions analog synths, which may have voices with unique (non-shared) parameters per voicecard. With a KeyStep mode, the firmware could set the parameters for the next voice to be triggered, without affecting the other voices. With all-digital synths, one could share the parameters between voices, which would make it impossible to change a voice without affecting the others.
That would also mean that VCM in KeyStep mode is impossible on the Solaris? It seems to me that I could definitely tell the difference when I tried it on my unit, but maybe I deceived myself :) ...
[quote]Actually, to implement his original premise, if you do it internally, you don’t need to use the sequencer. You just need to set up each voice’s parameters slightly differently at the start and leave them there. The only reason he’s using the sequencer is for key step mode so he can make the parameter change at each note. If all you need are random changes per note, and if this is all implemented internally then you don’t need the sequencer. We know when notes are played and can make the parameter change without the sequencer. The only reason you’d need a sequencer is for specific, user-controlled changes per-step.[/quote]
Yes, he is using the seqs in KeyStep mode because without having access to the firmware code, that's the most practical (and maybe the only) means to implement VCM on synths with such seqs. Since you have access to the code, I agree it could be implemented in a more straightforward way. (Still, implementing it with user-defined seqs allows for experimenting, fine-tuning and assessing what works and what doesn't).
So if we completely leave seq aside (and be completely off-topic wrt to ratcheting, sorry), would it be possible for you to extend RndTune to other parameters than "Tune" only? Maybe not in the next OS release, but in a following one? And with values that keep the same for each voice?