I’ve been using MidiBox as my main sequencer for several years now and always thought of recording my live performances in midi format.
Until now I was using all the 4 midi outs I have installed but since a couple of days I remapped all the tracks to OUT1 and set the midi channels accordingly.
What I’m looking for is to record midi data live while it’s being sent to my machines, on the fly, to record all the mutes and changes.
I’m trying to do it using an ancient MOTU interface using the “merge all” mode capturing one of the outputs with Cubase but all I get is midi garbage, stucked notes and so on.
Not sure if it has to be with the Midi interface not able to process all the midi data.
MIDIBOX -> MOTU-> MIDI DEVICES/COMPUTER
Any of you is recording live midi data with external outboard/DAW?
probably not related to your MOTU interface, but what you can do (and what any new SEQ software supports) is to shadow-output track MIDI data to another port/channel. So, you could basically just attach your SEQ to your computer (cubase will see it as four MIDI USB ports) and duplicate the MIDI output to relevant USB Ports and channels. Thus, capturing should be quite easy.
To activate it, within your SEQ go to MENU -> FX -> Dupl. and set up a duplication target for every track.
I was thinking about that; yesterday tried to install x64 midi drivers without success, but I have a spare x86 machine with drivers already installed to test it.
Regarding FX Dupl., I was looking into the manual and it is not very clear to me, can I just duplicate a track to a single different destination channel or I need to set it up for >1 channels?
no problem! In FX Duplication menu it should work like this:
Number of additional channels: 1
Port: e.g. USB1
FirstChannel: Channel number on the USB1 “port”, e.g. channel number 1
Then you will get a copy of the note data of that track on USB1, Channel 1. If you set up a higher number of additional channels, more channels will be used on that port to clone the note data - that makes no sense for recording, but in scenarios where you might want to output the track e.g. to multiple synths so that they would “layer” your sounds this is a nice feature.
am not really experienced with USB MIDI recording, went DAWless a while ago and never looked back ;-).
With RTOS as a reliable base and TK.'s code on top, as a first guess, i would not think the latency issues are caused by the SEQ app.
The problems might well happen within the operating system or the USB driver itself on your computer. Which OS and which computer hardware are you using? USB MIDI under windows is unfortunately a bit unreliable and i would not wonder, if multiple MIDI streams would cause jitter problems there.
Recommendation: if you are using windows currently and have access to a Mac, could you try it with that?
If you are already using a MAC, you could use a tool like MIDIPipe https://www.heise.de/download/product/midipipe-28614 to display and log inbound MIDI messages over USB - that way you should be able to analyze any potential latencies, before the MIDI messages are handled by the DAW. If these latencies are reproducable (e.g. by analyzing timestamps of two MIDI packets that should arrive around the same time but do have variable jitter over time, e.g. bassdrum and synth), this would be a starting point to investigate things in the SEQ app.
What I’m trying to do is to capture raw MIDI performances from the MidiBox for later playback and eventually record/mix the resultant audio on the fly when playing them (MIDI data) back to the hardware synths/drum machines and so on.
Was thinking of DAW because not really sure that an ancient hardware sequencer has the ability to record a huge amount of midi data in realtime.
Will try to go that way if I find one for cheap such as a QX3 or similar.