Vienna Symphonic Library Forum
Forum Statistics

196,182 users have contributed to 43,014 threads and 258,396 posts.

In the past 24 hours, we have 0 new thread(s), 8 new post(s) and 168 new user(s).

  1. Home
  2. Software
  3. Vienna Instruments Pro
  4. UPDATE: VI PRO 1.0.6853 and VE PRO 4.1.6853

  • UPDATE: VI PRO 1.0.6853 and VE PRO 4.1.6853

    PaulP
    VSL Team
    PaulP
    last edited
    last edited

    Hello everybody,

    We hope you enjoy your sunday with the new optimized updates, available in your Software USER AREA.

    Bug-fixes VI PRO 1.0.6853:

    • Fixed internal state of powerpan not properly restoring on preset load (Slot Mixer Tab)
    • OS X: Fixed right click or Ctrl-click not working in RTAS
    • WIN: Fixed crashes on Windows XP32 and Win XP64. Win XP64 is not actively
      supported, but works.

    Bug-fixes VE PRO 4.1.6853:

    • Fixed keyboard widget not updating when switching between docked VI Pro instances
    • Fixed VI Pro editors interfering with each other between VE PRO instances
    • WIN: Fixed crashes on Win XP32 and Win XP64.

    Of course all your input has been noted, and we´re working our way through many new ideas!

    Best,

    Paul

    Paul Kopf Product Manager VSL
  • S
    S

     I don't know if I am missing something, in that case forgive me!

    Is there a way to widen the "Preset-Matrix-Patch"  zone, so to see all the Preset or Matrix or Patch names,

    like, for example, "VE_SoundSet_AppassionataStrings_Sib5.2_v.1.0"?

    I know that in this case it is not so significant, but many of us have very large screen, so, why limiting it?

    Sergio
  • PaulP
    VSL Team
    PaulP

    Hi Sergino,

    right now there is no way to do that. It has been mentioned a few times before and we´ll see if we can offer a solution, as always [:)]

    For an immediate solution, I´d suggest to introduce abbreviations for your naming convention (as we do it) and take advantage of the Preset Information available for each customized preset.

    E.g., "VE_SS_AppStr_Sib5.2_v1.0"

    Thanks for your patience, changes like this are not as easy as it may seem. 

    Best,

    Paul

    Paul Kopf Product Manager VSL
  • I
    I

    Yes, this fixed the crash on XP32. Thanks for the quick patch!

  • BillB
    BillB

     Same build number for both?  Should we expect that from now on?

    Dorico, Notion, Sibelius, StudioOne, Cubase, Staffpad VE Pro, Synchon, VI, Kontakt Win11 x64, 64GB RAM, Focusrite Scarlett 18i20, August Forster 190
  • R
    R

    If we have BOTH VEPRO and VIPRO - we just update VEPRO, right?
  • K
    K

    If you use both, update both. They are seperate applications.
  • R
    R

    Thanks Karel.  All the best,
  • G
    G

    I've never needed any VE Pro license on the eLicenser plugged in my Host machine, as I'm running both VE Pro Server and any other VI / VI Pro plugin instance in the remote servers. In fact, I could run both the VE Pro setup and the VE Pro plugin inside my host software without any VE Pro license in my eLicenser key.

    Now, I've just noticed that you need a VE Pro license in the eLicenser also during the setup. I think this is just an error in the setup executable, as it never happened before. In fact, I installed any previous version of the VE Pro on my Host without any VE Pro license.

    I can also confirm that, once the new VE Pro 6853 is installed, you can remove the eLicenser and the plugin inside your host loads without any issues, as it did before.

    This makes my think that something went wrong compiling the setup executable of the last VE Pro release 6853.
  • K
    K

    You're right. Running the VE Pro Server Interface plugin requires no eLicenser at all. The license check is there because the installer installs both the VE Pro Server and the VE Pro Server Interface plugin.
  • G
    G

    I get your point, but the fact is that check has never been there before. I always installed every previous release without having any license on my eLicenser. Your consideration about the double server/plugin installation doesn't justify, in my opinion, this change. In every previous version you could install both of them, but you couldn't run the server without the license. This approach makes absolutely more sense to me. And in fact, this approach was the one for any previous version.

    It's not a big deal to move one key to the Host just during the setup. My wonder was about the reasons why you decided to change this behavior.
  • I
    I

    Yes, checking the license in installation is really shortsighted especially from a company that helps us use slave computers. We have computers without internet connections, without keyboards, without displays etc. and the computer used to extract or install the downloaded software isn't necessarily the computer used to run the software. No other company I know of does that and I'm disappointed that VSL would do something like this. If you trust the dongle then trust it. If you don't then don't make us use it.
  • G
    G

    I wouldn't say I'm disappointed of this change. I was just curious to know if it's a precise choice or just a mistake compiling the setup executable for the latest release.
  • D
    D
    last edited
    last edited

    @Gemini said:

    I wouldn't say I'm disappointed of this change. I was just curious to know if it's a precise choice or just a mistake compiling the setup executable for the latest release.

     

    How do you find the new licence scanning time? Is that better?

    DG
  • G
    G
    last edited
    last edited

    @DG said:

    How do you find the new licence scanning time? Is that better?

    Way much better. It's almost immediate and this is particularly noticeable when you open the VE Pro Server after a fresh start up of the system. In the same situation with any previous release, it took a way longer time, especially to scan the licenses.
  • K
    K

    I'll just remove that license check for the next update. It doesn't make much sense indeed.
  • G
    G

    Thank you Karel!

    I really appreciate your kind consideration! [;)]
  • P
    P
    Thank you!