ski 2011 wrote:
I've just sent in a bug report in which I complained that every feature of Logic X is missing.
[…]
Well, thanks for clarifying what your idea is all about. Still, if I saw the features I'm used to using now suddenly labeled as "advanced", or I had to hit some kind of button (even just one) to access the "advanced" stuff I'd immediately break out in hives. Big ugly ones, and I'd post pictures of them here and gross everyone out. So be careful what you wish for, because there will be consequences.
![]()
TequilaKez wrote: May 02, 2012
This happens to me all the time (like right now), even on small projects. Logic is apparently only using 66% CPU (out of %800) in activity meter. The performance meter in logic is barely showing 2 bars on cpu and nothing on HD. The rest of the system is fully responsive. Logic thinks it's fine, the interface is updating smoothly and it doesn't say 'not responding' in force quite menu.
All other applications are responding to mouse clicks/ keyboard almost instantaneously. Ableton is also unaffected.
Yes I'm using 9.1.7 logic with Lion 10.7.3 (logic but the problem started a few versions ago, not sure what version though). I can say it never happened with Snow Leopard but that could have been the logic version that was around at the time, who knows.
I found a workaround for the time being. If I alt-tab away from logic, then back in..... the change of window focus seems to reset the input buffer and it becomes responsive again.
It's definitely some kind of bug in logic, albeit one that only a few people are suffering so something relating to my system. I must stress the rest of my system is super fast, I have a very small number of apps installed, it's almost a fresh install. At the moment I'm working on a small project with 6 instances of NI Massive (latest update), 4 EXS24's and 4 audio tracks. But the problem has happened with sessions only containing logic plugins.
I've been doing some apps in cocoa lately and I've learned a little about about how OSX handles window focus and user input. It appears to be a problem with NSEvent reporting the mouse/keyboard activity to logic. Either something is preventing NSEvent from firing or Logic's delegate is not responding to the events.
The only thing that sets me apart from a clean barebones install is 2 UAD-2 cards, and 2 LCD monitors?
TequilaKez wrote:"We use a own develpoped Software Renderer.
I guess the problem is how the GUI is blitted to the System window.
I don't think it has to do with GUI redraw as my logic GUI remains fluid evn though logic doesn't respond to any input.
It is almost certainly to to with logics NSEvent handling.
https://developer.apple.com/library/mac ... rence.htmlAn NSEvent object, or simply an event, contains information about an input action such as a mouse click or a key down. The Application Kit associates each such user action with a window, reporting the event to the application that created the window. The NSEvent object contains pertinent information about each event, such as where the cursor was located or which character was typed. As the application receives events, it temporarily places them in a buffer called the event queue. When the application is ready to process an event, it takes one from the queue.
As you'd know if you're getting this problem, when logic finally does start responding again, all you previous mouse clicks and keystrokes get executed at once as logic logic plays catch-up with the event queue. Something is halting this process, stopping logic from 'taking one from the queue'. It's like it's waiting for some other process, perhaps part of the audio engine, to complete before getting back to handling the event queue.
TequilaKez wrote:… perhaps part of the "audio" engine, to complete before getting back to handling the event queue.

hypnotik wrote:thx fisherking
Can you try to use in your sessions a channel eq with analyzer ON + for instance a multimeter on a track ? And report us if you have this lagging issue ? (analyzer and multimeter must be feeded with sounds to make graphics activity)
Thanks for your input.


callingclouds wrote:Just thought I'd give an update regarding my situation. I thought that mouse setting had fixed it, but I'm just working on a track now and key commands aren't working again.
I also have Air Display installed so when it was mentioned here I thought it might be that, but you then said it wasn't that causing the problem, so who knows!
Very annoying situation, as I would like to keep Mountain Lion, but perhaps it is not gonna be possible.
What is most scary is that people still have this issue now after upgrading from Snow Leopard to Lion? I never had this problem with Lion, but then my Mac was preinstalled with Lion and didn't need upgrading. It seems like as soon as you upgrade, you are liable to get this issue on some machines.
I'm not currently experiencing issues with any other app whatsoever apart from Logic Pro 9.
I use an Edirol UA4FX sound card. Could this be the cause? What soundcards are other people using?
n6smith wrote:Chrishollis wrote:More people with this issue...
http://www.gearslutz.com/board/music-co ... litch.html
Thanks Chrishollis... and from comments in there, this issue also affects Cubase users so that kind of rules out Logic as being the cause.
Additional: I'm also seeing similar comments regarding ML and FCP on another forum... and I myself, had a similar issue this morning with ML on my test non music setup using Photoshop where the interface would become unresponsive for short periods of time... in a similar manner to those reporting issues with non responsiveness with Logic..so again, this would appear to rule out Logic as being at fault but rather some issue with OSX that is the root cause of these GUI issues...
Looking more and more like we need a ML fix..... to resolve these issues.
fisherking wrote:hypnotik wrote:thx fisherking
Can you try to use in your sessions a channel eq with analyzer ON + for instance a multimeter on a track ? And report us if you have this lagging issue ? (analyzer and multimeter must be feeded with sounds to make graphics activity)
Thanks for your input.
am around tonite to check things, but...i should point out, am running logic EXPRESS, so...i don't HAVE the multimeter. anything else i can check? here's a complex song with logic's eq, plus fabfilter's eq, and compression running...

fisherking wrote:ha, some of you who doubt me...LOL...
tonite, after a full day of fine-tuning mixes of 4 songs...i experienced an unresponsive logic.
went to adjust an eq, and...i moved the cursor...saw nothing happen....THEN the plugin showed a change.
then there was no visual showing the input signal (ie the analyzer)...then it came on.
went to close it...took a few seconds.
a rare event for me...but there it is...![]()
still, a whole day with no overload warnings, crashes. and the 32bit bridge (which, at least in lion, crashed several times a day), has not crashed ONCE today...a record.
nick1980webb wrote:not so good for me done a fresh reinstall of ML and all was well for a while and then....GUI stall
ski wrote:It all depends on what you're doing; if you're running a Logic production rig on a professional level, there's every reason not to update to Mountain Lion at this point. For many people it's proven to be a computer science experiment gone bad, and unfortunately so.
And now, a report from the trenches: from recent conversations with five of my colleagues (engineers, producers, and programmers) who all work at the highest levels in the music world, two are still on OS 9 systems, one is running Tiger, two are running SL. Thoughts of updating to Lion or ML are simply out of the question.
Food for Thought
May I recommend the proven stability of Snow Leopard and Logic 9.1.5? - - - - - - - - - - -
callingclouds wrote:..but I must stress I had absolutely no unresponsiveness issues in even my most complex of projects before I upgraded to Mountain Lion.
Return to Logic Studio Bugs & Workarounds
Users browsing this forum: No registered users and 1 guest