Recherche avancée

Sur d’autres sites (5910)

• avcodec/hevc : Add init for sao_edge_filter

  28 décembre 2023, par jinbo

  avcodec/hevc : Add init for sao_edge_filter
  Forgot to init c->sao_edge_filter[idx] when idx=0/1/2/3.
  
  After this patch, the speedup of decoding H265 4K 30FPS
  
  30Mbps on 3A6000 is about 7% (42fps==>45fps).
  Change-Id : I521999b397fa72b931a23c165cf45f276440cdfb
  
  Reviewed-by : yinshiyou-hf@loongson.cn
  
  Signed-off-by : Michael Niedermayer <michael@niedermayer.cc>
  

  • [DH] libavcodec/loongarch/hevcdsp_init_loongarch.c

• Playback drops frames or stutter on good hardware [closed]

  30 décembre 2023, par Lemonek

  I'm planning to use TDARR and tring to prevent any issues before with (re)encoding. And I have stumbled on issue with one TV Show - recently I have downloaded refreshed old show but playback stutters on TV or drops frames (few frames every few secs - so video plays nicely but suddenly few frames are dropeed and then for next few secs it playsnicely - no issues with sound)

  


  I guess this particular video has some options which causes issues or I dont know but here are some facts I have gathered (ffprobe -v quiet -print_format json -show_format -show_streams) :

  


  

  1. The TV is capable of playing FullHD HECV 10bit smoothly https://pastebin.com/0efSGjk9

  


  2. Original video stutters https://pastebin.com/vvLn8y4a

  


  3. Converted video (QSV) stutters (linux/ffmpeg https://pastebin.com/XbazLEft
Below cutout part of script parameters for converting - $FPS is supplied as without it ffmpeg does not create I Frames but that is not a problem here)

  


  


          -hide_banner -y -init_hw_device qsv:hw \
        -hwaccel qsv -hwaccel_output_format qsv \
        -i "$FILENAME_BACK" \
        -map 0:v:0 -map 0:a:0 \
        -c:v hevc_qsv -preset slow -global_quality 22 -g $FPS\
        -c:a copy \
        -movflags faststart "$FILENAME_OUTPUT"


  


  

  4. Converted video (NVENC) plays nicely (win/handbrake) https://pastebin.com/HbBNMZvT

  


  


  In the end I wish I could create "safe" parameters list which I will supply to TDARR and not to worry about issues while converting videos.

  


  Forgot to mention - Hardware on which Im planning to mass encode has Intel proc with QSV capabilities - I'm not planning to encode on NV.

  


  If needed - I can provide any other information.

  


• ffmpeg convert video to size 275x157 pixels [closed]

  21 janvier 2024, par degr

  I want to make video of exact size 275x157, but ffmpeg always make it 274x156.

  


  So far I try next list of commands :

  


  //it from my opinion, it should make vide of my size, and add padding if necessary, but result is same - 274x156
ffmpeg -i ScreenRecorderProject7.mkv  -strict -2 -filter:v "pad=275:157:(275-iw*min(275/iw\,157/ih))/2:(157-ih*min(275/iw\,157/ih))/2" WrathTrailer1334x750.mp4

//more advanced variant of previous command, not work also
ffmpeg -i ScreenRecorderProject7.mkv  -strict -2 -filter:v "pad=275:157:(275-iw*min(275/iw\,157/ih))/2:(157-ih*min(275/iw\,157/ih))/2" WrathTrailer1334x750.mp4

//it told width is not divisible by 2
ffmpeg -i ScreenRecorderProject5.mkv -strict -2 -vf scale=275x157 -aspect 1.75259 output.mp4

//in description it was mentioned it add 1px pad, but I feel it is wrong; result incorrect
ffmpeg -i ScreenRecorderProject5.mkv -strict -2 -vf pad="width=ceil(iw/2)*2:height=ceil(ih/2)*2" output.mp4


  


  Also I try to do so with movavi video editor, streamlabs and couple online video converters and always I'm getting wrong resolution. Cant understand what is wrong with that numbers