<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Verdana
}
--></style>
</head>
<body class='hmmessage'>
Completely agree that SYSEX is where this kind of functionality should reside.<br><br>This use of 0x7d is a bit antiquated, no? The reassignment of 0x00 to indicate 3 byte<br>SYSEX ID means there is a bit more flexibility in the system. Currently the following<br>are assigned:<br><br>0x00 0x00 0xXX American group<br>0x00 0x01 0xXX American group<br>0x00 0x20 0xXX European group<br>0x4X Japanese group (with holes)<br>0x5X Japanese group (with holes)<br>0x00 0x04 Japanese group<br><br>Getting a registration requires it be paid for, pretty ludicrous for what purports to be<br>an open standard. I would suggest that Open Source developers should simply take<br>one of the unassigned values for its own first digit, agree between themselves who<br>get the next two digits for their apps and SYSEX then be sent with 3 byte ID.<br><br>SLab hijacked 0x53 about 10 years ago for this purpose and bolted on a three more <br>digits for personal identification and there is little reason why this should not be done<br>again, this time in line with the current MMA SYSEX ID defs as above? If open source<br>goes and squats on 0x7d then everybody can go and haggle over which app gets the<br>next two digits.<br><br>There is probably going to be some complaints that SYSEX require an extra two <br>bytes and how that is going to degrade system performance at 31.25KHz, which <br>probably needs a pre-canned response as it is a non-issue.<br><br>This discussion is perhaps better aimed at LAD rather than LAU: LAU justs wants it <br>to work, LAD can horsetrade on the details. <br><br>It is possible that the MMA will take an issue with this since it does not actually fit <br>within the new SYSEX ID specs (0x7d has not been assigned in the new definition)<br>but I am pretty sure that if open source applications restrict themselves to their own<br>set of second and third digits then the MMA will not be so daft as to assign that <br>number to any manufacturer. For the apps that eventually go commercial then<br>it is their job, as a part of the commercialisation, to formally request their own ID<br>from MMA and then to recognise both of them if desired - the MMA assigned one <br>thanks to paying $$$ for the number, and the squatted ID for compatibility purposes.<br><br>Now, to tie this back into the original subject: this does not really help with assigning<br>MIDI controllers back to app controls as now the surface has to be configured to <br>generate more complex SYSEX messages, neither easy nor even possible with some of<br>them, but the argument of applications getting screwed by using the same number <br>is actually very easy to avoid, admittedly as long as it is done unanimously. Perhaps <br>linuxaudio.org might want to pick up the gauntlet of assigning the open sourced <br>digits?<br><br>Regards, nick<br><br>"we have to make sure the old choice [Windows] doesn't disappear”.<br>Jim Wong, president of IT products, Acer<br><br><br><br><br>> Date: Mon, 5 Oct 2009 19:19:17 +0200<br>> From: fons@kokkinizita.net<br>> To: linux-audio-user@lists.linuxaudio.org<br>> Subject: Re: [LAU] So what's the deal with controlling the aeolus organ?stops via midi<br>> <br>> On Mon, Oct 05, 2009 at 07:00:40PM +0200, Pedro Lopez-Cabanillas wrote:<br>> <br>> > The MMA requires that you use a registered manufacturer ID, but only for <br>> > commercial products. There is a special ID = 0x7D that is intended for <br>> > educational or development use only, and should never appear in a commercial <br>> > design.<br>> <br>> Where it is silently assumed that 'educational' and 'development'<br>> implies 'not distributed', or at least 'never used together with<br>> any other app using the same ID'.<br>> <br>> If two or more open source programs use 0x7D and they happen to<br>> see the same MIDI stream then one of them will be screwed. <br>> <br>> Ciao,<br>> <br>> -- <br>> FA<br><br>"we have to make sure the old choice [Windows] doesn't disappear”.<br>Jim Wong, president of IT products, Acer<br><br><br><br><br>> Date: Mon, 5 Oct 2009 19:19:17 +0200<br>> From: fons@kokkinizita.net<br>> To: linux-audio-user@lists.linuxaudio.org<br>> Subject: Re: [LAU] So what's the deal with controlling the aeolus organ?stops via midi<br>> <br>> On Mon, Oct 05, 2009 at 07:00:40PM +0200, Pedro Lopez-Cabanillas wrote:<br>> <br>> > The MMA requires that you use a registered manufacturer ID, but only for <br>> > commercial products. There is a special ID = 0x7D that is intended for <br>> > educational or development use only, and should never appear in a commercial <br>> > design.<br>> <br>> Where it is silently assumed that 'educational' and 'development'<br>> implies 'not distributed', or at least 'never used together with<br>> any other app using the same ID'.<br>> <br>> If two or more open source programs use 0x7D and they happen to<br>> see the same MIDI stream then one of them will be screwed. <br>> <br>> Ciao,<br>> <br>> -- <br>> FA<br>> <br>> Io lo dico sempre: l'Italia è troppo stretta e lunga.<br>> <br>> _______________________________________________<br>> Linux-audio-user mailing list<br>> Linux-audio-user@lists.linuxaudio.org<br>> http://lists.linuxaudio.org/mailman/listinfo/linux-audio-user<br> <br /><hr />Windows Live: Make it easier for your friends to see <a href='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' target='_new'>what you’re up to on Facebook.</a></body>
</html>