[lkml]   [2006]   [Jan]   [5]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [OT] ALSA userspace API complexity
On Thu, Jan 05, 2006 at 03:24:18PM +0100, Jaroslav Kysela wrote:
> On Thu, 5 Jan 2006, Heikki Orsila wrote:
> > err = alsa_simple_pcm_open(nchannels, sampleformat, samplingrate, frames_in_period /* 0 for automated default */ );
> Well, it's better to create only "fast parameter setup" and "default error
> recovery" functions.

And what would it look like? I would prefer all functions being
alsa_simple_* because a user could read interface documentation
alphabetically and see all the relevant functions as they are adjacent.

I would correct my earlier 'frames_in_period' to 'latency_in_frames' because
most users are not interested in period size. Latency on the other hand
matters. 10ms latency would just be samplingrate / 100 and the ALSA lib
would choose good approximate period/buffer sizes internally. Those who
need something better should just use the old way.

Heikki Orsila Barbie's law: "Math is hard, let's go shopping!"
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2006-01-05 16:29    [W:0.103 / U:6.088 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site