Seemed a little better at first for me at least, but sadly the GUI lag soon returned, this is a game changer for me Apple should have tested this before the release of ML - Pro Tools is fully ML ready and supported so why not Apples own ''flagship' DAW? Can't help but think that Apple have taken their eye off the ball as regards Logic (far more interested in selling iphones). Logic is simply unuseable in a professional context and I have just ordered a copy of Pro Tools 10. Enough is Enough!
If anything the lag seems to be getting worse; no longer need to have something graphically intensive working for it to happen. Completely ruined a session today with a singer in the voice booth looking at me saying ***?? C'mon Apple, for some of us our livelihood depends on your program... Please fix this.
I just bought a new macbook for the sole purpose of using Logic 9. This better freaking be fixed soon!
In general, it's not a good idea to buy a computer which needs a new OS before that OS has been out for a couple of months if you need to use it with a software which hasn't been updated sinc the OS was released. Having said that, I'm sure there will be a fix in the next Logic subrelease.
Logic is simply unuseable in a professional context and I have just ordered a copy of Pro Tools 10. Enough is Enough!
Maybe you should check the main Pro Tools forum before you confirm that order. It's full of people complaining about issues with Pro Tools 10. I have gotten rid of my Pro Tools rig, and am not looking back. I use Logic exlusively for professional work, and many I know has converted from PTHD to Logic and are really happy about it. Until a new Logic release is out, you either need to install Snow Leopard on another drive and boot from that drive, or use som of the known workarounds for the lag issue. And while we're talking about Pro Tools: I know from exerience that PT users historically are know to wait - and have to wait - weeks and months before they start using their PT rig on a new OS.
I hope Pro Tools works out for you ...
In my case, I was able to set up a double boot.
So now I use Snow Leopard for Logic and Mountain Lion for the rest.
I think it's a good idea to have at least two DAWs that we're proficient at.
I own Reason 6.5 but it still has no VST-AU plugin ability.
It's too bad ... their emulation of the SSL Mixer is very cool.
I looked at the Harrison Mix bus ... but it's got no midi.
I download demos for Ableton and PreSonus.
I haven't warmed up to Abelton Live, it's a little strange.
But PreSonus Studio one is making me smile.
I pushed it as hard as I could and the user interface never wavered.
It just feels like "fresh new code"
Makes me wonder if Logic X will have the same sharp and snappy response.
If it doesn't ... I'll be migrating. It's seems like Apple will provide me with nice gadgets
but I may have to look elsewhere for professional tools ... such is life ...
I am not getting into the PT vs Logic debate. All I am saying is PT 10.3 at least for me hasn't crashed once and is very smooth and fluid to interact with. My main point is how can it be that Avid ( historically known for being very slow to release updates) has PT software that is now fully supported on ML. Yet Apple release an OS on which there own software clearly has some problems. I am growing to like PT but I still love Logic . . . now where are those Snow Leopard Disks?
My main point is how can it be that Avid ( historically known for being very slow to release updates) has PT software that is now fully supported on ML. Yet Apple release an OS on which there own software clearly has some problems.
OK... (entering pure spculation mode here): Logic is way more CPU efficient than other DAWs, and also does things other DAWs (and other Apple apps) don't do. For instance, if you have two monitors, and moves one window over to monitor #2, it automatically adjusts it's size to fit the other monitor.
Logic has been developed for 20 years, of which 10 was before Apple acquired Emagic. My guess, partially based on things I've heard in the past, is that Logic originally broke some "rules" re. how things should be done - in order to deliver stuff others didn't deliver. And the road from Atari to 68k>PPC>Intel Mac may also have had it's bumps with various levels of tweaking the code.
So - it doesn't surprise me of Logic has problems with a new version of OSX: Maybe the new OS version reveals some black holes in the code. But - having said that, ideally, these issues should of course have been found by people who betatested Mountain Lion.
Maybe not enough of the ML testers are using Logic. And maybe the pro audio team is too busy working on something new and exciting to spend a lot of time with finding bugs in Logic, which only appear for some people, and only in some situations for these people. Maybe Apple simply should hire more pro audio developers and pro audio QA staff. Or wait, that's what they have done not long ago, according to various ads I've seen.... :-)
[/pure speculation mode]
I'm having the exact same problem. Just bought a brand new Mac Pro 12-core 2.44ghz running 10.8.1 and Logic 9.1.7. HORRIBLE behavior if I try to edit an effect or open one during playback. How excruciatingly frustrating! Logic and os X are both Apple and should be running in perfect harmony!
I would downgrade the os to Snow Leopard, which I loved, but my Mac Pro apparently doesn't have firmware support. So... ugh.
Is everyone calling Apple to register this complaint? I working at a software company, and I know that the more people that register a complaint over a bug, the more high priority that bug becomes.
So sadly, talking on here doesn't fix anything-- please call Apple and register the compaint!!! please!!!
Today I had a (very very frustrating) conversation with somebody in the highest level of tech support for Logic. Unfortunately he had never heard of this issue.
He explained that Apple has a hierarchy for bug fixes. They prioritize the ones that effect the most users. He then asked me to reinstall my entire computer again to prove to him that this is an Apple issue.
Of course I responded that I'd already done the tests to prove that it was Apple-related. He stated that that's really all they could tell me. I was pretty flustered but agreed to do what he asked.
Half an hour later I got an email from him and I'll copy/paste it here:
"I spoke with our site engineer and he stated what you already know. Apple is aware of the issue.
There is no resolution at this time. Please do not perform the troubleshooting steps we discussed.
The issue appears to be graphics related. Any GUI that has animation and/or motion. The workaround
is to not use the analyzer. I know this is not what you want to hear.
If you have any questions, please don't hesitate to reach out."
Considering what he told me about the hierarchical nature of bug fixes, I wrote back the following:
"Basically, I really just want to know that this bug is high in the "hierarchy" of bugs that you mentioned, and that a fix is in the works. Can you please confirm?
I can confirm Apple is investigating the issue.
got DEFINITIVE answers from a high-up Apple AR support. He said it is not a Logic issue, but a Lion and Mountain Lion Core Audio issue, and mentioned that the engineers are "working on it day and night to fix it."
He also listed two possible fixes, while the team is working on a fix for Mountain Lion. Here's what he wrote:
"1) Downgrade to the Snow Leopard OS until this is fixed. I know this is a complete annoyance to hear, but truthfully a lot of people are doing it and it's solving the problem for them.
2) Do a clean install of iLife. This is also solving the problem for a lot of people, and is quite a bit less of a pain since most of the professional Logic audio community doesn't use Garageband in the first place. For some reason, a clean install of iLife (and really, Garageband) is doing the trick. There is some sort of conflict happening between Garageband and the Lion/MT Lion OS that is causing updated iLife files to not load properly. A fresh/clean install of iLife (essentially, back to the older version found in the Lion installer) is doing the trick in most cases. If he chooses this route, please make sure to tell him NOT to update iLife to it's most current version release as this sis where things seem to go wrong. The original download version from the Lion installer is the one he'll want to use, if possible.
One note on this- Some users are finding it difficult to extract the iLife installer data from the Lion installer itself since Lion was our first App Store downloadable OS. But, if he goes to the installer (might have to redownload from App Store) and right-clicks on the installer file, select 'Show Package Contents', and the installer data for iLife can be found inside."
Hopefully that helps, at least in the meantime. I unfortunately can't install Snow Leopard on my 2012, Mac Pro but it's good to know there's one more thing I can try. Anyone know where I can find the Lion installer?"
I have tried to follow these directions about installing just iLife from the Lion installer, but can't find the file to do so. I right click on the installer, choose "show package contents" but don't see anything in there that indicates being the iLife installer... Can anyone offer some help?
iLife isn't part of the OS, it hasn't been for a few years. To reinstall an earlier version you probably need the physical disks or you would have had to save the old version from the app store (which might not even work if it installs system files).
It may work, but a lot of users aren't going to have the old installer available to try it out. Do you have specific version numbers of Garageband that are the bad one and the good older one?