RapidComposer: no parameters visible to my DAW?
-
- KVRAF
- 2064 posts since 13 Dec, 2016
I would like to buy RapidComposer, but only if the parameters of the program are exposed to the DAW. For my workflow this is essential, and any kind of generation buttons or sliders must be automatable, as I do a lot of generative and experimental composition and sound design. I downloaded the demo and loaded the plugin in Bitwig Studio, but not a single parameter is visible to the DAW. Are there any settings that need to be enabled first?
Its over for Bitwig--CUBASE WON !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
-
musicdevelopments musicdevelopments https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=223336
- KVRAF
- 6014 posts since 9 Jan, 2010
Hi enCiphered,
thanks for checking out the demo and for the question!
You're right: when using the RapidComposer plug-in in a DAW like Bitwig, there are no parameters exposed for automation. This is simply because the way phrase editing works in RapidComposer doesn't translate well to DAW automation. For example, generation sliders and controls are part of the Inspector, which only shows parameters for one selected phrase at a time. Since a composition can have many phrases, there's no fixed set of parameters that could be mapped to automation lanes in the DAW.
RapidComposer was designed mainly to be used inside its own interface where you can do all the editing and generation interactively. Trying to make all those options automatable in the DAW would be quite messy and limited.
There are tools included for algorithmic composition, like automatically regenerating selected phrases (at the end of a loop, or when the STOP button is pressed):

Thanks,
Attila
thanks for checking out the demo and for the question!
You're right: when using the RapidComposer plug-in in a DAW like Bitwig, there are no parameters exposed for automation. This is simply because the way phrase editing works in RapidComposer doesn't translate well to DAW automation. For example, generation sliders and controls are part of the Inspector, which only shows parameters for one selected phrase at a time. Since a composition can have many phrases, there's no fixed set of parameters that could be mapped to automation lanes in the DAW.
RapidComposer was designed mainly to be used inside its own interface where you can do all the editing and generation interactively. Trying to make all those options automatable in the DAW would be quite messy and limited.
There are tools included for algorithmic composition, like automatically regenerating selected phrases (at the end of a loop, or when the STOP button is pressed):

Thanks,
Attila
