Vienna Symphonic Library Forum
Forum Statistics

189,993 users have contributed to 42,697 threads and 256,908 posts.

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

  • VE Pro - only using RTAS plug on host - can I remove the AU component?

    Some plugins require the VST and/or AU to remain installed when using RTAS plugs.

    Does VE Pro require the presence of the AU if using RTAS for the host?

    The reason I ask: had a rare crash tonight...

    VE Pro 6853 all the way around. Host = protools 8.0.1cs2 (PPC)

    When installing VEP 6853 a few days ago, the installer crashed (auth error -- looks like Karel is aware of this and will fix the installer) -- however, the installer did not give me the option of only installing RTAS -- it was all or nothing. So although I only want the RTAS plug installed, the entire VE Pro collection was installed. No worries...

    Until my crash tonight -- and I saw the first 4 lines of the crash thread -- all kinds of references to audiounit.vienna, etc... forgot to save the crash. But thread 0 had a few entires that were all about VEPro audio unit. 

    WHAT is this about?

    SO my question (again) -- does VE Pro require the presence of the AU component even if only running RTAS? Why is this? Can someone from VSL please clarify?

    Thanks.

    J


  • last edited
    last edited

    I guess the answer is "no".

    I removed the AU component and then opened a protools session that accessed 2 instances of VE Pro (RTAS) and got this error:

    @Another User said:

    --------------------------------------------------------------------------------

    Missing or inactive plug-ins

    --------------------------------------------------------------------------------

    Track "VE Pro_xp" Insert 1 ("Vienna Ensemble Pro") has been made Inactive because a DAE error was encountered (error #-7054).

    Track "VE Pro_mbp" Insert 1 ("Vienna Ensemble Pro") has been made Inactive because a DAE error was encountered (error #-7054).

    Put the AU component back in place, and all is fine.

    Please add this to the documentation. Spectrasonics discusses this concept in their docs (Spectrasonics is dependent on the VST plugs, even for AU or RTAS). Ivory discusses it in their FAQ (need AU for RTAS to work). VE Pro docs should make a mention in the installation notes that the AU component must not be removed.

    Thx

    J


  • Why would you want to remove the AU component though, regardless of whether you use it or not?


  • I remove unused AU components else startup time for some apps takes too long. Such as Waveburner Pro or FinalCut Pro or Soundtrack Pro or Finale.

    It's really no big deal as long as it's documented. Just tell us to keep it installed, and we will.

    Had I not crashed tonight, I never would have seen this, as it was vepro that was reported as the thread 0 crash.

    Just document it so we don't have to discover this on our own. maybe add a line to the installer: "Vienna Ensemble Pro will install the RTAS and AU components that are required for the software to function" (or some other adequately geek speak that most will skip over). Maybe offer an option to only install the plugins for the host machines (without the server or standalone or directory manager, etc).

    Thx

    J


  • last edited
    last edited

    Karel,

    Crashed again (VEP 6853 on all machines) protools hosting.

    care to see a crashlog? 1st lines are:

    @Another User said:

    Thread 0 Crashed:

    0   libSystem.B.dylib             0xffff9268 __bigcopy + 296 (cpu_capabilities.h:242)

    1   ...audiounit.viennaensemblepro 0x55f98ebc NewMachOPlugIn + 36988

    2   ...audiounit.viennaensemblepro 0x561fa9c4 GetPluginFactory + 2235284

    3   ...audiounit.viennaensemblepro 0x55f8c084 CloseMachOPlugIn + 388

    4   ...audiounit.viennaensemblepro 0x55f90b94 NewMachOPlugIn + 3412


  • I am having regular crashes with the new build (and the one before) and I'm using the same version of PT as you Jeremy.

    I have sent the crash logs but heard nothing yet.

    The problem for me is that I have a couple of new situations in the setup so I can't point the finger at just one thing ALTHOUGH at a guess I would say it's the latest version of Kontakt.

    The new things I have in my system are:

    • Komplete 7 update which uses Kontakt version  4.1.1.3832

    Sometimes when I move a knob in Kontakt then VEPro will crash.

    Also knobs will just stop working in Kontakt (Mojo Horns were working yesterday but not today)

    • Pro Pemote  An application I use on my iPad via Bluetooth that is a Transport/Control surface. I note that when PT starts after a crash it will tell me that it couldn't load the ProRemote profile and I have to reinstall it. I've stopped using it (damn it was great) and I have not crashed today.............yet.

    After every PT Crash I must revert to a saved backup as the original PT file will load but crash VEPro when it begins to load Kontakt instruments.

    This scenario has been happening with every version of Kontakt and every version of VEPro. It's the same every time.

    PT crashes and that session will never load the VEPro session again. I must use a backup.

    I would say that this happens every day and sometimes twice.

    Not exactly a stable system any more.......but what software is to blame?

    When PT crashes it will always be during a save. Not every save and not every time. But this never happened before. I have included the PT crash log with the other logs I sent.

    Today I have not crashed so perhaps the culprit is Pro Remote.

    BUT Kontakt is still not showing some knobs on certain instruments and other menus have stopped working.

    NOTE the stand alone version of Kontakt is working perfectly. It's just the AU version inside VEPro that is flakey.

    I just keep working and try to forget about it.