|
|
Post by topshelfmg on Mar 19, 2017 2:51:44 GMT -6
So I am currently in the process of slowly learning and switching over to Cubase (I have PT 10 and 11, but never personally fell in love with either) but still have to finish up some projects with fast approaching deadlines in Logic Pro X. About a year ago, I got the biggest, baddest, Late 2013 Mac Pro 12 Core with 64GB of RAM so that I would have more than enough CPU (I typically run projects in 96K), and I wouldn't have to buy a new computer for years and years. I have had problems with these last projects overloading, and when I checked the CPU from within Logic, I learned that only cores 1 and 12 were overloading, while I want to say either cores 2-8 or 2-9 were at between 1/2 and 2/3 useage, and cores 8-11 or 9-11 were hardly being used at all... almost inactive. This is a relatively big, full band project, but definitely nothing outside the norm. There is also a fair bit of plugins but nothing ultra CPU hungry like Ozone 7 Advanced. I save most of the CPU hogs for after everything is printed.
Turns out that Logic is unable to process threads over multiple cores, and that each channel strip is permanently assigned to a particular core, and it is unable to split tasks across multiple cores. Is this STRICTLY a Logic problem, and will these issues go away once I switch to Cubase? I am only getting about 1/2 of the power at my disposal, and it's driving me nuts with all of these clicks, pops, and overload messages. I have heard Logic is notoriously bad at CPU distribution, since I have friends and colleagues that work at 96K constantly also, except from within Cubase or PT. They have less available CPU and RAM, and seem to never have any problems. My buffer size is currently at 1024 as well, which is insane that I am having CPU issues even then. I have read about a vague solution where you re-bus everything so that the plugins are theoretically spread across multiple cores, but it's extremely tedious and cumbersome, with no guarantees of it working.
Does anyone with Logic have a workaround, or is there any other solution to this besides shooting in the dark with the sub-bus idea where you would i.e. take all of the plugins from the mix buss and split them over two busses which you route every other track through, and then run the output of those busses to the mix bus? The thing with that, is there is nothing definitive about what core controls what in Logic, so it would be shooting in the dark. After experimenting, I believe core 12 (which is one of the cores overloading) pertains to the mix bus. But I have no more on the mix bus than I do in any other project or any other channel strip, and again, nothing ultra CPU heavy that the computer shouldn't be able to handle.
I went through the whole Logic multi-thread nonsense (switched from automatic to 24, etc), and double checked that all applications were closed, including Dropbox and Google Drive from the top of the screen. I am currently running 10.10.5 Yosemite with no intention of "upgrading" any time soon as I would lose some old plugins. I also don't want to print anything quite yet as I am currently mixing the vocals, and would like to be able to fine tune the instrumental to the vocals if need be. Save me RGO.
At least it is better than tape shed.
|
|
|
|
Post by b1 on Mar 19, 2017 7:34:19 GMT -6
I'd suggest trying Reaper before going with Cubase. It's lean and mean. I use it on a humongous catchall "noodling" project for writing and arranging new ideas. Tons of plugins, tracking 5 Vox, 2 Guitars triggering 5 Synths (incl. Kontkt loaded up). The project folder is over 41 GB, all on a 3.3 GHz Core 2 Duo with 8 GB RAM. I have a web browser, Email Client open plus several other programs running at the same time. Reaper does Scoring and Video. The installation file is 10.5 MB.... it just works.
|
|
|
|
Post by explorer on Mar 19, 2017 7:52:52 GMT -6
Here's how to balance cores in Logic - pay close attention to Live Input Mode etc: support.apple.com/en-us/HT201838The disadvantage of having a 12 core machine is that each core is slower than say a 6 core. Also be aware that some audio interfaces are more efficient than others (e.g. RME). Failing all that - make friends with the freeze function? |
|
|
|
Post by swurveman on Mar 19, 2017 8:29:34 GMT -6
I currently have a big Cubase 8 project with lot of plugins and vst's that is taxing about 50% of my i7 and half of my RAM. It won't even open. Meanwhile, I can open smaller projects. I have a tech calling me Monday. I'll let you know what he says
|
|
|
|
Post by topshelfmg on Mar 19, 2017 13:42:44 GMT -6
I currently have a big Cubase 8 project with lot of plugins and vst's that is taxing about 50% of my i7 and half of my RAM. It won't even open. Meanwhile, I can open smaller projects. I have a tech calling me Monday. I'll let you know what he says Thanks! Let me know what they say. I recently had my computer serviced about 2 or 3 months ago, and they said everything is in perfect shape now. So I'm curious to hear your findings. |
|
|
|
Post by topshelfmg on Mar 19, 2017 13:45:51 GMT -6
I'd suggest trying Reaper before going with Cubase. It's lean and mean. I use it on a humongous catchall "noodling" project for writing and arranging new ideas. Tons of plugins, tracking 5 Vox, 2 Guitars triggering 5 Synths (incl. Kontkt loaded up). The project folder is over 41 GB, all on a 3.3 GHz Core 2 Duo with 8 GB RAM. I have a web browser, Email Client open plus several other programs running at the same time. Reaper does Scoring and Video. The installation file is 10.5 MB.... it just works. Cubase is what I have to switch to since the one studio in town I do the most work out of besides my own uses Cubase (and he has sold me on it), plus I already went out and purchased it. Heard great things about Reaper though, but unforuntely it's not in the stars for me anytime soon. Good to know it's most likely just a Logic imperfection then! Most 96K projects are fine, this one is just not balancing the cores properly for whatever reason. |
|
|
|
Post by topshelfmg on Mar 19, 2017 13:50:22 GMT -6
Here's how to balance cores in Logic - pay close attention to Live Input Mode etc: support.apple.com/en-us/HT201838The disadvantage of having a 12 core machine is that each core is slower than say a 6 core. Also be aware that some audio interfaces are more efficient than others (e.g. RME). Failing all that - make friends with the freeze function? Thanks. This is the article I saw about the sub-bus method. Looking like I'll have to give it a shot for this. I opted for the larger core option in the 12 core configuration, so I was hoping that wouldn't be the case, but for whatever reason with this project that decision is biting me. Normally the advantages seem to outweigh the disadvantages, besides with issues such as this for whatever reason. Live input mode is just for if you are recording or if you have a software instrument track enabled right? How can I tell that Live Input mode is on or off? If so I'm not sure why it would be doing that, but I will try creating a blank crack with no input and having that selected during playback. Also, I wish that you could freeze bus tracks! Also, I am using a Motu 16a at the moment. |
|
|
|
Post by topshelfmg on Mar 19, 2017 23:09:20 GMT -6
So we have established that it is only Logic that will behave like this? If that is the case I will prioritize moving to Cubase.
|
|
|
|
Post by topshelfmg on Mar 20, 2017 0:31:36 GMT -6
Here's how to balance cores in Logic - pay close attention to Live Input Mode etc: support.apple.com/en-us/HT201838The disadvantage of having a 12 core machine is that each core is slower than say a 6 core. Also be aware that some audio interfaces are more efficient than others (e.g. RME). Failing all that - make friends with the freeze function?  I just tried the core distribution trick and made two stereo busses and split what I have on the mix bus between the two... with everything routed to the first bus, which is routed into the 2nd bus, which goes into the stereo out. The same thread, thread 24 (2nd half of core 12), which is giving me most of the problems is still doing the same thing, so unfortunately it didn't work. The first half of core 1, which is thread 1, is still giving me issues though it doesn't stay maxed out, especially now that I have froze the couple tracks I can right now. Would it be a good idea to freeze absolutely everything except what I am mixing currently, and unfreeze only if I have to adjust? When I bypass all of the plugins on the mix bus, the core 12 usage (or rather thread 24) goes down by about 1/4. Do you know what core/thread corresponds to what? It is driving me crazy that the first half of core 12 (thread 23) isn't being utilized at all, but thread 24 is maxed. |
|
|
|
Post by explorer on Mar 20, 2017 9:26:17 GMT -6
- I believe the MOTU drivers are fairly efficient. Make sure you try the latest versions? Sometimes a lower buffer size can work better than a higher one (weird I know). - I think the latest Logic update was meant to improve multicore performance - are you up to date? Updating OSX can also help. - You can also try changing the "process buffer" to large and "multithreading" to "playback only" when you aren't recording (in the Logic audio preferences). - Freezing tracks will turn them into audio files and print any plugins you are using on them. It will not disable any bus processing though. You can slide your mouse down the freeze buttons to activate it on a lot of tracks quickly (also works for solo, mute etc.). - If you play the project and bypass plugins while watching the CPU meter you can get an idea what exactly is giving you trouble. Don't forget to think about any routing. - Remember that just muting an audio track does not disable the plugin processing. You have to bypass the plugins or use the track On/Off buttons (Track Header components>On/Off). - Record/Input arming a track can also cause CPU spikes. Disabling inputs can also save a little power. - Sometimes it takes a few play throughs for Logic to balance the cores.
- I do find Logic more annoying for this stuff than Ableton Live. Haven't tried Cubase for a while.
- There is no manual way to assign plugins to cores. - This thread in the purple place might amuse you www.gearslutz.com/board/apple-logic-pro/1136148-logic-10-3-cpu-spikes.html |
|
|
|
Post by ChaseUTB on Mar 20, 2017 10:37:45 GMT -6
Wow and logic is made for OS X mac platform only and can't even function efficiently... that's crazy... I hope you get sorted and figure out thenroot of the problem plus an answer. I know stuff like this can be maddening especially when you feel like you are stuck.
I would try a Save as on the problematic session make a copy and save it to another partition or SSD/ HDD and see if that helps or hurts your performance... Good luck hope you get up and running asap 🙏
|
|
|
|
Post by swurveman on Mar 20, 2017 17:48:00 GMT -6
I currently have a big Cubase 8 project with lot of plugins and vst's that is taxing about 50% of my i7 and half of my RAM. It won't even open. Meanwhile, I can open smaller projects. I have a tech calling me Monday. I'll let you know what he says Thanks! Let me know what they say. I recently had my computer serviced about 2 or 3 months ago, and they said everything is in perfect shape now. So I'm curious to hear your findings. They said it was a RAM issue. I have only 6GB and they recommend at lest 8. Never had a problem before- and a run tons of plugins + VST's- but I used Drumagog for the first time and it shut me down. Out the door tomorrow to buy more RAM. |
|
|
|
Post by mrholmes on Mar 21, 2017 19:11:56 GMT -6
So I am currently in the process of slowly learning and switching over to Cubase (I have PT 10 and 11, but never personally fell in love with either) but still have to finish up some projects with fast approaching deadlines in Logic Pro X. About a year ago, I got the biggest, baddest, Late 2013 Mac Pro 12 Core with 64GB of RAM so that I would have more than enough CPU (I typically run projects in 96K), and I wouldn't have to buy a new computer for years and years. I have had problems with these last projects overloading, and when I checked the CPU from within Logic, I learned that only cores 1 and 12 were overloading, while I want to say either cores 2-8 or 2-9 were at between 1/2 and 2/3 useage, and cores 8-11 or 9-11 were hardly being used at all... almost inactive. This is a relatively big, full band project, but definitely nothing outside the norm. There is also a fair bit of plugins but nothing ultra CPU hungry like Ozone 7 Advanced. I save most of the CPU hogs for after everything is printed. Turns out that Logic is unable to process threads over multiple cores, and that each channel strip is permanently assigned to a particular core, and it is unable to split tasks across multiple cores. Is this STRICTLY a Logic problem, and will these issues go away once I switch to Cubase? I am only getting about 1/2 of the power at my disposal, and it's driving me nuts with all of these clicks, pops, and overload messages. I have heard Logic is notoriously bad at CPU distribution, since I have friends and colleagues that work at 96K constantly also, except from within Cubase or PT. They have less available CPU and RAM, and seem to never have any problems. My buffer size is currently at 1024 as well, which is insane that I am having CPU issues even then. I have read about a vague solution where you re-bus everything so that the plugins are theoretically spread across multiple cores, but it's extremely tedious and cumbersome, with no guarantees of it working. Does anyone with Logic have a workaround, or is there any other solution to this besides shooting in the dark with the sub-bus idea where you would i.e. take all of the plugins from the mix buss and split them over two busses which you route every other track through, and then run the output of those busses to the mix bus? The thing with that, is there is nothing definitive about what core controls what in Logic, so it would be shooting in the dark. After experimenting, I believe core 12 (which is one of the cores overloading) pertains to the mix bus. But I have no more on the mix bus than I do in any other project or any other channel strip, and again, nothing ultra CPU heavy that the computer shouldn't be able to handle. I went through the whole Logic multi-thread nonsense (switched from automatic to 24, etc), and double checked that all applications were closed, including Dropbox and Google Drive from the top of the screen. I am currently running 10.10.5 Yosemite with no intention of "upgrading" any time soon as I would lose some old plugins. I also don't want to print anything quite yet as I am currently mixing the vocals, and would like to be able to fine tune the instrumental to the vocals if need be. Save me RGO. At least it is better than tape shed. That is funny. I had the same problem with Logic 9 it seemed to be related to Adictive Drums... Anyway I did try all tricks too, busing out and audio tracks with no output as the active track. No chance one core always was on overload. The project had to go on and I muted a few of the slate plug ins and went on with the arrangement. From the moment on a second software instrument joined the show the power was spread over 4 cores instead of 1,2 cores. Please don't ask me why that is like it is the spread is even better if the active channel in an software instrument in record mode. It was the opposite of the usual tricks which made my session run with all plug ins in use. I still do not know why. |
|
|
|
Post by topshelfmg on Mar 22, 2017 22:03:54 GMT -6
So I am currently in the process of slowly learning and switching over to Cubase (I have PT 10 and 11, but never personally fell in love with either) but still have to finish up some projects with fast approaching deadlines in Logic Pro X. About a year ago, I got the biggest, baddest, Late 2013 Mac Pro 12 Core with 64GB of RAM so that I would have more than enough CPU (I typically run projects in 96K), and I wouldn't have to buy a new computer for years and years. I have had problems with these last projects overloading, and when I checked the CPU from within Logic, I learned that only cores 1 and 12 were overloading, while I want to say either cores 2-8 or 2-9 were at between 1/2 and 2/3 useage, and cores 8-11 or 9-11 were hardly being used at all... almost inactive. This is a relatively big, full band project, but definitely nothing outside the norm. There is also a fair bit of plugins but nothing ultra CPU hungry like Ozone 7 Advanced. I save most of the CPU hogs for after everything is printed. Turns out that Logic is unable to process threads over multiple cores, and that each channel strip is permanently assigned to a particular core, and it is unable to split tasks across multiple cores. Is this STRICTLY a Logic problem, and will these issues go away once I switch to Cubase? I am only getting about 1/2 of the power at my disposal, and it's driving me nuts with all of these clicks, pops, and overload messages. I have heard Logic is notoriously bad at CPU distribution, since I have friends and colleagues that work at 96K constantly also, except from within Cubase or PT. They have less available CPU and RAM, and seem to never have any problems. My buffer size is currently at 1024 as well, which is insane that I am having CPU issues even then. I have read about a vague solution where you re-bus everything so that the plugins are theoretically spread across multiple cores, but it's extremely tedious and cumbersome, with no guarantees of it working. Does anyone with Logic have a workaround, or is there any other solution to this besides shooting in the dark with the sub-bus idea where you would i.e. take all of the plugins from the mix buss and split them over two busses which you route every other track through, and then run the output of those busses to the mix bus? The thing with that, is there is nothing definitive about what core controls what in Logic, so it would be shooting in the dark. After experimenting, I believe core 12 (which is one of the cores overloading) pertains to the mix bus. But I have no more on the mix bus than I do in any other project or any other channel strip, and again, nothing ultra CPU heavy that the computer shouldn't be able to handle. I went through the whole Logic multi-thread nonsense (switched from automatic to 24, etc), and double checked that all applications were closed, including Dropbox and Google Drive from the top of the screen. I am currently running 10.10.5 Yosemite with no intention of "upgrading" any time soon as I would lose some old plugins. I also don't want to print anything quite yet as I am currently mixing the vocals, and would like to be able to fine tune the instrumental to the vocals if need be. Save me RGO. At least it is better than tape shed. That is funny. I had the same problem with Logic 9 it seemed to be related to Adictive Drums... Anyway I did try all tricks too, busing out and audio tracks with no output as the active track. No chance one core always was on overload. The project had to go on and I muted a few of the slate plug ins and went on with the arrangement. From the moment on a second software instrument joined the show the power was spread over 4 cores instead of 1,2 cores. Please don't ask me why that is like it is the spread is even better if the active channel in an software instrument in record mode. It was the opposite of the usual tricks which made my session run with all plug ins in use. I still do not know why. Thanks for the reply. That is so strange! I don't have a single virtual instrument on this project as it is all live recordings. I even created a "dummy track" that is totally blank that I will leave it on while I am playing it back. Doesn't seem to help all that much. Luckily the track is 90% done (still have to master, in a separate project file), but the deadline is in a week. And we are doing last minute lapsteel overdubs so I'm going to have to bypass everything on the mix buss and freeze a bunch of tracks so I can turn it off of 1024, cause I have had the latency really mess with recordings, even if there is no latency while recording through playback / over headphones, there is recording latency that puts the track off time. It seems to be thread 1 (1st half of core 1), and thread 24 (2nd half of core 12). What is infuriating is the first half of core 12 isn't even being utilized at all.... so just pull from that core Logic! Thread 24 seems to be isolated to mainly the mix buss... but yes, the bussing trick didn't work. Can't figure out thread one, but freezing whatever tracks I can seems to help. I just bought a Raven MTi2 this week and got it with a Cubase code in addition to Logic.... this will be my last ever project on Logic since there is no solution. You would think that the flagship Apple computer could run the flagship Apple DAW, but nope. They also locked Logic 10.3 behind an OS update, and if I update past Yosemite I will lose a good bit of plugins. I don't agree with those business tactics, and as a Logic user of almost a decade, I don't appreciate it. I left them one of those 200 word feedback messages but I doubt I will get a response. Bummer. At least it motivates me to move to Cubase 9 Pro faster. |
|
|
|
Post by topshelfmg on Mar 22, 2017 22:07:54 GMT -6
Wow and logic is made for OS X mac platform only and can't even function efficiently... that's crazy... I hope you get sorted and figure out thenroot of the problem plus an answer. I know stuff like this can be maddening especially when you feel like you are stuck. I would try a Save as on the problematic session make a copy and save it to another partition or SSD/ HDD and see if that helps or hurts your performance... Good luck hope you get up and running asap 🙏 Thanks for the feedback man, I will give that a try! Have it running from a Glyph StudioRAID thunderbolt... in RAID 1 mode. I guess it can't hurt to try it external. BUT, it says my disk usage is well below half, so it doesn't seem to be the hard drive. It just sucks because 90% of the project is done, with the first songs deadline being this week. It is making the fine tuning difficult, and I have to leave my mid/side EQ off the mix bus and just apply that in the mastering stage. I just left another post on how it is nonsense that Apple's flagship DAW can't even run properly on their beefiest flagship computer. Plus they are locking updates from this point forward behind an OS update as I said below, which I can't do since I need to say on Yosemite otherwise I will lose a bunch of older plugins I like. After this project... Cubase Pro 9, here I come. |
|
|
|
Post by topshelfmg on Mar 22, 2017 22:14:57 GMT -6
- I believe the MOTU drivers are fairly efficient. Make sure you try the latest versions? Sometimes a lower buffer size can work better than a higher one (weird I know). - I think the latest Logic update was meant to improve multicore performance - are you up to date? Updating OSX can also help. - You can also try changing the "process buffer" to large and "multithreading" to "playback only" when you aren't recording (in the Logic audio preferences). - Freezing tracks will turn them into audio files and print any plugins you are using on them. It will not disable any bus processing though. You can slide your mouse down the freeze buttons to activate it on a lot of tracks quickly (also works for solo, mute etc.). - If you play the project and bypass plugins while watching the CPU meter you can get an idea what exactly is giving you trouble. Don't forget to think about any routing. - Remember that just muting an audio track does not disable the plugin processing. You have to bypass the plugins or use the track On/Off buttons (Track Header components>On/Off). - Record/Input arming a track can also cause CPU spikes. Disabling inputs can also save a little power. - Sometimes it takes a few play throughs for Logic to balance the cores.
- I do find Logic more annoying for this stuff than Ableton Live. Haven't tried Cubase for a while.
- There is no manual way to assign plugins to cores. - This thread in the purple place might amuse you www.gearslutz.com/board/apple-logic-pro/1136148-logic-10-3-cpu-spikes.htmlThank you for all of the feedback! Thread 24 is the mix bus mainly I have figured out... so I have to leave off my mid/side EQ while finishing it and apply it in mastering, which kind of sucks. I have tried just about every option you said. I am on 10.10.5 Yosemite with no plans of upgrading as I would lose a ton of older plugins that I still regularly use, and they have the new Logic 10.3 locked behind an OS update, which as a Logic user of almost a decade, comes off rather insulting and is lousy business practices if you ask me. It didn't get me to upgrade, it just got me more motivated to fully learn Cubase 9 Pro faster and make a full switch. Nothing is armed, Motu drivers are up to date... it's in playback only, and I will try a smaller buffer size one last time to below 1024. Freezing tracks helps enough to get it going, and reduces the load to thread 1, but not by as much as I would ideally like it to. If I was able to freeze busses... that would help much more. I figured 12 Cores and 64GB of RAM would prevent any problems, which is why I decided to cash in the savings and make the investment to try to avoid things like this. Luckily the project is almost done.. the fine tuning is just going to suck. I appreciate your help. I'll try your suggestions one more time, but it's looking like I'm a Cubase guy now. |
|
|
|
Post by topshelfmg on Mar 22, 2017 22:17:23 GMT -6
Thanks! Let me know what they say. I recently had my computer serviced about 2 or 3 months ago, and they said everything is in perfect shape now. So I'm curious to hear your findings. They said it was a RAM issue. I have only 6GB and they recommend at lest 8. Never had a problem before- and a run tons of plugins + VST's- but I used Drumagog for the first time and it shut me down. Out the door tomorrow to buy more RAM. That makes sense. This Mac Pro has 64GB of RAM, so that isn't the problem It is a raw CPU thing where it just isn't utilizing all 12 cores as it should. Drumagog is a big CPU hog, so that also makes sense. I would recommend trying to get to 16GB of RAM so you don't have to upgrade again as fast. My old Macbook Pro has 16 GB of RAM and I was able to run 48K projects for a long time no problem. I run projects in 96K now though, since I got the new Mac Pro. |
|
|
|
Post by topshelfmg on Mar 22, 2017 22:48:45 GMT -6
So I tried switching multithreading to playback only.... and thread one got much better but thread 24 got worse. Quite frustrated. And I think my LA2A has a microphonic tube now as of tonight, which I am using on the lead vocals. Gosh darn it. Help me DAW gods. Attachments:
|
|
|
|
Post by mrholmes on Mar 23, 2017 3:54:13 GMT -6
That is funny. I had the same problem with Logic 9 it seemed to be related to Adictive Drums... Anyway I did try all tricks too, busing out and audio tracks with no output as the active track. No chance one core always was on overload. The project had to go on and I muted a few of the slate plug ins and went on with the arrangement. From the moment on a second software instrument joined the show the power was spread over 4 cores instead of 1,2 cores. Please don't ask me why that is like it is the spread is even better if the active channel in an software instrument in record mode. It was the opposite of the usual tricks which made my session run with all plug ins in use. I still do not know why. Thanks for the reply. That is so strange! I don't have a single virtual instrument on this project as it is all live recordings. I even created a "dummy track" that is totally blank that I will leave it on while I am playing it back. Doesn't seem to help all that much. Luckily the track is 90% done (still have to master, in a separate project file), but the deadline is in a week. And we are doing last minute lapsteel overdubs so I'm going to have to bypass everything on the mix buss and freeze a bunch of tracks so I can turn it off of 1024, cause I have had the latency really mess with recordings, even if there is no latency while recording through playback / over headphones, there is recording latency that puts the track off time. It seems to be thread 1 (1st half of core 1), and thread 24 (2nd half of core 12). What is infuriating is the first half of core 12 isn't even being utilized at all.... so just pull from that core Logic! Thread 24 seems to be isolated to mainly the mix buss... but yes, the bussing trick didn't work. Can't figure out thread one, but freezing whatever tracks I can seems to help. I just bought a Raven MTi2 this week and got it with a Cubase code in addition to Logic.... this will be my last ever project on Logic since there is no solution. You would think that the flagship Apple computer could run the flagship Apple DAW, but nope. They also locked Logic 10.3 behind an OS update, and if I update past Yosemite I will lose a good bit of plugins. I don't agree with those business tactics, and as a Logic user of almost a decade, I don't appreciate it. I left them one of those 200 word feedback messages but I doubt I will get a response. Bummer. At least it motivates me to move to Cubase 9 Pro faster. I am not sure if it is a logic problem. And I am not sure if you wont have just other problems with a different DAW. The more different tools join the show the more shit can happen that always has been the case, and I guess it always will be the case. Other things you can do: Take the project folder and copy it to the desktop erase the original one and copy it back. I have no idea why, but it helps sometimes. Save your key commands and projects notes and erase the p lists of logic. Start logic again. If everything fails you can do a clean install of OSX using a fresh SSD and you set up everything from scratch. You use this SSD for audio work only and for nothing else. For the rest you know there is a recording offset setting in the AUDIO settings. You measure the offset with a snare hit track one round trip and you can see the offset in the sample editor in milliseconds. For latency free tracking-monitoring you need an interface that routes the inputs directly to the outputs and lets you do an monitor mix. I love RME but Focusrite does it as well and many others too. With RME you end up with 2.0 ms latency with the Focousrite Saffire 40 at ø 2,7 ms. Cheers. Holmes PS: I think Apple lost the track with too many different Hardware-Setups and way too often major upgrades for the OS. All this is because they want to force us to buy new Apple gear. This attitude became so strange that you are not the only one who thinks to leave Apple I think Cubase wont save you. I did try to watch into Reaper Land and that is difficult at first but gets clearer if you read one of the well written manuals. |
|
|
|
Post by swurveman on Mar 23, 2017 9:07:41 GMT -6
They said it was a RAM issue. I have only 6GB and they recommend at lest 8. Never had a problem before- and a run tons of plugins + VST's- but I used Drumagog for the first time and it shut me down. Out the door tomorrow to buy more RAM. That makes sense. This Mac Pro has 64GB of RAM, so that isn't the problem It is a raw CPU thing where it just isn't utilizing all 12 cores as it should. Drumagog is a big CPU hog, so that also makes sense. I would recommend trying to get to 16GB of RAM so you don't have to upgrade again as fast. My old Macbook Pro has 16 GB of RAM and I was able to run 48K projects for a long time no problem. I run projects in 96K now though, since I got the new Mac Pro. Yeah, Drumagog must be a huge hog. With my 6Gb of RAM and i7 950 I often run 15-20 audio tracks , 7 FX Channels, 7 Group Channels, tons of plugins and 3 VST's with no problem. I can't even put one instance of Drumagog on for long and Cubase crashes. I'm looking for more RAM for my Gigabyte GA-X58A-UD3R (rev) 2 computer. Unfortunately, the local computer store said the RAM they sold me would work on my mobo, but it didn't. I'm having trouble finding the right RAM. I had this computer built for me, but the guy is no longer in business. So, I'm on my own. I currently have (3x2 Gb) Corsair RAM with DDR3 Timing: 9-9-9-24 1.65v. I'm a newbie. So, finding a suitable larger replacement is proving difficult. I thought this would be simple. LOL |
|
|
|
Post by jcoutu1 on Mar 23, 2017 9:49:19 GMT -6
crucial.com
|
|
