Hi Peter,
On Thu, Sep 30, 2010 at 1:00 AM, Peter Retep <[email protected]> wrote:
> I have compiled 1.0.0 beta1, (incl. applied the alsa patch and
> configured with --enable-debugging option).
Thanks for trying it. It won't have been useless even if the patch
didn't work: now you can play with the beta :)
> Do you have any other idea?
The error is really an ALSA error but ALSA doesn't give us any
information about it, and google doesn't know about it either. It
might be worth asking ALSA developpers what it means.
But if we accept the fact that unknown shit might happen to users,
what we could try is to recover from that error. Currently, liquidsoap
doesn't try, but the following patch will change that.
--- src/sources/alsa_in.ml (revision 7730)
+++ src/sources/alsa_in.ml (working copy)
@@ -124,7 +124,7 @@
self#log#f 2 "Overrun!"
| _ -> self#log#f 2 "Alsa error: %s" (string_of_error e)
end ;
- if e = Buffer_xrun || e = Suspended || e = Interrupted then
+ if true || e = Buffer_xrun || e = Suspended || e = Interrupted then
begin
self#log#f 2 "Trying to recover.." ;
Pcm.recover dev e
Of course, the Pcm.recover attempt might fail. In which case we should
perhaps try to fully restart the ALSA device.
Cheers,
David
------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
_______________________________________________
Savonet-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/savonet-users
