[gstreamer-bugs] [Bug 344937] [oggdemux] add support for queries in BYTES format

[GStreamer (bugzilla.gnome.org)]

Do not reply to this via email (we are currently unable to handle email
responses and they get discarded).  You can add comments to this bug at
http://bugzilla.gnome.org/show_bug.cgi?id=344937
 GStreamer | gst-plugins-base | Ver: HEAD CVS


Tim-Philipp Müller changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|normal                      |enhancement
            Summary|oggdemux cannot handle      |[oggdemux] add support for
                   |queries in format           |queries in BYTES format
                   |GST_FORMAT_BYTES...         |




------- Comment #7 from Tim-Philipp Müller  2006-06-29 20:30 UTC -------

> Ok, we don't know the exact number of bytes. But we can estimate and submit a
> better estimation afterwards (GST_MESSAGE_DURATION).

Messages are posted on the bus and are meant for the application (or to notify
pipelines to invalidate any cached durations they might hold, although that is
not yet implemented AFAIK), they won't be seen by downstream elements like the
elements from your tar plugin. I don't think posting duration messages with
BYTE durations on the bus is useful (even more so as they don't relate to the
individual streams either)



> That's not yet done, but I'll work on that if you agree on the concept:
> A query on a pad returns the figures of that pad (and only that pad).
> 
> This definition would be highly useful for the tar plugin (#303975). That's why
> I submitted this bug report.

Could you expand on how/where this would be useful for the tar plugin? And
where oggdemux fits into this? Why would you want to tar up raw vorbis/theora
streams?

And why can't this estimating be done in the tar elements (or why would it be
better not done there but in oggdemux?)


-- 
Configure bugmail: http://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.