Cubasis midi LFO cc??

[Deleted User]

Is there a way within cubasis to route a midi lfo (rozetta) to an au synth parameter?

thx

CracklePot

I don’t think so.
I think the AU has to support the older Midi CC assigning method.

audio_DT

Yeah, I find this a bit of a pain, and it’s why I always end up back in AUM, despite the beauty of my favourite sequencer, NS2. At some point, these teething problems of iOS music-making will be consigned to the past 🙂

[Deleted User]

@CracklePot said:
I don’t think so.
I think the AU has to support the older Midi CC assigning method.

@audio_DT said:
Yeah, I find this a bit of a pain, and it’s why I always end up back in AUM, despite the beauty of my favourite sequencer, NS2. At some point, these teething problems of iOS music-making will be consigned to the past 🙂

Well I found success by mapping rozetta lfo and a synth (spacecraft) via midi cc; had to go to the spacecraft manual and get the cc# chart. If a synths cc # are not provided, out of luck (for now)
Guess I’ve been spoiled in AUM

CracklePot

@hibjshop said:

@CracklePot said:
I don’t think so.
I think the AU has to support the older Midi CC assigning method.

@audio_DT said:
Yeah, I find this a bit of a pain, and it’s why I always end up back in AUM, despite the beauty of my favourite sequencer, NS2. At some point, these teething problems of iOS music-making will be consigned to the past 🙂

Well I found success by mapping rozetta lfo and a synth (spacecraft) via midi cc; had to go to the spacecraft manual and get the cc# chart. If a synths cc # are not provided, out of luck (for now)
Guess I’ve been spoiled in AUM

That is great. Spacecraft is awesome, glad it has midi CC.
Sometimes, if the CC mapping isn’t provided anywhere, the synth may still respond to a handful of the standard, useful CC#s. Like ModWheel, Volume, Filter Cutoff, etc.
It doesn’t hurt to check.

Same thing goes in some other host, such as AUM, in a situation where a synth doesn’t show any AU parameters, or if the AU crashes when trying to automate an AU parameter.
In those cases, Midi CC may still work.

[Deleted User]

Your full of good info, thx much👍🏼
I did find a way to map rozetta lfo to icegear synths. If you switch off the ‘active’ in roz lfo, then in the ice gear synth choose the midi parameter you want to modulate (its now waiting to register), go back to roz lfo and switch on the lfo ‘active’. It makes the connection.
Sorry if you knew this already, Im recently making my way into cubasis.

@CracklePot said:

@hibjshop said:

@CracklePot said:
I don’t think so.
I think the AU has to support the older Midi CC assigning method.

@audio_DT said:
Yeah, I find this a bit of a pain, and it’s why I always end up back in AUM, despite the beauty of my favourite sequencer, NS2. At some point, these teething problems of iOS music-making will be consigned to the past 🙂

Well I found success by mapping rozetta lfo and a synth (spacecraft) via midi cc; had to go to the spacecraft manual and get the cc# chart. If a synths cc # are not provided, out of luck (for now)
Guess I’ve been spoiled in AUM

That is great. Spacecraft is awesome, glad it has midi CC.
Sometimes, if the CC mapping isn’t provided anywhere, the synth may still respond to a handful of the standard, useful CC#s. Like ModWheel, Volume, Filter Cutoff, etc.
It doesn’t hurt to check.

Same thing goes in some other host, such as AUM, in a situation where a synth doesn’t show any AU parameters, or if the AU crashes when trying to automate an AU parameter.
In those cases, Midi CC may still work.

CracklePot

@hibjshop said:
Your full of good info, thx much👍🏼
I did find a way to map rozetta lfo to icegear synths. If you switch off the ‘active’ in roz lfo, then in the ice gear synth choose the midi parameter you want to modulate (its now waiting to register), go back to roz lfo and switch on the lfo ‘active’. It makes the connection.
Sorry if you knew this already, Im recently making my way into cubasis.

@CracklePot said:

@hibjshop said:

@CracklePot said:
I don’t think so.
I think the AU has to support the older Midi CC assigning method.

@audio_DT said:
Yeah, I find this a bit of a pain, and it’s why I always end up back in AUM, despite the beauty of my favourite sequencer, NS2. At some point, these teething problems of iOS music-making will be consigned to the past 🙂

Well I found success by mapping rozetta lfo and a synth (spacecraft) via midi cc; had to go to the spacecraft manual and get the cc# chart. If a synths cc # are not provided, out of luck (for now)
Guess I’ve been spoiled in AUM

That is great. Spacecraft is awesome, glad it has midi CC.
Sometimes, if the CC mapping isn’t provided anywhere, the synth may still respond to a handful of the standard, useful CC#s. Like ModWheel, Volume, Filter Cutoff, etc.
It doesn’t hurt to check.

Same thing goes in some other host, such as AUM, in a situation where a synth doesn’t show any AU parameters, or if the AU crashes when trying to automate an AU parameter.
In those cases, Midi CC may still work.

Did not know that one.
Thank you.
Midi learn has been a pain for mapping clock based stuff like LFOs.
I have mostly been successful mapping external controller knobs and such.
This will come in handy.
🤙🏻

Johne1

@CracklePot said:
I don’t think so.
I think the AU has to support the older Midi CC assigning method.

I’m at that very same crossroads myself, trying to map Rozeta LFO to AU instruments in Cubasis. I wasn’t aware that using CC’s is an older method? What is the new method that replaced it? Just using the names of the controls? That’s what I’m finding when I deep dive in Cubasis.