I can imagine that it's just really trivial. every device driven by NIHA created a virtual midi device with the device name in it (some sort of per-device-unique) (like my MMK3) every device driven by NIHIA created a virtual "- DAW 1" midi device (my KKMK2 + MMMK3) which just collides by the same name on the OS level (damn!) I also think that the Bome stack is complete and capable enough to do the correct job if used correctly NIHA uses another "MIDI stack" than NIHIA (the support told me) All new devices are driven by NIHIA (I have a list) NIHA is the "old" and still main agent. I think the situation is far more easy and less complex (which makes it more idiotic at the same time) They cannot start from scratch because it would break too many things. I think the actual problem is a historically problematic architecture between NIHIA, the controllers and the SW when it comes to instance focus & DAW control.
#M32 offline editor mac driver
While there exists a better driver for Windows - notably multi client capability - ( ) the Bome driver should be easily capable of what is needed. Nah, I don't think the root cause is missing capabilities of the Bome driver or licensing. ) or claim DAW control communication (Reaper, Ableton, Logic. But I believe things could be amended by adding commands to NIHIA that allow to change the routing of the messages: A SW client could inquire which controllers are available (they obviously can all connect simultaneously via the port mechanism) and then request focus (Maschine, KK. The point is, as long as NIHIA creates only one generalized virtual midi port, it will fail with different devices.
#M32 offline editor mac license
As far as i know, the newer NIHIA uses the Bome Virtual MIDI SDK ( ) and i am not sure if the implementation is wrong or if they only have some specific license to only use one virtual midi port for their NIHIA service. It has nothing to do with their own protocol but the MIDI stack they use for NIHA and NIHIA. You can now prepare shows ahead of time, learn the console operation, migrate your XL8 show to a PRO6 or vice-versa and so on – all from the comfort of your room without.I think they know exactly what the problem is. The Midas Offline Editor allows you to create, edit and view show files for either a XL8 or a PRO6 on any Intel-based Apple Macintosh computer running OSX 10.5 or OSX 10.6.
#M32 offline editor mac pro
MiDAS PRO - It employs technology developed from the class-leading XL8, offering the same exemplary sample - synchronized audio performance. You can now prepare shows ahead of time, learn the console operation, migrate your XL8 show to a PRO6 or vice-versa and so on – all from the comfort of your room without access to a console.