Vienna Symphonic Library Forum
Forum Statistics

196,693 users have contributed to 43,029 threads and 258,427 posts.

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

  1. Home
  2. Software
  3. Vienna Instruments Pro
  4. Ableton and Configure automation

  • Ableton and Configure automation

    D
    D

    I know this issue has a few mentions in the forum previously but I am still having the same issue with the latest updates from ableton and VE Pro 5. I have followed the process of creating my plugin in a new instance of VE Pro 5 and setting everything up in Ableton. The instance is recognized and I can play the instrument hosted in Ve Pro 5 no problem. I then add a new automation using parameter 1 and clicking on the VSTi within Ve Pro, so far everything is good. But When I click on the configure button within ableton I do not get any additional parameters displaying in Ableton like I should Its like there is no communication between back from VE Pro to ableton.

     

    I usuallly use VEP on a slave machine so I tried today running a VEP server on my mac (same machine as ableton) and connecting to the localhost version hoping it was an issue that affects only remote machines but the problem persists.

     

    I love the product and eveything about the workflow that VEP gives me but I would like to automate some plugins as I would be able to in Logic or Cubase. In addition as long as I can configure the data being sent to the plugin I could also use the remote instance of the plugin from the Push midi controller. Without any values to be able to configure this is not possible.

    Again, everything is uptodate 64 bit server (5.4.14074), latest Ableton (currently 9.6.2)

     

    Is there a solution?
  • D
    D

    Is this issue fixed in the new version 6 or is the functionality still broken?
  • PaulP
    VSL Team
    PaulP
    last edited
    last edited

    Hi Drew,

    This is now fixed in VE PRO 6, give it a try with a free demo license!

    Best,
    Paul

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

    You are indeed correct the functionality is fixed (again) in VE Pro6!

    Unfortunatly I run 2 licenses for VE Pro (2 sets of 3 slave machines)  and VE Pro 6 cannot coexist with VE Pro 5. I need compatability with VE PRO 5 for older projets and I have read on this community that once opened in version 6 they are no longer able to be used with 5

    I feel there really should be a process whereby 5 and 6 can coexist. I understand that purchasing an updated license prevents one from using an old version but I don't think its fair business to force a user to upgrade to version 6 on all licenses just because they wish to upgrade on one set of them.

    The licensing in eLicenser should take care of which is available to which machine (3 licenses on version 5, 3 on version 6 - simple) but overwriting a newer version and breaking the old one is not really on!

    Maybe both versions are registering the same VST ID ??

    Is there any chance the broken functionality will ever be fixed in version 5 (it did work then an update hosed it) ?

     

    FYI, uninstalling the demo 6 version and trying to reinstall version 5 failed initially. Ableton live did not recognize the plugins had been reinstalled (even with a rescan of the plugins). Unclicking Use VST Plu-in System folders, then clicking again did allow the plugins to show. No other plugins apart from VE PRO 5 had this issue.