Midipipe manual how to#

Even though my Electribe is the first gen version with just two Motion Sequences possible simultaneously, it breathes a ton of life into sequences by varying cutoff and envelope decay or distortion, or anything really! I'm only using the Electribe to pass controller data while the BS 2 is running an arpeggio. If you have a hardware sequencer with MIDI-transmitting knobs, I can highly recommend trying it with your favourite MIDI-controllable synth. So the pipe needs to go something like this: By setting it to CC 99 (NRPN MSB) with a value of 2 (I got this number from monitoring the incoming MIDI), the conversion of the second NRPN was successful! I repeated this technique for all of the knobs and it works perfectly now. My theory was that the first message conversion was 'hogging' the MSB somehow, and that if I could reinstate this missing line in the data being sent to Message Converter #2, it would work.įortunately I found that there is a tool in MIDIpipe called Set. The last AList in the chain showed that Pitch was being sent out as a single line CC rather than three lines of NRPN, but the other parameter still showed up as an NRPN.Īfter much faffing about I noticed that the NRPN was just two lines now the MSB line was gone. However, when I added the next Message Converter (mapping a different knob to another parameter), it did not work.

Midipipe manual how to#

Thanks to this thread I figured out how to set up the Message Converter correctly and could successfully use the Pitch knob on the Electribe to control Osc 1 Pitch on the BS 2. Sadly no joy.It's a long time since you had this issue, but thought I should post a discovery I made today when trying to get my Korg Electribe ER-1 to control a Novation Bass Station 2 using MIDIpipe.ĪList is just there to compare incoming vs outgoing events. In other words–a good problem to have!Īs an aside, knobby controllers such as the Novation ReMOTE SL range are relatively inexpensive on the used market, and far more oriented toward control of other devices than an actual synthesizer. Probably not though.That's the downside of having more parameters to work with than available CCs.

You could switch the Rev2 global setting to send CCs and hope one of the knobs that actually sends CCs is assigned to the parameter you want to control. They claim that there are too many controls for the CC format but other companies manage it quite well. Seems like a big waste of all those knobs and buttons being left with a sort of half finished functionality. Other companies manage to do both for every control. Instead it is left with some knobs being able to send CC and some not.

The Rev2 would be an amazing controller if it could just send CCs from every control.

This is one thing that bothers me about DSI.CC/NRPN limitations. I think therefore I've concluded that this isn't going to happen. This seems a little more complex than Midipipe (which in fairness is freeware), but it seems to have confirmed that the Rev2 is spitting out 14bit NRPN data and the poor old Noah can only handle 7-bit CC's - and no amount of converter programmes seem to be able to make them talk to each other correctly. So if Midipipe is sending a 14-bit Expression message and only changing one CC message's value, the target synth would only respond to the changed message while the other would presumably be set to 0.Update! - So I've just tried an alternative modifier programme called Bome Midi Translator. It also sounds like perhaps only one byte is being changed (the fine control only, no coarse control). So as a made-up example, 7-bit Expression messages might be sent as CC2, while 14-bit Expression messages might be sent as CC2 + CC45. AFAIK a 14-bit CC message uses two bytes sent as two different CC numbers - one CC number is the same that's used for the 7-bit CC version, while the other is a higher CC message. It sounds like Midipipe is sending 14-bit CC messages instead of the 7-bit CCs that are more common, especially on older synths.