<div dir="ltr">Could it be a memory issue? 'Top' could help show that. </div><div class="gmail_extra"> <div class="gmail_quote">On Mon, Aug 19, 2013 at 10:13 AM, Thomas DEBESSE <<a href="mailto:thomas.debesse@rcf.fr" target="_blank">thomas.debesse@rcf.fr</a>> wrote: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">2012/12/5 Krzysztof Konopko <<a href="mailto:krzysztof.konopko@youview.com">krzysztof.konopko@youview.com</a>>: > Just a guess... could it be something to do with clock/buffer timestamp > wrap-around or truncation? Don't know… > The timestamps are 64 bit integers which gives roughly 10^18. The base > time unit is ns (10^-9) so if we talking about hours we reach values at > most ~10^13. Feels like there's still enough capacity in the timestamp > type. But maybe specifically alsasink or the the hardware itself > truncates timestamps and doesn't handle wrap-arounds? Good idea, but I tested it with dozens of different hardware soundcards, with same issues. I have filled a detailed bug report in january but nobody has responded : <a href="http://lists.freedesktop.org/archives/gstreamer-bugs/2013-January/099131.html" target="_blank">http://lists.freedesktop.org/archives/gstreamer-bugs/2013-January/099131.html</a> Currently, I use a cron that stop / play my pipelines every three hours… All pipelines that contain alsasrc or alsasink module become silent or noisy after dozens of hours. A pipeline linking alsasrc to alsasink becomes unusable after approximatively three hours. It's hardware independant, Gstreamer 0.10 or 1.0 independant, seems distro independant. -- Thomas DEBESSE RCF Méditerrannée _______________________________________________ gstreamer-devel mailing list <a href="mailto:gstreamer-devel@lists.freedesktop.org">gstreamer-devel@lists.freedesktop.org</a> <a href="http://lists.freedesktop.org/mailman/listinfo/gstreamer-devel" target="_blank">http://lists.freedesktop.org/mailman/listinfo/gstreamer-devel</a> </blockquote></div> </div>