Sur d’autres sites (11434)

• FFMPEG xstack not recognizing inputs

  12 août 2020, par Josh

  I'm trying to arrange three input videos into a single output video using ffmpeg's xstack. I currently have the operations working with a vstack followed by an hstack, but would like to combine them into an xstack for performance.

  


  I've tried copying the syntax from multiple locations such as :

  


  https://trac.ffmpeg.org/wiki/Create%20a%20mosaic%20out%20of%20several%20input%20videos%20using%20xstack

  


  Vertically or horizontally stack (mosaic) several videos using ffmpeg ?

  


  My command is as follows :

  


  


  C :\ffmpeg\bin\ffmpeg.exe -i states_full.mp4 -i title.mp4 -i graphs.mp4" -filter_complex "[0:v] setpts=PTS-STARTPTS, scale=qvga [a0] ; [1:v] setpts=PTS-STARTPTS, scale=qvga [a1] ; [2:v] setpts=PTS-STARTPTS, scale=qvga [a2] ; [a0][a1][a2]xstack=inputs=3:layout=0_0|w0_0|w0_h0[out] " -map "[out]" -c:v libx264 -t '30' -f matroska output.mp4

  


  


  The command always errors out at the same spot, with the same error message :

  


  


  'w0_0' is not recognized as an internal or external command,
operable program or batch file.

  


  


  Some odd behavior is that even when I change the layout section to :

  


  layout=w0_0|0_0|w0_h0


  


  The error message is still on the middle '0_0' meaning it may be an error in formatting.

  


  This issue is very strange, as the vstack and hstack still work, only the xstack fails.

  


• GoPro (MP4) video timestamp sync with precision of milliseconds

  3 février 2021, par Raphael Ottoni

  I need your help with a data sync problem... I m currently trying to sync my GoPro video with real world time (a.k.a my notebook). I manage to sync date and time of my notebook and my GoPro 3+ black perfectly. The problem is that when the GoPro save the files in disk it round up the milliseconds on the creation_time (the milliseconds is always 000000) . Thus, turning the perfect sync impossible. In attachment is a picture of the meta information (extracted by ffprobe) of the MP4 video.

  



  My question is : What I have to do, so the GoPro actually save the creation_time with precision of milliseconds ?

  



  Another small question : Looking at the attachment figure, we see the "timecode" which is a time synchronization data in the format of hours:minuts:seconds:frame. I was thinking that I could use the "frame" value to calculate the missing milliseconds value. If we take this attachment, as a example, we can see that the frame value is "36". Meaning that the millisecond that it started to record was the one associated with the 36th frame of the FPS (in this video : 60fps) value : Some thing like 1000/60 * 36 which is 600 milliseconds, thus the actual creation_time of this video would be : 2017-07-19T18:10:34.600

  



  Is this logic right ? it didn't work ! I don't know what else to do.

  



  P.S : I need this kind of time precision because I will sync the video frames with a external sensor data that is recorded at 11hz.

  



  Please Help

  



  

  



  update

  



  I forgot to mention, even if you check the original raw file information, inside the GoPro SSD card, using "stats" to read the creation time (see attachment) it still has the same timestamp without milliseconds.

  



  

  


• Anomalie #2381 : Corriger le niveau d’intertitre

  9 juin 2018, par b b

  Il y a des H2 dans la dist, qui introduisent des listes d’articles, de résultats, ou des blocs (forum), je pense qu’ils peuvent rester comme ça.

  Si le bloc de forum sous le texte de l’article reste en h2, il va se retrouver "au même niveau" qu’un intertitre en h2 donc, c’est pas top non ?