Recherche avancée

Sur d’autres sites (5108)

• How to set frame offset for source and reference video for calculating using FFMpeg commandline ?

  1er septembre 2018, par Souvik Das

  I have a scenario where I am streaming a reference video on a server machine and receiving it at a client machine with exact same codec, using FFMpeg via UDP/RTP.

  So, I have a reference.avi file and a recording.ts file with me. Now, due to a network side issue and FFMpeg discarding old frames, often the recording.ts lacks exactly 12 FRAMES from the beginning. Sometimes, it may lack more frames in-between but that’d due to general network traffic and packet loss reason and I don’t plan to account for that. Anyways, due to those 12 frames, when I calculate the PSNR, it drops down to 13, even though remaining frames may/may not be affected.

  So, my aim is to discard first 12 frames from reference.ts and then compare. For that, I would also need to adjust the frames from recording.ts.

  Consider the following scenario :

  reference.ts has 1500 frames. So naturally I am going to cut-short it 1488. Then we have the following cases :

  1. recording.ts has 1500 frames. This is not affected. Still I will remove 12 frames to match the count. So frame 1 would then represent frame 13.
  2. recording.ts has 1496 frames. This is not affected. Still I will remove 12 frames even though it’d get to 1484 count assuming that frame 1 would then represent frame 13.
  3. recording.ts has 1488 frames. This is affected. No need to remove frames.
  4. recording.ts has 1480 frames. This is affected. No need to remove frames.

  Once that is done, then I will calcualte the PSNR. So, my FFMpeg should be able to do all this, hopefully in a single command on bash.

  A better alternative would be for FFMpeg to find the where the 13th frame is in recording.ts and then cut-short from the beginning. That’d be more preferred and even more if there is no cut-shorting required, i.e. if offset could be set in-line to command and no additional video output is generated for use in PSNR comparison.

  Current I am using the following command to calculate the PSNR.

  ffmpeg -i 'recording.ts' -vf "movie='reference.avi', psnr=stats_file='psnr.txt'" -f rawvideo -y /dev/null

  It’d be great if somebody could help me in this regard. Thanks.

• Anomalie #3075 : #LOGO_ARTICLE_RUBRIQUE_NORMAL ne retourne rien sous SPIP 3

  7 octobre 2018

  C’est juste que je déteste les comportements apparemment dérogatoires.

  Or, j’ai l’impression que _NORMAL et _SURVOL sont des suffixes qui permettent de ne retourner qu’un des 2 logos.
  Mais que ces suffixes ne marchent pas avec #LOGO_ARTICLE_RUBRIQUE

  Donc, oui, j’ai reçu une réponse qui met sur le même plan les suffixes _NORMAL/_SURVOL et _RUBRIQUE

  Mais puisque j’ai pu comprendre de travers par une systématisation abusive des suffixes en question (_NORMAL/_SURVOL), je penses qu’il faut, soit corriger le code (ce qui serait esthétiquement souhaitable), soit documenter la non généricité de ces suffixes (ce qui éviterait de passer à côté de l’info qui finalement n’est que dans le code).

  Et j’insiste qu’il n’est pas logique ni cohérent de ne pas pouvoir extraire le logo normal ou de survol dans toutes les situations.

• Is it possible to use FFmpeg to cut "random" sections from a folder of videos and concat them into 1 video ?

  14 novembre 2018, par EmmyStrand

  I realize this sounds like an easy question, and one that has been answered before. However, I cannot seem to find a script which can read a folder of videos with varying lengths, copy a random segment from each video, and concat them into a single video.

  An example :

  I have a folder with 150 videos labeled Fashion-Setlist-01.mp4, Fashion-Setlist-02.mp4, etc.
  Each are over 1 hour. I would like to pull a random 10 seconds section from each video and then randomly add them together resulting in a video. This may seem easy with only a few videos, but the plan is to read from potentially 100’s of videos. It should be possible to pull multiple sections from each video as well. I suppose we could run the script twice for more segments if the video needed to be longer.