Vienna Symphonic Library Forum
Forum Statistics

180,750 users have contributed to 42,140 threads and 254,362 posts.

In the past 24 hours, we have 3 new thread(s), 17 new post(s) and 48 new user(s).

  • Virtual Midi ports for XP 64, anyone?

    Obviously Maple Midi works only on 32 bit. Does anybody know of virtual Midi cables for XP 64?


  •  Something called LoopeBe30 (I think).

    http://www.nerds.de/en/order.html

    DG


  • I researched this topic in depth a few months ago. There are no perfect (and free) solutions for XP x64. However MidiOX does work pretty well and is free. In the end I decided to stop fiddling around and find another way of working. After some failed attempts, I found a way to ditch all the virtual MIDI cable stuff and work completely within a x64 host application. I hope this is at least a little helpful.


  • Great replies, thanks!


  • last edited
    last edited

    @musicpete said:

    After some failed attempts, I found a way to ditch all the virtual MIDI cable stuff and work completely within a x64 host application. I hope this is at least a little helpful.

    Hi! Could you tell me what is the way?

  • last edited
    last edited

    @rogeriodec2 said:

    Could you tell me what is the way?

    Of course!

    1) I use the following software: XP Pro x64 Edition, Cubase 5 x64, VE Pro x64. And most importantly: jbridge!

    2) Using jbridge I created a folder of bridged x64 versions of my plugins (The process is described in the jbridge manual). Due to a bug in jbridges helpe application I then had to recreate my folder structure from scratch, which took a few hours but paid off in the end. I ended up with 3 VST plugin folders:

    C:\Program Files\Steinberg\VSTplugins\

    C:\Program Files (x86)\Steinberg\VSTplugins\

    C:\Program Files (x86)\Steinberg\VSTplugins_jbridged\

    The first contains all the native x64 plugins (e.g.: Vienna Instruments, VE Pro, Kontakt 3.5, Battery 3, Play-x64, ...)

    The second contains all the native x32 plugins.

    The third contains all files jbridge needs to do its magic (i.e. for each plugin one .dll and one .txt file. e.g.: ezdrummer.64.dll and ezdrummer.64.txt). Again, all this is described in the jbridge manual in detail.

    3) I pointed my C5 to search only in the following folders for VSTs:

    C:\Program Files\Steinberg\VSTplugins\

    C:\Program Files (x86)\Steinberg\VSTplugins_jbridged\

    That way C5 will find the x64 plugins in the first folder and all the bridged versions of x32 plugins in the second folder. This works perfectly for me, no more memory limits. No more fussing around with virtual midi ports. Just load up as many GB of samples as possible and create music.

    One caveat: There are some plugins which don't work at all with jbridge at this thime. The author is working on it, and until he manages to fix this, I just deleted those plugins (they created bizarre crashes on startup of C5). Turns out that none of them were essential to my workflow and could easily be replaced with alternatives.

    I hope this was a little more helpful. If you have mroe questions, don't hesitate to ask!