MIDI Mapping for the Ns6

[acemc]

I have finish the mapping (will be in check this week)

Any good news for us on this mapping yet? I'm real curious to see the workaround.

[Support@MixVibes]

Only bad news :
- not ready to be included into 2.4
- can't use properly the joglight

I think I will release this as a 'user mapping'
(mappings have 30000 lines and weight 1.2Mb)

[acemc]

The jog light isn't much of an issue for me really. At the moment I have it mapped to be fully on (wht) while the deck is playing and turns red when the jog wheel is touched. What I'm really wanting is to map the strip search led's to vu meter outputs, fx led's to correspond with correct value's of software & the dry/wet slider to map properly to either amount or depth. Please post it as a user mapping as soon as you can.

mappings have 30000 lines and weight 1.2Mb

Wow!! You really have put some work into this one.
Thanks for the effort.

[BennyB]

What is the note and channel for the Strip Search leds?

[acemc]

What is the note and channel for the Strip Search leds?

The NS6 is using CC 4E with velocity 1 to 15. Channels 2 for deck A, 3 for deck B, 4 for deck C, 5 for Deck D. Obviously decks C + D not in use right now. Although it could be useful for the sampler channels I guess.
My issue isn't to get it to work - it does work, so long as the channel gain is between 1 & 15%. That's why I'm curious to see the workaround.

[BennyB]

What is the note and channel for the Strip Search leds?

The NS6 is using CC 4E with velocity 1 to 15. Channels 2 for deck A, 3 for deck B, 4 for deck C, 5 for Deck D. Obviously decks C + D not in use right now. Although it could be useful for the sampler channels I guess.
My issue isn't to get it to work - it does work, so long as the channel gain is between 1 & 15%. That's why I'm curious to see the workaround.

So you used the % as values I guess.

I assume the code you did so far looks like this:

Code: Select all

<mapping>
   <control alias="fam(Mixer).MasterMeter" value="%"/>
   <MIDI type="CC" parameter="0x4E" channel="0x2" value="%"/>
</mapping>

[acemc]

Thats exactly what the code looks like except I used "fam(Mixer).ChannelAMeter" instead of "fam(Mixer).MasterMeter".
The % value is too high with respect to the strip search led velocity values. What I don't understand is, most controller's don't have more than 15 led's for the meter's anyway. So how do they work then using % as a value??

[acemc]

I think I will release this as a 'user mapping'
(mappings have 30000 lines and weight 1.2Mb)

Please post this as soon as you can. I'm starting to lose my mind, trying to map this controller properly. Some of the mapping limitations in Cross are very frustrating. Like: only 1 button per function, if you map a button as a modifier - it can't be used for anything else, no "hold" option on loop buttons. There is actually a bug within the "application" part of the mappings, whereby you can't map any buttons with a modifier that is a "holder". You have to go back into your modifier, change it to toggle, go back to the mapping you wanted to create & create it, then go back to your modifier & change it back to "hold" again. Then after all of that, only to discover there's no output alias for "app(ShowSamplers)" <<--CRAZY!! After 3 weeks of trying my best, let's just say......I'm running out of steam.

[sylMV]

only 1 button per function, if you map a button as a modifier - it can't be used for anything else

This will be addressed soon.

no "hold" option on loop buttons.

I guess you're talking about autoloops. This might be adressed soon too.

There is actually a bug within the "application" part of the mappings, whereby you can't map any buttons with a modifier that is a "holder". You have to go back into your modifier, change it to toggle, go back to the mapping you wanted to create & create it, then go back to your modifier & change it back to "hold" again.

Have no problem with this...
Map the modifier as HOLD.
Open the mapping window for the command you want to map.
Push the corresponding button while holding the modifier and you're done. Can't be more simple...

Then after all of that, only to discover there's no output alias for "app(ShowSamplers)"

What would you need this for? Basically, we didn't think it could be useful...

<<--CRAZY!!

This was useless... as nothing's crazy in there and no need to yell...

[Support@MixVibes]

Can't give you the mapping for now, without the 2.4 it will be useless.