|
Post by gravesnumber9 on Oct 22, 2024 12:02:24 GMT -6
Quint have you landed on Cubase? I've always been Cubase curious so there's a part of me that's hoping you'll move in that direction so I can observe your observations. But there's also a part of me that would love to see another S1 power user.
|
|
|
Post by Quint on Oct 22, 2024 12:14:12 GMT -6
Quint have you landed on Cubase? I've always been Cubase curious so there's a part of me that's hoping you'll move in that direction so I can observe your observations. But there's also a part of me that would love to see another S1 power user. I haven't landed on it yet, but I'm definitely leaning that way towards Cubase. I'm evaluating it right now, to see how it goes. Cubase has a LOT of midi functionality, which I really like, such as being able to set up a generic midi remote. In an hour, I was able to set Cubase up to individually open and close plugins in each insert on my Stream Deck at the push of a button, and it looks like I'll be able to harness the MCU Sysex feedback for realtime updates of plugin name/status on those aforementioned SD buttons. It took me months to get this same sort of plugin control implemented on Luna, because Luna has no midi controller implementation, and I had to resort to crazy difficult work arounds. Cubase just seems incredibly capable of doing so many different things, but it seems to be done in a way that is a little more understandable and less daunting than Reaper. Reaper just left me with option overload, and I struggled with it. Granted, there will for sure be a learning curve with Cubase, but I'm not put off by it. It'll probably ultimately be what I go with, based on what I've learned about Cubase, S1, and Logic.
|
|
|
Post by damoongo on Oct 22, 2024 22:57:15 GMT -6
Quint have you landed on Cubase? I've always been Cubase curious so there's a part of me that's hoping you'll move in that direction so I can observe your observations. But there's also a part of me that would love to see another S1 power user. I haven't landed on it yet, but I'm definitely leaning that way towards Cubase. I'm evaluating it right now, to see how it goes. Cubase has a LOT of midi functionality, which I really like, such as being able to set up a generic midi remote. In an hour, I was able to set Cubase up to individually open and close plugins in each insert on my Stream Deck at the push of a button, and it looks like I'll be able to harness the MCU Sysex feedback for realtime updates of plugin name/status on those aforementioned SD buttons. It took me months to get this same sort of plugin control implemented on Luna, because Luna has no midi controller implementation, and I had to resort to crazy difficult work arounds. Cubase just seems incredibly capable of doing so many different things, but it seems to be done in a way that is a little more understandable and less daunting than Reaper. Reaper just left me with option overload, and I struggled with it. Granted, there will for sure be a learning curve with Cubase, but I'm not put off by it. It'll probably ultimately be what I go with, based on what I've learned about Cubase, S1, and Logic. Don’t forget to assign the 8 QC (quick control) for the most used parameters on your favorite plugs. It takes 2 seconds and they are global. So any project you open those plugs in, those parameters are mapped to your control surface.
|
|
|
Post by thehightenor on Oct 23, 2024 0:14:33 GMT -6
I haven't landed on it yet, but I'm definitely leaning that way towards Cubase. I'm evaluating it right now, to see how it goes. Cubase has a LOT of midi functionality, which I really like, such as being able to set up a generic midi remote. In an hour, I was able to set Cubase up to individually open and close plugins in each insert on my Stream Deck at the push of a button, and it looks like I'll be able to harness the MCU Sysex feedback for realtime updates of plugin name/status on those aforementioned SD buttons. It took me months to get this same sort of plugin control implemented on Luna, because Luna has no midi controller implementation, and I had to resort to crazy difficult work arounds. Cubase just seems incredibly capable of doing so many different things, but it seems to be done in a way that is a little more understandable and less daunting than Reaper. Reaper just left me with option overload, and I struggled with it. Granted, there will for sure be a learning curve with Cubase, but I'm not put off by it. It'll probably ultimately be what I go with, based on what I've learned about Cubase, S1, and Logic. Don’t forget to assign the 8 QC (quick control) for the most used parameters on your favorite plugs. It takes 2 seconds and they are global. So any project you open those plugs in, those parameters are mapped to your control surface. Yes this feature is amazing - and a bit over looked.
|
|
|
Post by thehightenor on Oct 23, 2024 0:17:12 GMT -6
Quint have you landed on Cubase? I've always been Cubase curious so there's a part of me that's hoping you'll move in that direction so I can observe your observations. But there's also a part of me that would love to see another S1 power user. I haven't landed on it yet, but I'm definitely leaning that way towards Cubase. I'm evaluating it right now, to see how it goes. Cubase has a LOT of midi functionality, which I really like, such as being able to set up a generic midi remote. In an hour, I was able to set Cubase up to individually open and close plugins in each insert on my Stream Deck at the push of a button, and it looks like I'll be able to harness the MCU Sysex feedback for realtime updates of plugin name/status on those aforementioned SD buttons. It took me months to get this same sort of plugin control implemented on Luna, because Luna has no midi controller implementation, and I had to resort to crazy difficult work arounds. Cubase just seems incredibly capable of doing so many different things, but it seems to be done in a way that is a little more understandable and less daunting than Reaper. Reaper just left me with option overload, and I struggled with it. Granted, there will for sure be a learning curve with Cubase, but I'm not put off by it. It'll probably ultimately be what I go with, based on what I've learned about Cubase, S1, and Logic. Please share your method for getting SD to open close plug-ins in Cubase - I’d like to have a go at that Can you select which plugin is inserted into which slot? If it’s just open and close I already have that in my sideshowfx profile. But being able to pick a certain plugin from an icon on SD - that would be great.
|
|
|
Post by Quint on Oct 23, 2024 0:43:08 GMT -6
I haven't landed on it yet, but I'm definitely leaning that way towards Cubase. I'm evaluating it right now, to see how it goes. Cubase has a LOT of midi functionality, which I really like, such as being able to set up a generic midi remote. In an hour, I was able to set Cubase up to individually open and close plugins in each insert on my Stream Deck at the push of a button, and it looks like I'll be able to harness the MCU Sysex feedback for realtime updates of plugin name/status on those aforementioned SD buttons. It took me months to get this same sort of plugin control implemented on Luna, because Luna has no midi controller implementation, and I had to resort to crazy difficult work arounds. Cubase just seems incredibly capable of doing so many different things, but it seems to be done in a way that is a little more understandable and less daunting than Reaper. Reaper just left me with option overload, and I struggled with it. Granted, there will for sure be a learning curve with Cubase, but I'm not put off by it. It'll probably ultimately be what I go with, based on what I've learned about Cubase, S1, and Logic. Please share your method for getting SD to open close plug-ins in Cubase - I’d like to have a go at that Can you select which plugin is inserted into which slot? If it’s just open and close I already have that in my sideshowfx profile. But being able to pick a certain plugin from an icon on SD - that would be great. I'm working on this as we speak. Once I get it all sorted, I'll share it with you.
|
|
|
Post by thehightenor on Oct 23, 2024 5:52:12 GMT -6
Please share your method for getting SD to open close plug-ins in Cubase - I’d like to have a go at that Can you select which plugin is inserted into which slot? If it’s just open and close I already have that in my sideshowfx profile. But being able to pick a certain plugin from an icon on SD - that would be great. I'm working on this as we speak. Once I get it all sorted, I'll share it with you. Great - thank you!
|
|
|
Post by Quint on Oct 23, 2024 6:10:38 GMT -6
I'm working on this as we speak. Once I get it all sorted, I'll share it with you. Great - thank you! Can you describe a little more what Sideshow does or doesn't do with opening and closing plugins? In any case, what I did with Luna, and what I think will be able to be done with Cubase, is to do the following things: 1. Open and close any individual plugin GUI in any individual insert with one push of a button on the Stream Deck. 2. That same SD button push will also automatically cause your hardware controller to display the MCU parameters for the plugin GUI you've just opened. 3. The insert buttons on the SD will update realtime to display the name and image of the plugins loaded in those inserts, as you change channels in Cubase. 4. Plugins that are open will be shown as such on the SD with an orange ring around the button image. 5. Similarly, the selected channel name will update on a different button on the SD as well. 6. You'll be able to turn on/off plugins from the SD. 7. You'll be able to load plugins into Cubase, using only buttons on the SD. Plugin options will be displayed as sort of a "rack" of favorites, if you will.
|
|
|
Post by thehightenor on Oct 23, 2024 8:04:00 GMT -6
Can you describe a little more what Sideshow does or doesn't do with opening and closing plugins? In any case, what I did with Luna, and what I think will be able to be done with Cubase, is to do the following things: 1. Open and close any individual plugin GUI in any individual insert with one push of a button on the Stream Deck. 2. That same SD button push will also automatically cause your hardware controller to display the MCU parameters for the plugin GUI you've just opened. 3. The insert buttons on the SD will update realtime to display the name and image of the plugins loaded in those inserts, as you change channels in Cubase. 4. Plugins that are open will be shown as such on the SD with an orange ring around the button image. 5. Similarly, the selected channel name will update on a different button on the SD as well. 6. You'll be able to turn on/off plugins from the SD. 7. You'll be able to load plugins into Cubase, using only buttons on the SD. Plugin options will be displayed as sort of a "rack" if favorites, if you will. Wow that sounds awesome. All the sideshowfx profile can do is open and close the plugin editor you last used in Cubase. It can however launch any VI you want and has dedicated icons for the most popular ones - like Kontakt and Halion7 etc My Stream Deck XL is dedicated to the sideshowfx profile - though it can still do Windows tasks as they run on the Stream Deck software unaffected by the sideshow profile. If your macros run using Cubase MIDI remote interaction then Id' need to buy another Steam Deck but I'd be happy to do that if it meant I had a mini rack of launchable favourite plugin processors -
|
|
|
Post by Quint on Oct 23, 2024 9:02:28 GMT -6
Can you describe a little more what Sideshow does or doesn't do with opening and closing plugins? In any case, what I did with Luna, and what I think will be able to be done with Cubase, is to do the following things: 1. Open and close any individual plugin GUI in any individual insert with one push of a button on the Stream Deck. 2. That same SD button push will also automatically cause your hardware controller to display the MCU parameters for the plugin GUI you've just opened. 3. The insert buttons on the SD will update realtime to display the name and image of the plugins loaded in those inserts, as you change channels in Cubase. 4. Plugins that are open will be shown as such on the SD with an orange ring around the button image. 5. Similarly, the selected channel name will update on a different button on the SD as well. 6. You'll be able to turn on/off plugins from the SD. 7. You'll be able to load plugins into Cubase, using only buttons on the SD. Plugin options will be displayed as sort of a "rack" if favorites, if you will. Wow that sounds awesome. All the sideshowfx profile can do is open and close the plugin editor you last used in Cubase. It can however launch any VI you want and has dedicated icons for the most popular ones - like Kontakt and Halion7 etc My Stream Deck XL is dedicated to the sideshowfx profile - though it can still do Windows tasks as they run on the Stream Deck software unaffected by the sideshow profile. If your macros run using Cubase MIDI remote interaction then Id' need to buy another Steam Deck but I'd be happy to do that if it meant I had a mini rack of launchable favourite plugin processors - This is how I have it set up for Luna, and I haven't seen anything thus far that I think would prevent me from setting it up this same way for Cubase. If anything, Cubase should be easier to do it for, because it actually communicates with the world outside of itself, thru midi, where as Luna is pretty closed off. I had to do a bunch of image recognition stuff in Keyboard Maestro to get it to work in Luna. Total pain in the ass, but it worked. It just occured to me. Are you on Mac? I use Keyboard Maestro to do some of this stuff. It's really powerful. That said, Keyboard Maestro is Mac only, and you would need to buy KM, but it's not expensive.
|
|
|
Post by Tbone81 on Oct 23, 2024 18:30:08 GMT -6
I'm a big fan of HW inserts in Cubase. I use them for hybrid mixing all the time. One thing to be careful of. They are GLOBAL. If you adjust input/output level on the plugin interface of your "La2a HW" insert when working on song A, then you open song B, the levels will now be where you left them in song A. Again, they are GLOBAL. So I always use a trim plugin right before and after the HW insert plugin, and I do any gain staging from there. Also, if you don't already have it, check out the free plugin "Snapshot" that lets you take photos of your analog gear settings and upload them into the plugin so they live with your sessions... Easy recall Good to know about the global thing. That kind of sucks. They need to fix that. However, I suppose there is a silver lining here. If I use trim plugins, as you suggested, I could set up presets on the trim plugins for varied gain staging uses. I was disappointed that Cubase didn't have presets for the HW inserts plugin, as I was wanting to use presets for different gain staging uses, but the trim plugins could do the same thing. But Cubase really just needs to update to get rid of the global thing, and add presets. I want to correct something about the HW send/receive gain in Cubase….they are not really global, not in the way that was just described. When you pull up a fresh instance of a HW plugin it will default to the last used I/O settings, but once you change those settings it’ll save with the session and it WONT change anything in any other session. I did a double take when I read that so I just double checked. Changing the send/receiving gain won’t harm any other session.
|
|
|
Post by Quint on Oct 24, 2024 10:53:45 GMT -6
Good to know about the global thing. That kind of sucks. They need to fix that. However, I suppose there is a silver lining here. If I use trim plugins, as you suggested, I could set up presets on the trim plugins for varied gain staging uses. I was disappointed that Cubase didn't have presets for the HW inserts plugin, as I was wanting to use presets for different gain staging uses, but the trim plugins could do the same thing. But Cubase really just needs to update to get rid of the global thing, and add presets. I want to correct something about the HW send/receive gain in Cubase….they are not really global, not in the way that was just described. When you pull up a fresh instance of a HW plugin it will default to the last used I/O settings, but once you change those settings it’ll save with the session and it WONT change anything in any other session. I did a double take when I read that so I just double checked. Changing the send/receiving gain won’t harm any other session. Ok. Good to know. That makes a little more sense to me, as the previous description seemed to me like a huge oversight on the part of Steinberg. That said, it would still be better if it just always started at unity gain, or something like that. In my case, I think this will end up being moot for me. My intention is just to set all of my HW inserts at unity within Cubase. That way, I don't ever have to worry about the gain setting that the HW inserts plugin was set at the last time I used it. My intention is to leave the HW insert plugin on Cubase always set to unity, and then use trim plugins that I am able to actually create presets for, and then exclusively gain stage into and out of the HW inserts plugins using standalone trim plugins. Trim In > Dither> HW Insert > Trim Out On that note, I'm wondering if there is a trim plugin out there that can be used as a pair, where they communicate with one another. In other words, if I increased the gain on the Trim In instance of said trim plugin, the gain on the Trim Out instance of said trim plugin would auto adjust to accordingly decrease the gain. Maybe Cubase's trim plugins can do this? I haven't tried it yet. Edit: Bluecat might have just the thing I need, but the link feature on this plugin might not offer enough individual links, so I might still be looking. www.bluecataudio.com/Products/Product_GainSuite/
|
|
|
Post by veggieryan on Nov 12, 2024 12:47:06 GMT -6
I guess UAD is reading this thread because they just quietly added dual buffers to LUNA... check the release notes for today's v1.7.3 release.
Interesting. Kudos to them.
UAD: Since you are reading this, please add hardware inserts and an AI drummer like Logic so I can switch back to LUNA.
Also, can you allow a 32 sample buffer size for 96 khz sample rates? 32 works well in Logic for some interfaces...
|
|
|
Post by Quint on Nov 12, 2024 13:02:21 GMT -6
I guess UAD is reading this thread because they just quietly added dual buffers to LUNA... check the release notes for today's v1.7.3 release. Interesting. Kudos to them. UAD: Since you are reading this, please add hardware inserts and an AI drummer like Logic so I can switch back to LUNA. Also, can you allow a 32 sample buffer size for 96 khz sample rates? 32 works well in Logic for some interfaces... It's just one more indication that UA has started slow walking away from DSP... Interestingly enough, I think they already sort of had a dual buffer in place, but only for instrument VI tracks that were armed for record. Any track which was recording audio still was subject to the overall global buffer. Looks like they've basically just opened the instrument buffer up to be used by ANY track now. But, yeah, it looks like Luna has dual buffers now. So I'm sure non-Apollo users will be pleased by this.
|
|
|
Post by veggieryan on Nov 12, 2024 13:23:51 GMT -6
They also reduced the latency of the Lion and Ruby plugins. I guess all my whining paid off...
|
|
|
Post by Quint on Nov 12, 2024 13:25:24 GMT -6
They also reduced the latency of the Lion and Ruby plugins. I guess all my whining paid off... What was the latency before and what is it now? Whatever it is now, the fact that they were able to reduce it at all is, I think, an indicator that they always could have released those plugins at a lower latency, but intentionally chose not to.
|
|
|
Post by veggieryan on Nov 12, 2024 13:28:29 GMT -6
UAD, can you go ahead and reduce the latency of the other UADx plugins so we can monitor through them?
As of now I can't really use any of them for a DAW monitoring workflow...
|
|