Closed jreus closed 2 years ago
hmm, this looks right to me. We have definitely used multiple models before. But anecdotally the FAILURE IN SERVER /u_cmd failed
error seems to happen in some synths for no discernable reason. Possibly https://github.com/victor-shepardson/rave-supercollider/blob/d4bd3dd898999f23606f1804ccb3d678e35b994a/plugins/RAVE/RAVE.sc#L6 is not working as expected. You might try putting the two RAVEs each in a different SynthDef.
The reason for the weird RAVEControl
stuff is that SC makes it hard to pass an arbitrary string to a UGen at construction. I'm using the "unit generator commands" method to pass the model filename later, which means bookkeeping both an ID of the Synth and of the RAVE UGen within the SynthDef. This is not well documented and I am probably doing it wrong. But I think there should be a more user-friendly alternative, analogous to how Klank.ar
lets you pass an array of frequencies -- I will try this soon, hopefully eliminating RAVEControl
entirely, and letting you just pass the filename to RAVE.ar
in a SynthDef, like you would expect.
closing, new version is up which no longer uses u_cmd
Heya @victor-shepardson - I'm trying to have a SuperCollider patch with multiple RAVE models running and trying to figure out the best way of proceding. The usage of the RAVE Ugen is unlike anything I've seen in SuperCollider before, it's a bit of a mind trip trying to understand!
I was hoping to have a single synth with both RAVE models running in it. Something like this:
But that last line returns a
FAILURE IN SERVER /u_cmd failed
error. Is there a reason why I shouldn't be putting multiple RAVE Ugens in a single synth? Is there a better approach?many thank yous!