Vienna Symphonic Library Forum
Forum Statistics

196,053 users have contributed to 43,014 threads and 258,388 posts.

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

  1. Home
  2. Sample Libraries
  3. Vienna Instruments Libraries
  4. VI Pro - File Browser / Custom Preset (VSL, do we have a problem?)

  • VI Pro - File Browser / Custom Preset (VSL, do we have a problem?)

    R
    R

    It looks like the VI Pro doesn't display the Custom Folder with the custom Preset and Matrix files that were created in the original VI. I can't find anything in the manual or in the videos that explains the custom file handling. Did I overlooked it?

    Here is what I observe:

    • The save command will not open a standard File Selector Dialog window!
    • You can't select your own location for the Custom files. This was possible in VI through the Directory Manager app.
    • A new custom Preset and Matrix is saved in the "user/Shared Folder/VSL Custom Data/" directory
    • Nested Folder will not be displayed. Major limitation.
    • Custom files in VI Pro have a new extension (vipreset" and "vimatrix") instead of the old extension fxp (no mention of that significant change anywhere?)
    • VI Pro can't open original VI custom files. This would be a major problem !!!

    This is the first major roadblock I' hitting so far in VI Pro after the first day of positive experience.
  • D
    D
    last edited
    last edited

    I can answer a few of your points:

    The fixed location of the Custom Files has been introduced because so many people were having Permissions problems. This is supposed to fix that issue.

    VI Pro should open legacy Presets. If yours can't be opened, send them to support@vsl.co.at so that they can take a look at them.

    DG
  • N
    N

    All I can say is that I have no problems under OSX.6.4 and Logic 9.1.1. Everything works fine, every controller is routable and the learn-function works excellent. The custom presets are loading as expected. Everything what I did was first to load the latest e-licenser update, installing VEPro6776 and then installing VIPro6776. After that the directory manager of VIPro had no data inside, so I was browsing for everything, set the custom- and stretch-folder and since then everything works fine. 
  • R
    R

    OK, I worked a little bit more today with the browser and I have to say: This looks bad!

    It seems that you guys went a step back in computer evolution. I thought the whole "Save" and "Load" files has been figured out, then why are you trying to reinvent the wheel by coming up with a "square" shape?

    1) Force the user to place user files in one pre-defined location. This is so wrong for so many reasons. Permission issues, sorry I missed that flood of complaints. These are not Library files that belong in a specific location, demanded/suggested by the OS. These are user files and and the user has to have the choice to put them where ever he wants. Locally, second drive, external drive, network drive. THink one step further about backups. The user plans his backup/archive scheme with the smart location of various files. If the user doesn't have the choice to organize his files in a compact way, this makes the backup procedure more complex in order to make sure to look in yet another location for valuable data.

    2) No nested folders? What's up with that?

    3) When you want to save a file into an existing folder, you have to type its name in the first field. One step away from the command line interface.

    4) You can expand only one (!!!) folder at a time in the directory tree?

    5) OSX uses triangles, WIndow uses dotted lines to display exended directories. Why do you have to come up with a new way with this vertical lines?

    6) If you create Folders or move Preset Files in the "VSL Custom Data" directory directly in the Finder, then you won't see them in the Plugin browser until you do a save. Then the browser data will be refreshed.

    I'm really baffled how this crippled browser interface made it to the final version or even passed the beta testers. No complains from the users, strange? This is a big step backwards from the previous version and I don't care if the new browser has a Search feature. 

    Any chance that the VSL team can address these issues any time soon or explain what the reasong was behind such a major step back?
  • J
    J
    last edited
    last edited

    @Edgar Rothermich said:

    then why are you trying to reinvent the wheel by coming up with a "square" shape?

    Because that's what VSL does.

    They will attempt to reinvent the wheel at every opportunity.

    There is no use to argue. As my kids taught me from preschool, "you get what you get and you don't get upset".

    If the VSL products weren't so freaking brilliant, they wouldn't last a moment in the real world. But as long as they continue to make stuff that is simply better than anything and everything else, we will have to live with the "we can invent --- a wheel!" mentality. I really do love the products, but they need to "get out a bit".

    As for the paths for presets, yeah, already 2 threads on that.... welcome to the club.