MichaelBenjamin ·
currently it seems it does not, so there needs to be a manual reinitialize in code. this cpu could be saved easily if stage(0) would be retriggered if a voice is stolen.
From the original SynthMaker forum (2004–2014), with its members’ names and dates.
MichaelBenjamin ·
currently it seems it does not, so there needs to be a manual reinitialize in code. this cpu could be saved easily if stage(0) would be retriggered if a voice is stolen.
infuzion ·
Wouldn't this be more of a bug than a new feature?
rl ·
Agreed. Up to recently I also had the false assumption that stage(0) is always active when a new voice is triggered (even when stolen). This could be workaroun-ed by using the Env module, but that doesn't save CPU.
infuzion ·
rl wrote: infuzion wrote: Wouldn't this be more of a bug [report] than a new feature?
Up to recently I also had the false assumption that stage(0) is always active when a new voice is triggered (even when stolen). This could be workaroun-ed by using the Env module, but that doesn't save CPU.
Maybe it will get the proper attention in the Bug forum then. I imagine that something happened or was overlooked the the voice-code interaction was changed a few versions ago.
Wrote something here? To have a post removed or your name hidden, write to [email protected].