Vienna Symphonic Library Forum
Forum Statistics

200,608 users have contributed to 43,204 threads and 259,106 posts.

In the past 24 hours, we have 4 new thread(s), 9 new post(s) and 72 new user(s).

  1. Home
  2. Software
  3. Vienna Instruments Pro (legacy)
  4. UPDATE: New versions of all VSL software available in your USER AREA

  • UPDATE: New versions of all VSL software available in your USER AREA

    PaulP
    VSL Team
    PaulP
    last edited
    last edited

    Hello everybody,

    We have just released a whole bunch of Software Updates for:

    • Vienna Instruments 4.1.7847
    • Vienna Instruments PRO 1.1.7846
    • Vienna Ensemble 4.1.7846
    • Vienna Ensemble PRO 4.1.7846
    • Vienna Imperial 1.0.524
    • Vienna Suite 1.2.1512
    • MIR 1.3.1844

    As always, our development team has added some cool bug-fixes and, most significantly, has managed to increase the loading speed for Vienna Instruments and Vienna Instruments PRO on OS X!

    Please find all updates in your User Area, along with the changelogs!

    Best,

    Paul

    Paul Kopf Head of Product Marketing, Social Media and Support
  • D
    D

    Thank you, VSL team.  It's so nice to have the VI Pro GUI working now in Cubase 64 (OS X)!
  • PaulP
    VSL Team
    PaulP

    Hi Bill,

    very good suggestion, thanks for the input!

    We´re glad you like the new versions [:)]

    Paul

    Paul Kopf Head of Product Marketing, Social Media and Support
  • D
    D
    I'm always a fan of speedy loading times. Thanks Paul and VSL team!
  • Cyril BlancC
    Cyril BlancC
    last edited
    last edited

    @ddas said:

    I'm always a fan of speedy loading times. Thanks Paul and VSL team!

    To give back to Caesar what belongs to Caesar, you have to thanks VSL developer's,  Martin Saleteg, he re-program lousy Mac OS X's memory allocation routines[:D]

    Martin deserve a spécial bonus [;)]

    Thanks again Martin

    Best

    Cyril
  • K
    K

    WOW - my 6.6 gig template went from taking 5-6 minutes to load to now just over a minute! You guys are insane!

    Thank you thank you! [Y][B]
  • S
    S

    Damn... was so excited when I saw the "file association" fix mentioned for OS X... however it still doesn't work here. If I have an open 64-bit server running, and double click an .mframe32, it will still just add those instances to the 64-bit server and vice versa....:/
  • K
    K

    OS X has a way of confusing file associations. If a simple reboot doesn't fix things, you could try rebuilding the Launch Services database by executing this command in a Terminal:

    /System/Library/Frameworks/CoreServices.framework/Frameworks/LaunchServices.framework/Support/lsregister -kill -r -domain local -domain system -domain user
  • S
    S

    Karel, thanks, I tried all of the above - still doesn't work....

    With all due respect, the VEP software is the ONLY software I have that exhibits this problem. If I change file association for .txt, for .mov, for .mp4, whatever, it will all work accordingly after doing so. The problem is not that the OS doesn't know which software it is associated with. If I "info" an .mframe64, it will say that this opens with VEP Server 64-bit. If I look at an .mframe32 file, it will say that it opens with the VEP Server software (non 64-bit). And it DOES, if it is the first server software that is launched. The problem seems to occur when you try to launch either a 64-bit metaframe or a 32-bit one when the server software is running - then it will just add the instances to the currently open software instead of opening the 32-bit or 64-bit server software accordingly. The problem must be somewhere in the way the VEP Server software works.