Jaroslav Kysela wrote:
On Mon, 16 Jun 2003, Joern Nettingsmeier wrote:
Jaroslav Kysela wrote:
On Mon, 16 Jun 2003, Jaroslav Kysela wrote:
thanks for the clarification. i'd be glad to help, but i doubt i could
meet the coding standards of alsa-lib. at least i could help test it.
do you or any
On Monday 16 June 2003 18.03, Jaroslav Kysela wrote:
[...]
> > Maybe ALSA shouldn't mess with (N)RPNs at all, unless
> > applications ask for it?
>
> I think that events are clear, so all applications using direct
> sequencer API should handle them as well.
Yes, that's a point... However, if ALSA
>Yes, Paul mentioned it and I see that the standard is not so good. Does it
>affect also XRPN encoding (some LSB or MSB bytes might be missing)?
>In that case the current implementation is broken.
now that i think about it, i recall what i realized was the MIDI
spec's intent: you are supposed to
Jaroslav Kysela wrote:
On Mon, 16 Jun 2003, Jaroslav Kysela wrote:
thanks for the clarification. i'd be glad to help, but i doubt i could
meet the coding standards of alsa-lib. at least i could help test it.
do you or anyone of the alsa core developers have plans to tackle this
some time soon ?
Jaroslav Kysela wrote:
On Mon, 16 Jun 2003, Jaroslav Kysela wrote:
thanks for the clarification. i'd be glad to help, but i doubt i could
meet the coding standards of alsa-lib. at least i could help test it.
do you or anyone of the alsa core developers have plans to tackle this
some time soon ?
On Monday 16 June 2003 13.19, Jaroslav Kysela wrote:
> On Mon, 16 Jun 2003, Jaroslav Kysela wrote:
> > > thanks for the clarification. i'd be glad to help, but i doubt
> > > i could meet the coding standards of alsa-lib. at least i could
> > > help test it. do you or anyone of the alsa core develop
On Monday 16 June 2003 11.10, David Olofson wrote:
[...]
> I'm going to have another look at it. There has to be some
> explanation why it mysteriously Just Works(TM).
Yep, the explanation is most probably that I was using ALSA rawmidi
input... :-) With the ALSA sequencer "driver" I get the CC ev
>maybe i should consider dropping 14-bit resolution (the crappy faders on
>the peavey hardly manage 127 distinct positions) and just use the MSB
>part of the 14bit controller. ardour does perform lowpass filtering of
>controller values, right ?
it doesn't filter the values directly, but the var
>Initial code is in CVS. It is not tested, but hopefully, without any major
>bugs. It seems that we have also missing encoding of CONTROL14 events.
14 bit MIDI is almost impossible to parse in any sane fashion. if you
read the spec carefully, you'll see that it requires a timeout be
attached to e
Jaroslav Kysela wrote:
On Mon, 16 Jun 2003, Joern Nettingsmeier wrote:
either i have not understood the semantics of nrpm, or nrpm events are
not detected as such. when i move a slider, i always get four separate
normal controller events: two on 98/99 encoding the control number as a
14bit va
On Monday 16 June 2003 10.57, Jaroslav Kysela wrote:
> On Mon, 16 Jun 2003, David Olofson wrote:
> > On Monday 16 June 2003 10.29, Jaroslav Kysela wrote:
> > [...]
> >
> > > The driver code and alsa-lib does not handle nonreg and reg
> > > parameters. They simply pass them like standard controllers
On Monday 16 June 2003 10.29, Jaroslav Kysela wrote:
[...]
> The driver code and alsa-lib does not handle nonreg and reg
> parameters. They simply pass them like standard controllers, so the
> four event sequence is ok. I think that we may add this piece code
> to seq_midi_event.c.
This is weird..
On Monday 16 June 2003 09.51, Joern Nettingsmeier wrote:
[...]
> > What you get is plain tuples, and that's all
> > there is to it. (Well, it's all I *want* anyway, as I don't want
> > to do stuff that's outside the MIDI spec...)
> >
> > Here's some code, which isn't heavily tested, but does seem
Paul Davis wrote:
hello alsa gurus !
i have bought a peavey studiomix midi controller on ebay, and it sends
NRPN messages (non-registered parameter numbers). when i move a slider,
it sends the slider number encoded in 98 and 99 and the value in the
DATA ENTRY controllers 6 and 38. i would like
hello david !
thanks for your reply.
David Olofson wrote:
On Sunday 15 June 2003 18.16, Joern Nettingsmeier wrote:
[...]
/*{SND_SEQ_EVENT_NONREGPARAM, extra_decode_nrpn},*/
/*{SND_SEQ_EVENT_REGPARAM, extra_decode_rpn},*/
};
which makes me think it might not yet be implemented
>hello alsa gurus !
>
>i have bought a peavey studiomix midi controller on ebay, and it sends
>NRPN messages (non-registered parameter numbers). when i move a slider,
>it sends the slider number encoded in 98 and 99 and the value in the
>DATA ENTRY controllers 6 and 38. i would like to map these
On Sunday 15 June 2003 18.16, Joern Nettingsmeier wrote:
[...]
> /*{SND_SEQ_EVENT_NONREGPARAM, extra_decode_nrpn},*/
> /*{SND_SEQ_EVENT_REGPARAM, extra_decode_rpn},*/
> };
>
> which makes me think it might not yet be implemented
I'm using NRPNs to control the mixer in the cur
hello alsa gurus !
i have bought a peavey studiomix midi controller on ebay, and it sends
NRPN messages (non-registered parameter numbers). when i move a slider,
it sends the slider number encoded in 98 and 99 and the value in the
DATA ENTRY controllers 6 and 38. i would like to map these to or
18 matches
Mail list logo
