Good choice. In the grand scheme of things, having more actual synthesis techniques under the same roof is always more valuable. The modulation system in Rapid is already sufficient enough for most common tasks. My posts were simply expressing my own personal thoughts and feelings on why I haven't yet purchased Rapid. It was on my radar already a while ago.parawave wrote: ↑Sun Jul 26, 2020 1:42 pmNo need to put so much effort into lenghtly post. We don't deny the practical use of any feature request. It's just a matter of priority. It will definitely come at some point.bmanic wrote: ↑Sun Jul 26, 2020 11:23 amWould be nice if Rapid implemented the matrix 'amount' field as a modulation target. That would make it immensely more powerful. Then simply introduce a modulation mapper function so that the user can exactly scale any modulation to their liking and suddenly Rapid would be a lot more capable.
To give you a litte insight about the decision process: We decided to favor Granular Synthesis over MSEGs and Custom Routings because it simply offered a greater palette of possible sounds. There were also a lot of customesr requesting a Granular Oscillator. So it came first.
At the moment you can already do a lot of linear keymapping stuff by just using keyfollow on LFO / Sequence depth, or velocity, or keyfollow on mix gain / pan. We will think about something cool that suits Rapids workflow. It will be some kind of hybrid between keymapping curves and a "via control". In short: Two operators, one function, one target.
When it comes to synthesis requirements I'm probably quite biased as my first ever synth that I put a lot of effort into and programming was the Kurzweil K2000 which was/is immensely flexible (but also limited in some regards). I can definitely understand that the majority do not have my requirements. However, ask your sound designers of what they think. I'd be quite surprised if some of them don't feel like they've ran into "a wall" sometimes when making sounds for Rapid, purely from a modulation/expression point of view.
I'm very interested in the development of Rapid now that it is so fleshed out and has so much potential. One of the main reasons being the really good CPU usage/optimization. I'd like to replace some of the other synths I have available due to simple convenience. Would love to be able to do the things I did with Camel Audio Alchemy (mainly it's modulation system) in a new modern synth with all the cool wavetable stuff.
The quickest way to make Rapid a lot more flexible is to simply add all modulation slots as modulation targets. It's a single feature but very powerful. No idea how hard that would be to implement as I don't know your code/framework.
Bonus feature would be a modulation "mapper" where you could take any modulation input and scale it according to your own wishes.
EDIT: Forgot to thank you for the good demo! It's very nice to be able to go through all the parameters. 20 minutes seems like a really good demo time and it's much nicer than constant noise bursts or similar. Being able to save presets but not load them would be a further refinement to the demo that could be nice for some people but personally the lack of saving doesn't bother me.
.
)
