Forum Jump
Have installed what I believe to be all the latest software - License control center, ViennaInstrumentsSoftwareOSX-1.12 and ViennaEnsembleSoftwareOSX-2.0-beta3
A quick check reveals that Ensemble starts up fine in standalone mode but when Logic comes to scan newly installed AU units the progress bar gets to the Vienna Ensemble and gets stuck (how long should it take to check it through?). During the period it is trying to scan, the Vienna Ensemble Service (It actually says Vienna Ensemble Server in the title bar) starts up and there is a brief showing of the UI. Logic doesn't even give up on the scan to states that Validation has failed.
I have removed the Ensemble component from my Components Library for now and Logic starts OK.
Dual PPC G5 4 gig RAM
OS is 10.4.10
Logic is 7.2.3
How can you tell I am running VI 1.12 as in LOGIC AU listing it is classed as 1.0 - Ah Found it: Open up the Component with control click/ show package contents and read the text in the Info.plist
|
|
|
|
|
|
please consider VI 1.12 and VE 2.0 beta are different plugins. have you already tried to validate manually(IIRC logic menu AU manager)
christian and remember: a CRAY is the only computer that runs an endless loop in just four hours ...
|
|
|
|
|
|
cm wrote:please consider VI 1.12 and VE 2.0 beta are different plugins. have you already tried to validate manually(IIRC logic menu AU manager) christian Perhaps I wrote badly but I am fully aware that VI 1.12 and VE 2.0 beta are different plugins. That is why I mention the removal of the VE plugin. I have now fixed it but if others have a similar problem consider the following. If Logic freezes at the point where it is checking VE it will never get to the stage where it will open. As I understand it, you cannot open LOGIC AU MANAGER other than from within logic and I couldn't get Logic to start with the VE component in the Library - catch 22. With the VE component removed from the library, Logic would start and when selecting AU MANAGER the AU MANAGER was aware that VE existed (before I removed it). With Logic started I dropped the VE component back into the library and then selected AU manager and manually asked it to rescan VE which was then validated in a couple of seconds. It can now be loaded into Logic
|
|
|
|
|
|
apologies - i've been not aware you already solved it ... i think is is a good description for other users running into a similar issue ...
i remember some AU validation issues also with VI, but hopefully this can be fixed in the release version of Vienna Ensemble.
christian and remember: a CRAY is the only computer that runs an endless loop in just four hours ...
|
|
|
|
|
|
cm wrote:apologies - i've been not aware you already solved it ... i think is is a good description for other users running into a similar issue ... i remember some AU validation issues also with VI, but hopefully this can be fixed in the release version of Vienna Ensemble. christian Actually it was only after you mentioned the Manual Scan that I tried what I mentioned in my previous post. It was just a guess that I could re-introduce the VE component to the Library with Logic Open before starting AU Manager.
|
|
|
|
|
|
This method doesnt work for me. Anyone else found a solution to this?
|
|
|
|
|
|
Had the same problems, removed the VE, and still trying to work with the ViennaInstruments.component,
but now either Logic 8 or Logic 7.2.3 freeze sometimes when launching an existing song with some error messages from the vienna.
Should I reinstall the VIenna Instruments plug ?``Thanks
|
|
|
|
|
|
You cannot post new threads in this forum.
You cannot reply to threads in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.