Recherche avancée

Sur d’autres sites (11633)

• Question with complex ffmpeg compositing, overlays, visualizations etc [closed]

  14 novembre 2023, par Michael Ciesielczyk

  I'm trying to make a video that will consist of an underlying video that will need to repeat until the end of the video. The video's length as well as to video elements will come from a wav audio file. There will also be one static image overlay and 3 to 5 more images that will be overlayed at set intervals.

  


  I was able to get a little ways with a few of the elements but when I have tried to put them all together in one go I can't figure it out. And I'm trying to get it in one got to get the best possible image quality I can so I don't end up re encoding the video multiple times. I'm also using this as a template for multiple videos so when I get it figured out I can just change the images to generate the new videos.

  


  so I have these elements :

  


  background video: bg.mp4
audio file: test.wav
static image: logo.png
rotating images: 1.png, 2.png, 3.png


  


  so I have :

  


  ffmpeg -i test.wav -filter_complex " 
[0:a]avectorscope=s=1320x1240:zoom=1.5,pad=3840:2160[vs]; 
[0:a]showwaves=s=1280x202:colors=White:mode=line[sw];[vs][sw]overlay=x=(main_w- 
overlay_w)/2:y=(main_h-400)[bg]" -map "[bg]" -map 0:a  -y -acodec aac video.mp4


  


  This gets me my 4k video file and my two visualizations and my audio in my video file placed about where I want them.

  


  I can get the rotating images to appear at the right times overlayed on the bg.mp4 file with this.

  


  ffmpeg -i bg.mp4 -i 1.png -i 2.png -i 3.png -filter_complex "[0] 
[1]overlay=x=0:y=0:enable='between(t,0,4)'[out];[out] 
[2]overlay=x=0:y=0:enable='between(t,4,8)'[out];[out] 
[3]overlay=x=0:y=0:enable='between(t,8,12)'[out]" -map "[out]" video.mp4


  


  But I can't figure out how to do it all together. I have ended up with bg.mp4 file playing inside the avectorscope visual. like the rest of that box was cropping it. And I know I can loop an overlay video with -stream_loop -1 and shortest=1 but I'm not sure what to do in order to have the bg video loop until the end of the audio.

  


  I think some of my trouble is I am terrible dyslexic and a missing comma or missing close quote and it's a no go.

  


  Anyone able to help me put this together ?

  


  Oh and one last thing. I'm also wanting to put some simple text overlayed. like with

  


  overlay=0:0,drawtext=fontfile=/usr/share/fonts/TTF/Vera.ttf:fontcolor=
white:x=200:y=200:text='"text'[out]"`


  


  thank you to anyone who can help me !

  


• ffmpeg scale question.It succeed when the size is 2048,but when 4096 failed [closed]

  7 septembre 2023, par 徐谷歌

  if :

  


  ffmpeg -y -loop 1 -i ./rebirth/image4.png -loop 1 -t 1.4 -i temp.png -filter_complex "[0]scale=2048:2048[video0],[video0][1]xfade=transition=fade:duration=0.8:offset=0.1" -c:v libx264 -r 30 -pix_fmt yuv444p temp.mp4


  


  it goes right.but when temp.png is bigger,it goes wrong,like :

  


  ffmpeg -y -loop 1 -i ./rebirth/image4.png -loop 1 -t 1.4 -i temp.png -filter_complex "[0]scale=4096:4096[video0],[video0][1]xfade=transition=fade:duration=0.8:offset=0.1" -c:v libx264 -r 30 -pix_fmt yuv444p temp.mp4


  


  I have enlarge the temp.png in the 2nd example.the size of image4.png is 1152x1152.

  


• FFmpeg - Wave64 (.w64) file format : question regarding chunk GUIDs

  26 janvier 2023, par pdu

  I am having trouble understanding the headers of the Wave64 (.w64) files generated by ffmpeg and especially the GUIDs.

  


  The specification

  


  I have found this document which describes the file format and the GUIDs. I have also found other websites (here and here) that (indirectly) point to the same document. So this document is the only thing I have.

  


  According to this document the GUIDs are 128bits/16bytes long and should start with the FourCC of the Wave file format, but in lowercase instead of uppercase (see page 3). It also says that the 64bits fields are stored in little-endian (see item 3 of the list page 1), but it does not say anything about 128bits fields (but it should be the same).
For example the GUID for the RIFF chunk is : 66666972-912E-11CF-A5D6-28DB04C10000.

  


  The problem

  


  When I open a .w64 file generated by ffmpeg with an hex editor, I get this : 72 69 66 66 2E 91 CF 11 A5 D6 28 DB 04 C1 00 00. At the beginning, 76 69 66 66 stands for riff in ASCII. We can see that 0x66666972 from the spec was indeed stored in little-endian order (so far, so good). If we continue, we have 2E 91 and CF 11, which are still little-endian for 0x912E and 0x11CF. But now it gets weird : the following group of bytes are : A5 D6 and 28 DB 04 C1 00 00 for 0xA5D6 and 0x28DB04C10000 in the spec. So it is in big-endian now ?

  


  For reference, the relevant ffmpeg source files are wavenc.c, w64.h and w64.c.
I have also found this thread where someone implemented a .wav to .w64 converter (see the .7z attachment in the first post) and the GUIDs are stored in the same way as ffmpeg.

  


  Conclusion

  


  Seeing that two different implementations are doing the same thing, it probably means that I am missing something. Do you have any explanation ?