MIXVIBES Dj Community old forum

a crap ^^
btw is this xml stuff as nasty as python when it comes to tabs and formatting?

FO!!! xml-beautifier: this document cannot be processed... AAAHHH!!

Almost there, which out do I use to indicate a pad is playing, and will it conflict with padloaded?

Is there a simple permanent NOTE ON command ? I need to revise my mapping for 2.50RC as my trickery with notes works no more.

discopex wrote:Is there a simple permanent NOTE ON command ? I need to revise my mapping for 2.50RC as my trickery with notes works no more.

I am with you discopex.
Would it be possible to get an updated list of MIDI map commands for input and output
Also an example for the format used on the following features stated on the RC release.
- Provide MIDI-macros mappings, allowing multiple simultaneous commands behind a single control.
- Allow mapping of shifted MIDI-outs.

I know it is just RC so I am testing.

discopex wrote:Is there a simple permanent NOTE ON command ? I need to revise my mapping for 2.50RC as my trickery with notes works no more.

What do you mean? What doesn't work anymore?

sylMV wrote:

discopex wrote:Is there a simple permanent NOTE ON command ? I need to revise my mapping for 2.50RC as my trickery with notes works no more.

What do you mean? What doesn't work anymore?

As I didn't know how to light up certain pads, I set the mapping to have note on depending on key lock state - the note was on whether the state was true or false. In 2.5RC they do not light up anymore, I'm thinking there are changes to keylock state with the new key functions. Is there a simple way to just output a note that would then stay on permanently?

discopex wrote:As I didn't know how to light up certain pads, I set the mapping to have note on depending on key lock state - the note was on whether the state was true or false

I don't get this...

discopex wrote: In 2.5RC they do not light up anymore, I'm thinking there are changes to keylock state with the new key functions.

It you programmed some leds depending on the key lock state, they should always go on/off depending on this state!
I doubt there might be a bug in Cross concerning this state, but we need to check it.

discopex wrote:Is there a simple way to just output a note that would then stay on permanently?

Basically, you want to light up some leds at startup and never switch them off?

sylMV wrote:

discopex wrote:As I didn't know how to light up certain pads, I set the mapping to have note on depending on key lock state - the note was on whether the state was true or false

I don't get this...

discopex wrote: In 2.5RC they do not light up anymore, I'm thinking there are changes to keylock state with the new key functions.

It you programmed some leds depending on the key lock state, they should always go on/off depending on this state!
I doubt there might be a bug in Cross concerning this state, but we need to check it.

discopex wrote:Is there a simple way to just output a note that would then stay on permanently?

Basically, you want to light up some leds at startup and never switch them off?

Exactly, to see them better in the dark ! some leds have their beatflash or some other function so it would be dull for the others to remain unlit (grey). Just need a way to output note state to them constantly.

Then you can use the 'Startup' (turn on) and 'Shutdown' (turn off) device-events.

Code: Select all

<output-mappings>
  <device-event name="Startup">
    .... All your MIDI messages here ...
  </device-event>
  <device-event name="Shutdown">
    .... All your MIDI messages here ...
  </device-event>
...
... The rest of your out mappings. ...
...
</output-mappings>


I remember trying that but it wouldn't do the trick for some reason (might be controller dependant, Quneo in this case). But I'll revisit this function.