garageCube

[mowgli_uk]

I'm trying to map my xone4d for use with modul8 and I'm finding some strange problems.
Basically the buttons on the 4d work ok if I map them to the media bank or things like the transformer switch but if I map them to a layer switch they don't work. The correct midi numbers appear there when in MIDI mapping mode but they don't work. Is there a reason why modul8 would behave differently depending on the interface switch?
The xone 4d manual states that the buttons are sending note on message on press and note off on release but other buttons only send note on and they behave the same.

Any clues would be greatly appreciated!

[mowgli_uk]

I still haven't resolved this, any clues?

[The Midi Thief]

I've had controllers that have behaved like that and where I couldn't configure the midi messages in the controller. In that case I think I mapped it through a custom module. I can't remember if I did just made a toggle button or if I did the toggling in code by reading the midi value and setting a value to true or false every time the button is pressed on the midi controller.

Have you checked in the manual if you can configure the midi messages on your Xone:4D? There are usually ways around it. You could probably solve it in MidiPipe too.

Also check the incoming midi messages in Modul8 to see if there is any other value that differs when you press and when you release the button. If there is another value that differs you can use that in a custom module.

Let us know how it goes. I'm interested in the Xone:4D.

[mowgli_uk]

Thanks for the suggestions.

The Xone doesn't allow for much configuration of it's MIDI messages at all.

I've spent a fair amount of time trying to resolve this with Midipipe to no avail. Midipipe allows you to change note on/off messages to CC but for some strange reason only globally, as in ALL notes will become a single CC which is pretty useless really.

I've also had some very strange results when monitoring what MIDI messages are coming out of Midipipe and which ones are being received by Modul8 in the PrintDirectEvent module, they are often different!

I've managed to get all kinds of strange behaviours while messing about with Midipipe but no useful ones ie. I can switch layers on but can't switch them off!

I've been suggested to look into bomes but I had a quick look at its documentation and it looks extremely complicated (and expensive!) to do something which initially should be quite simple to do. To be honest I'm not even sure if it would do what I want reliably.

The module route is probably the most efficient and cost effective. I don't have much experience at all making modules but I'll give it a go as I HAVE to get this working! I've been experimenting over the years with the perfect set up to do AV reliably and I thought the Xone4D was THE SOLUTION. If you have any tips regarding how to create such a module I'd be grateful.

I have to say that I am annoyed with the fact that something theoretically simple and straight forward like using a pretty standard piece of MIDI equipment with Modul8 becomes such a painful experience, specially when EVERY other MIDI enabled software I've tried with the Xone worked straight away with no headaches or strange behaviours. I can understand why something like a launchpad or APC40 have certain issues when working with Modul8 but the Xone?

[The Midi Thief]

I can draw up a little module skeleton for you tonight when I'm in front of my other MBP. It should be a fairly simple deal. Since there are at least two ways to achieve this you might want to PM me the midi data you get out from PrintDirectEvent when pressing an releasing the button.

[mowgli_uk]

That would be great thanks!
I'll pm you this evening.

very much appreciated.