Re: [seq24-users] seq24/alsa sequencer architecture question

[Florian S. <mis...@gm...>]

On Friday 30 March 2007, Gareth Edwards wrote:
> Hi there,
>
> I've been studying the seq24 code with a view to modifying the code for
> my own application and I've got a question about the way it is written -
> I'm an ALSA newbie so please forgive if it's a stupid question.
>
> The output thread seems to take great care of its timing accuracy in
> setting it's sleep time in the main timing loop (so much that there is
> an command line option to increase the thread priority, presumably to
> increase this accuracy) - but the alsa sequencer API seems to look after
> this timing for you. I guess I'm not seeing why seq24 needs to go to the
> lengths it does when it could just supply the events to the sequencer
> API and then relax?
>
> If the answer is "go away and read the API docs properly so you
> understand them", then that's fine <G>

Well, i suppose some people think it's easier to manage the timing in their 
own app and dispatch messages directly rather than relying on alsa seq's 
queues and timing. Alsa offers support for both paradigms.

Flo


-- 
Palimm Palimm!
http://tapas.affenbande.org