Re: [Linuxsampler-devel] Build failure: probable gcc-3.4.1 issue?

[Christian S. <sch...@so...>]

Am Donnerstag, 7. Oktober 2004 18:21 schrieb Rui Nuno Capela:
> stuff, cause I'm still fighting with some problems, so please go ahead and
> commit it.
>
>
> OK. I'll apply it tonight.

I also made the transition to gcc 3.4 tonight. Hope latest version still 
compiles for gccs < 3.4.

> On another subject, I noticed that linuxsampler maps MIDI channels number
> in a off-by-one difference to ALSA sequencer numbering, which equals the
> native low MIDI command address level. I think the following table shows
> this mismatch:
>
> MIDI     MIDI
> channel  channel
> address  number   linuxsampler  alsa-seq
> -------  -------  ------------  --------
> 0        1        All channels  0
> 1        2        1             1
> 2        3        2             2
> ...      ...      ...           ...
> 15       16       15            15

I first tended to say no, this is fine, because the majority of musicians is 
used to the 1..16 indexing of MIDI channels, but then I remembered that 
everyhting else in LS is indexed starting by 0 (sampler channel, audio 
channel, etc.). So to avoid having an exceptional case here, I now changed 
MIDI channel indexing globally to the low level variant 0..15, too.

> Moreover, the "All channels" linuxsampler specification doesn't seem to
> work at all, being just single mapped to MIDI Channel 1 (address 0).

Yep, fixed now in latest CVS:

> be. Additionally, I think this MIDI channel numbering should be
> explicitly, if not, better documented.

I agree this should be mentioned in the documentation. Would you like to add 
it to the LSCP RFC or should I do it? Again, MIDI indexing is now 0..15 and 
16 would be "list to all MIDI channels", but on LSCP level the keyword "ALL" 
should be used instead of 16; I tend towards adding a WRN result, if somebody 
tries to use 16.

CU
Christian