Logic Pro 10.0.2 Serious Bug

L

LSchefman

Logician
Very serious bug:

With a multitimbral instrument plugin, such as Kontakt or one of the EastWest plugins, making the plugin inactive on either the plugin GUI button or on the Inspector button crashes the program. This is repeatable and verifiable.

Note: This happened repeatedly creating a 9 part multitimbral instrument (East West instruments can be 9 part multitimbral). I just checked it with an 8 part instrument and it seems to be OK. May be related to the number of parts.

Doesn't happen with single stereo instrument plugins.

I would not install this update. I wish I hadn't.:brkwl:
 
Sort by date Sort by votes
LSchefman said:
I would not install this update. I wish I hadn't.:brkwl:
Click to expand...

It's been mentioned many times on the LUG, but worth repeating: Before installing any update, copy Logic to another location on your computer, rename it, after which you can move it back. That way, after updating, you can still easily access the previous version of Logic.

Alternatively, if you make regular backups, e.g. with Time Machine, you should be able to retrieve 10.0.1 from one of those.

kind regards

Mark
 
Upvote 0
Markdvc said:
It's been mentioned many times on the LUG, but worth repeating: Before installing any update, copy Logic to another location on your computer, rename it, after which you can move it back. That way, after updating, you can still easily access the previous version of Logic.
Click to expand...

Yup, that's certainly great advice!

I wound up creating new 8 channel presets for Play and Kontakt, and they work.

I wonder what the problem is with 9?
 
Upvote 0
So far, Graeme, nine part Kontakt and Play instruments crash Logic.

Also I've been having very frequent crashes on record commands. Something's very wrong here.
 
Upvote 0
Hmm on my system just loading an instance of Kontakt in multitimbral mode ie 8 stereo-8 mono and then bypassing the plugin crashes Logic every time. Obviously the workaround is not to bypass it but it definitely is a bug which I have addressed to Apple
 
Upvote 0
I'm not denying that this bug should be fixed, but there's a very simple workaround:
Just switch the track off using the new On/Off button.

From Logic help:
Turning off a track lets you silence a track while still hearing other tracks in the project assigned to the same channel strip.

When no other track is assigned to the same channel strip, turning off a track also saves processing power, because plug-ins on the channel strip are no longer processed. Turning a track off (or turning it back on) takes slightly longer than muting or unmuting the track, due to internal pre-processing.
Click to expand...
 
Upvote 0
Colin Shapiro said:
I'm not denying that this bug should be fixed, but there's a very simple workaround:
Just switch the track off using the new On/Off button.
Click to expand...

If only it was that simple.

For some reason when you do that, while you can now load the instance of the plugin, and the button works, in the sense that it turns the instrument off, however, MIDI stops working completely, not only in that track but in the entire DAW regardless of the button position.

Something is oddly off-kilter. I'm a patient person, they will fix it.

Trust me, there is something fundamentally wrong with 10.0.2. I was not having this problem with the earlier update.
 
Upvote 0
Markdvc said:
LSchefman said:
Trust me, there is something fundamentally wrong.
Click to expand...

It would be good if you could mention some system details, as we ask for here under #4:

http://www.logic-users-group.com/index.php?q=forum-rules-terms-of-use.html

If you haven't already done so, it would also make sense to send this to Apple, including details, crash logs etc.

http://www.apple.com/feedback/logic-pro.html

kind regards

Mark
Click to expand...

I have let Apple know.

Things seem to be erratic; I restarted the computer, and now the button works as expected as long as I don't turn the plugin off. Once I do that, it crashes. Sorry for not including system details:

Mac Pro, 8 core, 2008 model, OSX 10.8.4, 12 Gb RAM, Logic X 10.0.2. Many plugin suites, and am checking them one at a time.
 
Upvote 0
Logic 10.0.2 crashes are real

Yep... Me too.

Made the mistake of just automatically doing the update and now the session that I had to finish this weekend, wont' even open because of this bug.

I also tried the other suggestion listed here, "turning off the effected tracks" and to no avail. My session still will won't open. So I have 2 questions here...

Is anyone else having this problem that has found a workaround?
And is there a way to go backwards to 10.0.01 until they fix this madness...

Aaargh:brkwl:
 
Upvote 0
Back
Top