[lkml]   [2009]   [Apr]   [28]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [ANNOUNCE] OSS Proxy 1.2 using CUSE
At Tue, 28 Apr 2009 18:01:08 +0200,
Miklos Szeredi wrote:
> >From the README:
> | ALSA contains OSS emulation but sadly the emulation is behind
> | multiplexing layer (which is in userland) which means that if your
> | sound card doesn't support multiple audio streams, only either one of
> | ALSA or OSS interface would be usable at any given moment.
> This seems to imply (and I was hoping very much) that this won't be a
> limitation of a CUSE based OSS Proxy. But at the moment I'm finding
> that while ossp is doing some playback other ALSA apps cannot start
> playback and vice versa.
> In fact if something else is playing though ALSA and I start a
> playback through ossp, then ossp will print some errors, return EIO
> and get into a bad state, that it recoveres from only by starting the
> playback twice more (after stopping the other playback through ALSA).

Are you using pulse plugin for ALSA, too?
Looks like ossp tries the pulseaudio. If you are using the native
ALSA, of course it'll block the access by PA...


> ossp-padsp[mszeredi:24123] ERR: pa_stream_write() failed (Connection terminated)
> osspd ERR: failed to read_fill 16 bytes from fd 7 (Connection reset by peer)
> osspd WARN: S[1/24122] communication with slave failed (can't read reply: Connection reset by peer)
> E: socket-client.c: socket(): Address family not supported by protocol
> E: context.c: waitpid(): No child processes
> ossp-padsp[mszeredi:24130] ERR: failed to connect context, state=5 (Bad state)
> Thanks,
> Miklos

 \ /
  Last update: 2009-04-28 18:45    [W:0.095 / U:14.520 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site