Jump to content

Beatworld

Member
  • Posts

    20
  • Joined

  • Last visited

Beatworld's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. Great, thanks for the quick confirmation/answer. Cheers
  2. I'm posting this question for a friend. My question is related to compound meters, for example 6/8. Most typically, 6/8 is conducted as 2, with the dotted eighth getting the beat. I know that DAWs like DP allow you to specify beat values in the conductor track. You could set up 6/8 as 2 beats of dotted-eighths, 3 beats of quarters or 6 beats of eighths. I don’t see that option in Logic. It appears to me that the beat is always the denominator—the eighth note in this example. Does that match what you know? I could easily be missing something. Any help really appreciated. Thanks in advance.
  3. Please confirm Waves v9 plugins are still working ok with 10.10.3. One user at Gearslutz says Waves are not working now. He had them working ok in 10.10.1 and 10.10.2. Thanks
  4. This might help: http://www.macworld.co.uk/how-to/mac-software/revert-back-mavericks-from-yosemite-3581872/
  5. I had EXACTLY the same problem. In fact I have posted quite a bit about it on the "Yosemite is out, consensus with Logic X" thread here. There is a lot of discussion about the problem at Apple Support Community Discussions in Logic Threads. It is a real problem caused by a combo of Yosemite not liking certain Mac hard ware and graphics cards, and many plugins requiring updates to reduce increased cpu loads in Yosemite. You will not resolve it unfortunately. I have given up after 10 days of troubleshooting. I went back to 10.9.5 (via Time Machine Recover) and everything is fine once again. Good luck
  6. Even with the Apogee Maestro software uninstalled, the Duet 2 disconnected and selecting internal audio for input and output (buffer 1024) the high cpu load continues when using Logic 10.0.7. So I think we can rule out the Duet 2. Have you tried doing this just to confirm it ? On Gearslutz I posted thread asking if anyone else is having the issue. Over 150 people have viewed the thread and no one has replied. I assume that means very few people with a mid 2011 iMac have gone Yosemite and use Logic. Surely anyone with that set up who is not having the high cpu load issue would say so. Looks like a mid 2011 iMac issue. cheers
  7. I feel your pain! I have software monitoring off and the buffer at 1024.
  8. Can you remember if after the Yosemite install rebooted itself, you shutdown again manually before using Logic without issue? Repairing Permissions: is it possible the permissions repaired are in a log somewhere? If so this would be a good log to read. I'm 99.7% certain that I didn't shut down again manually before using Logic after the Yosemite reinstall. Because when I tested Logic and it worked I was so happy I used it for a few hours immediately ! I had a good look at the permissions log in Disk Utility at the time. Most of the items repaired I'd never heard of. I was looking for any obvious ones related to audio but don't recall seeing any. I did a repair permissions after the initial Yosemite install and the number repaired was significantly less that the number after the reinstall. cheers
  9. Can you narrow it down to which plugins? maybe there will be updates for the offenders. Haven't really been able to so far. I'm pretty sure I've got latest versions of just about everything. As a starting point the increased cpu load seems to apply across the board once plugins are used. I've deleted old demos and things I don't use but I still have just over 600 AU plugins. The thing is I'm struggling to run really modest projects. eg: 5 song EP mastering job 5 stereo interleaved audio files No more than say 5 inserts on each song maybe 10 inserts on the stereo bus 24/88.2 this is not a big project. I have several similar or smaller EP mastering projects, all suffer the same problem. And don't forget for about 3 hours after I reinstalled Yosemite everything seemed normal again. That is what I find really weird. But now after shutting down my iMac after that ok day the problem returned after rebooting the next day. The joke is all I did that next day before booting Logic was repair permissions with Disk Utility ! I've reset SMC, PRAM, deleted Logic preferences, rescanned all the AU plugins about 15 times, deleting user AU cache before each re-scan. I've noticed that NuGen SEQ-2 is now an uber cpu hog. Likewise TDR Slick EQ GE. When I load a saved project the CPU and HD meters in the transport bar max out before I've even hit play. I've updated firmware on my external HD. I've tried running small projects that are backed up on my system drive, rather than from the external HD. Same issue. I've stared at the Activity Monitor but can't see anything. I've un-installed stuff like iStats, DropBox....and on and on. Driving me nuts. cheers
  10. Thanks for the suggestion. Turning off wifi made no difference.
  11. After 3 days of trying everything known to man I gave up and reinstalled Yosemite. I'm very pleased to report that step has solved my huge cpu load issues. Go figure ! cheers I spoke too soon. Logic worked fine for about 3 hours yesterday after the reinstall of Yosemite. I shut down last night. Boot up today, repair permissions....and now Logic has the same major cpu overload again !!! It seems to be caused by plugins, not audio drivers. Driving me insane.
  12. After 3 days of trying everything known to man I gave up and reinstalled Yosemite. I'm very pleased to report that step has solved my huge cpu load issues. Go figure ! cheers
  13. I'm experiencing a significant increase in CPU load. I've installed the Yosemite certified Apogee Duet 2 driver. I've selected inbuilt audio as an output and the problem still exists. Buffer at 1024. Everything fine as at 10.9.5 Logic 10.0.7 It seems that booting 9.1.8 in 32 bit mode is ok, no increase in cpu load I can detect in quick tests. Anyone have any suggestions please. Thanks EDIT: update, tried deleting plist preferences, reinstall Logic 10.0.7. Problem persists. Seems basically most/any third party plugins causes huge cpu hit. Ugly ;9
  14. Yes, further research points to a SL issue with a number of applications. The problem seems to be the remote ceasing to work with some "third party" applications after going to SL.
×
×
  • Create New...