best service ENGINE plugin window blocks input in Logic 9

Question

Level 1

0 points

best service ENGINE plugin window blocks input in Logic 9

I'am using Logic Pro 9 (up-to-date version) on my MacBook Pro (Mac OS X 10.8.2) with best service ENGINE sample player as AU plugin. Software is running all in 64 bit mode.

I experience a blocked user interface every time I open the ENGINE plugin window in Logic. If I keep clicking the close button very hard it happens after some time that the plugin window ist getting closed again. ENGINE behaves like ignoring all clicks if open in Logic, "saving" them for later execution. It totally blocks all input. If you managed to get the window closed Logic is running again without troubles. While not accepting my inputs the ENGINE sample player plays sounds normally.

The ENGINE software works well in standalone mode if not called as AU Plugin in Logic. All others AU plugins also work without problems. I'm also using Automap from Novation. But the AU plugin version of ENGINE without Automap support doesnt work too.

Any idea regarding this issue? Many thanks in advance!

MacBook Pro with Retina display, OS X Mountain Lion (10.8.2)

Posted on Dec 2, 2012 11:52 AM

Reply

Answer 1

Pancenter

Level 6

14,644 points

Dec 2, 2012 12:00 PM in response to talex

Well known issue, it's not just with that particular plugin, take a look here.

https://discussions.apple.com/thread/4142085?answerId=20443081022#20443081022

Reply

Answer 2

talex Author

Level 1

0 points

Dec 2, 2012 12:11 PM in response to Pancenter

Hmm, for me it's just an issue with ENGINE - all other plugins and Logic itself is working fine, no hangs or blocking inputs. It's just ENGINE. Is it possible to run just 1 single plugin in 32 Bit in a 64 Bit Logic? Maybe it's a problem with the 64 Bit binaries.

Reply

Answer 3

Pancenter

Level 6

14,644 points

Dec 2, 2012 4:48 PM in response to talex

talex wrote:

Hmm, for me it's just an issue with ENGINE - all other plugins and Logic itself is working fine, no hangs or blocking inputs. It's just ENGINE. Is it possible to run just 1 single plugin in 32 Bit in a 64 Bit Logic? Maybe it's a problem with the 64 Bit binaries.

I was just noting that the behavior you describe is consistent with a known conflict of Logic in combination with Mountain Lion.

I'm sure if you were running Snow Leopard you would not see the blocked input.

Reply

Answer 4

talex Author

Level 1

0 points

Dec 3, 2012 7:14 AM in response to Pancenter

From my point of view it's not sure if it is a Logic / Mountain Lion problem - the interface bug occurs only when using best service ENGINE in Logic. That means the problem can be hunted down to the ENGINE AU plugin. Therefore it's nor a general Logic bug. I think it must be something with 64 Bit and the ENGINE software.

So what I'am seaching for is any users that experienced similar troubles with Logic and the ENGINE plugin or other AU plugins and teh question is if they found a solution for this issue.

By the way regarding this other discussion: I can start/stop playback in Logic via MIDI MMC while the ENGINE window is open and blocking input. So the Logic engine works fine. It's really only the ENGINE plugin windows that is blocked.

Reply

Answer 5

Pancenter

Level 6

14,644 points

Dec 3, 2012 8:40 AM in response to talex

talex wrote:

By the way regarding this other discussion: I can start/stop playback in Logic via MIDI MMC while the ENGINE window is open and blocking input. So the Logic engine works fine. It's really only the ENGINE plugin windows that is blocked.

I know it's a lot to read but if you had read the thread and the several other similar threads you would find that your above statement coincides perfectly with the Logic/ML hang. It's more of a ML/Graphics related bug however the interaction with Logic and some graphics intensive plugins is also part of the problem. It's been discussed at great length here, in fact the last Logic update specifically targeted this behavior, while it helped it didn't eradicate it.

Good luck on finding your answer.

Reply

Answer 6

SiavashR

Level 1

0 points

Jan 28, 2013 10:54 AM in response to Pancenter

I am having the exact problem. The click function doesn't work within Engine. it works with everything else. I just reinstalled it and the same issue is going on. Did u find a solution ?

Reply

Answer 7

SiavashR

Level 1

0 points

Jan 28, 2013 10:55 AM in response to SiavashR

and i'm on Version 10.6.8 so it has nothing to do with OSX

Reply

Answer 8

Jan 28, 2013 1:52 PM in response to SiavashR

SiavashR wrote:

and i'm on Version 10.6.8 so it has nothing to do with OSX

Actually it is.... It's down to a part of OS X/CoreAudio/Prokit/Core Apps that either hasn't updated correctly or is missing an update that should have been performed a while ago... or has installed something that is in conflict with something else.. This is why it only affects a group of people rather than everyone... irrespective of their OS version... as it has been reported as occuring in SL, Lion and ML... though the vast majority of users have noted this only happening in Lion or ML...

For example, I have never been able to reproduce this issue on any of my systems here... ranging from SL to ML... but I have seen it occur on an identical Mac/OS X/Logic Version to one I own.. Once I cloned my computer and installed the clone on my client's identical iMac, the issue vanished for him... Reinstalled OS X and Logic from scratch on his iMac and the issue returned... so there is something that has been installed,updated correctly or not installed for that matter...on my computer that either prevents or fixes the issue.

In the meantime we are awaitng a fix from Apple... to fully cure this issue for all OS X users... one and for all hopefully!

Reply