Recherche avancée

Sur d’autres sites (11582)

• Merging multiple videos in a template/layout with Python FFMPEG ?

  14 janvier 2021, par J. M. Arnold

  I'm currently trying to edit videos with the Python library of FFMPEG. I'm working with multiple file formats, precisely .mp4, .png and text inputs (.txt). The goal is to embed the different video files within a "layout" - for demonstration purposes I tried to design an example picture :

  


  

  


  The output is supposed to be a 1920x1080 .mp4 file with the following Elements :

  


  

  • Element 3 is the video itself (due to it being a mobile phone screen recording, it's about the size displayed there)

  


  • Element 1 and 2 are the "boarders", i.e. static pictures (?)

  


  • Element 4 represents a regularly changing text - input through the python script (probably be read from a .txt file)

  


  • Element 5 portrays a .png, .svg or alike ; in general a "picture" in the broad sense.

  


  


  What I'm trying to achieve is to create a sort of template file in which I "just" need to input the different .mp4 and .png files, as well as the text and in the end I'll receive a .mp4 file whereas my Python script functions as the navigator sending the data packages to FFMPEG to process the video itself.

  


  I dug into the FFMPEG library as well as the python-specific repository and wasn't able to find such an option. There were lots of articles explaining the usage of "channel layouts" (though these don't seem to fit my need).

  


  In case anyone wants to try on the same versions :

  


  

  • python --version :
Python 3.7.3

  


  • pip show ffmpeg : Version : 1.4 (it's the most recent ; on an off-topic note : It's not obligatory to use FFMPEG, I'd prefer using this library though if it doesn't offer the functionality I'm looking for, I'd highly appreciate if someone suggested something else)

  


  


• lavfi/drawutils : improve colorspace support

  2 juin 2022, par rcombs

  lavfi/drawutils : improve colorspace support
   Introduce ff_draw_init2, which takes explicit colorspace and range
  
    args
  
   Use lavu/csp and lavfi/colorspace for conversion, rather than the
  
    lavu/colorspace.h macros
  
   Use the passed-in colorspace when performing RGB->YUV conversions
  The upshot of this is :
  
   Support for YUV spaces other than BT601
  
   Better rounding for all conversions
  
   Particular rounding improvements in >8-bit formats, which previously
  
    used simple left-shifts
  
   Support for limited-range RGB
  
   Support for full-range YUV in non-J pixfmts
  Due to the rounding improvements, this results in a large number of
  
  minor changes to FATE tests.
  Signed-off-by : rcombs <rcombs@rcombs.me>
  

  • [DH] libavfilter/drawutils.c
  • [DH] libavfilter/drawutils.h
  • [DH] tests/ref/fate/filter-chromashift-smear
  • [DH] tests/ref/fate/filter-chromashift-wrap
  • [DH] tests/ref/fate/filter-decimate
  • [DH] tests/ref/fate/filter-fps-down
  • [DH] tests/ref/fate/filter-fps-down-eof-pass
  • [DH] tests/ref/fate/filter-fps-down-round-down
  • [DH] tests/ref/fate/filter-fps-down-round-up
  • [DH] tests/ref/fate/filter-fps-start-drop
  • [DH] tests/ref/fate/filter-fps-start-fill
  • [DH] tests/ref/fate/filter-fps-up
  • [DH] tests/ref/fate/filter-fps-up-round-down
  • [DH] tests/ref/fate/filter-fps-up-round-up
  • [DH] tests/ref/fate/filter-framerate-12bit-down
  • [DH] tests/ref/fate/filter-framerate-12bit-up
  • [DH] tests/ref/fate/filter-framerate-down
  • [DH] tests/ref/fate/filter-framerate-up
  • [DH] tests/ref/fate/filter-metadata-signalstats-yuv420p10
  • [DH] tests/ref/fate/filter-minterpolate-down
  • [DH] tests/ref/fate/filter-minterpolate-up
  • [DH] tests/ref/fate/filter-mpdecimate
  • [DH] tests/ref/fate/filter-overlay_yuv420p10
  • [DH] tests/ref/fate/filter-overlay_yuv422p10
  • [DH] tests/ref/fate/filter-pixfmts-pad
  • [DH] tests/ref/fate/filter-pixfmts-tinterlace_pad
  • [DH] tests/ref/fate/filter-testsrc2-yuv420p
  • [DH] tests/ref/fate/filter-testsrc2-yuv444p
  • [DH] tests/ref/fate/filter-tpad-add
  • [DH] tests/ref/fate/filter-tpad-clone
  • [DH] tests/ref/fate/filter-unsharp-yuv420p10
  • [DH] tests/ref/fate/filter-untile

• Watermarking with scale2ref conundrum - video resizes to watermark rather than watermark scaling to fit video

  6 janvier 2023, par Robert Dio

  Hope you can hep me figure out where I am misleading myself. I am trying to watermark a bunch of videos with varying resolution sizes with a .png watermark file that is 1200x600. I have videos that are as large as 2480x1280 and as small as 360x141.

  


  I had originally thought that ffmpeg could handle it, but I am having issues with the conversion, and I am pretty sure it is my misunderstanding of how to leverage scale2ref command properly. Now, from scale2ref documentation they say this :

  


  


  Scale a subtitle stream (b) to match the main video (a) in size before overlaying

  


  'scale2ref[b][a] ;[a][b]overlay'

  


  


  I understand that stream[b] is my watermark file, and stream[a] is my video file.

  


  My ffmpeg command is this :

  


  while read -r line || [[ -n "$line" ]]; do fn_out="w$line"; (/u2/vidmarktest/scripttesting/files_jeud8334j/dioffmpeg/ffmpeg -report -nostdin -i /u2/vidmarktest/scripttesting/files_jeud8334j/"$line" -i /u2/vidmarktest/mw1.1200x600.png -filter_complex "scale2ref[b][a];[b][a]overlay=x=(main_w-overlay_w)/2:y=(main_h-overlay_h)/2" /u2/vidmarktest/scripttesting/files_jeud8334j/converted/"$fn_out" -c:v libx265); done < videos.txt 


  


  To do some 'splainin, it is going to be part of a bash script that will be cron-ed so we can make sure we have all our latest submissions to the directory watermarked.

  


  The problem is this :

  


  All of my converted videos are scaled to fit 1200x600 now, rather than remaining in their original configuration with the watermark being the part that should be scaled to fit the video.

  


  To note, that in this section : [b][a]overlay=x=(main_w-overlay_w)/2:y=(main_h-overlay_h)/2, many will say I need to switch the [a] and [b] values. When you do that, the watermark is obscured by the video, not interlaced. Switching those two values puts the [b] value (the watermark) over the [a] value (the video).

  


  Any feedback will be highly appreciated, welcomed, and graded :)

  


  I am expecting to get the watermark to adjust to the video resolution, but am failing miserably. What do I not know about ffmpeg and scale2ref that is causing my problem ?