gdgross Posted December 5, 2012 Share Posted December 5, 2012 Logic 9 has been very unstable for me the last several weeks. In general, it's been less stable than v8. I've probably lost 5-10 hours of work over the last week because of the program crashing. it's very frustrating. I'm on mountain lion, running logic in 32 bit mode on a 2011 macbook pro upgraded to 8GB RAM. Generally large sessions with both audio and midi tracks. Not a lot of plugins running yet as I haven't got into really mixing the tracks yet. Mostly just editing audio at this point. Any general advice to keep me from throwing my computer out the window?? it's pretty maddening to have logic show me the pinwheel of death after an hour's worth of work and lose everything. I know the obvious. Save early and often.... Link to comment Share on other sites More sharing options...
Rev. Juda Sleaze Posted December 5, 2012 Share Posted December 5, 2012 Any reason you're not running it in 64bit? Link to comment Share on other sites More sharing options...
nightkrawler Posted December 5, 2012 Share Posted December 5, 2012 I'm on mountain lion this is likely your problem. mountain lion is a piece of crap in terms of performance w/ Logic. it is really impossible for me to believe that Apple did any serious testing of Logic before releasing this OS given my experiences and what i have heard from others. i have experienced 50% CPU usage while IDLING (aka, doing NOTHING, no tracks, no audio files, no VSTs) on Logic + Mountain Lion. I would recommend you downgrade to 10.6.8. if it's an option. Link to comment Share on other sites More sharing options...
nightkrawler Posted December 5, 2012 Share Posted December 5, 2012 Any reason you're not running it in 64bit? what does that have to do w/ the program crashing? he said he isn't using a lot of plugins. also many plugins are just not ready for 64 bit yet. Link to comment Share on other sites More sharing options...
n6smith Posted December 5, 2012 Share Posted December 5, 2012 Nightkrawler Mountain Lion (10.8.2) and Logic 9.1.8 working perfectly here with no heavy CPU usage or any other anomalies ... (other than the known issue with graphical draw slowdown when using a few specific plugins) so you should add to your comments "For me..." rather than make a sweeping statement that implies it would be the same way for everyone because that plainly isn't the truth... As for your CPU issue, please take a screen shot of the entire Logic window when this is happening along with the detailed CPU usage window... and if possible a screenshot of the Activity monitor in list view by CPU usage..when this is occurring as well as the specs of your computer... and post the lot up here so we can take a look/see and help you work out why you are seeing such high use during idle as that is not the norm at all.... Cheers.. Link to comment Share on other sites More sharing options...
n6smith Posted December 5, 2012 Share Posted December 5, 2012 Any reason you're not running it in 64bit? what does that have to do w/ the program crashing? he said he isn't using a lot of plugins. also many plugins are just not ready for 64 bit yet. Umm... There are very few AU plugins that are commonly used by most.. that haven't been converted to 64bit these days... and those that are still 32bit tend to be either old software like Sylenth who's developer has just stopped work on it, it seems... or there are better/equivalent plugins to replace those that are not being converted in a prompt manner. Almost all the major plugins are now available as 64bit AUs... However, If you find the 32bit bridge in 64bit Logic.. to be somewhat unstable with certain 32bit plugins you may use.. you can always use VEP5 to run and convert those 32bit plugins to 64bit and then Logic never uses it's 32bit bridge at all. Also, running in 64bit mode allows Logic to use and benefit from that extra memory the OP has installed..... so it makes sense to use 64bit mode unless there is a very good reason not to... I cannot recall the last time I needed to actually run Logic in 32bit for any period of time... Link to comment Share on other sites More sharing options...
Bouncer Posted December 5, 2012 Share Posted December 5, 2012 lol i was saying the same thing 2 years ago.... Link to comment Share on other sites More sharing options...
nightkrawler Posted December 5, 2012 Share Posted December 5, 2012 Any reason you're not running it in 64bit? what does that have to do w/ the program crashing? he said he isn't using a lot of plugins. also many plugins are just not ready for 64 bit yet. Umm... There are very few AU plugins that are commonly used by most.. that haven't been converted to 64bit these days... and those that are still 32bit tend to be either old software like Sylenth who's developer has just stopped work on it, it seems... or there are better/equivalent plugins to replace those that are not being converted in a prompt manner. Almost all the major plugins are now available as 64bit AUs... However, If you find the 32bit bridge in 64bit Logic.. to be somewhat unstable with certain 32bit plugins you may use.. you can always use VEP5 to run and convert those 32bit plugins to 64bit and then Logic never uses it's 32bit bridge at all. Also, running in 64bit mode allows Logic to use and benefit from that extra memory the OP has installed..... so it makes sense to use 64bit mode unless there is a very good reason not to... I cannot recall the last time I needed to actually run Logic in 32bit for any period of time... i would say i use Sylenth more than any other AU, so that's a problem for me. re: CPU issue, will post screenshots later tonite. Link to comment Share on other sites More sharing options...
n6smith Posted December 5, 2012 Share Posted December 5, 2012 i would say i use Sylenth more than any other AU, so that's a problem for me. re: CPU issue, will post screenshots later tonite. Yes.. it's unfortunate that Sylenth is now basically 'abandon ware' because it's a pretty good softsynth... However, it does work well with VEP5 so you could use that to get around the need for the 32bit bridge... (at an extra cost of course). For me, I stopped using Sylenth given it will not be updated any further and switched over to Zebra II and Diva, both of which are outstanding replacements... Also, I suspect it won't be long until the 32bit bridge is done away with altogether... so then VEP5 would become the only worthwhile alternative to enable Sylenth to be run if that occurs.. should you want to upgrade to the next version of Logic. Anyhow, I'll look out for your screenshots.. and see if I (or anyone else) can help track down the cause of your issue... Link to comment Share on other sites More sharing options...
gdgross Posted December 8, 2012 Author Share Posted December 8, 2012 No particular reason I'm running in 32 bit mode other than I never changed and can't remember how now.... something I check somewhere and it boots up as 64b next time, right? It seems that the crashing is related to either the melodyne plugin or a particular session that I'm working on. Either way, it seems that it crashes when I'm working in melodyne on one or more tracks, which is quite annoying after half an hour of manual tuning, lol! I'll take a screen shot next time it crashes, but all it looks like is a big session open with a melodyne plugin window or two. I had a couple days to cool down and enable myself to post with some smiles! heh Link to comment Share on other sites More sharing options...
ski Posted December 8, 2012 Share Posted December 8, 2012 Saying that you're not using a lot of plugins doesn't mean much without having something to compare it to. That said... In 32-bit mode, you will run out of RAM for Logic to operate when ram usage hits approx. 3G. Even though 32-bit apps claim a 4G footprint, Logic loses its mind as RAM usage approaches and/or hits 3G. So here's a thought, just a thought... Melodyne might be the culprit, and here's my thinking... if the RAM usage of your project, combined with whatever RAM usage Melodyne approaches that 3G limit, expect crashes. To switch to 64-bit mode, quit Logic. Hit CMD-I on the app and uncheck the 32-bit box. Re-launch Logic. Downside: should you instantiate any 32-bit plugins, the dreaded 32-bit Bridge will kick in to host them. The Bridge is a poorly designed piece of software and you can expect it to crash on a regular basis. So you have to pick your poison: 1) run Logic in 32-bit mode and be constrained by the 3G RAM usage limit (expect crashes on certain projects) 2) run Logic in 64-bit mode and deal with the POS Bridge in the event you use 32-bit plugs 3) run Logic in 32-bit mode and use it with Vienna Ensemble Pro to host 64-bit plugs 4) run Logic in 64-bit mode and use it with Vienna Ensemble Pro to host 32-bit plugs, with the caveat that not all 32-bit plugs will work when hosted in VEP Link to comment Share on other sites More sharing options...
DanRad Posted December 9, 2012 Share Posted December 9, 2012 I've had some intermittent trouble with Melodyne. Be sure to empty out the folder that stores the Melodyne files. I ALWAYS bounce the melodyne parts and then disable it. That way there are no errant melodyne parts floating around. Also, that way you can cut and paste them. Melodyne seems to run "on the side" and has its own ideas about time and where you are in the song and stuff.. Bouncing the parts avoids this problem. Link to comment Share on other sites More sharing options...
gdgross Posted December 9, 2012 Author Share Posted December 9, 2012 Well, switched over to 64 bit mode, and have been working in melodyne all afternoon, no crashes yet! keeping my fingers crossed.. And yeah, my habit as well: once I've done any significant editing, in melodyne or another tool, I bounce to a a new track and mute and freeze the old one. (in case I ever need it again.) Link to comment Share on other sites More sharing options...
fisherking Posted December 9, 2012 Share Posted December 9, 2012 i am having a great time in ML, with logic 9. running 64bit. my last remaining 32bit plugin is also sylenth1, which i use...a lot. occasionally (and less often then ever before), the bridge crashes; i click the window, there's a short beachball, and the bridge is back up, and all is well. shame about sylenth1. i love this plugin, and have amassed a ridiculously large preset library for it, but seems we'll never see a 64bit AU (the plugin hasn't been updated since 1880 or something...actually 2009 LOL). btw, if you throw logic out the window, won't that take you mac with it? not a good idea... Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.