Vienna Symphonic Library Forum
Forum Statistics

194,027 users have contributed to 42,906 threads and 257,900 posts.

In the past 24 hours, we have 4 new thread(s), 19 new post(s) and 105 new user(s).

  1. Home
  2. Sample Libraries
  3. Vienna Instruments Libraries
  4. VI crashes validation in Logic 7.2 but eventually passes....

  • VI crashes validation in Logic 7.2 but eventually passes....

    S
    S
    When Launching Logic 7.2, both Logic 7.2 and its AU Manager program crashed while trying to validate the VI plugin. (I've already upgraded to the latest available OSX version of the VI software)

    Since it appears VI was tested with Logic 7.1 and worked, this behavior may be peculiar to Logic 7.2... Am running dual 2.5GHz G5, 7GB RAM, OS 10.4.5.
  • S
    S
    Opening Logic's AU Manager in Logic's preferences (which automatically causes Logic to quit, it showed that Vienna Instruments had "crashed validation." I ran AU Manager (obviously, without Logic being open) and Vienna Instruments passed validation after several minutes. Logic reopened thereafter and I could play my first Vienna Instrument!
  • G
    G
    I seem to be having the exact same problem as Steve had, unfortunately not the same luck resolving it.Can't seem to get it to "passed validation"! [8o|]
  • D
    D
    Hi Guys,

    Do you know, is Logic 7.2 supposed to work with VI?

    Regards

    Dave Hage
  • J
    J
    My Vienna Instruments are working fine on Logic 7.2

    Julian
  • J
    J
    ....though I must admit AU validation was a pig - it crashed Logic and evntually the whole computer - it seemed to have something to do with synchrosoft. However on reboot and a second AU validation process that took 10 minutes (perhaps thats why people are thinking it's crashed) everything worked OK and subsequent launches were fine.

    Julian
  • S
    S
    Guy:

    Were you able to get Logic to open without it attempting to validate VI? If not, double-click the Logic Pro application icon, then hold down the Shift and Control keys until a dialog pops up or Logic is fully loaded. This known as AU Safe Mode. This will load only those Audio Units that have already passed the Audio Units Validation Tool. Once you've got Logic to open in this fashion, then go to the AU Manager which you can access as follows: Logic Pro Menu/Preferences/ Start AU Manager. Starting the AU Manager causes Logic itself to quit. Then find the Vienna Instruments on the list of Audio Units, check it and tell THE AU Manager to recheck it. At this point I would recommend a long walk around the block, a sip of good single malt or some other similarly diverting or anesthetizing activity - - since this going to take a while and will look like it has crashed once you see the spinning ball after the the progress bar as been going for a while. Do not panic, just keep diverting yourself. When you comeback, the AU Manager will, most likely announced that VI has passed validation.
  • G
    G
    Thanks Steve and Julian!

    Yes, we seem to have had the same struggle with this !@#$%%?&* but I also finally got through after about 10 minutes. A good thing a saw Steve's 1st post... otherwise you want to call 911!

    Hopefully VSL will warn people about this .

    Now I could proceed in doing somethIng that has never been attempted before: Writing a set of variations on "Twinkle, Twinkle Little Star".
  • J
    J
    Now I could proceed in doing somethIng that has never been attempted before: Writing a set of variations on "Twinkle, Twinkle Little Star".[/quote]

    No you need to wait for the mahogany veneered celeste (performance patch) coming in Vienna Instruments percussion. [:D]

    Julian
  • P
    P
    My experiences were identical to the above. I know that VI failed authorization at one point, because I got to Logic's AU Manager and confirmed it. On a second attempt, it probably was passing, but it took so long I assumed it had crashed.

    Another caution on long AU validation times: if you right click the Logic dock icon, it will tell you "Application not responding." As a diagnostic, that can be misleading because it's not a crash. It says that all the time during a normal boot.