Vienna Symphonic Library Forum
Forum Statistics

196,939 users have contributed to 43,042 threads and 258,497 posts.

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

  • Plugin issues after moving content

    Hi

    We recently moved our Vienna Instruments Cube from one system to a new Mac Pro. I have run the Vienna Instruments Directory Manager and made sure all content folders are shown correctly, which they are. If I run the standalone Vienna Instrument, it lists all matrices, patches etc. correctly, and I can load content without issue.

    However, the plugin version (Audio Unit under Logic) is not working correctly. When I instantiate it, it shows no content at all, and I can load nothing. Similarly, if I load a Logic song which contains pre-loaded Vienna Instrument instances, although they show th ecorrect matrix name, they load no content. In other words - standalone sees content fine, plugin sees no content.

    Any help in trying to resolve this would be hugely appreicated.

    Many thanks

    Jules

  • just a guess ... whereas the stand-alone has read the new locations the plugin used some cached information - have you already tried to simply reboot the machine?
    christian

    and remember: only a CRAY can run an endless loop in just three seconds.
  • Hi Jules,

    Please reboot. Then remove all content-folders from Directory Manager and reassign them as follows:

    Add all content folders of your Symphonic Cube again by Drag & Drop from your Finder. (Please don´t launch Vienna Instruments or Logic before doing so).

    Only by going through this "reassign - procedure" Directory Manager will memorize the correct paths and VI can locate its samples.

    Best,

  • Hi Chris, Maya - sorry not to reply sooner, I'm juggling work with configuring systems at the moment.

    I will try your suggestions ASAP and report back. I may not have rebooted, as I figured restarting Logic would have been sufficient.

    Regards

    Jules

  • Rebooting the system did not resolve the issue.

    Following Maya's content reassignment procedure also did not work - I have repeated it as described twice, with reboots between, and the AU version of the plugin still sees no content. In fact the standalone VI is now also not seeing any content.

    Would really appreciate your help resolving this.

    Many thanks

    Jules

  • A couple of thoughts come to mind regarding your situation.

    Have you tried launching the License Control Center application to make sure that it is reading your licenses on the key? If it is not, then the patches will not show within the Vienna Instrument interface.

    Also, make sure you have repaired your disk permissions and restarted your machine afterwards.

  • Hi Austin - thanks for your post

    Pretty sure it's not a license issue, as all my installed licenses appear correctly in the Vienna Instruments GUI when I fire it up, it's just the content that isn't listed. It's a weird one.

    I'll try repairing permissions though when I'm back in the studio tomorrow.

    Thanks again

    Jules

  • It worked!!!

    I uninstalled the VI and associated applications. Did a clean reinstall, relocated the content folders, rebooted, repaired permissions, rebooted, and everything now works!! [:D]

    Thanks for all the help and sorry to have been hogging forum bandwidth with this - no idea what the initial problem was.

    Jules

  • this is an issue which is still not 100% clear to me ... under certain conditions, mostly related to an update or an install, file permissions seem to be broken. this appears as files do not install, files do not extract, sometimes they don't even load (as consequence of inability to read preferences?) ... overall the behavior is very similar to damaged RAM

    this is something that really needs to be fixed in an upcoming OS X version, because it is leading users to work as root, which is basically not a good advice ...
    christian

    and remember: only a CRAY can run an endless loop in just three seconds.
  • Not sure I totally understand the implications of repairing file permissions (or how/why they get broken in the first place), but I agree that it's caused a whole load of frustration in this instance.

    Jules