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 539200 - vorbisenc sometimes produces non-reproduceable headers
vorbisenc sometimes produces non-reproduceable headers
Status: RESOLVED INVALID
Product: GStreamer
Classification: Platform
Component: gst-plugins-base
git master
Other Linux
: Normal normal
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-06-19 23:12 UTC by Olivier Crête
Modified: 2008-06-20 17:40 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
test case to show the problem (908 bytes, text/plain)
2008-06-19 23:13 UTC, Olivier Crête 		Details

Description Olivier Crête 2008-06-19 23:12:32 UTC 
depending on when I plug the vorbisenc to my audiotestsrc, I get different headers.. This makes it extremely hard to predictably pre-generate SDP offers for live audio. I'm attaching a simple test.. Btw, it fails about half the time here..
Comment 1 Olivier Crête 2008-06-19 23:13:14 UTC 
Created attachment 113081 [details]
test case to show the problem
Comment 2 Olivier Crête 2008-06-19 23:35:44 UTC 
Arg, the problem is that the tee sends the TAG event to the first one, but not the second one.

So the solution is twofold:

1. Have the tee buffer and forward events intelligently...

2. Convince the xiph-rtp people to not pass the tags in the configuration="" parameter, they're not really required for decoding anyway
Comment 3 Stefan Sauer (gstreamer, gtkdoc dev) 2008-06-20 08:54:17 UTC 
Oliver, does the patch in Bug #474016 help?
Comment 4 Olivier Crête 2008-06-20 17:40:59 UTC 
The patch in bug #474016 does alleviate the problem (ie it works fine).

Although I now think that rtpvorbispay should remove the comment header and regenerate the ident field so to not have it depend onthe comment header.. But that is probably for another day.