Vienna Symphonic Library Forum
Forum Statistics

200,865 users have contributed to 43,214 threads and 259,138 posts.

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

  1. Home
  2. Sample Libraries
  3. Vienna Instruments Libraries (legacy)
  4. Load preset on startup yes or no

  • Load preset on startup yes or no

    P
    P
    Hi,

    The changelog for v1.11 for the Mac lists the following improvement:

    "Support for startup.fxp to load preset on startup"

    1. Is this accurate?

    2. Can one specify a preset to load on startup for the Standalone, the plug-in or both? (Note: I realize that the plug-in automatically loads whatever preset was loaded the last time the host program's file was saved - that's not what I mean.)

    3. How does one specify a preset to load on startup?

    Thanks,
    Peter
  • cmC
    VSL Team
    cmC
    create a preset, save it as *startup* (without asterisks) - you might see the .fxp extension or not depending on your system settings
    christian
    and remember: only a CRAY can run an endless loop in just three seconds.
  • P
    P
    Thanks - tried it and it works.

    What I was hoping was that I could specify a different startup preset for each of my standalone instances. Sadly (and logically), since all the standalones share the same VI Custom Data folder, that appears not to be possible (the first standalone loads the startup preset, and additional standalones open empty).

    Or can anyone think of a workaround? Is it possible that you can have multiple custom data folders, each linked to a different standalone?

    (For those who haven't followed the relevant threads, having multiple standalone instances of VI is an effective way of getting around the 3GB RAM limit per host program).

    PL
  • D
    D
    last edited
    last edited

    @plurye said:

    Thanks - tried it and it works.

    What I was hoping was that I could specify a different startup preset for each of my standalone instances. Sadly (and logically), since all the standalones share the same VI Custom Data folder, that appears not to be possible (the first standalone loads the startup preset, and additional standalones open empty).

    Or can anyone think of a workaround? Is it possible that you can have multiple custom data folders, each linked to a different standalone?

    (For those who haven't followed the relevant threads, having multiple standalone instances of VI is an effective way of getting around the 3GB RAM limit per host program).

    PL

    I've tried a few things and it makes no difference, so I think that we are stuck with only one preset at a time, until VSL implements some of my (or others) previous suggestions.

    DG
  • P
    P
    DG -

    Just curious, what were your suggestions re default presets?

    PL
  • D
    D
    last edited
    last edited

    @plurye said:

    DG -

    Just curious, what were your suggestions re default presets?

    PL

    A couple are [URL=http://community.vsl.co.at/viewtopic.php?t=11052&iframe=true]here.[/URL]

    DG