6 Oct
2009
6 Oct
'09
5:34 p.m.
On Monday, October 5, 2009, Fons Adriaensen wrote:
On Mon, Oct 05, 2009 at 07:00:40PM +0200, Pedro
Lopez-Cabanillas wrote:
The only devices or programs that would be screwed are those bad or poorly
designed/written.
In addition to the manufacturer ID, there should be enough additional bytes to
uncertainly identify a particular model among others using the same
manufacturer ID. The device (soft in this case) receiving a message should be
able to distinguish between legitimate and spurious messages using the model
ID bytes, checksums and/or some other mechanism.
Regards,
Pedro
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. 
6 Oct
6 Oct
6:21 p.m.
New subject: [LAU] So what's the deal with controlling the aeolus?organ?stops via midi
On Tue, Oct 06, 2009 at 09:34:03PM +0200, Pedro Lopez-Cabanillas wrote:
In addition to the manufacturer ID, there should be
enough additional bytes to
uncertainly identify a particular model among others using the same
manufacturer ID.
Sure, e.g. four unique bytes at the start would solve
the problem. But there is no central authority in the
open source world to assign them.
A truly random sequence of 8 or more bytes would work
as well. But it means that even transmitting seven bits
requires 11 bytes. No problem for system dumps etc., but
for frequent short messages the overhead is too much.
Ciao,
--
FA
Io lo dico sempre: l'Italia รจ troppo stretta e lunga.
6:58 p.m.
New subject: [LAU] So what's the deal with controlling the aeolus organ?stops via midi
Pedro Lopez-Cabanillas wrote:
On Monday, October 5, 2009, Fons Adriaensen wrote:
Checksums are not always used for simple parameters, I guess they are
used for complete dumps and the model number or device number also could
have a FLOSS-twin. For e.g. the Matrix-1000 you can have several
Oberheim Matrix-1000 and give them device numbers, so that only one
Matrix-1000 will use received data. It would be really good if there
would be a first ID for FLOSS, but there isn't, so it might be the best
way to make this ID changeable by the GUI.
On Mon, Oct 05, 2009 at 07:00:40PM +0200, Pedro
Lopez-Cabanillas wrote:
The only devices or programs that would be screwed are those bad or poorly
designed/written.
In addition to the manufacturer ID, there should be enough additional bytes to
uncertainly identify a particular model among others using the same
manufacturer ID. The device (soft in this case) receiving a message should be
able to distinguish between legitimate and spurious messages using the model
ID bytes, checksums and/or some other mechanism.
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.
5522
days inactive
5522
days old
linux-audio-dev@lists.linuxaudio.org
2 comments
3 participants
participants (3)
-
Fons Adriaensen -
Pedro Lopez-Cabanillas -
Ralf Mardorf