Recherche avancée

Sur d’autres sites (9385)

• Revision f7f0eaa581 : Add adaptation option for VBR. Allow min and maxQ to creep when the undershoot

  13 octobre 2014, par Paul Wilkins

  Changed Paths :
   Modify /vp9/encoder/vp9_firstpass.c

  
   Modify /vp9/encoder/vp9_firstpass.h

  
   Modify /vp9/encoder/vp9_ratectrl.c

  
   Modify /vp9/encoder/vp9_ratectrl.h

  
  
  Add adaptation option for VBR.

  Allow min and maxQ to creep when the undershoot
  or overshoot exceeds thresholds controlled by the
  command line under_shoot_pct and over_shoot_pct
  values.

  Default is 100%,100% which disables adaptation.

  Derf results for example undershoot% / overshoot% :-

  Head :- Mean abs (%rate error) = 14.4%

  This check in :-
  25%/25% - Mean abs (%rate error) = 6.7%
  PSNR hit -1% SSIM -0.1%

  5% / 5% - Mean abs (%rate error) = 2.2%
  PSNR hit -3.3% SSIM - 1.1%

  Most of the remaining error and most of the quality hit is
  at extreme data rates. The adaptation code still has an
  exception for material that is in effect static so that we
  don’t over adjust and over spend on YT slide show type
  content.

  (Rebase of If25a2449a415449c150acff23df713e9598d64c9
  to resolve a auto-merge error)

  Change-Id : Iec4e1613ef0d067454751d8220edb7058dfbd816

• FLV to MP4 conversion keeping PTS consistent

  16 janvier 2019, par M.Do

  The input file has the following video settings but playsback in media player at 29.97 FPS

  Video
  
  Format                      : AVC
  
  Format/Info                 : Advanced Video Codec
  
  Format profile              : Baseline@L2.1
  
  Format settings             : 2 Ref Frames
  
  Format settings, CABAC      : No
  
  Format settings, ReFrames   : 2 frames
  
  Codec ID                    : 7
  
  Duration                    : 1 min 30 s
  
  Width                       : 480 pixels
  
  Height                      : 360 pixels
  
  Display aspect ratio        : 4:3
  
  Frame rate mode             : Constant
  
  Frame rate                  : 14.985 (15000/1001) FPS
  
  Color space                 : YUV
  
  Chroma subsampling          : 4:2:0
  
  Bit depth                   : 8 bits
  
  Scan type                   : Progressive
  
  Color range                 : Limited
  
  Color primaries             : BT.601 NTSC
  
  Transfer characteristics    : BT.709
  
  Matrix coefficients         : BT.601

  However, another coded application will not accept the file as a valid file frame rates are only NTSC or PAL
  How can I force the frame rate to be presented as 29.97 without changing the duration of the clip ?

• ffmpeg - Timecode & Fractional Frame Rate (Duplicating Frames)

  29 mars 2018, par Nimble

  I record two different frame rates using ffmpeg, 60 and 100. Or at least I thought I was recording 60 and 100, now it seems it’s actually 59.94 and 99.98.

  Here is the command I was using :

  ffmpeg -y -thread_queue_size 9999 -guess_layout_max 0 -f dshow -video_size 1920x1080 -rtbufsize 2147.48M -framerate 60 ^
  
  -pixel_format yuyv422 -i video="Game Capture HD60 S (Video) (#01)":audio="ADAT (5+6) (RME Fireface UC)" -map 0:0,0:1 ^
  
  -map 0:1 -c:v h264_nvenc -preset: llhp -pix_fmt yuv420p -b:v 40M -minrate 40M -maxrate 40M -bufsize 40M -b:a 384k -ac 2 ^
  
  -r 60 -af "pan=mono|c0=c0, adelay=84" -vsync 1 -max_muxing_queue_size 9999 -f segment -segment_time 600 ^
  
  -segment_wrap 9 -reset_timestamps 1 C:\Users\djcim\Videos\PC\Camera\CPC%02d.ts ^
  
  -thread_queue_size 9999 -f dshow -video_size 3440x1440 -rtbufsize 2147.48M -framerate 100 -pixel_format nv12 ^
  
  -itsoffset 00:00:00.215 -i video="Video (00 Pro Capture HDMI 4K+)" -thread_queue_size 9999 -guess_layout_max 0 -f dshow ^
  
  -rtbufsize 2147.48M -i audio="SPDIF/ADAT (1+2) (RME Fireface UC)" -map 1:0,2:0 -map 6:0 -c:v h264_nvenc -preset: llhp ^
  
  -pix_fmt nv12 -b:v 250M -minrate 250M -maxrate 250M -bufsize 250M -b:a 384k -ac 2 -r 100 -af "adelay=141|141" -vsync 1 ^
  
  -max_muxing_queue_size 9999 -f segment -segment_time 600 -segment_wrap 9 -reset_timestamps 1 ^
  
  C:\Users\djcim\Videos\PC\PC\PC%02d.ts

  I thought all was well with my frame rates, sure ffmpeg was duplicating frames every once in a while, but I thought it was just a random occurrence caused by ffmpeg dropping a frame during processing and therefore needed to duplicate one to make it up. I didn’t think duplicating a few frames would be noticeable in the footage... until I was reviewing some from the first output, which is actually a camera, and noticed very slight stutters consistently 3 times a minute. This began to bug me, it was very noticeable and I wanted smooth footage. A bit confused I decided to try the first output by itself and watch ffmpeg to see when frames were being duplicated and found that it was duplicating frames every 17 second (16.66 to be more precise).

  After doing the math (1/16.66=.06) I realized that the frame rate of that first capture card was actually 59.94. Doing the same thing for the other output I found that my "100fps" footage is actually 99.98. But what does that really entail ?

  Should I change the fps to 59.94 and 99.98 ? Wont that cause synchronization issues as 99.98 (100*.0002=99.98) isn’t the same standard as 59.94 (60*.001=59.94) ? Or does that mean I just need to set the second output to 99.9 (100*.001=99.9) to match the standard of the first output and drop frames ? If that is the case does this mean in my editing program, Adobe Premiere, I would need to export the final video as 59.94fps not 60fps to avoid duplication of frames ? Or is there some method within timecode that remedies this issue ?

  I guess I just really don’t understand drop frame and non-drop frame timecode / timecode in general. Up until yesterday when something said 60fps I thought it meant literally 60fps but I guess 99% of the time it actually means 59.94. I’d really like to just avoid the duplication of frames as it ruins what would be a smooth experience but don’t know if I can while trying to keep everything synchronized.

  Any help or insight would be appreciated, sorry if my question is a bit confusing I am undoubtedly confused.