alsasink underrun recovery issue in a synchronized streaming usecase

[danny.smith]

Hi all,

I am using scenario where we stream synchronized audio from one sender to
multiple receivers using the approach outlined in the 2015 Gstreamer
conference in Dublin by Sebastian Dröge (Synchronised multi-room media
playback and distributed live media processing and mixing).

I have set up my latencies towards a more "low-latency" usecase and it works
fine.

When I stress my receivers by doing other stuff on the same platform I get
alsasink underruns which are expected due to small buffers and period times
but not a problem for my usecase. However, quite often the pipeline does not
recover correctly from these underruns. Audio can disappear completely,
sometimes it comes back a while later. It can also become distorted.

We are using gstreamer 1.10.4 and kernel 4.x. Any ideas or hints on what
might be causing this? The pipeline seems to be running fine.

Regards,
Danny





--
Sent from: http://gstreamer-devel.966125.n4.nabble.com/
_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel

[Nicolas Dufresne-5]

Le samedi 24 février 2018 à 00:55 -0700, danny.smith a écrit :

> Hi all,
>
> I am using scenario where we stream synchronized audio from one sender to
> multiple receivers using the approach outlined in the 2015 Gstreamer
> conference in Dublin by Sebastian Dröge (Synchronised multi-room media
> playback and distributed live media processing and mixing).
>
> I have set up my latencies towards a more "low-latency" usecase and it works
> fine.
>
> When I stress my receivers by doing other stuff on the same platform I get
> alsasink underruns which are expected due to small buffers and period times
> but not a problem for my usecase. However, quite often the pipeline does not
> recover correctly from these underruns. Audio can disappear completely,
> sometimes it comes back a while later. It can also become distorted.
>
> We are using gstreamer 1.10.4 and kernel 4.x. Any ideas or hints on what
> might be causing this? The pipeline seems to be running fine.

Sounds like a bug which will require a lot of investigation to explain.
 Can you file a bug on bugs.gnome.org ?

>
> Regards,
> Danny
>
>
>
>
>
> --
> Sent from: http://gstreamer-devel.966125.n4.nabble.com/
> _______________________________________________
> gstreamer-devel mailing list
> [hidden email]
> https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel

_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel

[danny.smith]

Hi Nicolas,

While looking through bugzilla I found this thread which seems to discuss a
similar issue:

https://bugzilla.gnome.org/show_bug.cgi?id=692953

Is this issue solved? the last comment is from 2016.

Regards,
Danny



--
Sent from: http://gstreamer-devel.966125.n4.nabble.com/
_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel

[danny.smith]

This error was actually due to a bug in a device driver. Gstreamer is working
correctly.

Regards,
Danny



--
Sent from: http://gstreamer-devel.966125.n4.nabble.com/
_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel