|
||
Title: THE FUTURE OF MIDI-OX??? with Ableton PUSH 2/3 Post by pattherat on Feb 13th, 2025, 5:48am is this the end for midi-ox .... ??? i.e no more future releases? I was working on converting a PUSH 2 into a generic MIDI controller, by mapping CCs and notes to other thingies, but MIDI-OX won't respond to notes below 32, thus preventing data transform maps being used on the top row of the push 2's combo knobs/buttons (notes 0 -12). Dammit. A few simple changes to the C++ code if note >=0) { } instead of: if(note>=32) { } and you'd have a surefire, world-wide winner!! (maybe) ;-) |
||
Title: Re: THE FUTURE OF MIDI-OX??? with Ableton PUSH 2/3 Post by Breath on Feb 13th, 2025, 5:45pm Hi MidiOx works for all Midi values, but you can program it to filter out a range of Notes that are sent to a Midi Output. Check in the Input Monitor (check that it has "Monitor - Input" at the top of the window). This only shows the raw Midi data coming in to MidiOx from all connected Midi Inputs. There is also Options / Midi Filter... that can filter out Midi data so it won't appear in the Input Monitor Very useful to filter out F8 Midi active. But this Option will not filter out a range of Notes sothat won't be the problem. There is not point checking a datamap as that only works on the Midi data once it is in. So if you are not seeing notes below 32 then the Push is not outputting it or it is filtered before MidiOx sees it. I checked with a synth (Hydrasynth) that can change the Octave of the keyboard. MidiOx sees Notes on any channel from Note 127 down to Note 0 Let me know how you get on. All the best Royce |
||
MIDI-OX User Forum » Powered by YaBB 1 Gold - SP 1.3.1! YaBB © 2000-2003. All Rights Reserved. |