Is there any documentation for the squillions of interesting-looking
event types defined in snd_seq_event_type? I'm only familiar at all
with the MIDI-based types, and I've failed to find anything referring
to most of the others except for the trivial generated documentation.
I'm particularly
On Wednesday 10 Dec 2003 12:35 pm, David Garcia Garzon wrote:
> [...]
> Each port has also the type bitmasks defined as follows:
> SND_SEQ_PORT_TYPE_SPECIFIC Hardware specific port
> SND_SEQ_PORT_TYPE_MIDI_GENERIC Generic MIDI device
> SND_SEQ_PORT_TYPE_MIDI_GM General MIDI compatible device
> [etc
On Wednesday 10 Dec 2003 7:38 am, Clemens Ladisch wrote:
> Chris Cannam wrote:
> > Is there any documentation for the squillions of
> > interesting-looking event types defined in snd_seq_event_type?
>
> The source.
Ah.
> > I'm particularly intrigued by the SND_S
While trying to track down the source of some poor timing in
sequencing, I've noticed that my ALSA sequencer queue timer has a
tendency to fall suddenly behind.
I have a little test program (available on request) that just starts a
queue and every second or so compares the queue timer against
On Sunday 14 Dec 2003 2:02 pm, Jan Depner wrote:
> If I'm not mistaken the timing for your audio is coming from your
> sound card not your system clock.
Is that so? Obvious though it is, that simply hadn't occurred to me.
I mentally ruled out a hardware problem quite early on because I
wasn't s
On Sunday 14 Dec 2003 2:34 pm, Chris Cannam wrote:
> On Sunday 14 Dec 2003 2:02 pm, Jan Depner wrote:
> > If I'm not mistaken the timing for your audio is coming from your
> > sound card not your system clock.
>
> [...]
> I mentally ruled out a hardware problem quit
On Sunday 14 Dec 2003 2:34 pm, Chris Cannam wrote:
> On Sunday 14 Dec 2003 2:02 pm, Jan Depner wrote:
> > If I'm not mistaken the timing for your audio is coming from your
> > sound card not your system clock.
>
> [...] what if you have more
> than one soundcard o
On Monday 15 Dec 2003 1:30 am, Pedro Lopez-Cabanillas wrote:
> The ALSA MIDI sequencer can use several timer sources. By default,
> it uses the Linux system timer functions [...]
> Other timer sources are PCM devices and the RTC timer.
Ah... so that puts Jan's comment into perspective. I could ha
On Monday 15 Dec 2003 9:16 am, Chris Cannam wrote:
> This seems to suggest that the default system-based timer is doing
> something a bit naive, like assuming it was called back on time
> without actually checking.
Hmm yes, even this crappy little patch to alsa-kernel/core/timer.
On Wednesday 17 Dec 2003 3:13 pm, Jaroslav Kysela wrote:
> Thanks for insigh to the problem. Can you try the attached patch?
Yes, that's a success. Thank you. It's still not absolutely perfect,
but it's significantly better than the original version. I've seen
one slippage (of about 40ms, und
I notice that if you send to a non-running sequencer queue an event
scheduled for exactly the current time of the queue, then the event
is delivered immediately: the queue doesn't wait to be started first.
Is this intentional? I had thought the main reason for allowing
queues to stop and star
On Monday 12 Jan 2004 5:19 pm, Chris Cannam wrote:
> I notice that if you send to a non-running sequencer queue an event
> scheduled for exactly the current time of the queue, then the event
> is delivered immediately: the queue doesn't wait to be started
> first.
>
> Is th
I asked about this on the JACK list just now and was recommended to
bring the question here instead. So here we are.
If I'm running JACK with output to my first (and only) PCM device, and
I have a JACK client running that also sets up an ALSA sequencer
queue with its timer set to the ALSA PCM
On Thursday 13 May 2004 7:12 pm, Jaroslav Kysela wrote:
> Maybe, lost interrupts can cause this. Actually, there is no
> correction in the PCM slave timer code for this situation.
Looking over the figures again, it looks like (for the test case
forwarded to me) the sequencer queue is actually con
Takashi Iwai wrote:
> At Sun, 8 Jun 2003 22:06:30 -0400,
> Drake Wilson wrote:
>
>>... I have a draft, or part thereof. It is in similar spirit to the
>>module overviews in the API reference, and I hope it to be of some
>>use, if not optimal.
>>[...]
I missed this until now. Just to add that th
15 matches
Mail list logo
