[Gstreamer-bugs] [Bug 142962] New: - Error converting wav file to ogg/vorbis
bugzilla-daemon at bugzilla.gnome.org
bugzilla-daemon at bugzilla.gnome.org
Sat May 22 07:46:21 PDT 2004
http://bugzilla.gnome.org/show_bug.cgi?id=142962
GStreamer | gst-plugins | Ver: HEAD CVS
Summary: Error converting wav file to ogg/vorbis
Product: GStreamer
Version: HEAD CVS
Platform: Other
OS/Version: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: gst-plugins
AssignedTo: gstreamer-maint at bugzilla.gnome.org
ReportedBy: thaytan at mad.scientist.com
QAContact: gstreamer-maint at bugzilla.gnome.org
I'm using the following script to read a wav file and encode to ogg/vorbis:
INFILE=$1
shift
OUTFILE=$1
shift
gst-launch filesrc location="$INFILE" ! typefind ! spider ! \
audioconvert ! rawvorbisenc managed=true quality=0.85 ! { queue ! oggmux !
filesink location="$OUTFILE" } $@
The file output has 4096 null (\0) bytes at the start before the Ogg header. It
seems to be cause by a DISCONT event to new offset 4096 feeding down the
pipeline before any buffers are pushed from oggmux. rawvorbisenc and oggmux just
pass it on, resulting in filesink seeking to 4096 bytes in before data output.
My reasoning for it looks like:
* spider instantiates wavparse to read the file
* wavparse does some seek in the filesrc to a different offset, resulting in a
DISCONT downstream
* the DISCONT is passed downstream.
Since they're encoders, either oggmux or rawvorbisenc should handle this
discont, shouldn't they?
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
You are the QA contact for the bug, or are watching the QA contact.
More information about the Gstreamer-bugs
mailing list