Vienna Symphonic Library Forum
Forum Statistics

194,156 users have contributed to 42,912 threads and 257,926 posts.

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

  • OK, so here's a little more experimentation on my computer. The workaround does not work perfectly the very first time I boot up the computer (first load time: 4'45", all 10 collections licensed BTW). However, if I put the computer to sleep instead of shutting it down, the workaround in the first post of this thread works every single time for me (first load time: <5").

    I'm not claiming this is "the" solution to the problem--but worth exploring...

  • Yes but a boot from sleep mode is not an initial boot. Once Vienna Instruments has been initially booted (in either Logic, Standalone. or whatever you use) it's ready to go pretty much straight away.

    The current big issue is waiting to get VI,s up and running from a cold start.

    Julian

  • Agreed, but in case it wasn't clear I'm actually talking about a "lukewarm" boot, by which I mean: quit Logic Pro/VI entirely before you go to sleep, wake from sleep, start Logic Pro/VI. So while the computer boot is not "cold," Logic Pro gets a fresh start.

    In any case, thanks for your comments. We're probably all in agreement that it would be nice to fix this issue.

  • last edited
    last edited

    @Another User said:

    I think everyone (ncluding VSL themselves) are encountering 7 minute boot times in OSX for the full 10 colections of the Symphonic Cube.


    Well, I'm encountering 1:40 in OS X. That's with the first five Collections, so I suppose it could be one of the second five that's causing the problem. But it's consistent 1:40 every time.

  • last edited
    last edited

    @hkieffel said:

    Agreed, but in case it wasn't clear I'm actually talking about a "lukewarm" boot, by which I mean: quit Logic Pro/VI entirely before you go to sleep, wake from sleep, start Logic Pro/VI. So while the computer boot is not "cold," Logic Pro gets a fresh start.

    In any case, thanks for your comments. We're probably all in agreement that it would be nice to fix this issue.


    Once the VSL server daemon has been woken from it's deep deep sleep (initial boot) it doesn't matter which app is active the Vienna Instuments will start pretty much straight away. So for example if you turn your computer on in the morning open the Vienna standalone app (takes about 7 minutes with the Symphonic Cube) VI should launch 3-5 seconds after selecting it.

    So the cold boot times for Vienna Instruments (particularly in OSX) is the issue that it would be good to resolve..... I'm sure VSL ad Synchrosoft are working on it.

    J.

  • Julian, I have to repeat myself repeat myself: on my machine it DOES NOT TAKE SEVEN MINUTES the first time after starting up. It takes one minute and forty seconds.

    I'm certainly not saying that your problems aren't real, nor am I saying I haven't had problems with Syncrosoft dongles; I still can't launch Cubase SX3 on my main G5, and for the longest time I simply couldn't get two Scarbee libraries to launch.

    But 7-minute load times are not par for the course. The worst company in the world wouldn't release a product that takes seven minutes to launch. There is almost certainly something different about your system that Syncrosoft doesn't like.

  • last edited
    last edited

    @Nick Batzdorf said:

    Julian, I have to repeat myself repeat myself: on my machine it DOES NOT TAKE SEVEN MINUTES the first time after starting up. It takes one minute and forty seconds.

    I'm certainly not saying that your problems aren't real, nor am I saying I haven't had problems with Syncrosoft dongles; I still can't launch Cubase SX3 on my main G5, and for the longest time I simply couldn't get two Scarbee libraries to launch.

    But 7-minute load times are not par for the course. The worst company in the world wouldn't release a product that takes seven minutes to launch. There is almost certainly something different about your system that Syncrosoft doesn't like.


    Nick,

    I quote Herb:

    "I think there is a general missconception.
    I think Maya's 30 to 60 seconds startuptime refer to a startup of a VI after of opening a new logic project and not a startup after rebooting the computer.

    That means after a reboot you have to wait several minutes, depending how much content is added in your Directory Manager of the VI.

    If you change to a different logic project (no reboot), the startuptime of the first VI instance should be less than one minute (with the whole Symphonic Cube added)

    If your workflow needs a lot of reboots of your computer (changing the studio etc.) we recommend only to add the instruments in Directory Manager which were needed.

    I have also talked with our developement team to add a save/load option into Directory Manager, so you can easy and fast setup the needed instruments for a certain project.

    best
    Herb"

    The point is the load times currently increase with the number of instruments. If you had the full cube installed plus appassionata strings your initial load tmes would be a magnitude greater. Although you state "The worst company in the world wouldn't release a product that takes seven minutes to launch." I am afraid 7 minute launch times (on G5.s) are currently the case and have been confirmed by a fair number of VSL users on this forum, including Herb! I currently get launch times of 2 minutes for the whole collection when booted Windows XP2 so there is room for improvement and I'm sure it will come.

    Julian

    [/i]

  • If that's true then I'm eating crow.

    But I still find it hard to believe that the increase as you add libraries is *exponential.*

    Tomorrow I'll try moving the dongle that's on my PC to the G5 (I have five Collections on the G5 but the dongle for a fifth is on a PC right now).

  • Well, as you predicted, adding the fifth Collection back to the G5 (it had been there all along, but moving the dongle back activated it) increased the initial start-up time to 2:10. I guess that means each Colleciton takes additional time. It seems unlikely that adding five more would increase the load time to seven minutes, but it's possible.

    Another issue is that the Collection I "moved" back didn't appear in the Vienna Instruments player even though I ran the directory utility, but I'm not going to worry about that right now.

  • last edited
    last edited

    @hkieffel said:

    So while the computer boot is not "cold," Logic Pro gets a fresh start.
    .


    But this is because vsldaemon is already running after the "sleep" the same thing happens under WinXP if you hibernate - you get <15s load times quite easily.

    It's a shame the process takes so long. It would be nice if VSL could implement a complete licence scan every 30 days or something rather than every time you use the plugin.

  • last edited
    last edited

    @Nick Batzdorf said:

    Well, as you predicted, adding the fifth Collection back to the G5 (it had been there all along, but moving the dongle back activated it) increased the initial start-up time to 2:10. I guess that means each Colleciton takes additional time. It seems unlikely that adding five more would increase the load time to seven minutes, but it's possible.

    Another issue is that the Collection I "moved" back didn't appear in the Vienna Instruments player even though I ran the directory utility, but I'm not going to worry about that right now.


    I find that the scanning process in directory manager (this occurs everytime you have a cold boot) is taking about 6-7 seconds per folder - in OSX (you can watch this happening in Activity Monitor) There are about 60 folders for the full Cube plus appassionata Strings. My MacBook Pro boots the same collections in 5 Minutes 45 seconds. Bit quicker than the G5 but still a looong time!

    Julian

  • Maya covers the above issues on

    http://community.vsl.co.at/viewtopic.php?t=9000

    Julian

  • Thanks Julian. I have egg on my face.

  • And by the way, I apologize for inadvertently insulting VSL earlier in this thread. [:)] [:O]ops: [:O]ops: [:O]ops: