switch from studio one to cubase 12

Audio Plugin Hosts and other audio software applications discussion
RELATED
PRODUCTS

Post

chk071 wrote: Tue Jun 14, 2022 5:27 pm What exactly do you mean with "up and running"? Setting the keyboard up as a generic MIDI controller is surely as easy as in any other DAW.
"Up and running", for me meant the 8 sliders assigned to volume and the transport working (record-stop etc.. I also assigned buttons to open up VST tracks and audio tracks, and undo and redo. It takes seconds in Mixcraft and is very intuitive. I have owned Studio One from since it first came out, but have stayed with 4.5 Pro. It is my favorite DAW and the one I use all the time. Up until now I have used ny Nektar Panorama P6 with it and it just works with the included template, but yesterday I decided I wanted a big studio change and removed it. I thought it would be easy to get my legacy Remote working, but nope.

So I decided to try it on Cubase 12 Pro. It should have been a piece of cake with the new remote thingy. But nope again. Mixcraft 9 does it the old fashioned simple way and it is easy peasy. The more I use this DAW the more impressed I am.

Post

I'll have a look. On my Novation keyboard (Impulse 49), I can set up the keyboard to act as a Maeckie HUI device, which maps the sliders and knobs to the DAW's track's controls. I remember you could do something similar with Automap, if your device uses Automap (and if you use it).

Edit: Yep, just as I thought: You could do it in Automap, but, I'm pretty sure that you can't do it anymore in more current versions of Studio One and Cubase. So, like you do it in Mixcraft, you would have to do it using the controller in MIDI CC mode.

Post

dellboy wrote: Tue Jun 14, 2022 5:44 pm
chk071 wrote: Tue Jun 14, 2022 5:27 pm What exactly do you mean with "up and running"? Setting the keyboard up as a generic MIDI controller is surely as easy as in any other DAW.
"Up and running", for me meant the 8 sliders assigned to volume and the transport working (record-stop etc.. I also assigned buttons to open up VST tracks and audio tracks, and undo and redo. It takes seconds in Mixcraft and is very intuitive. I have owned Studio One from since it first came out, but have stayed with 4.5 Pro. It is my favorite DAW and the one I use all the time. Up until now I have used ny Nektar Panorama P6 with it and it just works with the included template, but yesterday I decided I wanted a big studio change and removed it. I thought it would be easy to get my legacy Remote working, but nope.

So I decided to try it on Cubase 12 Pro. It should have been a piece of cake with the new remote thingy. But nope again. Mixcraft 9 does it the old fashioned simple way and it is easy peasy. The more I use this DAW the more impressed I am.
Just use the Mackie controller if you can't find your keyboard. I have Keylab mk ii and it doesn't recognized by Cubase and S1 while in Live and Bitwig its recognized immediately. I'll post my setup later today when I'm on my PC.
Using: Cubase Pro 15, Reason 13, Tascam US-4x4HR, MODX6, DM12D, LaunchKey 49, Yamaha guitar(Pacifica 612v) and bass (BB234) and some virtual instruments and synths.

Post

EnGee wrote: Tue Jun 14, 2022 6:26 pm Just use the Mackie controller if you can't find your keyboard.
I'm not sure if that works for all controllers (I doubt it, TBH). For my Novation, there was a firmware update, which made it work with the Maeckie HUI protocol. That was after Novation discontinued Automap.

Post

chk071 wrote: Tue Jun 14, 2022 6:36 pm
EnGee wrote: Tue Jun 14, 2022 6:26 pm Just use the Mackie controller if you can't find your keyboard.
I'm not sure if that works for all controllers (I doubt it, TBH). For my Novation, there was a firmware update, which made it work with the Maeckie HUI protocol. That was after Novation discontinued Automap.
Yes you are right. Not all use this template. However, it is good to try all the Mackie templates and see first.

For Cubase, I haven't used the 'new' mapping system because the previous configuration in C11 already works in C12. Anyway, for S1 it might be different from Cubase, but here is my Cubase configuration (just in case it might be similar). Notice that there are two ports for each controller (in case of KK M, Cubase already did the config, but for the Keylab I had to do it all as explained in the manual):
KK auto config in Cubase.jpg
KeyLab mkII as a Mackie controller.jpg
and for the VST/Track quick controls:
KK M controlling Track Quick Controls.jpg
KeyLab mkII config with VST Quick Controls.jpg
You do not have the required permissions to view the files attached to this post.
Using: Cubase Pro 15, Reason 13, Tascam US-4x4HR, MODX6, DM12D, LaunchKey 49, Yamaha guitar(Pacifica 612v) and bass (BB234) and some virtual instruments and synths.

Post

I'm probably going to replace my Oxygen Pro Controller with a LaunchKey MK3 for the MIDI Remote integration. It's really deep with Cubase. Plug-and-Play, and even the screen reacts to what you're adjusting with the controls (faders, knobs, etc.).

Likely to get a LaunchKey Mini for my Laptop, as well.

I've never had luck using any controller with Mackie/HUI emulation because the faders and knobs jump parameters far too much. It just isn't practical, so I feel like it's more useful to just get something like a Keystation and save on space than get all of the extras if you're going to end up using them very little - if at all. I feel like Nektar is the only other viable option if you want usable DAW controls on the controller, but anything below their Panorama series is fairly sketchy in terms of quality.

I don't use any of the knobs and faders on my M-Audio controller. I don't even have it sitting in a position where I can use the transport, because it just never seemed practical to use it for anything but the keys. In retrospect, I could have saved money and gotten a Keystation, and it wouldn't have change anything on a practical level. The Pads can be useful, to some extent, but I have a Maschine MK3, so why would I ever use it for that?

I still think the Oxygen Pro series has the most unusable Aftertouch I've ever experienced on a MIDI Controller.

I think a big advantage Novation has over a lot of other controllers is that they have a device driver that can negotiate communication between the controller and the DAW. This is basically what Nektar does with their DAW Integration, and I think anything short of that is going to lead to an unsatisfactory user experience if you try to use anything beyond button presses and transport controls. The Faders and Knobs (when not endless encoders) always suck - regardless of their quality - without that level of negotiation.

Same issue with the Oxygen Pro in Studio One. Doesn't matter how well things are mapped. Practically, it's just an unsatisfactory user experience.

I am liking the direction Steinberg is going with this. Other vendors just need to get on board, but I think many will not put in the effort to arrive at a solution that works as well as Novation (or Nektar).

I think I prefer the controller layout that Native Instruments has. 8 endless encoders and you just switch between what they control - because non-mechanical faders without driver negotiation to facilitate pickup feels awful to use (and often does nothing but create more work for you to do while using it)...

If I said you are blocked, I won't see your posts. Please kindly refrain from quoting or replying to me.
"Notifications for Nothing" are annoying. Blocking me in return is a good way to avoid this.


Post

Trensharo wrote: Wed Jun 15, 2022 2:50 pm I feel like Nektar is the only other viable option if you want usable DAW controls on the controller, but anything below their Panorama series is fairly sketchy in terms of quality.
In the end I gave up trying to make my old Novation controller work with either Cubase or Studio One and put the Nektar P6 back in a totally different position the to the left side. The result is that I am now actually using it all the time, including the sliders, knobs, and transport. I used to have it in front of me under the computer monitor as this seemed the most logical position, but in reality I was not using it. I tended to use my computer keyboard for transport etc all the time, which I am not doing any longer.

Post

Yea. For anyone else reading the issue isn't that the controlleys don't work on other controllers, but that there is no pick up so once you change tracks or banks the faders and non-endless pots are out of sync and cause anything to jump to their position once you move them.

So, I don't see a point in getting a co trolleys with faders. Its better to get one with endless pots only and just switch them between level, sends, pan etc.

Something like a Komplete Kontrol or Maschine MK3.

Nektar uses a driver to negotiate this, so their controllers have pickup in quite a few DAWs, like Cubase.

Don't think it works in Studio One, unless they've updated it since the last time I checked.

The only issue with Nektar is their controllers in the ~$200 range are kind of bad in terms of key bed quality.

A Maschine MK3 and a Keystation will give you everything you need. Or a Maschine Mikro and an A/M Series controller.

If I said you are blocked, I won't see your posts. Please kindly refrain from quoting or replying to me.
"Notifications for Nothing" are annoying. Blocking me in return is a good way to avoid this.


Post Reply

Return to “Hosts & Applications (Sequencers, DAWs, Audio Editors, etc.)”