sslug-teknik team mailing list archive

[Donald J Axel <donax@xxxxxx>]

On Wed, 27 Jul 2011 18:20:49 +0200
Atte André Jensen <atte@xxxxxxxx> wrote:

> On 07/25/2011 11:53 AM, Donald J Axel wrote:
> 
> > PAR 65536:65536 DAR 3:2, 30.02 fps, 90k tbr, 90k tbn, 180k tbc
> >      Metadata:
> >        creation_time   : 1945-07-07 17:27:21
> > [mp4 @ 0x95c9e60] Frame rate very high for a muxer not
> > effciciently supporting it.
> > Please consider specifiying a lower framerate, a different
> > muxer or -vsync 2
> >
> > Den siger framerate er vanvittig høj, 90000 (der er ikke noget
> > udstyr som kan vise 90000 billeder i sek.)
> 
> Hvor ser du 90.000? Jeg ser "30.02 fps" i fejlmeddelelsen...

Åh undskyld, det er linien timebase, som jeg mistolkede: 

[mpeg4 @ 0x95ca340] timebase 1/90000 not supported by MPEG 4
standard, the maximum admitted value for the timebase denominator
is 65535                                                      

Jeg Prøver at finde ud af hvad 90k tbr betyder. 
Google//ffmpeg tbr tbn tbc:

http://stackoverflow.com/questions/3199489/meaning-of-ffmpeg-output-tbc-tbn-tbr

Well it's all about time. FFMpeg uses in fact three different timestamps in different bases in order to work.

    * tbn = the time base in AVStream that has come from the container
    * tbc = the time base in AVCodecContext for the codec used for a particular stream
    * tbr = tbr is guessed from the video stream and is the value users want to see when they look for the video frame rate

--http://ffmpeg-users.933282.n4.nabble.com/What-does-the-output-of-ffmpeg-mean-tbr-tbn-tbc-etc-td941538.html--

There are three different time bases for time stamps in FFmpeg. The
values printed are actually reciprocals of these, i.e. 1/tbr, 1/tbn and
1/tbc.

tbn is the time base in AVStream that has come from the container, I
think. It is used for all AVStream time stamps.

tbc is the time base in AVCodecContext for the codec used for a
particular stream. It is used for all AVCodecContext and related time
stamps.

tbr is guessed from the video stream and is the value users want to see
when they look for the video frame rate, except sometimes it is twice
what one would expect because of field rate versus frame rate.

========================================================================
Gjentagelse af errmsg (laaange linier) i 
Message-ID: <j0hphh$tci$1@xxxxxxxxxxxx> 
========================================================================

> PAR 65536:65536 DAR 3:2, 30.02 fps, 90k tbr, 90k tbn, 180k tbc
>     Metadata:
>       creation_time   : 1945-07-07 17:27:21
> [mp4 @ 0x95c9e60] Frame rate very high for a muxer not effciciently 
> supporting it.
> Please consider specifiying a lower framerate, a different muxer or -vsync 2                                                     
> [buffer @ 0x95d3860] w:720 h:480 pixfmt:yuv420p tb:1/1000000 sar:65536/65536 
> sws_param:                                          
> [transpose @ 0x95c5380] w:720 h:480 dir:1 -> w:480 h:720 rotation:clockwise 
> vflip:0
> [mpeg4 @ 0x95ca340] removing common factors from framerate
> [mpeg4 @ 0x95ca340] timebase 1/90000 not supported by MPEG 4 standard, the 
> maximum admitted value for the timebase denominator is 65535                                                      




> -- 
> Atte
> 
> http://atte.dk   http://modlys.dk
> 
> 


-- 
Donald Axel <donax@xxxxxx>