What is Reddit's opinion of
MIDI-OX?
From 3.5 billion Reddit comments
➔ MIDI-OX website
By popularity on Reddit, this Service is:
92 reviews of this app found across Reddit:
Your midi controller is probably sending random midi data because of debris buildup on the knob connectors. It probably needs to be inspected and cleaned by somebody who repairs electronics. You can install Midiox app on your computer to see if some of the knobs send random data without being touched, if this is the case:
Mac has Sysex Librarian, which is seemingly an amazing program.
Sadly for Windows we don't have anything as nice, though I like MIDIOx (http://www.midiox.com/)
Basically you just set it up to listen/receive sysex on the MIDI port of your choosing, then you put a MIDI cable out from your synth to the in of the interface, and send. When it's sending you'll see the number going up in the window, and when it finishes the number will stop.
Before you reset/overwrite your patches, I recommend testing that it works. The way I did it was I first backed up my sysex, then on the first patch I just changed the AMP to 0 so there was no audio, then I re-imported it to see that the import worked and my export also worked.
Good luck!
Depending on your DAW, if you bind that MIDI message to a dummy control (e.g. set up a macro knob that doesn't do anything in Ableton and bind the fader to it) it may stop it being passed to other devices.
Alternatively you could filter it out using something like MIDI-OX and loopMIDI. Set MIDI-OX to receive messages from your keyboard and relay them back out to loopMIDI, and set your DAW to read from loopMIDI. Then use the mapping in Options→Data Mapping to handle input Ctrl messages with a Ctrl # of 7 (volume) and set the output event type to Discard and it'll throw the messages away before they get to your DAW.
Personally, I'd go for a can of Servisol Super 10 and clean up the scratchy pot, though. :)
If you have or can get ahold of a midi interface for your computer, hook the ultranova to it (Un-out to interface-in) and use an app called MidiOx to view the incoming messages from your UN. I'd be willing to bet the UN is using that particular CC number for something else, its just a matter of figuring out what and changing it.
Have you got the DIN connectors the right way round on the P95? The OUT plugged into the IN and the IN plugged into the OUT, assuming that the MIO is this? You could try simplifying the problem with Midiox to see if the pc is receiving the midi in any way before it actually comes to setting up Abletons preferences.
Any MIDI that comes to the RP201 on it's MIDI IN port won't necessarily get passed through to it's MIDI OUT. That's possibly why your JX-03 isn't playing any notes from the PC.
Does the RP201 have a MIDI THRU function (either a physical plug or a configuration setting to pass MIDI IN data through to the MIDI OUT port, often called "Soft Thru"). If so then use that.
Alternately if you plug both the RP201 and VP-03 into a computer (via a cheap USB MIDI cable) then Studio One can talk to each of them independently (but make sure you set up the MIDI ports in Studio One - there are YouTube vids for this). The only problem with this setup is that by default playing on your RP201 won't send notes to your JX03, however you can run free software such as Midi-OX which can easily listen for MIDI data received from one port and then send it out via a different one(s).
I believe a program for Windows called MIDIOX can do this, although I use Mac so i haven't used it myself. http://www.midiox.com
For people who need a solution for this on Mac, there is a program called MidiPipe
Do your homework, obviously, but I would like to contribute MidiOx which helped me monitor and track midi messages while doing dev stuff for a different project. Its neat and you can get feedback for signal and note transmission as you test your creation.
One way to rule out whether it's an issue with your DAW or with the interface is to see what MIDI-OX logs when you play keys quickly - my best guess is that your interface is dropping "note off" messages, hence the stuck notes.
I have seen articles indicating a flaw with the cable's electrical interface, which may work with some MIDI keyboards by accident (rather than by design) but even after fixing that problems with dropping longer messages seem to be common.
Personally, I bought myself a second hand MIDISPORT 1x1 and that works properly for me, but it did cost about four times as much as one of those cheap cables. On the plus side, no stuck notes...
So is it just a cable with USB on one end and MIDI on the other? The first thing I would try is disconnecting the cable going into the MIDI in port on the keyboard, so you’re just running MIDI out to the computer. If that doesn't help, here's a link I found that seems like a similar issue to what you are having. I’m not sure if this person was able to resolve their issue, but it'd be worth checking out:
http://www.midiox.com/cgi-bin/yabb/YaBB.pl?board=query;action=display;num=1577131840
One of the first programs I install on all my computers is Desktop Restore. Basically you set up your icons, and save them. Then you can easily restore them if anything get's moved around. It just tends to happen with Windows. Didn't seem to affect the program moving to Windows 11.
http://www.midiox.com/index.htm?http://www.midiox.com/desktoprestore.htm
Which MIDI to USB cable are you using? If it's one of these cheap and nasty ones then that's probably where the fault lies. :( You should be able to see what MIDI messages it's receiving in MIDI-OX which would give you further confirmation as to whether it's an issue with the keyboard or USB interface rather than with your DAW.
Personally, I use a second hand M-Audio MIDISPORT 1x1 for connecting my older MIDI devices to my PC and it works well.
I wouldn't recommend those cables, they are not well made (this article covers some of the issues) unfortunately. It's worth spending a bit more money to buy one made by a reputable manufacturer (e.g. M-Audio, Roland, Yamaha).
In any case, for connecting a USB-MIDI controller to a 5-pin DIN MIDI device you'll need a USB MIDI host rather than a USB MIDI interface.
There are dedicated USB MIDI host boxes that can serve this purpose, however if you have a computer nearby then this is likely an easier (and much cheaper) solution; plug the controller and the MIDI interface into two of the computer's USB ports, and use software like MIDI-OX to route MIDI from the controller to the interface, and then connect the interface to the loopstation via a 5-pin DIN cable.
One general purpose utility I like to keep handy for tracking down MIDI problems is MIDI-OX. You’ll need to, of course, run the MIDI through your PC. It can monitor all MIDI messages and show you what’s going on. Since it works on the MIDI level, it can show problems with timing, voltage, malformed messages, etc., that a serial monitor can miss.
These some old ass 32bit software out there for free that may or may not work, but is supposed to be able to make a computer keyboard (or whatever else you want?) send MIDI commands
There's also some cheap software that'll turn a gaming controller into a MIDI controller. Which just sounds cool.
It might be simple as not using the correct ASIO driver/settings so the sound source is delayed. If not the issue will be your computer more than likely. Be it a hardware or OS issue. It is very rare the controller itself will have any noticeable latency unless it is defective. And if anyone makes a low latency controller it is Akai for sure.
The best way to test latency is to install MIDIOX or similar MIDI monitor and check the controller's speed from there. If you see none you can rule out the controller and controller's driver.
Try setting mod wheel to output to DIN, might stop it being routed through the USB or settings it's min and max value to 0 in the mpk249's
Failing that, you could reroute your midi through Midi-Ox and use it's midi filter to filter out that modwheel cc before it gets to your daw.
Welcome to the joys of windows and multi monitors. It can't keep icons in the right locations for the life of it. I use this super tiny app and it works like a champs for years.
To clarify, you want the pitch wheel to send expression CC data instead?
Pitchbend isn't a CC, so there's no easy transformation to CC data. Also, the wheel is bi-directional, and the default value is halfway (64). The pitch wheel is springloaded to return to this position. Contrast with an expression pedal which is springloaded to return to 0 (or 127 if inverted).
While Reaper can easily do CC to CC transformations, it doesn't do this (and I don't know of any DAW that can).
I would suggest mapping the modwheel (CC1) to expression (CC11) using JS:MIDI CC Mapper. Or simply assigning modwheel to whatever expression is assigned to in the virtual instrument. You could try assigning pitchwheel in the virtual instrument but the facts I laid previously would make it unlikely to work.
If you're really intent on getting things to work take a look at MIDI OX: http://www.midiox.com/ but I'm not sure if even that can do it.
This freeware utility, DesktopRestore, is a life saver.
It adds a right-click shell extension which lets you save and restore your desktop layout. So when Windows inevitably breaks your desktop, putting it back together is super easy. Just remember to save your layout after you make changes. You can identify icons which weren't included in the last save thought the Unmatched Icons choice.
Although I don't use this feature, you can also save multiple layouts, and switch back and forth between them.
This is on windows
you want midi ox and loop midi
open loop midi and create a new midi channel, leave loop midi open
open midi ox and have it listen to your HW midi input, set it to filter whatever you want (there are faqs/help files to work this out) and set the output to be the virtual midi cable you created with loop midi
in ableton select the virtual midi cable as the midi in (make sure to deselect the HW midi in) and pipe your midi out to the Boomstar.
(I've needed to do similar because my midi KB pitchwheel is spazzing out and constantly sending Pitchbend data, tried switch spray to clean the pot but it's still sending crap so I just block the data using the above method)
Well you set the two most common settings. I would look into a 3rd party program that preserves the desktop icon location. I used to have one for some remote desktop users that had multiple monitors, but i havent had to use one in years.
a 3rd party program which you would have to search for, would allow you to save the icon locations and probably one click restore them to the saved places when they get messed up. im not sure you can prevent them getting messed up without narrowing down the cause a bit more and if it is a game, good luck getting the game deves to fix it. easier to work around.
EDIT: this is the one i used many years ago. http://www.midiox.com/desktoprestore.htm
Your interface only has 2 outputs and 1 headphone jack (and I'm guessing the headphone jack mirrors the stereo output on the back.) You can have the click track and music in mono though (the "hard pan" method) You need more outputs for stereo music + other tracks.
The only possible solution I can think of is MIDIOX I never used it and can't help you. You'd have to program MIDIOX and be knowledgeable of Remote mapping codecs. Good luck with that. Sadly, the easiest solution would be to buy a bunch of knobs (or MIDI pedals if that's your thing)
Does Ableton's MIDI indicator light go on when you press anything on your keyboard? If so then you just haven't mapped it yet and need to go into the MIDI mapping.
Not sure if you are on Windows or OS X but if you are on Windows you can download this tool: http://www.midiox.com/
It's a bit complicated but it's relatively easy to see if anything is working or not. If you mash your keyboard with that program open it should show you the actual MIDI commands from your keyboard.
i think that a program like midi-ox would help.
i think that what you'd do is have to send the midi signal out thru the d550 into a midi interface that's plugged into your computer. from there, i am pretty sure there's a way to essentially view the midi signal that's being received.
i haven't done this, but i used midiox a while back to load tx81z patches and it worked great. i'm pretty sure i encountered this usage of midi-ox somewhere in my research.
You can try using http://www.midiox.com/ to see what is being sent from the BCR2000.
edit: I'm at work right now (and will be til super late ... because of meetings with people in other countries ... /nothappy). But, I'll see what I can dig up.
No program for windows 7, and all the advice on the net says to download: http://www.midiox.com/index.htm?http://www.midiox.com/myoke.htm#Download
This doesn't work though, as the bloody installer is "interrupted"
i've never used expressionpad, but when i was setting up a wiimote input for reason, i had to use midiyoke to dump to a midi channel that i could pick up in reason. i haven't messed with this in years, honestly, so i don't quite remember how to set it up... i also might have needed to use midiyoke because it worked as a standard midi playback device addressable in glovepie...
basically, i guess, what software is handling the midi on computer, being received from the ipad? you can use midiox to see what kind of midi data is actually being received which will undoubtedly be useful in tracking down the disconnect.
They will send you the update file and you need to dimitnthru midi. If you have an audio interface it will most likely have midi.
If not they make a USB to MIDI converter called modi sport uno @$30?
There are also some free utilities that work which I used. I have a gew but Midi OX works well
What is your MIDI footswitch? As long as it's sending MIDI continuous controller 64 messages it should work, assuming you've ticked the "Track" checkbox next to it in the MIDI Ports section of Ableton's preferences. Do you at least get a little activity light blinking in the top right corner when you press and release the pedal?
If you need to double check the messages the footswitch is sending, MIDI-OX can display these for you.
If you run MIDI-OX, what does it report when you press and release the pedal? You should see MIDI CC 64 going between 0 (released) and 127 (pressed). You can use the Alesis editor software to remap the pedal to other MIDI CCs so this will at least let you check to see whether the keyboard is still sending standard sustain messages.
MIDI-OX still exists, is still free, and is still powerful. :) If you need a virtual MIDI cable then loopMIDI is good and free too and works with 64-bit applications.
I would say it's probably more straightforward to remap the controller using your DAW's native control mapping settings (or on the controller itself) than rely on additional software in the middle to translate for you but I'm not too familiar with Reason to know how tricky it may be there...
Try using http://www.midiox.com/ to see if any MIDI notes/control changes are getting to your PC at all. It'll show a continuous stream of note information if things are going well - and on which channel that note information is being sent on. If it does, then the problem is somewhere with your reaper setup. If not, then you know the problem is beween your kit and the presonus.
Here's a walkthrough to set up MIDI-ox. https://www.youtube.com/watch?v=VXRHgFfeIIk
If you use MIDI-OX does that show you anything meaningful about the information coming in? Do you see the right sequence of note on/note off messages, or is it indicating a problem?
Is your USB MIDI interface cable something like the one in this article? If so it might be worth splashing out on something by a reputable manufacturer (e.g. M-Audio or Roland) as those very cheap cables are not well made at all, sadly.
Edit: Sorry, I don't know my lefts from my rights apparently, the MIDI activity light is in the very top RIGHT of the screen..!
Do you know if the controller works in other programs? Have you tried unplugging it and plugging it back in in case it's stuck in some state (e.g. Edit mode?) You can apparently perform a full reset of the keyboard by plugging it in when holding the Octave "-" and Octave "+" buttons together.
To rule out an Ableton issue, do you have some MIDI monitoring software? On Windows MIDI-OX is very good, if you run it and select your keyboard in Options->MIDI Devices you should then see note on and note off messages in its output window when you play the keys, just to ensure that something is coming through from the keyboard.
What was the problem you were having with the USB MIDI interfaces? Did they get detected by your computer (and have working drivers?) Bear in mind that the MIDI coming out of your Clavinova is going in to your computer, so you should connect the MIDI OUT of the keyboard the MIDI IN of the USB interface.
If you're on Windows then MIDI-OX is a very useful utility for displaying what exactly the MIDI interface is seeing, when you run it if you click Options->MIDI Devices you should be able to see your USB interface in the "MIDI Inputs" list and be able to select it, at which point pressing keys should show MIDI messages in the Input Monitor (View->Input Monitor).
Once you've actually got your computer talking to your Clavinova I'm not really sure what to recommend on the software front, though, at least for free - what sort of software did you have in mind?
If you're on Windows then you could try using a combination of MIDI-OX and loopMIDI. You'd create a virtual MIDI port with loopMIDI and then set up MIDI-OX to receive messages from it and send output to the Casio CT-650, then you'd set the software that's producing the MIDI messages to send to the virtual MIDI port. Within MIDI-OX you could then use a combination of Patch Mapping rules to change General MIDI patch numbers into ones suitable for the CT-650 and Data Mapping rules to remap percussion note events from General MIDI channel 10 to the corresponding percussion note number on MIDI channel 4 on the CT-650.
You may also wish to set up Data Mapping rules to also choose which incoming MIDI channels (other than 10) are mapped to output on 1-3.
Presumably your MIDI controller is sending one continuous controller message when you press the pad (with the velocity mapped to the controller value) and a second message when you release it (with the controller value set to 0)?
One solution could be to use some software to filter MIDI messages before they reach Ableton, throwing away the continuous controller message with a 0 value. One way way to do this is with loopMIDI and MIDI-OX. Create a new virtual MIDI port using loopMIDI and then set up MIDI-OX to receive from your MIDI controller and transmit back out to the loopMIDI virtual MIDI port. Then, in Options->Data Mapping add a mapping that takes Event Type Ctrl, set the Ctrl # min and max to 108 (to match your controller's CC number), set the Amount field's min and max to 0 and the Output event type to Discard. If you then enable the data mapping it will discard any CC 108 messages with a value of 0.
Ableton Live would then need to be set up to receive from the loopMIDI virtual MIDI port instead of the controller's regular MIDI port.
Usually when people say "I´m getting 7ms latency", they are most likely not taking about MIDI latency, but about their actual, overall, latency.
Meaning the time it takes from them hitting a drum pad (in your example) to the time when they hear back the sound from your speaker - that is the time it takes from the MIDI being sent&processed by your plugin/sampler, and a "one-way" trip of digital-to-analog conversion when Reaper spits back the audio through your interface and speaker.
the numbers Reaper shows in the top right are usually "round-trip" latency, meaning they show a full "trip" of an (audio) signal from the analog domain into your computer, any processing done in there being applied, then tacking the trip back out from digital to analog and to your speakers.
​
there IS something like MIDI latency though, of course, as even for 30 year old standard, it can be done better or worse on the hardware side - these latencies are most likely going to be absolutely minimal, but I believe you can test these with a programm like "MIDI OX", which was designed to monitor that kind of thing:
Does this behavior coincide with something you might have changed in your DAW? Does it happen with every note across every octave? If it happens only on specific keys then your keybed might need some cleaning.
If it’s a software issue, then I suggest installing a midi listener (Mac, Windows). This tool will show the midi stream in real-time so you can troubleshoot the root of the problem. For example, you might see that the doubling of notes does not coincide with the midi stream from you keyboard.
MIDI-OX is a really awesome program that makes it pretty easy to save and load patches from your computer (http://www.midiox.com/). Probably a good idea to replace the little memory battery in the DX7 sooner than later as well - no fun losing all of your hard patch work ;)
Enjoy!
reaper has no trial version but 60 days full version and after the evaluation period a nag screen reminder to pay and this month https://splice.com/daws/38929163-live-10-lite-vst-by-ableton is free and you can insert virtual instrument rewire ableton lite in reaper to use the session view of ableton in reaper if you route the midi out of ableton into reaper tracks with https://www.tobias-erichsen.de/software/loopmidi.html or use http://www.midiox.com/ to connect your midi controller to both apps so with the midi map from ableton you can do lots of things in reaper and after 60 days you decide...
there is no "tuning" it's all about the pitchbend midi message.
Pitch bend has a 14-bit range, from 0 - 16383
8192 steps in each direction, while middle is neutral
-8192
0
8192
if your controller happens to send a value of -450, the track in ableton is set to -450, if you play computer keyboard or anything else it will always be out of tune. (-450)
this is the reason you have to reset the value by moving the pitch wheel, otherwise disconnecting or changing input method will not be in tune.
you could simply create a new song and try, it will be at 0, till it receives a faulty message.
​
you can realtime log all midi messages with a monitoring program.
on a mac use midi monitor, on a Pc use midi-ox, they are both free.
​
what you have to find out is where this message comes from
but it will almost certainly come from your controller pitch wheel.
move that one while monitoring and observe the messages.
knock on the table/controller, see if vibrations send unwanted messages.
you could then try to clean the pitch wheel encoder with contact cleaner, or simply disconnect the pitchwheel inside.
this way you can still use your controller, it's not the end of the world not having a pitch wheel.
> With your setup do you experience noticeable delay from the USB Midi?
No, nothing noticeable. I'm using Ableton.
Maybe start off by closing Reaper and using a MIDI monitor to test your incoming MIDI (http://www.midiox.com/ is one for PC, https://www.snoize.com/MIDIMonitor/ for Mac)
you can rewire lite with reaper and with http://www.midiox.com/ and https://www.tobias-erichsen.de/software/loopmidi.html connect your midi controller to both apps to select midi clips session view in Reaper.
check to see your computer is receiving midi with this tool outside of S1
If you pc shows it's receving midi on this then you need to set up a midi keyboard in S1.
https://www.youtube.com/watch?v=FiNqa2PUZG8
https://www.youtube.com/watch?v=cfhaWe8HuOw
2 tutorials
I probably could use a DAW, but I think I'd probably use any of the numerous non-DAW programs that send customizable MIDI signals. One example is MIDIOX. Of course that being feasible depends entirely on how the synth maker has set up the synth. I'm trying to find out which synths are set up to do what I want. I know almost all synths take note on and note off MIDI signals but MIDI has a ton more possible signals and I'm looking for a synth that can receive these signals and (for example) behave as though a specific knob (depending on the signal) were being turned.
On a PC loopMIDI and MIDI-OX are recommended on this page from Ableton.
I have only a little experience with PCs and don't know much about either loopMIDI or MIDI-OX but I trust the folks at Ableton know what works.
MIDI-OX has it with a data mapping function
This isn't an answer to your question, but to avoid confusion in the future: MPK Mini MK2 is not a synthesizer. It's a MIDI controller. A synthesizer is something that synthesizes sound, which the MPK Mini does not do. It just sends MIDI messages that tell other things (like, in your case, a synthesizer or sampler in your DAW) what to do like play notes when you play the keyboard or affect parameters when you turn the knobs. So the synthesizer you play could be a VST or one that comes with your DAW, but the keyboard you got just tells those synthesizers what to do.
As far as your questions goes, I've never used Pro Tools much myself so I don't know what within the software could cause the problem. I would recommend downloading MIDI monitoring software (MIDIMonitor for OSX or MIDI-OX for Windows) to see if your MPK is sending the correct data (e.g. Note On when you press a key and then Note Off when you release it). I'd also recommend downloading another DAW (most of them have free trials) and testing it out there to see if you get the same issue. It seems like your controller came with Pro Tools, but that doesn't mean it's the best software for you (IMO it's a bloated mess, but that may just be me), so you could benefit from trying a few out to see what feels best to you.
I have an Akai MPK-49 MIDI controller that's plugged into my computer via USB. It worked fine until last week, when my computer won't recognize any of the inputs. Everything is showing up as being registered on the controller's screen, but nothing's happening on my computer. The issues started in Reaper, so I downloaded MIDI-OX to try to get to the bottom of it, but there weren't any inputs showing up in it either. Any suggestions on what to troubleshoot? I've tried reinstalling the driver, disconnecting/reconnecting the USB, to no avail. There was one time a few days ago when it randomly started working for a few minutes, but it hasn't worked since.
From what i see in the manual, when you press a flash button it will send a note on message with a velocity equal to the fader position, possibly when you release that flash button it sends a note off message. It doesn't send a midi note if you only move the fader.
This data should be able to be used to control execs in MA, but if you know exactly what messages are sent then you can be more specific.
I'd suggest plugging the console into a computer using a USB midi interface (doesn't need to be fancy, the cheap one's are fine). If you use MIDI-OX, make sure you're listening to the correct input, and then open an input monitor window. This will basically show the raw midi data as it's being received from the LC-24. Once you know what's being sent and when, you can work out how you want to use it in MA.
I would like to reply to my question as I've figured it out. Hopefully this can help someone like me in the future.
​
After debugging the MIDI signals with MIDIOX it appears that with the KeyStep you have to press pretty firmly into the keybed to trigger aftertouch.
Ableton was correctly sending the signals the entire time, but I just wasn't pressing hard enough to send the aftertouch signals.
Good thing the keystep is built like a tank, because you have to press darn hard to trigger this.
​
I hope someone can learn from my experience!
Is your computer running windows? Midiox (http://www.midiox.com/?http://www.midiox.com/moxdown.htm) is what most people use for this sort of thing on windows. With it you can choose an input and output midi device (keyboard is input, midi adapter is output) and it’ll pass the data through
If you're on Windows, you can use MIDI-OX to generate a NOTE-OFF event immediately preceding every NOTE-ON event... Alternately MIDI-OX can instead generate an ALL NOTES-OFF... These will be generated in real-time, btw...
​
MIDI-OX also has a native midifile player...
​
I cannot here go into the exact specifics of how to implement the above changes, but I vouch that it can be done...
​
I'll send you the entire source code for my project so you can take bits from it as you please, it's pretty self explanatory. - https://pastebin.com/L4NAVBnk
I have stopped working on the project as I was having some hardware issues (not related to the MIDI specifically) and it was becoming a bit of a hassle in the end. But as for what the idea was, it was this: https://youtu.be/HjmJbCADqYo
From the code you only really need the MIDIUSB library (If using a Leonardo or Pro Micro (or any other board with a 32u4) which I HIGHLY recommend as it's basically just "plug 'n' play" like a commercial USB MIDI device. Don't need to mess about with creating a MIDI port via software and blah blah blah and if you're going to use potentiometers the "ResponsiveAnalogRead" library smooths out the readings a bit so they're a bit more accurate. Both libraries are available online, can't remember where I got them from exactly but if you can't find them let me know and I'll ZIP them up for you.
Those libraries and the function on line 215 that sends the actual MIDI data over the USB:
// Send the actual MIDI commands void sendControl(byte channel, byte control, byte value) { midiEventPacket_t event = {0x0B, 0xB0 | channel, control, value}; MidiUSB.sendMIDI(event); MidiUSB.flush(); }
If you're using WIndows you can use MIDIOX to see which channels and such are being sent by the device. Very handy tool! http://www.midiox.com/
I hope this is of some help! If you have any more questions about the code or in general I'll do my best to answer them. :)
You need a midi utility to transform one input two two different outputs (one for each application), and a midi virtual cable to connect from that utility to your applications.
I don't know what operating system are you using, but if you're on Windows, the midi virtual cable I use is called loopMidi ( https://www.tobias-erichsen.de/software/loopmidi.html ). You can create as many virtual cables as you want.
As the midi utility I use it'scalled MidiOX ( http://www.midiox.com/ ).
The idea is use your midi controller as an input in MidiOX, then filter/transform the messages if you need to and forward them to two different midi virtual cables configured as outputs (let's called them loopmidi1 and loopmidi2). Then, on your first application use loopmidi1 as an input and on your second application use loopmidi2 also as an input.
If you're on a Mac I suppose the idea is the same, but you will need different software (I'm sorry I can not recommend any as I'm not a Mac user).
Hope that helps.
I have the B-3 V and load it into an empty project and I just get activity on channel 1 when I play notes on my MIDI controller. Cubase shouldn't be sending anything on 16 unless you set it up to do so, which in an empty project with just the B-3 V on it, I assume you haven't.
Do you have other MIDI devices attached to your system? I would try disabling them and see if you still see activity on 16. How are you monitoring this? Are you using MIDI-Ox to see the activity on 16?
Hey, jumping on this thread even though the original question was answered (figured it was better not to open a new one since the specifications I have are exactly the same ones as the OP, Kawai ES110 + Scarlett 2i4). I am trying to connect the Piano to the Interface through MIDI - bought a standard MIDI cable and connected one end to the OUT of the Piano and the other end to the IN input of the Interface - though I'm not getting anything (testing the MIDI input with <strong>MIDI-OX</strong> but I'm not getting anything).
​
Does anyone have any idea of what should I do to get this working properly? Is there any drivers I forgot to install before going for it?
Thanks!
Could use http://www.midiox.com/. Set the Linnstrument as the input in Midiox, download something like loopMidi to create virtual midi ports, then map the Linnstrument signal inside midiox to the two new virtual midi outputs. Inside Ableton use on of the virtual midi ports as it's input, and in your MPE softsynth use the other virtual midi port.
not necessarily the solution to this problem, but I recommend 'Desktop Restore'. You can save desktop layouts and restore them at wish.
Are you recording the parts using a midi keyboard? I had a similar issue where the pitch of my notes was suddenly shifting up a half-step. I used Midiox to analyze the signal coming from my keyboard and discovered that my pitch bend was randomly sending data as if I was tweaking it while playing.
That will help you find problems in the complete end to end signal path, but debugging the USB converter could be tricky. You will probably need an oscilloscope and a reference to the MIDI signal specs. That might be more trouble than it's worth, especially since those kinds of keyboards are a dime a dozen on the second hand market.
If you just need to input midi notes, the midiplus X4, nektar gx49, or m-audio keystation would probably be good for you.
The way the blofeld talks to the outside world is very clunky and idiosyncratic and a PITA really.
I've been hunting around for good software to use with the Blofeld and have settled on three essential tools which pretty-much do everything:
Firstly, download Spectre from the Blofeld site and get familiar with it. The button labels are a bit cryptic (ie you click "Upgrade" to send any MIDI file that isn't sample data, and "Transfer" just to send sample data) but once you get comfortable with it then it's fine. It's also essential if you want to play with samples.
I'd also strongly recommend MIDI-OX for backing up your data via SysEx and for general MIDI tools and This Blofeld Editor which has a decent editor and more importantly is a great patch organisation tool. Both of these tools are also quite cryptic, ugly and old-school (ie clunky) but once you get your head around them they're invaluable.
If it is remembering the monitors identities (3 identical, right) then just swap them around. BTW I use displayfusion to manage the backgrounds and taskbars and also http://www.midiox.com/index.htm?http://www.midiox.com/desktoprestore.htm to make windows remember where I put my icons, you may be having the same problems
You can factory reset by holding select while you power it on. This board only advertises octave transpose, but maybe there's a hidden step transpose? Is your data slider all the way down to rule out some strange CC mapping? Factory reset will clear these controls, regardless...
If that doesn't fix your problem, use a MIDI monitor program on your computer to see if the board is outputting pitch bend control. Here are some free MIDI tools to allow you to view the MIDI stream from your controller...
MIDIox Windows
Snoize MIDI Monitor OS X
If you see continuous pitch bend messages, then you will need to crack the board open and check your pitch bend internals. Does the pitch wheel move before you feel the spring inside want to engage?
If you don't see pitch bend messages, then WTF. Check your reference pitch?
I like to use desktop restore to save my icon layout, and be able to restore it from a desktop context menu when (if) they get goobered up.
Midi-Ox? I think that is a program to replace midi codes by other midi codes. It sits between your MIDI in/output and Traktor. For example, Traktor cannot do anything with "Program Change" codes; only note codes and "Control Change" (CC) are usable. So "Program Change" has to be replaced by one of the above to be usable in Traktor.
That said: I've never been able to get the non-free Midi-Ox or one of the other similar programs to work.
BTW this looks like a reasonable page explaining what kinds of MIDI messages there are.
If you have a MIDI interface of some sort, you can download MIDIOX and see exactly what it's transmitting.
If not, some gear will indicate the presence of MIDI messages (regardless of channel). Of what I have, my TX81Z, MJC8 and BCR2000 have LEDs while my Mopho shows a black dot (inside the MIDI settings menu). If you have something similar, it'll let you see if a message is sent on keypress/release.
I'm going to guess your dynamics range is being compressed, to verify install http://www.midiox.com/ and play fortissimo, if I'm right your Data2 NotOn values will not be above 96 as they should (https://en.wikipedia.org/wiki/Dynamics_(music)) but instead much lower, in the 60's range (midiof returns hex so 96 = 60 and 60=3C) so as a result your notes become more even in the digital piano because their loudness varies between a smaller range of values.
OK, lets make sure the iconnect is actually working since it's probably not an FL problem.
Download and install MIDI-OX, it's the 3rd link on that page. It's a useful MIDI monitor/transformation utility.
Close all open programs and launch MIDI-OX.
Click the MIDI device icon and select your USB MIDI interface. I've selected my TouchOSC Bridge in this picture. Click OK. If you don't see your device close MIDI-OX, unplug and replug the USB end of the MIDI interface, restart MIDI-OX
You might need to open the MIDI input monitor window in MIDI-OX.
You should now see note-on and note-off messages in the MIDI input monitor window when you play the Casio keys. If you don't, try switching the MIDI cable plugged into the Casio.
Let me know what happens.
Are you on OSX or PC? I use a late 80's Roland D-50 synth as my MIDI controller, and one quirk it has is that it sends an "all notes off" message that prevents sustain pedal from working with Reason (though it works fine with the built-in sounds).
What I did was use MIDI Monitor to track down what the offending CC number was, and then use MIDI Pipe to filter out that message. You may be able to at least get a workaround going with that method.
If you're on PC, you should be able to both monitor and filter the MIDI with MIDI-OX. Open up Midi-OX or MIDI Monitor before you open Reason, and then once the problem starts showing up, look at MIDI-Ox/Monitor to see what is going on.
It's enabled, which is good. I'd try toggling the clock setting and set a synth to clock slave to see if that's an issue.
Also, try MIDI-OX and see if it can receive MIDI in and send MIDI out http://www.midiox.com/ so we can determine if the issue is Reaper or not.
Note this only works on PS4, PS3, X360, and Wii. The XBOne does NOT work this way.
You unfortunately have to run it through a PC.
Get a USB to MIDI cable, as well as the RB3 MIDI Pro adapter. http://www.amazon.com/Cable-Converte.../dp/B0017H4EBG
Then you need a program called: MIDI-OX http://www.midiox.com
You then need to configure MIDI-OX to remap the USB MIDI to the other adapter. This video will walk you through it.
Yea, a computer would work fine. You just need an audio interface to connect the ESQ-1 to it... but really, if you go that route, might as well learn how to do the sysex patch saving method, as it can be used on a plethora of other synths. Essentially, you send sysex data from your synth to some program that can read it (like Midi OX). That data can be saved as a file on your computer, re-uploaded into Midi OX at any time, then sent back to your ESQ-1. Nevertheless, if you want to just do the tape out method, you can record into Audacity, or something else.
This is the writable cartridge you'd be looking for. There are other cartridges out there for the ESQ-1, but a lot of them don't allow you to write anything to it. They're semi-rare, but if you keep an eye on ebay or craigslist, you might see one pop up.
I haven't used EZ Drummer or the like, but I have some nice drum samples set up with Reason and Edrum Monitor was handy as fuck for me with midi drumming. Your kit sends a set midi note(at least mine does anyway) so changing which one it sends with it and saving presets is good if you like to fiddle around with different type of drums and samples. Messing around with orchestral percussion can be a lot of fun.
also midi yoke
If your on windows you can use Midiox to check out what messages your midi controllers are sending.
Have you tried blowing out any dust using a can of compressed air.
And if there not under warranty anymore you can open it up and clear out any dust.
To back up the positions of your desktop icons, use this:
http://www.midiox.com/html/desktop.htm
Many times e.g. when starting a fullscreen game for the first time, or updating your graphics drivers, it will change your desktop resolution and muck up the icons. This solves that... and OP's problem.
If you have a Mac, download MIDI Monitor (it's free) and capture some MIDI data coming into the computer. If you are on a PC, I guess you can use MIDI-OX, but I'm unfamiliar with it.
There is software that lets you turn almost anything into a midi signal. I once had the pedals of a racing wheel game controller as an ableton controller. It used this when I remember correctly: http://www.midiox.com/myoke.htm and something like this: http://www.otk.it/mjoy/. But I'm not a 100% sure, it's been over a year ago and I didn't use it more than once or twice. If you Google something like "joystick to midi controller" you'll find plenty. Then just set it up like any other midi controller in Ableton.
try a different midi sequencer than ableton. Or put http://www.midiox.com/ in there to see if your events are coming in at all and if you're getting flooded with the dumb "I'm really here" events that can come every couple milliseconds :O
reinstall the midi interface's driver - drivers on cheap interfaces are notorious. If this fixes the problem, get a better midi interface.
read through your roland's manual (if you've lost it, it's on roland's site) It's painful, but it will save you grief in the long run. You should know how to set which channel you're sending on, how to set local control off, how to set it to listen on all channels, all the control filtering it's capable of, etc, etc.
good luck to ya!
I don't know of a tool that does something graphicly, but I used Midi OX for testing in the past. It will show you data coming in and going out of the device.
I'm not sure if it's helpful or not.
A controller needs to send the correct midi event information to a sound module. That means the padkontrol needs to send correct out the right midi notes on the right midi channel. If you want to automate the triton Knobs you can do this with midi control change info. You can find this information in the manual, or you can use a computer to find how to set up stuff like this. For example, suppose I want to trigger drum hits and need channel and note information on the Triton. Plug in a midi interface on the triton, start up the incredibly useful Midi-Ox or a DAW then record to see the info. Record note presses and twist each knob, read the midi event info, (notes and cc changes are both midi events), then jot down the info numbers and midi channel. Read the padkontrol manual for a means to edit what it sends out, make the midi channel and midi notes match.
For drum hits, find the notes you want and set your Padkontrol drum pads to output those notes. (It also helps to set the velocity sensitivity of the controller so the trigger sounds best. I am sure the velocity settings are in the manual)
Put a computer in the mix to sort output/input details to get gear controlling other gear. Then you can make the settings on the controller match the sound module. Read the manual on your gear. Learning how midi works takes a bit of trial and error. Have the manual open, a pen and paper handy, and pay attention to the signal chain while running the controller through the computer.
EDIT: Rewritten to make it more clear. RTFMMF. http://www.midiox.com/
I've been designing a simultaneous EEG/MIDI acquisition script with some code from http://www.midiox.com/ I don't have it finished yet but it seems like it would fit your bill. The MIDI acquisition seems fine and you can do MIDI output too I believe. It's worth a look.
If you were able to map controls in Mixxx and make them work, then it most certainly is not a hardware issue.
I just did a quick google and it looks like traktor and the x-session have a lot of posts from users having similar issues.
One of the first forum posts I followed said to use this program to see exactly what signals each control is actually sending.
If you want to press one note and have it trigger several instruments, then use the combinator, or get MidiOX and Midi Yoke and use it to route your keyboard to multiple channels/devices and then feed those into Reason.
Edit: oh wait, you're on a mac. sorry
Open up MIDI-OX, connect to your controller, and then twist the knobs around. The program will show you all the MIDI messages being sent. Combine it with MIDI-Yoke (same website) and you can patch MIDI connections around however you like, and it even lets you intercept and change certain messages.
The other way to answer this question is that many manufacturers of MIDI hardware have a technical document describing all of the MIDI messages a device will send. I'm not sure which knobs you mean when you say "parameter knobs", but it appears from the document that most of the knobs send messages.
midi yoke (virtual midi-port) + midi ox (sending midi clock) http://www.midiox.com/ together with wacNetworkMIDI (v1.5.0) http://chippanfire.com/software/ works pretty stable for me. this setup also allows to sync more than two laptops
>I believe it was Midi In and Out, though I'm not positive.
Double check. IIRC, these are not program specific, but universal to your computer. The ins/outs should be named the exact same thing in both reason and ableton (though the controller name itself may change). Since it works with reason, this could clue you in to which ones to pick in ableton (perhaps there's even an option besides "axiom 25 classic which will have your appropriate ins.)
>I've had it on presets 18-20 mostly because that's what the tutorial said to use.
true, but he was also using the axiom 61. I would try to unplug it / reset it and plug it in. Use whatever preset it has by default (or just go back to 1 in case it saves your last chosen preset as default)
If all else fails, you can always try midi yoke. Monome community uses it to hook their gear up to max/ableton. It might be a workaround for your keyboard (should be pretty straightforwar, hopefully. specific yoke steps are a bit out of my knowledge base). You can find midi yoke / midi ox here: http://www.midiox.com/index.htm?http://www.midiox.com/myoke.htm