Vienna Symphonic Library Forum
Forum Statistics

194,197 users have contributed to 42,912 threads and 257,931 posts.

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

  • After watching the numbers fall over the last few weeks, i'm astonished how quickly the VI loads now. Mac or PC, i can remember much longer loading times for lesser VST's without CP not that long ago. The work and effort that must have gone into getting this to work even better, beggars belief.
    My how the technology flies.........

    Now, Christian M seems to have gone quiet, so.....

    How's MIR coming along?

    Alex.

    p.s. Just Kidding!

    [[:|]] [H]

  • last edited
    last edited

    @Another User said:

    SYNCROSOFT:
    Unfortunately we were forced to withdraw the License Control Installer
    5.0.5.0 from our download page due to an error.

    We strongly recommend to update your installation.


    Please find the updated LCC (5.0.5.1) here:

    http://www.syncrosoft.com/downloads/

  • Maya,

    I just updated a few days ago with 5.0.5 - is this 5.0.5.1
    Something different?

    Rob

  • last edited
    last edited

    @Rob Elliott said:

    Maya,

    I just updated a few days ago with 5.0.5 - is this 5.0.5.1
    Something different?

    Rob


    Yes, 5.0.5.1 is different from 5.0.5.0 according to Syncrosoft and they strongly recommend to update to version 5.0.5.1.

    Best

    M a y a

  • Thanks Maya for the fast reply. I'll update today.


    Rob

  • last edited
    last edited

    @Another User said:

    SYNCROSOFT:
    Unfortunately we were forced to withdraw the License Control Installer
    5.0.5.0 from our download page due to an error.

    We strongly recommend to update your installation.


    Please find the updated LCC (5.0.5.1) here:

    http://www.syncrosoft.com/downloads/

    Maya,

    this link leads to a 5.0.4 VERSION. What is the issue?

    Rob

  • last edited
    last edited

    @Another User said:

    SYNCROSOFT:
    Dear Customers,

    although we withdrew the License Control Installer 5.0.5.0 just recently
    from our download page and replaced it with an updated version 5.0.5.1
    just today, it turned out the issue wasn't solved by this installer
    regarding all aspects.

    Consequently, we will withdraw the Syncrosoft License Control installer
    version 5.0.5.1 as well and replace it by a *proper* version tomorrow.

    We sincerily apologize for any inconveniences (...).


    What happened is that Syncrosoft has withdrawed version 5.0.5.1 also shortly after I posted it here.
    Hopefully a final version of 5.0.5.x will be available tomorrow. I am sorry for the confusion.


    Best,

    M a y a

    Ps.: Sort of a "Catch the update, if you can" game. [;)]

  • last edited
    last edited

    @Another User said:

    SYNCROSOFT:
    Dear Customers,

    although we withdrew the License Control Installer 5.0.5.0 just recently
    from our download page and replaced it with an updated version 5.0.5.1
    just today, it turned out the issue wasn't solved by this installer
    regarding all aspects.

    Consequently, we will withdraw the Syncrosoft License Control installer
    version 5.0.5.1 as well and replace it by a *proper* version tomorrow.

    We sincerily apologize for any inconveniences (...).


    What happened is that Syncrosoft has withdrawed version 5.0.5.1 also shortly after I posted it here.
    Hopefully a final version of 5.0.5.x will be available tomorrow. I am sorry for the confusion.


    Best,

    M a y a

    Ps.: Sort of a "Catch the update, if you can" game. [;)]


    Thanks Maya - just reminds me of ANY software's 'updates' are really suspect until everyone else tries them and works the bugs out. I am usually a 'late comer' on updates for this reason. I just don't have time to fiddle with computers. [:'(]

    Rob

  • last edited
    last edited

    @Maya said:

    SYNCROSOFT:
    Dear Customers,

    although we withdrew the License Control Installer 5.0.5.0 just recently
    from our download page and replaced it with an updated version 5.0.5.1
    just today, it turned out the issue wasn't solved by this installer
    regarding all aspects.

    Consequently, we will withdraw the Syncrosoft License Control installer
    version 5.0.5.1 as well and replace it by a *proper* version tomorrow.

    We sincerily apologize for any inconveniences (...).


    Syncrosoft ... the Trabant of software protection??

    julian

  • last edited
    last edited

    @julian said:



    Syncrosoft ... the Trabant of software protection??

    julian


    Julian, your claws are showing.....

    [:D]

  • last edited
    last edited

    @julian said:



    Syncrosoft ... the Trabant of software protection??

    julian


    Julian, your claws are showing.....

    [:D]


    Can you imagine what 'claws and teeth' are showing inside of VSL's conference rooms. I can imagine Herb and crew are fed up with this subsupplier. On one hand - they are needed to protect their investment on the other - they are possibly preventing sales or at the very least ticking off existing customers [:'(]

    Rob

  • last edited
    last edited

    @julian said:



    Syncrosoft ... the Trabant of software protection??

    julian


    Julian, your claws are showing.....

    [:D]

    Yeh!

    The trouble is I'm working on a multi cue commercial project as we speak and due to the still (unfortunately) very long load times using the Vienna Instruments system I HAVE to work with the old Orchestral Cube library to meet my deadlines.

    Don't get me wrong the Vienna Instruments are wonderful but in the Logic/Mac environment they do not yet fit into a commercial multi-cue workflow where a director might be present and can't just while away the day waiting for each cue to load.

    I can't get a Mac initialisation time for Vienna instruments anywhere near the 50"-60" Maya has quoted - takes 2'30" for an empty VI AU to open in Logic for the first time (have any other Mac users got down to 1 minute with the full 10 instrument collection?)

    Currently I can load a maxed out Logic session using the Pro edition EXS version (RAM wise) in just over 4 minutes from booting my computer in the morning.

    An equivalent RAM load - this time using the Vienna Instruments - though improved - recently is nearly 4 minutes longer.

    I recently calculated to review a 15 cue project with the production's director would involve me with over 2 hours of load time!!

    In a time conscious industry this just doesn't fly.

    I think VSL have made great moves forward in their application of Sampling technology and enable tracks to be created that would have been unfeasible a few years ago. However in getting their system on to our system (i.e. the license scanning issues and data loading issues) the Vienna Instruments appear, at least on a MAC system to be behind the curve. My system has a potential capability to transfer into RAM at over 200MB/second. With the Vienna Instruments, taking scanning and loading into account, loads are averaging at under 10MB/second - one twentyeth of the sysyems theoretical limit.

    There rant over!

    Now I'm looking to be able to incorporate the wonderful Vienna Instruments into my projects in the near future....hopefully!


    Julian

  • last edited
    last edited
    well to not exaggerate things .... i could imagine there turned up other issues not related to VSL licenses and so they had to withdraw the version.

    for users with registered ViennaInstruments Libraries i've therefore temporary re-activated the download from the user area

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

    @Another User said:

    one twentyeth of the sysyems theoretical limit
    julian, also here we have to face the relations.
    you can't compare RAM usage for arguing loading times, because the footprint of a loaded sample header with ViennaInstruments is significantly smaller than with any other app, so the number of loaded samples is much higher (i'd say 2.5 times average) - this samples have to be read from a harddisk.

    harddisks can still deliver just ~30 MB/s random read, if you have a very fast drive (10.000 rpm, NCQ) possibly 40 MB/s ... this affects the theoretical limit. of course your PCI-bus can deliver ~250 MB/s to memory or processor in best case - but when does such a case really occur?

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

    Yes I realise theoretical limits (my 4 disc SATA 2 raid is capable of transfering large files at over 200 MB) don't equate to actual load times and one only has to look at the sample count of the VSL library to realise the magnitude of available samples.

    However it feels to me that in load times we have taken a step back recently (even accounting for the 16 bit to 24 bit data size increase)

    Ever since first purchasing the Pro Library and latterly I have found them to be both brilliant to work with and, on my system at least, extremely stable/reliable. It is only with the load times (both initialisation times and sample header load) i encounter log jams and I am hoping within a few months they will improve.

    Julian

  • news again: 5.0.6.1 http://syncrosoft.com/downloads/ [;)]

    and remember: only a CRAY can run an endless loop in just three seconds.
  • ...very speed..but sometimes a message display "...error no valid license...etc"
    restart and all good....but....

  • last edited
    last edited

    @Another User said:

    the footprint of a loaded sample header with ViennaInstruments is significantly smaller than with any other app


    Just out of interest, what is the footprint per sample, cm?

    This is something that just came up in a discussion I was having about Kontakt 2, so I'm especially curious.

  • Anyone of your 'courageous' ones tried this latest version???


    A very timid Rob Elliott [:O]ops:

  • Rob-- I was wondering the same thing. I got 5.0.5.0 loaded, and all *seemed* to be fine-- then I go out of town for a few days and discover that within 24 hours that versions have come and gone rather conspicuously.

    I do find this very troubling, especially when the new and improved 5.0.6.1 seems to have caused one user a problem already. [*-)]

    The mere exodus of two versions in such a short time indicates that one set of problems continues to be exchanged for different set of problems.

    It feels odd to have the now defunct 5.0.5.0 still running, but until I hear otherwise or until 5.0.5.0 totally falls apart on me, I'm going to hold my ground until further reports come in.