MIDI out issues

[JP Burtell]

Has anyone else had issues with the MIDI out object on Windows 10? I've never had problems before using any of the popular MIDI loopback devices (i.e. LoopBe1, loopMIDI) with ABox 2.42 until recently. MIDI in still works fine, and the output works for about a second, then the object gets the red outline and ceases sending data.

Any ideas or suggestions would be appreciated.

Thanks, and I hope you all are doing well.

Cheers,

John

[Sevendy]

It's been a long time (17 years!) since I played with this, but I do have some ABox MIDI files that probably worked at some time. As far far as I can determine, I'm seeing something similar to what you describe: when I hit "Play", there's a single, short burst of data that registers on the "loopMIDI" control panel, but the target application is seeing CC 64 "Hold Pedal" messages on all 16 channels (!), there's no sound and the "MIDI Out" shows the red box, and then nothing. I tried stringing just a MIDI In and MIDI out together and got the same result: 16 channels of CC 64. I do need to emphasize that it's been so long since I played with this, I'm not sure I know what I'm doing.

"MIDI In", on the other hand seems to work fine.

[JP Burtell]

Hello Sevendy,

Thank you for your reply, and it seems we are experiencing the same problem.

Fortunately, for the time being I have found a workaround. Using jbridge and MuTools Mux VST I've been able to host Reaktor 6 inside ABox and it's fairly stable.

Thanks again for your help though. I'll keep playing with and reply if I can find a solution for the MIDI out.

Best,

John

--
You received this message because you are subscribed to the Google Groups "Analog Box" group.
To unsubscribe from this group and stop receiving emails from it, send an email to analog-box+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/analog-box/c8827ef9-d44f-4efa-a1c3-b6a8e03e2196n%40googlegroups.com.

[Sevendy]

Following your lead, I had no trouble coming up with something similar, routing the MIDI output to a VSTi MIDI synth in ABox; this worked just fine. Oh well...like I said, it's been forever since I tried this stuff. I did play around some more--different Windows compatibility modes, outputting to the MS software synth, etc.--but always the same behavior.

[Sevendy]

Ok--I've got another work around: use VSTHost in "Slave" mode, and the associated VST plugin "Legree" in Abox. Instead of outputting MIDI to a virtual cable in ABox (which fails), stream it to the Legree plugin; process the streamed MIDI data in VSTHost/slave, generating wave data; this wave data is then available in ABox as wave output from Legree, and can be further processed in, or output from, ABox.

What I hoped to do--but have been unsuccessful, however--is to output the streamed MIDI data from VSTHost/slave directly to a virtual cable, which should be possible if I understand the manual.