[gst-devel] How to save an ogv stream in a file

[Carlos Eduardo Matos Ellery]

Hi Ben, no success yet. :(

Today I've tried your cortado (thank you very much), but the behavior
is the same. The clock on cortado seekbar still show 27:40 to 27:50.
I've compiled my own liboggz and used oggz-basetime, but checking with
diff command, the output file generated by oggz-basetime is exactly
the same of the original file. Running oggz-info still returns
content-duration = 27min. I've tried other tools that come with
liboggz, like fix-eos and rewrite-pages, but without success. The only
win was that setting the starttime param of the cortado applet gives
me a right progress of the seekbar (it steps sec by sec from the begin
to the end), but as I said, the clock still show 27:nn. I've compiled
my own cortado too, with the master snapshot of the git but, as
expected, the result is the same.

Some alternative?

Best regards,

Carlos Eduardo Matos Ellery




On Wed, Jul 7, 2010 at 12:20 AM, Benjamin M. Schwartz
<bmschwar at fas.harvard.edu> wrote:
> OK.  The problem is that your file represents 10 seconds from about 27:40
> to 27:50.  In Ogg terms, your "basetime" is 27:40.  The Cortado applet
> shows the entire 27:50 range in the seek bar.  There are two solutions.
>
> 1.  Change the basetime.  You can do this using the oggz-basetime tool
> from the oggz tools (liboggz) ... but oggz-basetime isn't compiled by
> default or shipped by most distros, so you'll have to compile it yourself.
>
> 2.  Use the latest Cortado from Git, which fixes this problem by starting
> the seek bar at the basetime ... which also means you have to use a
> pre-release .jar of Cortado.  I happen to have a build environment set up
> for it, so here's a special jar built from HEAD, just for you:
>
> http://bemasc.net/~bens/cortado-0.6.0-plus-ellery.jar
>
> --Ben
>
>