[Bug 732945] Unable to seek giosink

[GStreamer (bugzilla.gnome.org)]

https://bugzilla.gnome.org/show_bug.cgi?id=732945
  GStreamer | gst-plugins-base | unspecified

Phillip Wood <phillip.wood> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|encodebin creates           |Unable to seek giosink
                   |unplayable m4a files        |

--- Comment #5 from Phillip Wood <phillip.wood at dunelm.org.uk> 2014-07-09 15:40:48 UTC ---
(In reply to comment #4)
> Can you provide the encodebin profile.

[profile-m4a]
name = m4a
description = MPEG 4 Audio
format = video/quicktime, variant=iso
type = container

[streamprofile-m4a-1]
parent = m4a
type = audio
format = audio/mpeg, mpegversion=4, stream-format=raw
presence = 1


> Notice this:
> 
> 0:00:19.077658053 27666 0x7f8670004cf0 WARN                   qtmux
> gstqtmux.c:1649:gst_qt_mux_start_file:<muxer> downstream did not handle seeking
> query
> 0:00:19.077709467 27666 0x7f8670004cf0 WARN                   qtmux
> gstqtmux.c:1658:gst_qt_mux_start_file:<muxer> warning: Downstream is not
> seekable and headers can't be rewritten
> 
> Also notice that sound-juicer uses giosink, not filesink. Can you test case
> (need to write it in C or Python) a muxing pipeline with giosink. Might be
> where the problem is. I'm not familiar with seeking a sink, but I think that's
> what mp4mux. For mp4 we put the header and index at the start, hence we need to
> seek back in the file at EOS, and prepend that data. It is likely that giosink
> is missing this feature. But I'm pretty much guessing at the moment.

Thanks, I think you're right. I just changed the sound-juicer pipeline to use
faac ! mp4mux instead of encodebin and I get the same error so it looks like
giosink is the problem. For mp3 encoding xingmux manages to put the Xing header
at the front of the file with giosink though.

-- 
Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.