MIXVIBES Dj Community old forum

Code: Select all

Out fam(Player)[@].TrackArtist (String)

can this value used in MIDI mappings (sysex Output or something)

Only for a few devices such as Denon decks.
There's unfortunately no standard way of sending text over MIDI...

You can't even get manufacturers to agree on how to handle LED's...

In fact, you have some manufacturers that start from scratch on every controller instead of sticking to a 'basic' standard mapping for all their controllers (cough *Vestax* cough).

Another departs from the 'norm' of using note to define the light and velocity to define the appearance and instead uses notes to define what you want to see, and then velocity to define the light. And they use multiple notes per light making it confusing as hell (and wasteful from an addressing standpoint)... (cough *Denon* cough).

How they encode their platters and everything else can vary greatly...

Which makes things REAL difficult for people trying to map controllers. Even with a good MIDI spec it gets tough because the actual implementation could be a little flaky and unusual behavior can result... which is why it's so hard to map a controller without one.

What you 'could' do is use the Out fam(Player)[@].TrackArtist (String) and send it to Bomes and then use it to do the processing necessary to get it in the format needed for the software. This would be similar to the setup of the Stanton System 3 (SCS3d/SCS3m) or System 1. BTW, daRouter is really just Bomes... and uses the same mappings.

i know the MIDI Problems :P i build my own Controllers and some microcontroller MIDI devices


but my qustion is how i send this string value out (the Definition of the XML in the .mappings file)

(the Format is not the Problem i write some max patchs to handle all my mappings)

but i dont find the way how i send this string out

nillin wrote:i know the MIDI Problems :P i build my own Controllers and some microcontroller MIDI devices


but my qustion is how i send this string value out (the Definition of the XML in the .mappings file)

(the Format is not the Problem i write some max patchs to handle all my mappings)

but i dont find the way how i send this string out

nillin you are registered for 3 days and i like you allready

+100

Best regards
Marxon

sylMV wrote:Only for a few devices such as Denon decks.
There's unfortunately no standard way of sending text over MIDI...

meaning, there's some code in Cross to send text using the Denon format

However, if you can handle them using Max, here are the kind of lines needed in the mappings file:

Code: Select all

<mapping>
  <control alias="fam(Player)[0x1].TrackArtist" value="miditext"/>
  <miditext kind="DENONS3700_1" channel="0x1"/>
</mapping>


There are 4 kinds available:
- "DENONS3700_1" (1st line of the Denon S3700/S3900)
- "DENONS3700_2" (2nd line of the Denon S3700/S3900)
- "DENONHC4500_1" (1st line of the Denon HC4500)
- "DENONHC4500_2" (2nd line of the Denon HC4500)
You can find the MIDI messages sent in the Denon docs.

Hope this helps a bit

Nice One =) this helps

MusicMeister wrote:You can't even get manufacturers to agree on how to handle LED's...

In fact, you have some manufacturers that start from scratch on every controller instead of sticking to a 'basic' standard mapping for all their controllers (cough *Vestax* cough).

Another departs from the 'norm' of using note to define the light and velocity to define the appearance and instead uses notes to define what you want to see, and then velocity to define the light. And they use multiple notes per light making it confusing as hell (and wasteful from an addressing standpoint)... (cough *Denon* cough).

How they encode their platters and everything else can vary greatly...

Which makes things REAL difficult for people trying to map controllers. Even with a good MIDI spec it gets tough because the actual implementation could be a little flaky and unusual behavior can result... which is why it's so hard to map a controller without one.

Welcome to my daily pain...

Yep, but that next set of controllers you're mapping for should be a lot easier...

If we could AT LEAST get the rest of them to print the ENTIRE spec and not just part of it... that would be a major thing for the win column for me!

sylMV wrote:

sylMV wrote:Only for a few devices such as Denon decks.
There's unfortunately no standard way of sending text over MIDI...

meaning, there's some code in Cross to send text using the Denon format

However, if you can handle them using Max, here are the kind of lines needed in the mappings file:

Code: Select all

<mapping>
  <control alias="fam(Player)[0x1].TrackArtist" value="miditext"/>
  <miditext kind="DENONS3700_1" channel="0x1"/>
</mapping>


There are 4 kinds available:
- "DENONS3700_1" (1st line of the Denon S3700/S3900)
- "DENONS3700_2" (2nd line of the Denon S3700/S3900)
- "DENONHC4500_1" (1st line of the Denon HC4500)
- "DENONHC4500_2" (2nd line of the Denon HC4500)
You can find the MIDI messages sent in the Denon docs.

Hope this helps a bit

Actually, I'm not using it yet and it helps me a lot..