I had a bit of a play, this might help. If a modulation already exists then double clicking clears it without the crash (also modulations can be added back to just those controls). A rough guess the crash is due to the app trying to remove an element from an array that is not there or maybe the array has not been created correctly?
Oddly there appeared fairly random behaviours, I could remove the two modulations from stream 1 time and pitch and then add modulations only to stream 2 balance and stream 3 balance. It seemed to be set to only allowing 2 modulations at a time. I found a similar one where random 2 will allow any modulation destination but only 4 at a time.
I'll check out the beta, thanks Daniel
Tried the beta and the lfo issue is fixed. I did however have an instance just click and cut out. The buffer became full of what looks like a dc signal maybe. In the attached screenshot you can see the buffer display is fully white and the signal out has maxed even though there is no noise to be heard, I'll see if I can reproduce it. Could be an fl studio thing, I've seen reaktor do something similar with feedback buffers,
One thing of note the lfo rates and stream rates feel like they are reversed, Normally I'd expect speed to increase by turning up the dials.
Hi!
Thanks for the feedback! Not sure what the dc/noise thing could be, If you know a reliable way to make that happen please let me know!
I also recently released version 0.3.2 with some bugfixes that might help with some of these issues.
One thing of note the lfo rates and stream rates feel like they are reversed, Normally I’d expect speed to increase by turning up the dials.
In the 1.0 beta you can select different units of measurement for time-based parameters (like seconds, Hz, quarter notes, etc.) If you set the lfo rate in seconds then you will see the speed decrease as you increase the knob. You can select a different timebase by clicking the little ‘T’ button next to the knob. (I guess Hz would indeed be a better default here)
