Recherche avancée

Sur d’autres sites (3751)

• Usurper of FATE

  31 juillet 2010, par Multimedia Mike — FATE Server

  Mans sent a message to the FFmpeg-devel list today :

  A new FATE

  Mike’s FATE system has done a great job over the last few years. It
  is however beginning to prove inadequate in various ways :

  [various shortcomings already dissected at length on this very blog]

  To address the above-mentioned issues, I have been working on a
  replacement system which is now ready to be announced.

  Check it out : http://fate.ffmpeg.org/.

  Considering that he just obsoleted something I’ve poured a lot of time and energy into over the last 2.5 years, is my first reaction to this news supposed to be unbridled joy ? Hey, I’m already on record as stating that I wouldn’t mind throwing away all of FATE if there was a better alternative.

  I’m not certain but I’m pretty sure that at this point, the original FATE server is practically obsolete. Mans is already testing all of his configurations as well as the configs I test. As soon as the other FATE installations switch over to the new server, I should be able to redirect fate.multimedia.cx -> fate.ffmpeg.org, sell most of my computers, and spend more time with my family.

  Thanks, Mans !

• how to encoded a 10bit .tif file into an HDR video by ffmpeg in command line [closed]

  6 juin 2024, par ziyuan

  how can i encoded a RGB 10 bit tif file into a hdr video by ffmpeg ?

  


  and one more question : should the input tiff must be 16bit big- or little- endian ?

  


  i have try the method here : How can I encode RGB images into HDR10 videos in ffmpeg command-line ?
,the same command and setting as the method. However i got this : code 1026 : YUV color family cannot have RGB matrix coefficients

  


  here is the tiff file i have tried :https://drive.google.com/file/d/1G8oYf9-FQJJPNUxwB0_FmlvBaMnUhCVL/view?usp=drive_link

  


  and i found that :
the procedure information it seems like the ffmpeg automatically set the output format as gbrp16le even when i set the -pix_fmt yuv420p10le.

  


• vsync flag usage in ffmpeg while filtering

  13 octobre 2022, par antortjim

  I am trying to apply a threshold to an input video with ffmpeg, but I observe the following warning emitted for every processed frame

  


  [mp4 @ 0x56360181a200] Non-monotonous DTS in output stream 0:0; previous: 182272, current: 182272; changing to 182273. This may result in incorrect timestamps in the output file.


  


  where the previous and current are always 1 less than the value to which the DTS (Decoding Time Stamp) is changed

  


  I have noticed this warning is emitted only if I set -vsync passthrough (which I changed from the original -vsync 0 which is seen in many online examples).

  


  # input.mp4 has resolution 790x790
ffmpeg -vsync passthrough  -i input.mp4  -f lavfi -i color=808080:s=790x790 -f lavfi -i color=black:s=790x790 -f lavfi -i color=white:s=790x790 -filter_complex '[0:v][1:v][2:v][3:v]threshold' -an -c:v h264_nvenc threshold.mp4


  


  Shall I leave the vsync flag set to the default (auto or -1), or is -vsync passthrough essential to guarantee the frames are displayed in the right order ? In that case, how do I handle this warning ? Some other online examples I found of users experiencing this warning are different from mine, because in their case they are concatenating videos (see 1, 2

  


  From the documentation on the -vsync flag, at the end, I see :

  


  


  With -map you can select from which stream the timestamps should be taken. You can leave either video or audio unchanged and sync the remaining stream(s) to the unchanged one

  


  


  Maybe this warning should be handled with -map ? But I don't know how.

  


  Sidenote, I keep getting the deprecation warning asserting me to change -vsync for -fps_mode, however doing so breaks the command.

  


  FFPEG Version :

  


  commit 28ac2279adb860ea8b90d3073603912bf3eb6a83 from ffmpeg master branch

  


  ffmpeg version N-108625-g28ac2279ad Copyright (c) 2000-2022 the FFmpeg developers
built with gcc 9 (Ubuntu 9.4.0-1ubuntu1~20.04.1)
configuration: --enable-nonfree --enable-cuda-nvcc --enable-libnpp --enable-gpl --extra-cflags=-I/usr/local/cuda/include --extra-ldflags=-L/usr/local/cuda/lib64 --disable-static --enable-shared
libavutil      57. 39.101 / 57. 39.101
libavcodec     59. 50.100 / 59. 50.100
libavformat    59. 34.101 / 59. 34.101
libavdevice    59.  8.101 / 59.  8.101
libavfilter     8. 49.101 /  8. 49.101
libswscale      6.  8.112 /  6.  8.112
libswresample   4.  9.100 /  4.  9.100
libpostproc    56.  7.100 / 56.  7.100


  


  OS

  


  Ubuntu 20.04.4 LTS