1. IMPORTANT:
    We launched a new online community and this space is now closed. This community will be available as a read-only resources until further notice.
    JOIN US HERE

AU killing Logic

Discussion in 'ABSYNTH' started by popsicko@hotmail.com, Mar 13, 2004.

Thread Status:
Not open for further replies.
  1. popsicko@hotmail.com

    popsicko@hotmail.com NI Product Owner

    Messages:
    164
    I updated to the latest version of AB2 and now it totally messes up my Logic Autoload file. When I open Logic, it won't bring up my Autoload file. When I open it manually I can't load any Audio Instruments into a track. It just gives me options for Audio out only. When I remove AB2 from the components folder all is well. This wouldn't be a problem if AB2 was a full blown DAW, but it's not.
    Any clues?
    Brad
     
  2. pazzap

    pazzap Forum Member

    Messages:
    32
    people are saying the same problem with kontakt au, which is really scaring me from buying the NI komplete. all i read are problems:(

    does anyone know if pro 53 has these problems?
     
  3. hyerstay

    hyerstay NI Product Owner

    Messages:
    143
    First of all, what are you specs? System version, ram, Logic version, Absynth version, etc.

    If ever you can't choose audio instruments, it usually means that your core audio driver is not loading. (With Absynth in), go and check Logic:preferences:Audio Hardware & Driver. Make sure your driver is chosen and Core Audio is on.

    If you tell me more, I can help more. I have all of my NI apps/plugs running fine in my config (see my sig).

    BTW, I have not heard of this problem with either Absynth or Kontakt before.

    Pazzap, all you read are problems because a lot people here whine and complain instead of trying to get their problems fixed. For those of us that have things working, we must grit our teeth to enter these forums and try to help. I'll probably get flamed for this, but most people's problems here are their own responsibility. I'm not talking about missing or broken features, but whether something runs or not.

    (For OS X Logic users), you really need to have the newest OS X revision, the newest NI update and the newest version of Logic. Compatibility bugs get fixed in those minor releases and and they make a big difference.

    For example, people still running Logic 5.5 will have problems with various AUs. Switch to 5.5.1 and they go away. Staying current with this stuff can save a lot of headaches. That, and good housekeeping of your computer. (Start with buying TechTool Pro 4 and DiskWarrior.)

    Anyway, I sympathize that it can be hard sometimes to get everything working in any complex setup, and I'm happy to help. Do not give up.

    Cheers
     
  4. popsicko@hotmail.com

    popsicko@hotmail.com NI Product Owner

    Messages:
    164
    I forgot that I had the same problem with Kontakt. I think 1.5.2 fixed it, but have not used it much yet. As for my set up, here goes.

    Powerbook G4 867
    640mb ram
    M Audio duo (latest drivers)
    Oxygen 8 (latest drivers)
    Logic 6.3.3
    R4.04
    AB2.04
    Kontakt 1.5.2
    Vokator1.04
    fm7
    pro53

    I'm not a newbie, I've been at this for a quite a while, and I consider myself to be more familiar with Mac's than NI. heh heh! Everything else works as good as can be expected. Absynth2, Fm7, and Pro53 were the most stable things that NI ever sent my way. I recently updated AB2 and thats when the trouble started. Logic will start with my Autoload file as long as AB2 is not in the component folder. Anyway, I hope there is a simple fix for this. I don't know what it would be. Reinstalling does not help. I think it's just a problem with this update. I'd appreciate the help if you know the answers. Not everybody comes to complain. Though NI is becoming an increasingly easy target for criticism. If the R4 update turns out to be as good as we are hearing, they'll get my cash next time.
    Nite
    Brad
     
  5. hyerstay

    hyerstay NI Product Owner

    Messages:
    143
    ...

    Thanks for giving more info. What version of OS X are you running?

    Ok, the first thing to try would be to remove your Autoload file and start Logic. If that works, you may have to go and rebuild your Autoload. Did you have Absynth plugged into a track in your Autoload? It may be trying to get to the old version or something.

    If you really don't want to rebuild your Autoload, you could try turning off your audio device and booting Logic with Core Audio off or set to internal, so you can remove Absynth from active tracks. I would also double-check that the correct AU version is actually there.

    Further more, go and look in Library/Application Support/Native Instruments and see if anything Absyth-related is there. I don't think there should be with this version (mine has only Kontakt DFD stuff). You could also poke around in Library/CFMSupport and see if there is any Absynth stuff there (shouldn't be, just more Kontakt DFD stuff). One more place to look is ~/Library/Preferences and ~/Library/Preferences/Absynth. Make sure the Absynth Edit, Libraries and Samples aliases are valid.

    Oh, here is a bonus tip: By default the Finder search does not search in System or Library, so when searching, switch to Search in Specific places and add System and Library. They should stay in that list until you remove them (and why would you?). This should help for all future under-the-hood work.

    Feel free to email me the crash log for Logic (in ~/Library/Logs/CrashReporter/), at jason at hyerstay dot com.

    Check back when you get a chance. Good luck.
     
Thread Status:
Not open for further replies.