Vienna Symphonic Library Forum
Forum Statistics

182,251 users have contributed to 42,214 threads and 254,729 posts.

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

  1. Home
  2. Software
  3. Vienna Instruments Pro
  4. VEPro and DP8 - Event Input stuck notes and MIDI problems

  • VEPro and DP8 - Event Input stuck notes and MIDI problems

    D
    D
    I've been working with DP and VEPro for some time, and in general find it very useful. There are, of course, little bugs that I've worked through, but I thought I had a pretty stable system going. I have a MacPro Quad-core running DP8 as my DAW, with VEPro running in both LocalHost and on 5 slaves (3 PCs and 2 MacMini).

    I recently created a new "Orchestra Template" with the following (basically) VEPro connections (each computer has only one instance of VEPro)

    ----LocalHost: 4 instances of EW PLAY + 1 instance BATTERY + 1 instance G-Player - all with several audio outputs bussed through DP

    ----MINI-1: EWPLAY VOP + NI Synths (absynth, FM8, Massive)

    ----MINI-2: EW Stromdrum2

    ----PC1: 1 instance of EW PLAY + 7 Vienna Brass II instruments

    ----PC2: i instance of Steinberg HSO

    ----PC3: 1 instance EW QL Pianos


    I am using a V-Rack in DP to host the Vienna Plug-in as well as the VEP "Event Inputs" plugs that I use to send MIDI to more than one port.


    I have absolutely NO problems with the slave computers. MIDI goes out (either through the initial VEPro instance or a secondary "event input") and audio comes back without incident.


    The issue I am having is with the LocalHost, admittedly the most complex of the bunch. When I load the project, it seems to be working. I enable a track and send MIDI via my S80 keyboard and hear the sounds as expected. However, when I put the project into "play," I no longer am able to play the instrument. Futhermore, if I record some MIDI information into the track, I do not hear it on playback and more often than not, get some stuck notes which I have to go through each instrument to unstick (command-1 doesn't do it alone).


    After doing some research here, I have tried these fixes, to some success, but nothing permanent:

    ---1. repair permissions on HD

    ---2. make sure all Event Input channel outputs match the initial VEPro instance's output

    ---3. in DP preferences, make sure project is set to "All Plug-ins in Real-Time"

    ---4. Disconnect and re-connect Event Input plugs to to the initial VEPro


    I am running VEPro version 5.1.11947 and have hesitated to update because I have achieved some stability with this version. I have other templates using similar setups and have not had problems with event input channels "mis-firing" (or not sending) MIDI. I have looked over the changelogs for the more recent updates of VEPro to see if this issue has been addressed and did not see anything, so unless someone can tell me that it is worth updating and will fix the problem, I am afraid of any other issues that may arise from an update.


    Please let me know if you have any information regarding this issue with Event Inputs. I have noticed that this problem is not mine alone, and that some recommend using alternate MIDI send options (IAC driver, Apple Netwrok, MIDIoverLAN, etc...), but I would rather use the VEPro inputs I was promised.


    Thanks for your time,

    Burt


    COMPUTER: MacPro 2X2.66 Quad-Core Intel Xeon RAM: 16 GB 1066 MHz DDR3 OS: 10.7.5 DAW: DP 8.01 VEPro: 5.1.11947
  • J
    J
    "The issue I am having is with the LocalHost, admittedly the most complex of the bunch. When I load the project, it seems to be working. I enable a track and send MIDI via my S80 keyboard and hear the sounds as expected. However, when I put the project into "play," I no longer am able to play the instrument. Futhermore, if I record some MIDI information into the track, I do not hear it on playback and more often than not, get some stuck notes which I have to go through each instrument to unstick (command-1 doesn't do it alone)." I have exacly the same situation and no solution for me yet. The only way for me to oveleap this problem in specific session where it happens is to remove problematic instrument and event input and place it either to other ensamble instance or assign to working event input. It's really disturbing the workflow. If someone from Vienna could refer to that problem would be great.