Vienna Symphonic Library Forum
Forum Statistics

182,172 users have contributed to 42,208 threads and 254,684 posts.

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

  1. Home
  2. Software
  3. Vienna Instruments Pro
  4. [SOLVED] VI - VIP - VEP on OSX Standalone - MIDI BUG

  • [SOLVED] VI - VIP - VEP on OSX Standalone - MIDI BUG

    R
    R

    Hello,

    I've been using VI/VIP/VEP on OSX (10.6.8) without any glitches for now.

    I recently updated to the last versions of each, and now don't get any MIDI IN response when playing on my keyboard, while using standalone versions.

    All my other music software (Logic, PLAY, Kontakt) DO respond to MIDI without any problem. VI/VIP/VEP through Logic as AU plug-in is ok too.

    I just can't get my MIDI keyboard to play notes while using the standalone versions. I checked the MIDI setup, and both of my Alesis MasterControl MIDI Ports are enabled. Tried to install earlier versions of VSL software, updated to the last Alesis drivers, nothing changed !

    Does anyone have a clue on what could be going wrong?

    Thanx for any help!

    P.S. : I've got the same software running on my MacBook Pro, playing on an Akai LPK25, everything is fine.
  • G
    G
    Check the versions of any plug-ins or standalone that you use. It has to be match.
  • R
    R

    The versions are the same for plug-ins and standalones :

    VEP 4.1.8783

    VI 4.1.8777

    VIP 1.1.8778

    Tried to delete preference files from both Library and Home Library (VSL software and my Alesis MasterControl), reinstall, nothing changed [:(]

    UPDATE :

    I've made some deeper researches :

    - When pluging another MIDI keyboard (my LPK25) and activating it in software preference, everything works fine on the LPK25.

    - My Alesis MasterControl is a control surface with one pair of IN/OUT MIDI ports. In the drivers, the control surface MIDI ports (sending messages to control software) used to be called "Control Port", and the physical MIDI ports (where my keyboard is plugged) called "MIDI Ports".

    In the latest releases of drivers from Alesis (since OS 10.6 compatible ones if I remember well), both control surface and MIDI ports are now called "Alesis MasterControl MIDI Ports" in the drivers and then appear so in all software. In VSL, I can't activate one of these ports only without having the other being activated too (because of the same name?), whereas I can in other software like PLAY or Kontakt.

    When I touch buttons on my control surface, VSL software get the message since I can see the keys playing on the screen, but it doesn't work if I use my keyboard keys (so the "secondary" MIDI port). Is it because they both have the same name that VSL software is confused? Because all other software I use correctly respond to my control surface buttons, and my keyboards keys.

    So is it an Alesis driver issue (though occuring only in VSL), or a VSL software bug about handling MIDI ports?

    If anyone at support staff could get an eye on this issue, thank you so much!
  • M
    M
    Hi. I just updated my VIPro and VEPro to the new version and am experiencing a similar irregularity. I often use VEPro standalone on my slave to play a simple piano (Kontakt) sound when composing. I connect to it via MIDI over LAN (I'm using an AKAI MPK88). Everything works fine when I first call up the software, but if I leave it on overnight VEPro no longer receives MIDI until I restart the application-- and the only way to restart the app is to force quit because when I quit normally I get a spinning beach ball. Never had this problem until I updated VEPro.
  • K
    K

    Do you get a hang report when this happens? If so, it would be useful to send this to  for me to look at. Thanks.
  • R
    R

    Hello Karel,

    Thank you for looking into this.

    I don't get any hang report, since there is no crash, just no response for keyboard MIDI port.

    If I try to activate just one port of my Alesis MasterControl in the VSL preferences (could be either first/Control port or second/MIDI port) and then click "Close", when I return back in the preferences, both ports are again activated/selected. Looks like VSL software consider both MIDI ports as one/the same. Probably because they both have the same name?

    Have no idea what to do next. I contacted Alesis too, but I have no hope there, since their mail support is quite lousy [:(]
  • R
    R

    Any news from VSL about this MIDI handling bug?
  • K
    K

    It's being investigated. Thanks for reporting this.
  • R
    R

    Thanks again, will keep an eye on the thread!
  • R
    R

    Hello,

    Was hoping to get this bug fixed in the new release of VI Pro 2, but it's still there [:(]

    Any news, it's been 3 months now since I reported this.

    Thanx
  • R
    R

    Hello,

    No news for a long time about this issue and any fix.

    Would it be possible to get "thick box" to activate options in Audio/MIDI Preferences pane, in state of just "selecting"?

    This would probably fix the issue of having both of my MIDI ports (because they have the same name) being activated, even if I only select one.

    Thanx for your feedback about this issue!
  • R
    R

    Problem solved, not thanks to VSL support though! 

    This guy here made my day : http://www.logicprohelp.com/forum/viewtopic.php?t=68448

    The change of MIDI ports names by editing the MacOS X AudioMidiSetup .mcfg preference file was the answer.

    VSL software still have issues managing MIDI ports having same names though, because of the way the user interface handles "select/highlight" options in the configuration panel... thick boxes should really be used instead!

    The workaround mentioned here is worth a look!