Vienna Symphonic Library Forum
Forum Statistics

194,614 users have contributed to 42,925 threads and 257,982 posts.

In the past 24 hours, we have 3 new thread(s), 9 new post(s) and 121 new user(s).

  • Storing/reloading matrixes

    Sorry if this has been covered before but I can't seem to find anything about it in the manual. If I want to create and store a new patch (or just a Matrix), fine, I can save the matrix by clicking the disk icon and storing. But uhm... how do I load it back up? It doesn't seem to appear in the matrix list by itself... The default folder that VSL wants me to store matrixes in, can't be used. It is owned by "system" and read-only when I did an info on it!! I tried repairing permissions, it found no problems here, and the folder still belongs to "system" [*-)]

    EDIT: I deleted the folder and created it again myself, now it works. Seems like an issue with the installer...?

  • I'm not sure what computer you are using, but you do have a Director Manager application where all of your installed factory setups were originally organized. What appears in this window also appears on the right side of the VI console, which enables you to select the matrices or patches you want.

    In the Directory Manager, there is a "browse" button at the bottom which allows you to select your custom folder. Add that to the directory manager window. On some computers, it is necessary to shut down and reboot in order for this to take effect. Otherwise, your custom folder should appear among the choices the next time you open an instance of VI Cube.

    Hope that helps.

  • JWL thanks. Read my edit above for more info[:)] It works now. Mac Pro here btw.

  • last edited
    last edited

    @Simon Ravn said:

    EDIT: I deleted the folder and created it again myself, now it works. Seems like an issue with the installer...?


    Ah-- good job. Not sure why it goes in and out from time to time. The common workaround is to clear the Directory Manager and re-establish the folder paths just as you've done.

  • last edited
    last edited

    @Simon Ravn said:

    JWL thanks. Read my edit above for more info[:)] It works now. Mac Pro here btw.


    Simon-- you're quick!! [:P] You managed to edit your original post, fix the problem and post twice more in the time I could respond!

    Glad you're back in stride!

    Total thread time-- 8 minutes!! [H]

  • i'd like to add that the custom folder (location mostly set during the first installation) might have its permissions set to *read only*, so just setting permissions to *read and write* should fix such a problem too.
    christian

    and remember: only a CRAY can run an endless loop in just three seconds.
  • last edited
    last edited

    @cm said:

    i'd like to add that the custom folder (location mostly set during the first installation) might have its permissions set to *read only*, so just setting permissions to *read and write* should fix such a problem too.
    christian


    Thanks for the reminder, cm.

    I must take a moment to say thanks to you and your team for caring SO much about your users. You guys are really amazing not only for your product-- but for your genuine and enduring interest in the human beings who use your product.

  • last edited
    last edited

    @cm said:

    i'd like to add that the custom folder (location mostly set during the first installation) might have its permissions set to *read only*, so just setting permissions to *read and write* should fix such a problem too.
    christian


    Yes, it was set to "read only" but I couldn't change it, because owner was "system". Deleting it and creating it again worked though.