vsthost and virtual midi cables?

[milo2112]

Hi all,

I am having problems getting vsthost to send midi info to a virtual midi cable (loopbe1) via the midi output window. Can someone offer some tips? Does vsthost not play nice with virtual ports?

milo

[RunBeerRun]

I use Savihost w/Midiyoke all the time, should be the same. Do you have Loopbe otherwise working? Made sure there's not 2 things on a single asio driver?

[milo2112]

Savihost and loopbe works great. For some reason, I can't get vsthst to work.

[RunBeerRun]

I have it running right now, with midiyoke, it's an older version of Vsthost, 1.44.

The only time it didn't work for me was having two things on the asio driver, one of them was a midi effect which didn't need sound. So beyond this I have no idea, it shouldn't be too picky.

[arakula]

I am having problems getting vsthost to send midi info to a virtual midi cable (loopbe1) via the midi output window.

VSTHost is not interested in whether this is a virtual MIDI port.

What exactly do you mean by "... the midi output window"? What exactly did you configure?

And which version of VSTHost is this?

And which version of Windows?

[Taliesin63]

Hi all,

I am having problems getting vsthost to send midi info to a virtual midi cable (loopbe1) via the midi output window. Can someone offer some tips? Does vsthost not play nice with virtual ports?

milo

yeah, i realize this is a seven-and-a-half year old thread... but people will still stumble across it, if they're googling for why they're not seeing their Midi Yoke paths from within VSTHost!

the issue here is bittedness. v1.48+ of VSTHost are all 64-bit programs. as such, they will not be able to see the Midi Yoke virtual cables, as Midi Yoke is still a 32-bit application, creating 32-bit virtual pathways. i'm pretty sure that there is some arcane incantation involving particular command-line parameters to 64-bit VSTHost, chicken lips and goat's blood, which will allow for post-v1.47 versions of VSTHost to be able to see the Midi Yoke cables, but I'm not at all certain what that might be. i am going to attempt to install and run a pre-v1.48 version on my Win10 machine, in parallel with my current v1.56 install... and hopefully have both function as expected/hoped!

film at eleven!

[experimental.crow]

Hi all,

I am having problems getting vsthost to send midi info to a virtual midi cable (loopbe1) via the midi output window. Can someone offer some tips? Does vsthost not play nice with virtual ports?

milo

yeah, i realize this is a seven-and-a-half year old thread... but people will still stumble across it, if they're googling for why they're not seeing their Midi Yoke paths from within VSTHost!

the issue here is bittedness. v1.48+ of VSTHost are all 64-bit programs. as such, they will not be able to see the Midi Yoke virtual cables, as Midi Yoke is still a 32-bit application, creating 32-bit virtual pathways. i'm pretty sure that there is some arcane incantation involving particular command-line parameters to 64-bit VSTHost, chicken lips and goat's blood, which will allow for post-v1.47 versions of VSTHost to be able to see the Midi Yoke cables, but I'm not at all certain what that might be. i am going to attempt to install and run a pre-v1.48 version on my Win10 machine, in parallel with my current v1.56 install... and hopefully have both function as expected/hoped!

film at eleven!

http://www.copperlan.org/

[ENV1]

the issue here is bittedness. v1.48+ of VSTHost are all 64-bit programs.

Whoever gave you that info has misinformed you.

Even the currently latest version (1.56) is still available as both 32bit (x86) and 64bit (x64).

Find both variants plus a special Win98/ME/NT4 build here under 'Downloads'.

[ENV1]

wrong button - quote should have been edit