MIDI in from hardware in Max for Live?
Hi all –
I’m trying to write a patch for my new Midifighter 3D that will let me trigger combos.
Im running into the most basic of problems though –
Outside of Max for Live (in Max 5) I can parse midi from the Midifighter fine.
Inside M4L I cant get midi from any device – any device I try gives an ‘error opening device (MIDI HARDWARE)’ message.
Is it possible to monitor the MIDI output of a device in Max for Live, or do I have to use it in Max 5 and run the 2 programs side by side?
Thanks in advance,
not sure why you get that error, but to get midi from a device into a M4L device, the device needs to be on a MIDI Track and you need to arm recording on that track so the MIDI gets to the device.
You can also investigate using Control Scripts and the M4L API Object model, but I’m not sure there’s a control script for that controller.
Thanks Peter –
Its a brand new model of controller, so I doubt there would be a control script.
Also, even on a MIDI channel I get the same error – midi mme error 7 opening midi inputs and outputs. I think the MIDI will come through the channel OK, but im looking to parse the midi globally from the hardware (so to constantly monitor, by hardware device rather than ableton channel)
I think you’re a little confused here; you cannot directly access other midi ports besides the midiin object which M4L provides in Midi effects. That’s because Live is in charge of the way midi in & output is handled, not M4L.
Also; you don’t need controller scripts in Live perse to get the controller to work. Controller scripts are basically templates which tell Live what to do based on specific midi input. But that doesn’t mean that you can’t manually midi map everything yourself (for example).
As such I’d suggest to start by double checking that Live is receiving the right midi data and then use midiin in the M4L patch to process it.
I made a patch for a logitech extreme 3D joystick for a friend and chose to make a standalone version via IAC so that some controls (like a scale chooser for example) could be mapped to a controller. I can post the patch if you want to. I started with a MFL version before hitting this mapping problem and don’t remember getting the ‘error opening device (MIDI HARDWARE)’ message using HID…