|
|
Post by RealNoob on Sept 13, 2024 14:07:02 GMT -6
OK, so I have bounced around. I am sure a couple of you remember seeing that - PT, SO, MB32C, Luna, Logic. Reaper. - PT - seems to be resource heavy, stops playback way too much.
- SO - I was having some outboard issues
- MB32C - Automation is a nightmare
- Luna - all the slots (insert/input/send/out) are broken up into group that you are forever toggling
- Logic - at the time, you could not change the routing of the mains away from 1/2. May be fixed now?
- Reaper - just kind of clunky
What the heck do I do? The cache in PT is set to 1024. I m running a MBP M2MAX with 96G ram and SSD. It's a solid machine. Any thoughts?
I'd prefer to fix PT and stay with it.
|
|
|
|
Post by kcatthedog on Sept 13, 2024 14:18:05 GMT -6
That seems an odd problem to have with PT’s: never heard that before: sure it’s not your session ?
Why, with logic, do you need to change 1-2, can you not just set channels or groups, what ever, to what ever outs you want and use a patchbay to send where you want ?
|
|
|
|
Post by svart on Sept 13, 2024 14:19:31 GMT -6
Reskin reaper in a PT skin?
|
|
|
|
Post by RealNoob on Sept 13, 2024 14:25:32 GMT -6
That seems an odd problem to have with PT’s: never heard that before: sure it’s not your session ? Why, with logic, do you need to change 1-2, can you not just set channels or groups, what ever, to what ever outs you want and use a patchbay to send where you want ? Not a big session and not the first time - PT. Logic - need out to go to 15/16 of BigSix for outboard purposes. |
|
|
|
Post by anders on Sept 13, 2024 14:38:51 GMT -6
I'm often going out from a different pair of outs in Logic. What you can do if you need to use the stereo bus, is to add the Utility plugin "I/O" (put it last in the plugin chain) to your Stereo bus and route it to 15/16.
If you'll be bouncing to disk at some point, you just hit the "disable" button on the I/O plug.
And if you're doing this regularly, add this I/O routing to your default template.
|
|
|
|
Post by RealNoob on Sept 13, 2024 14:47:12 GMT -6
I'm often going out from a different pair of outs in Logic. What you can do if you need to use the stereo bus, is to add the Utility plugin "I/O" (put it last in the plugin chain) to your Stereo bus and route it to 15/16. If you'll be bouncing to disk at some point, you just hit the "disable" button on the I/O plug. And if you're doing this regularly, add this I/O routing to your default template. Interesting. I was working with Apple support who never arrived at a solution for me. Thanks |
|
|
|
Post by the other mark williams on Sept 13, 2024 15:00:14 GMT -6
That seems an odd problem to have with PT’s: never heard that before: sure it’s not your session ? Why, with logic, do you need to change 1-2, can you not just set channels or groups, what ever, to what ever outs you want and use a patchbay to send where you want ? Not a big session and not the first time - PT. Logic - need out to go to 15/16 of BigSix for outboard purposes. I'm often going out from a different pair of outs in Logic. What you can do if you need to use the stereo bus, is to add the Utility plugin "I/O" (put it last in the plugin chain) to your Stereo bus and route it to 15/16. If you'll be bouncing to disk at some point, you just hit the "disable" button on the I/O plug. And if you're doing this regularly, add this I/O routing to your default template. Interesting. I was working with Apple support who never arrived at a solution for me. Thanks You can also just go into Audio MIDI Setup (the Mac systemwide app) and highlight the driver you're using (in your case, SSL BiG SiX), click the button "Configure Speakers," and then you can just choose whichever pair you want to be your "1/2," if that makes sense. All your systemwide audio will use that pair. [EDIT: See my other post below about getting Logic's 'Stereo Outs' to show up where you want on your BiG SiX.] |
|
|
|
Post by doubledog on Sept 13, 2024 16:04:32 GMT -6
So which version of Pro Tools are you using? If it's up to date I'd also be surprised if that system could not keep up, but if it is a current (or close to current) version, then maybe look at what else you have on the system that could be running in the background -- virus scanner, file system/disk indexing, internet thingies? Personally I keep mine disconnected and I use a physical iLok and never iLok cloud. Anyway, I'm sure there are a ton of background processes and if one of them gets greedy... I'm not a mac guy so I can't tell you how to optimize it but I'm sure someone else here has more knowledge on that. (I optimize my system by disabling things I don't need/use/want but since I'm on Windows that won't help you...)
and what about plugins - what do you typically run, or what was running when you say it stops? I do have some plugins that are very resource heavy and I find it better to freeze or commit those effects once I get what I want (or get close - sometimes I'll freeze, unfreeze, adjust, etc. a few times and then at the end "commit").
|
|
|
|
Post by prene1 on Sept 13, 2024 17:20:28 GMT -6
I receive sessions from whatever daw and throw it all in Mixbus v10.
Reaper for me is my personal but it’s a bunch of crap that starting to piss me off.
Protools will always be protools.
But for mixing, mixbus give me the console feeling and what do you find strange with its automation? I have no issues automating, but I have so many controllers in front of me.
|
|
|
|
Post by the other mark williams on Sept 13, 2024 17:44:51 GMT -6
Actually, RealNoob - just to make sure I'm understanding what your Logic problem was with regards to using the SSL BiG SiX: It sounds like you wanted what Logic calls the "Stereo Outs" to go out 'USB 15/16' instead of 'USB 1/2'? Do I have that right? If that's all it was, you can go to the Logic Pro Settings, then go to the Audio tab, then the I/O Assignments tab, and there you can assign the Stereo Outs to go to whichever set of driver outputs you want to use. You should be able to get the 2-bus to come up on whatever set of faders you want on the BiG SiX. |
|
|
|
Post by RealNoob on Sept 13, 2024 18:24:36 GMT -6
I receive sessions from whatever daw and throw it all in Mixbus v10. Reaper for me is my personal but it’s a bunch of crap that starting to piss me off. Protools will always be protools. But for mixing, mixbus give me the console feeling and what do you find strange with its automation? I have no issues automating, but I have so many controllers in front of me. The way the automation lanes don't nest like other daws. Makes it tough when you have a lot, to know what's what as they don't accept the color of the track. |
|
|
|
Post by phdamage on Sept 13, 2024 19:02:02 GMT -6
If I were starting over, I would absolutely start with Reaper. It is super light on CPU, infinitely customizable and just has some features I wish all DAWs did - wet/dry for all plugs, slider for speed/pitch, among others
|
|
|
|
Post by reddirt on Sept 13, 2024 21:06:58 GMT -6
Must be a session from hell that stops an M2 Max with 96 gig of ram - possibly something's wrong somewhere else?
Cheers, Ross
|
|
|
|
Post by BenjaminAshlin on Sept 13, 2024 21:18:08 GMT -6
Only solution is the one you haven't mentioned. Cubase.  |
|
|
|
Post by Dan on Sept 14, 2024 10:39:34 GMT -6
If I were starting over, I would absolutely start with Reaper. It is super light on CPU, infinitely customizable and just has some features I wish all DAWs did - wet/dry for all plugs, slider for speed/pitch, among others many people hate Reaper but everyone young seems to use it or Logic because they’re cheap and Reaper doesn’t have the bugs of Logic. Pro Tools and Logic have insane development issues. You cannot use the new versions with the bug fixes on your OS often despite daws being trivial to run on any current computer suitable for low latency audio. Computers also outpaced the audio engine of Cubase and Nuendo years ago. Steinberg needs to rewrite it because the engine collapses before most Apple Silicon and Intel 12th gen onward processors give out. |
|
|
|
Post by BenjaminAshlin on Sept 15, 2024 17:42:00 GMT -6
If I were starting over, I would absolutely start with Reaper. It is super light on CPU, infinitely customizable and just has some features I wish all DAWs did - wet/dry for all plugs, slider for speed/pitch, among others Computers also outpaced the audio engine of Cubase and Nuendo years ago. Steinberg needs to rewrite it because the engine collapses before most Apple Silicon and Intel 12th gen onward processors give out. That's incorrect now days. On the M series, Cubase is the only DAW that can sit with Reaper performance wise. All other daws perform objectively worse, because they can't utilize multicore performance as well as Reaper or Cubase. Anyway, Cubase 13 is half price at the moment. |
|
|
|
Post by the other mark williams on Sept 15, 2024 17:48:12 GMT -6
Computers also outpaced the audio engine of Cubase and Nuendo years ago. Steinberg needs to rewrite it because the engine collapses before most Apple Silicon and Intel 12th gen onward processors give out. That's incorrect . On the M series, Cubase is the only DAW that can sit with Reaper performance wise. All other daws perform objectively worse, because they can't utilize multicore performance as well as Reaper or Cubase. Anyway, Cubase 13 is half price at the moment. What's the honest assessment of Cubase on Mac at this point? I know historically the Mac version was seriously outpaced by the PC version. Is this still true? |
|
|
|
Post by BenjaminAshlin on Sept 16, 2024 3:55:38 GMT -6
That's incorrect . On the M series, Cubase is the only DAW that can sit with Reaper performance wise. All other daws perform objectively worse, because they can't utilize multicore performance as well as Reaper or Cubase. Anyway, Cubase 13 is half price at the moment. What's the honest assessment of Cubase on Mac at this point? I know historically the Mac version was seriously outpaced by the PC version. Is this still true? It is better on M1 Mac now than PC. Reaper and Cubase seem to have the best (by a margin) multicore performance on M series (which is the M series strong point). I'm currently tossing up if I move my studio computer back to Apple. |
|
|
|
Post by Quint on Sept 16, 2024 7:55:13 GMT -6
What's the honest assessment of Cubase on Mac at this point? I know historically the Mac version was seriously outpaced by the PC version. Is this still true? It is better on M1 Mac now than PC. Reaper and Cubase seem to have the best (by a margin) multicore performance on M series (which is the M series strong point). I'm currently tossing up if I move my studio computer back to Apple. So Cubase used to be worse on Mac than PC, but now it's BETTER on Mac than PC? |
|
|
|
Post by gravesnumber9 on Sept 16, 2024 8:41:20 GMT -6
Computers also outpaced the audio engine of Cubase and Nuendo years ago. Steinberg needs to rewrite it because the engine collapses before most Apple Silicon and Intel 12th gen onward processors give out. That's incorrect now days. On the M series, Cubase is the only DAW that can sit with Reaper performance wise. All other daws perform objectively worse, because they can't utilize multicore performance as well as Reaper or Cubase. Anyway, Cubase 13 is half price at the moment. $179 for competitive crossgrade for Cubase Pro perpetual license? That's very reasonable. I'm not in the market but that's affordable enough to make it worth double checking to make sure I should continue to not be in the market. |
|
|
|
Post by bluesholyman on Sept 16, 2024 10:03:48 GMT -6
What the heck do I do? The cache in PT is set to 1024. I m running a MBP M2MAX with 96G ram and SSD. It's a solid machine. Any thoughts?
I'd prefer to fix PT and stay with it.
It was not said, so I am assuming all your disk I/O is on the internal drive? Possibly some contention there. I don't know you or your experience so if this is choir preaching, apologies. I'd put plugins/vst and projects on separate external ssd drives and just run PT/Apps from the internal disk. |
|
|
|
Post by Dan on Sept 16, 2024 10:28:02 GMT -6
Computers also outpaced the audio engine of Cubase and Nuendo years ago. Steinberg needs to rewrite it because the engine collapses before most Apple Silicon and Intel 12th gen onward processors give out. That's incorrect now days. On the M series, Cubase is the only DAW that can sit with Reaper performance wise. All other daws perform objectively worse, because they can't utilize multicore performance as well as Reaper or Cubase. Anyway, Cubase 13 is half price at the moment. Okay they fixed it. Cubase was far behind Reaper and Logic the last time I tried it. DAW Bench posted what the exact problem was a while ago but it was there for a few years when the performance + efficiency core cpu designs came out. |
|
|
|
Post by christopher on Sept 16, 2024 11:29:11 GMT -6
I’m guessing you are heavy into soft synths. That’s a tough one.
Try Reason, see if you can demo it. The built in synths are usually solid. See Dua Lipa etc. The SSL mixer sounds pretty good. If you’ve never used it, just know hit ‘tab’ on the keyboard to see the back of the rack, where you can patch cables like analog. Super fun.
(Edit: I went and saw the new 13 reviews are meh as far as DAW goes .. I thought they might be up to speed, guess not 😔)
|
|
|
|
Post by RealNoob on Sept 17, 2024 22:30:50 GMT -6
I had assumed it was resource issues when I got the stops, due to the code given. Tonight, I wanted to quantify the usage so I set up a project, set up 3 plugs on each channel and threw six verbs in there. I used the system usage window and the resource pull was VERY low. So it appears it may be simply tryin to do too many things on multiple screens while mixing. I will need to focus, I believe.
|
|
