Can anybody explain what's going on here? Logic 8/Audio Unit Manager, suddenly decided to not validate anymore "Vienna Instruments", I have work on a daily basis, this is really annoying!
-
Audio Unit Manager suddenly won't validate VI! Problem solved!
-
This is an emergency, can anybody PLEASE say something? I've tried checking the box to force validation in AU manager, same results, even with the update 8.01 VALIDATING AUDIO UNIT: pass TESTING OPEN TIME: COLD: Time to open Audio Unit: 13.530 ms WARM: Time to open Audio Unit: 0.135 ms FIRST TIME: FATAL ERROR: Initialize: result: -1 validation result: couldn't be opened Also from time to time during this nightmare Syncrosoft License Control won't work. I've reinstalled VI, installer, syncrosoft, changed de light bulb of my desk lamp etc... so I don't know what comes before the egg or the chicken, or is my computer fucked up!
-
Hi Guy,
a "-1" error message mostly points at some kind of driver conflict.
What happens if the Syncrosoft LCC "doesn´t work"? It doesn´t start?
Does Vienna Ensemble work? Do both VI and VE work in standalone mode?
Did you install anything, change anything in your setup before this happened?
Thanks for the additional info.
Best,
Paul
Edit: Which OS?
Paul Kopf Head of Product Marketing, Social Media and Support -
I don't use or own Logic and not quite sure of (the extent of) your problem, but in case this is of any help in DP a similar (?) problem can be solved by trashing the audio unit info cache thus forcing re-examination of all AUs next start up.....
..... might be worth a shot....
good luck!
-
I'd follow the advice given by others but I'd also recommend that If you do not have a copy of Alsoft's DiskWarrior, you should consider obtaining one and using it to rebuild the directory of your startup disk. Using DiskWarrior to rebuild the directory of my startup disk has, countless times, fixed otherwise inexplicable and unfixable problems for me. For example, when I updated Altiverb from version 5 to version 6, Logic issued a message that it could not find Altiverb 5 -- it apparently could not "see" version 6 and would not validate it. After rebuilding the directory with DiskWarrior the problem disappeared. Similarly, Ozone 3 demanded its serial number every time I opened it, although I had entered it correctly when I installed it. Again, after rebuilding the directory with DiskWarrior, this problem disappeared. These are but two of many, many such examples.
-
Ha! I just bought Disk Warrior, and then I read your email, I guess it was the right move at this stage, especially after the apple care people told me it could be anything! Funny, you pay them all that money to get help and you're told it could be anything! Wow, I could of figured that out.... So I'm in he process of rebuilding directories. PLEASE KEEP ME IN YOUR PRAYERS.@stevesong said:
I'd follow the advice given by others but I'd also recommend that If you do not have a copy of Alsoft's DiskWarrior, you should consider obtaining one and using it to rebuild the directory of your startup disk. Using DiskWarrior to rebuild the directory of my startup disk has, countless times, fixed otherwise inexplicable and unfixable problems for me. For example, when I updated Altiverb from version 5 to version 6, Logic issued a message that it could not find Altiverb 5 -- it apparently could not "see" version 6 and would not validate it. After rebuilding the directory with DiskWarrior the problem disappeared. Similarly, Ozone 3 demanded its serial number every time I opened it, although I had entered it correctly when I installed it. Again, after rebuilding the directory with DiskWarrior, this problem disappeared. These are but two of many, many such examples.
