Re: [LAD] [LAU] So what's the deal with controlling the aeolus organ?stops via midi

Completely agree that SYSEX is where this kind of functionality should reside.

This use of 0x7d is a bit antiquated, no? The reassignment of 0x00 to indicate 3 byte
SYSEX ID means there is a bit more flexibility in the system. Currently the following
are assigned:

0x00 0x00 0xXX American group
0x00 0x01 0xXX American group
0x00 0x20 0xXX European group
0x4X Japanese group (with holes)
0x5X Japanese group (with holes)
0x00 0x04 Japanese group

Getting a registration requires it be paid for, pretty ludicrous for what purports to be
an open standard. I would suggest that Open Source developers should simply take
one of the unassigned values for its own first digit, agree between themselves who
get the next two digits for their apps and SYSEX then be sent with 3 byte ID.

SLab hijacked 0x53 about 10 years ago for this purpose and bolted on a three more
digits for personal identification and there is little reason why this should not be done
again, this time in line with the current MMA SYSEX ID defs as above? If open source
goes and squats on 0x7d then everybody can go and haggle over which app gets the
next two digits.

There is probably going to be some complaints that SYSEX require an extra two
bytes and how that is going to degrade system performance at 31.25KHz, which
probably needs a pre-canned response as it is a non-issue.

This discussion is perhaps better aimed at LAD rather than LAU: LAU justs wants it
to work, LAD can horsetrade on the details.

It is possible that the MMA will take an issue with this since it does not actually fit
within the new SYSEX ID specs (0x7d has not been assigned in the new definition)
but I am pretty sure that if open source applications restrict themselves to their own
set of second and third digits then the MMA will not be so daft as to assign that
number to any manufacturer. For the apps that eventually go commercial then
it is their job, as a part of the commercialisation, to formally request their own ID
from MMA and then to recognise both of them if desired - the MMA assigned one
thanks to paying $$$ for the number, and the squatted ID for compatibility purposes.

Now, to tie this back into the original subject: this does not really help with assigning
MIDI controllers back to app controls as now the surface has to be configured to
generate more complex SYSEX messages, neither easy nor even possible with some of
them, but the argument of applications getting screwed by using the same number
is actually very easy to avoid, admittedly as long as it is done unanimously. Perhaps
linuxaudio.org might want to pick up the gauntlet of assigning the open sourced
digits?

Regards, nick

"we have to make sure the old choice [Windows] doesn't disappear”.
Jim Wong, president of IT products, Acer

> Date: Mon, 5 Oct 2009 19:19:17 +0200
> From: fons@email-addr-hidden
> To: linux-audio-user@email-addr-hidden
> Subject: Re: [LAU] So what's the deal with controlling the aeolus organ?stops via midi
>
> On Mon, Oct 05, 2009 at 07:00:40PM +0200, Pedro Lopez-Cabanillas wrote:
>
> > The MMA requires that you use a registered manufacturer ID, but only for
> > commercial products. There is a special ID = 0x7D that is intended for
> > educational or development use only, and should never appear in a commercial
> > design.
>
> Where it is silently assumed that 'educational' and 'development'
> implies 'not distributed', or at least 'never used together with
> any other app using the same ID'.
>
> If two or more open source programs use 0x7D and they happen to
> see the same MIDI stream then one of them will be screwed.
>
> Ciao,
>
> --
> FA

"we have to make sure the old choice [Windows] doesn't disappear”.
Jim Wong, president of IT products, Acer

> Date: Mon, 5 Oct 2009 19:19:17 +0200
> From: fons@email-addr-hidden
> To: linux-audio-user@email-addr-hidden
> Subject: Re: [LAU] So what's the deal with controlling the aeolus organ?stops via midi
>
> On Mon, Oct 05, 2009 at 07:00:40PM +0200, Pedro Lopez-Cabanillas wrote:
>
> > The MMA requires that you use a registered manufacturer ID, but only for
> > commercial products. There is a special ID = 0x7D that is intended for
> > educational or development use only, and should never appear in a commercial
> > design.
>
> Where it is silently assumed that 'educational' and 'development'
> implies 'not distributed', or at least 'never used together with
> any other app using the same ID'.
>
> If two or more open source programs use 0x7D and they happen to
> see the same MIDI stream then one of them will be screwed.
>
> Ciao,
>
> --
> FA
>
> Io lo dico sempre: l'Italia è troppo stretta e lunga.
>
> _______________________________________________
> Linux-audio-user mailing list
> Linux-audio-user@email-addr-hidden
> http://lists.linuxaudio.org/mailman/listinfo/linux-audio-user
                                                _________________________________________________________________ Windows Live: Make it easier for your friends to see what you’re up to on Facebook. http://www.microsoft.com/middleeast/windows/windowslive/see-it-in-action/social-network-basics.aspx?ocid=PID23461::T:WLMTAGL:ON:WL:en-xm:SI_SB_2:092009

_______________________________________________
Linux-audio-dev mailing list
Linux-audio-dev@email-addr-hidden
http://lists.linuxaudio.org/mailman/listinfo/linux-audio-dev
Received on Tue Oct 6 00:15:03 2009