After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 707984 - Random audio track for one dvb-t stream.
Random audio track for one dvb-t stream.
Status: RESOLVED OBSOLETE
Product: GStreamer
Classification: Platform
Component: gst-plugins-bad
1.0.8
Other Linux
: Normal normal
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2013-09-12 16:44 UTC by Jan ONDREJ (SAL)
Modified: 2013-09-27 12:31 UTC
See Also:
GNOME target: ---
GNOME version: 3.7/3.8


Attachments
Audio is playing. I can't tell which track, but at least plays. (3.36 KB, application/x-gzip)
2013-09-12 16:44 UTC, Jan ONDREJ (SAL)
Details
No audio - silence. (4.11 KB, application/x-gzip)
2013-09-12 16:45 UTC, Jan ONDREJ (SAL)
Details

Description Jan ONDREJ (SAL) 2013-09-12 16:44:42 UTC
Created attachment 254794 [details]
Audio is playing. I can't tell which track, but at least plays.

For one channel on my DVBT list, audio channel is randomly selected each time I start dvb-t. I can reproduce this problem using gst-launch-1.0 by running this command:

gst-launch-1.0 playbin -vvv uri=dvb://Markiza

Other channels has no problems, just this one (I don't know why).
This channel has 2 audio tracks, mul = multilanguage, sk = slovak - native for me. When I start playing, it's randomly selected that:

1. no audio is playing - disabled track is selected
2. mul track is selected
3. sk track is selected

This happens in this order, often there is no audio, which is undesired.
Attaching output from gst-launch-1.0 for playing audio and silence.
In my application I can switch to another track, which works, but it's disturbing.
Comment 1 Jan ONDREJ (SAL) 2013-09-12 16:45:11 UTC
Created attachment 254795 [details]
No audio - silence.
Comment 2 Sebastian Dröge (slomo) 2013-09-13 07:45:30 UTC
This should be a duplicate of bug #634407. Can you check again with 1.1.1 or a newer version?
Comment 4 Tim-Philipp Müller 2013-09-14 16:08:49 UTC
Could you try with 1.1.x please?
Comment 5 Jan ONDREJ (SAL) 2013-09-14 18:51:15 UTC
Unable to reproduce with 1.1.4. Any chance to backport fix to 1.0 branch?
Comment 6 Sebastian Dröge (slomo) 2013-09-16 10:10:19 UTC
Depends on someone to find the exact commits that fix it, and then only if these commits are considered safe enough to be backported. Otherwise you'll have to wait until 1.2.0, which should be there soonish.
Comment 7 Sebastian Dröge (slomo) 2013-09-27 12:31:55 UTC
With 1.2.0 being released now, let's close this.