Skip to contentSkip to conversation

priority inversion & inheritance

linux-audio-dev Kai Vehmanen 1 participant 1 message Jul 12, 2002 1 message not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

#1 lore raw

note! cross-posted to alsa-devel; some questions about the

      korg1212 driver...
Quoted 2 lines · Martijn Sipkema
Quoted 1 line

Ok, I guess here\'s the first real case against const-nframe.

I thought i had already mentioned this several time :)

You didn't say it loud enough.. ;)

[soundcards for which 'sample_rate/interrupt_frequency' is fractional]

Quoted 3 lines
Quoted 2 lines

at least with ALSA you\'d be in trouble anyway as ALSA will wake your driver only when period_count samples are available. If you set

Perhaps this could be changed/added in ALSA?

Well... I wish you luck in getting that change accepted. :)

Quoted 5 lines
Quoted 2 lines

So like Paul said, do we need to support these soundcards...? For JACK-style operation both the above scenario are really, really bad.

I don\'t have hardware that behaves like this :)
But still, the yamahas are a common hardware. Is the korg card the 1212? I think it would still be nice to support these.

But even with a non-const-nframe, these might still be hopeless cases. As for the korg 1212, it doesn't be a similar case as the yamaha. Its current driver in ALSA CVS seems to have hardcoded values for total buffer size and interrupt frequency. The used values are 8 blocks of 1024 sample frames (ie. period_size=1024, buffer_size=8192). This is a pretty sucky configuration. Unfortunately as part of the driver is implemented as DSP-code, changing the default might not be easy.

Anyways, I don't have this card myself and have never tested it so the above analysis might be totally wrong. So correct me I'm wrong here...

Quoted 5 lines
Quoted 4 lines

Basicly same approach is now in used in regards to the nframes issue. If you try to use ecasound with a JACK driver (well, if there was such an driver) with non-const-nframes, ecasound would just raise an error and exit. In a way this makes sense as until I rewrite ecasound (which will

Is adding an intermediate buffer for drivers with non-const nframes much work?

Some. I'd have to add code for the ringbuffer. Doesn't sound bad, but for me it's a few hundred lines of new code that I have to maintain but very likely nobody will ever use. The worst thing is that it would ruin my beautiful codebase. ;) I hate having multiple code paths that do essentially the same thing. The logic for handling JACK i/o is already pretty hairy (connecting the JACK inputs and outputs to the ecasound signal graph, master&slave timing modes, handling commands from the ecasound ui, commands from jackd, etc, etc).

But again, the problem is really not what I have to do. All major ecasound subsystems have been rewritten multiple times. If it needs to be done again, I'll do it. But I'm not sure if it as likely that someone will rewrite csound, pd, <insert-big-app-here> just to support JACK.

Signature · 9 lines
 http://www.eca.cx
 Audio software for Linux!



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
PC Mods, Computing goodies, cases & more
http://thinkgeek.com/sf