ffmpeg – kotzen for run-aways

Narf. Zitat:

On Wed, Dec 3, 2008 at 3:12 PM, sean darcy <seandarcy2 at gmail.com> wrote:
I’m using ffmpeg to repackage vob files to play on a ps3 ( for some reason the ps3 doesn’t like some vob’s, but always likes ffmpeg’s )
I often get the message that the codec frame rate differs from the container frame rate. How does a “container” have a frame rate? Is this a interlacing issue?
ffmpeg even with vcodec copy changes the frame rate of the video stream to 29.97 from 59.94. Should I force ( -r 59.94) the original frame rate, or does ffmpeg know what it’s doing?

 
The video container specifies a framerate, as does the video stream itself. In some cases, usually caused by badly written encoding programs, the two can disagree. When this happens, ffmpeg is obviously forced to believe one and not the other.
If ffmpeg picks the wrong one, you can, ask you mentioned, force the other framerate if you believe it to be correct.
Dark Shikari

 
Nunja. Ein ffmpeg-kodiertes File erzeugt bei mir:

Seems stream 0 codec frame rate differs from container frame rate: 30000.00 (30000/1) -> 29.97 (30000/1001)

Und während es super in mplayer abgespielt wird, ist das Ergebnis der Nutzung in OpenShot eine reine Katastrophe. Keine Ahnung, welche fps OpenShot sich da ausdenkt, sie ist nur eines: total falsch. Und Drecks-ffmpeg ist nicht in der Lage, ein korrektes File zu erzeugen, obige Meldung wird erzeuigt nach:

ffmpeg -i 25fps-source.mp4 -r 30000/1001 -sameq -vsync -1 -acodec libmp3lame -ac 2 -ar 44100 -ab 192k -threads 2 -y -copyts 29.97fps-target.mov

Videobearbeitung unter Linux: Foltermethoden des 21. Jahrhunderts.
Fsck³ :(