I used foobar2000 v.1.1.10 and foo_midi configured for using Hyper Canvas VST to play midi files. Result was perfect for me. Unfortunately, updating foo_midi to v1.150 I lost possibility to use Hyper Canvas VST. In Advanced section of Preferences I set path to C:\Program Files\Steinberg\VstPlugins\Edirol where in my case is located Hyper Canvas.dll, but in regular MIDI decoder configuration page I can only choose between Emu de MIDI, BASSMIDI and MUNT. Before updating there was also EDIROL HQ Software Synthesizer.Any ideas where is the problem and how can be solved?

I have sent you a message containing a link to an alternate download of foo_midi.zip which contains another vsthost.exe. This one should reveal more about the failure through the exit code in the Process Monitor log.

I have sent you a message containing a link to an alternate download of foo_midi.zip which contains another vsthost.exe. This one should reveal more about the failure through the exit code in the Process Monitor log.

I've tested new version vsthost.exe. Logfiles with brief descriptions are in Uploads - (fb2k).

Hello! Downloaded MIDI decoder v.1.156, but couldn't launch EDIROL Hyper Canvas. win7 x64. foobar2000 v.1.1.13. Whether it will be repaired? The same problem that is described at the beginning of a topic.

It was broken because my new external VST host binary uses stdin and stdout to communicate with foo_midi, but Hyper Canvas emits debug notices to stdout, breaking communications. I've changed the output path to use stderr instead. If some other VSTi manages to break that as well, I'll just pass the names of the two named pipes straight to the VST host and let it open them directly, instead of bothering with standard handles.

EDIT: Okay, I'm not taking any more chances. Now I pass the pipe names directly to the VST host module and let it connect to them directly. No more potential problems from VST plug-ins touching the standard handles.

Hi, kode54! MIDI plug-in together with EDIROL Hyper Canvas generates a set of processes and doesn't kill them. (Win7 x64, Foobar2000 v.1.2.5, foo_midi v.1.199). I start Foobar. Everything is ok. I start *.mid the file, and two processes "vsthost32.exe * 32" are created. Now I start other *.mid the file. One more process is created. Now them 3. And so indefinitely. Are killed only by handles. Each process about 30 Mb occupies memories - terrible leak: (