Vienna Symphonic Library Forum
Forum Statistics

180,783 users have contributed to 42,141 threads and 254,364 posts.

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

  • Logic can't see an existing VEPRO instance

    Hi,

    I'm trying to use the Vienna Ensemble Pro AU3 plugin in Logic 10.4.6. However, I can't let it recognize any MIDI channel created on ports other than 1. Here is what I do.

    1. Run VEPRO 7 server, then Logic.

    2. Create a virtual instrument, by choosing Vienna Ensemble Pro AU3, Multi-timbral, 16 parts, and choosing Port 1. Logic creates 16 tracks for Inst 1.

    3. Create another virtual instrument, by choosing Vienna Ensemble Pro AU3, Multi-timbral, 16 parts, and choosing Port 2. Logic creates 16 tracks for Inst 2.

    4. Open the Vienna Ensemble Pro AU3 plugin on the first track of the first Port (Inst 1, Port 1, Chan 1), and create an instance "VSL".

    5. Open the Vienna Ensemble Pro AU3 plugin on the first track of the second Port (Inst 2, Port 2, Chan 1), and try to connect to instance "VSL".

    This is not possible. I'm asked to create a new instance, without any chance to choose the existing one. This means that MIDI messages can be sent to the VEPRO mixer channels assigned to Port 1, but there is not way to do the same with mixer channels assigned to Port 2.

    When openin the plugin already connected to the instalnce "VSL" I would expect to see the name selected. On the contrary, I only get the "NEW" option. But that connections is working. If I click Connect, the "VSL" instance is shown as connected.

    Another strange thing: after creating a second VEPRO instance, and then deleting it because not useful, the Logic tracks that were "Inst 1" are now called "Untitled". The name of the instrment in the Logic mixer is still Inst 1.

    What am I doing wrong?

    Paolo

    Image

    Image

    Image

    Image


  • See this thread: https://www.vsl.co.at/community/posts/t52861-Building-LogicPro-AU3-templates-from-scratch

  • Thank you very much! So, the trick is duplicating an existing track already using that VEPRO instance, and then manually changing the port number. Odd, but easy! Paolo

  • you can also grab this template and instructions here:

    https://www.logicprohelp.com/forum/viewtopic.php?f=9&t=143416

    The way you were doing it, you were creating seperate VEP plugin instances with only 16 channels each.  And you can only have one VEP plugin per VEP instance.

    You need to basically create the first 16 part multi timbral set of tracks..and then you need to use LogicPro's "New Track with next Channel" command to add more tracks to the same VEP plugin (and VEP instance), which you can then change to  new ports.

    There problem however, is that LogicPro has a bug where if you try to use that "New Track with Next Channel" command with channel 16 selected, it doesn't work as epxected.  So you have to do that little tap dance that dbudde figured out.  You create 16 of them, then you change the port of the last one to port 2, channel 1 (so that you will be able to use that New Track with Next Channel command on it without trouble, 15 more times.  But then use it on port 1 chan 15 again to get the channel 16 back.

    It will make sense when you do it a few times.

    Then make sure to submit a bug report to Apple about this, we shouldn't have to do this little tap dance, we should be able to hit "New Track with Next Channel" up to 127 times until we have created up to that many tracks into an AU3 plugin.  Also they should improve the new track wizard to allow us to create multi timbral tracks up to 127 parts.


  • Hey Dewdman42. How is the VEPRO7 AU3-plugin working by now? Is it reliabke enough to use in professional production or am I better of with the normal instance in Logic? 

    THX 

    Urs


  • It has been fine for me so far.  Unless/Until VSL designates it is not beta anymore, then I can't say whether or not to use professionally, but I personally haven't had any problem come up yet.