1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

10.0.2 Serious Bug

Discussion in 'Logic Pro X' started by LSchefman, Aug 21, 2013.

  1. LSchefman

    LSchefman Senior member

    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:
  3. Markdvc

    Markdvc Administrator Staff Member

    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

  4. HKC

    HKC Senior member

    Same thing here ......
    Post the issue to Apple, I have but the more the merrier
  5. LSchefman

    LSchefman Senior member

    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?
  6. Graeme Douglas

    Graeme Douglas New Member

    Addictive Drums runs 11-part multi-timbral kit into mono and stereo Aux channels without a hitch. Is it only nine orchestral-type Kontakt and Play instruments that are affected?
  7. LSchefman

    LSchefman Senior member

    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.
  8. HKC

    HKC Senior member

    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
  9. Colin Shapiro

    Colin Shapiro Senior member

    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:
  10. LSchefman

    LSchefman Senior member

    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.
  11. Markdvc

    Markdvc Administrator Staff Member

  12. LSchefman

    LSchefman Senior member

    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.
  13. dflo0816

    dflo0816 New Member

    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...

  14. LSchefman

    LSchefman Senior member

    Fixed now in 10.0.3.
  15. dflo0816

    dflo0816 New Member

    Thanks... downloaded and up and running.

Share This Page