Vienna Symphonic Library Forum
Forum Statistics

194,774 users have contributed to 42,933 threads and 258,005 posts.

In the past 24 hours, we have 5 new thread(s), 17 new post(s) and 112 new user(s).

  • BUG: VE Pro 7043 Mac will hang if you move your Kontakt or Spectrasonics samples directory...

    VE Pro 7043 32-bit server, Mac OS 10.6.4

    Repeatable bug:

    Change the hard drive or path to your sample library for Kontakt or Spectrasonics (possibly others too, but can verify these). the way you are supposed to tell Spectrasonics plugs where the new "steam" folder is to

    1) delete the alias to STEAM in the user folder

    2) launch the plug in your VI host, and the program will ask where the STEAM folder is... 

    The BUG in VE Pro is that you can not select the STEAM folder. Dialog box from hell (can't cancel or select anything). Force quit is the only way out.

    Workaround, use a different host, such as Logic.

    For Kontakt, you are supposed to be able to manually tell K4 where the sample folder is, but again, VE Pro hangs (dialog box from hell, can't cancel, or confirm -- only force quit)

    Workaround -- launch K4 standalone, tell K4 where the library now lives, go back to VE Pro, all is fine.

    BASICALLY, VE Pro does not play nice with the VI plugin's dialog boxes for "find the path to the new library location"

    Am I the first person to increase their sample drive to 2TB? Wonder why others have not discussed this... :-(


  • Thanks for the report. I'll investigate this.


  • Hi Karel,

    Thanks for staying on top of everything!

    J


  • Ok, this is definitely a bug. A workaround however is to use the application menu at the top rather than the rightclick popup menu's. I'll try to get this sorted asap.


  • Thanks Karel! Working a little late tonight? 

    FYI, I have never used the "application menu" to add a VI -- only right-click or the icon tray. I typically only go to the menu for channel sets and presets. But it's great to have more than one way to do something.

    This "bug" will only show up when people migrate to new or larger drives for library storage, and only if they don't use standalones and only if they use VE Pro as their primary VI host. So I can understand if this is not a priority to fix, since there is clearly a workaround using the standalones and alternate host. Thanks for keeping up with all of us.

    Best,

    J