[gstreamer-bugs] [Bug 590859] Conversion of MOV to OGG looses sync

[GStreamer (bugzilla.gnome.org)]

If you have any questions why you received this email, please see the text at
the end of this email. Replies to this email are NOT read, please see the text
at the end of this email. You can add comments to this bug at:
  http://bugzilla.gnome.org/show_bug.cgi?id=590859

  GStreamer | don't know | Ver: 0.10.13

Tim-Philipp Müller changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEEDINFO




------- Comment #4 from Tim-Philipp Müller  2009-08-05 22:47 UTC -------
> Tried oggconvert-0.3.2-5.fc11.noarch but it doesn't seem to work at all.

Not sure if I've ever heard of this tool ..

> Transmaggeddon on Fedora/Rawhide KVM machine was so incredibly slow, that I
> gave up on it (after waiting for half an hour and the ETA was still growing not
> shrinking).

Surprising, wonder what's going on there. It shouldn't really be much slower
than the equivalent gst-launch pipeline. I'm sure Christian will have a look at
it.

I only asked as an easy way to find out whether it's a bug in the pipeline
description or not (since transcoding tools are more likely to get the pipeline
right for more cases).


> > Does it work if you use vorbis?
> > 
> > Have you tried inserting a ... ! videorate ! video/x-raw-yuv,framerate=25/1 !
> > ... or so before theoraenc?
> 
> Hmm, that makes a difference.

"makes a difference" = better/fixed, or just not completely broken but there is
still a problem?

Does 'that' refer to the videorate or vorbis? Obviously, it should work with
flacenc as well, so if it doesn't, that's still a bug (I only asked if it works
with vorbis because vorbis is more widely used with ogg than flac, at least for
video files, and the chances that the vorbis encoder does the right thing here
are higher).


> So, I guess it was just a PEBKAC, right?

If it's just the missing videorate, then I guess so. There isn't really a
straight-forward fix here that I can see. I do think we should be doing
something smarter here though, but I'm not sure it can easily be done or is
worth doing in the 0.10 timeframe (I'm sure someone else will comment if they
have some ideas). Otherwise I'll put it into the stuff-to-fix-for-0.11/1.0
list.


-- 
See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.

You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=590859.