Paul Davis wrote:
> On Sat, 2006-08-19 at 05:16 -0700, Stephen Cameron wrote:
>> On Fri, 2006-08-18 at 20:39 -0400, Stephen Sinclair wrote:
Audio doesn't use setitimer()-driven sleeping. It's interrupt-driven,
not timer-driven.
>>> Yes, the driver is interrupt driven, but the driver inte
On Sat, 2006-08-19 at 05:16 -0700, Stephen Cameron wrote:
> On Fri, 2006-08-18 at 20:39 -0400, Stephen Sinclair wrote:
> > > Audio doesn't use setitimer()-driven sleeping. It's interrupt-driven,
> > > not timer-driven.
> >
> > Yes, the driver is interrupt driven, but the driver interrupt handler
On Fri, 2006-08-18 at 20:39 -0400, Stephen Sinclair wrote:
> > Audio doesn't use setitimer()-driven sleeping. It's interrupt-driven,
> > not timer-driven.
>
> Yes, the driver is interrupt driven, but the driver interrupt handler
> is only responsible for getting the data off the card's FIFO and
Hello...
> Ah, interesting. Thanks.
> I feel like I should have known that. I'm going to go read up on
> audio drivers now..
I also thank everyone who had given their thoughts and opinion. At least
you gave me clue on what is really going on in some audio applications.
I'll dig more about MIDI
The user application code is woken up by the interrupt from the audio
interface, not from a timer firing - in addition to getting data from
the card and storing it in memory, the interrupt handler wakes up any
processes that are waiting on the audio data. So HZ is irrelevant.
SCHED_FIFO is neede
On Fri, 2006-08-18 at 20:39 -0400, Stephen Sinclair wrote:
> > Audio doesn't use setitimer()-driven sleeping. It's interrupt-driven,
> > not timer-driven.
>
> Yes, the driver is interrupt driven, but the driver interrupt handler
> is only responsible for getting the data off the card's FIFO and
>
Audio doesn't use setitimer()-driven sleeping. It's interrupt-driven,
not timer-driven.
Yes, the driver is interrupt driven, but the driver interrupt handler
is only responsible for getting the data off the card's FIFO and
storing it in memory. (i.e., initialing a DMA transfer.) It doesn't
do
On Fri, 2006-08-18 at 20:26 -0400, Stephen Sinclair wrote:
> I've certainly seen setitimer()-driven sleeping get much better
> response time on a kernel compiled to 1000 Hz (with preemption) over
> one compiled to 100 Hz (without preemption).
>
> >From this, I think it should be possible to say th
I've certainly seen setitimer()-driven sleeping get much better
response time on a kernel compiled to 1000 Hz (with preemption) over
one compiled to 100 Hz (without preemption).
From this, I think it should be possible to say that one could read
the audio card with smaller buffers more quickly,
On Friday 18 August 2006 23:07, Stephen Cameron wrote:
[...]
> xruns are, I think, JACK's equivalent of my deadline-missed
> message. It calls such tardiness an "xrun". JACK is the
> Jack Audio Connection Kit, an app that is useful for sync'ing
> and communicating audio data between various audio
--- Mulyadi Santosa <[EMAIL PROTECTED]> wrote:
> > High HZ will improve MIDI timing though. MIDI is more likely to be
> > polled than interrupt driven.
>
> polled? Well, interesting. Do you mean MIDI playback?
I know at least some MIDI sequencers (eg. the one I have written)
rely on simple get
Hello...
> > recording audio doesn't involve using the system timer at all. the
> > only clock involved is the sample clock that drives the audio
> > interface.
I see. I took a wrong conclusion then
> > having HZ set too high could conceivably make the system more
> > likely to xrun, but thi
On Fri, 2006-08-18 at 12:38 -0400, Paul Davis wrote:
> On Fri, 2006-08-18 at 23:10 +0700, Mulyadi Santosa wrote:
> > Is there any relationship between kernel HZ and audio timing? I imagine
>
> no. or almost none.
>
> recording audio doesn't involve using the system timer at all. the only
> clock
On Fri, 2006-08-18 at 23:10 +0700, Mulyadi Santosa wrote:
> Is there any relationship between kernel HZ and audio timing? I imagine
no. or almost none.
recording audio doesn't involve using the system timer at all. the only
clock involved is the sample clock that drives the audio interface.
ha
Hello everyone
I am kinda interested to study the effect of changing kernel HZ
(internal timer frequency) and the audio processing. Since I am a
newbie in Linux Audio, I will be glad to receive any comments,
especially the constructive ones.
Is there any relationship between kernel HZ and
15 matches
Mail list logo
