Recherche avancée

Sur d’autres sites (10357)

• ffmpeg x11grab moov atom not found

  30 mars 2021, par Jintor

  2 FFMPEG process

  


  (1) generating a ffmpeg x11grab to a .mp4
(2) take the .mp4 and restream it simultaneously to multiple rtmp endpoints

  


  ISSUE the generated file in (1) have this error "moov atom not found"

  


  This is the command that generate (1) :

  


  ffmpeg -re -y -f x11grab -draw_mouse 0 -framerate 30 
-video_size $RESOLUTION -i :$DISPLAY_NUM -c:a aac -c:v libx264 
-movflags +faststart -preset ultrafast -crf 28 -refs 4 -qmin 4 
-pix_fmt yuv420p -filter:v fps=30 file.mp4


  


  in the (2) => when I try to ffmpeg -i file.mp4 output somewhere : I get "moov atom not found" so the (2) can't read or open (1).

  


  What I'm I missing

  


  in (1) -movflags +faststart doesn't seem to fix the issue

  


  ••••••• EDIT : more details on the context ••••••

  


  I'm using openvidu : webrtc with kurento and coturn.

  


  The record feature creates a .mp4 on the fly as the chat is going on.

  


  To start the recording, there is an API call i can make to my server and it automatically stops when all users leaves the chatroom OR do an other api call to stop. see composed video in this link https://docs.openvidu.io/en/2.17.0/advanced-features/recording/

  


  openvidu have also webhooks.

  


  My problem is not how to stop ffmpeg, but getting FFMPEG to encode while the mp4 or other is being generated "on the fly".

  


  There is 2 options :

  


  OPTION 1 : individual => 1 .webm per camare => this .webm ffmpeg can restream as hls or RTMP => it's working.

  


  OPTION 2 : ** but the issue is with "Composed" video => it's using ffmpeg to x11grab the session... but it's mp4 without moov ato, so ffmpeg don't do anything with this.

  


  see the composed.sh script here
https://github.com/OpenVidu/openvidu/blob/master/openvidu-server/docker/openvidu-recording/scripts/composed.sh

  


• lavu : add an API function to return the Libav version string

  2 juillet 2015, par wm4

  lavu : add an API function to return the Libav version string
  This returns something like "v12_dev0-1332-g333a27c". This is much more
  
  useful than the individual library versions, of which there are too
  
  many, and which are very hard to map back to releases or git commits.
  Signed-off-by : Janne Grunau <janne-libav@jannau.net>
  

  • [DH] .gitignore
  • [DH] Makefile
  • [DH] cmdutils.c
  • [DH] doc/APIchanges
  • [DH] libavutil/avutil.h
  • [DH] libavutil/utils.c

• Aspect ratio problems at transcoding with ffmpeg [closed]

  19 novembre 2023, par udippel

  I have a huge collection of videos from the last 20+ years, videos in all sorts of formats. I use gerbera as open source UPnP-AV media server. Our TV handles only very limited of these formats. Therefore I use the transcoding feature of gerbera (I don't want to convert the 2000+ files ; thereby avoiding loss of multiple audio tracks, (multiple) subtitles, and so forth).

  


  This is my current unified argument line for ffmpeg :
-c:v mpeg2video -maxrate 20000k -vf setdar=16/9 -r 24000/1001 -qscale:v 4 -top 1 -c:a mp2 -f mpeg -y
It works pretty okay, except of the aspect ratios. Well, I don't understand this fully, because ffprobe for File A states :
Stream #0:0: Video: mpeg4 (Simple Profile) (XVID / 0x44495658), yuv420p, 624x464 [SAR 1:1 DAR 39:29], 1500 kb/s, 25 fps, 25 tbr, 25 tbn, 25 tbc
This file displays very well.
File B comes as :
Stream #0:0(eng): Video: h264 (High), yuv420p(tv, bt709, progressive), 960x720, SAR 1:1 DAR 4:3, 23.98 fps, 23.98 tbr, 1k tbn, 180k tbc (default)
This file displays horribly squeezed vertically and doesn't fill the screen left and right neither, with the same settings of the TV. Also, playing this file (and others, naturally) the TV doesn't offer the 14:9 display option, which is available e.g. for the file further up.

  


  Both have same SAR, DAR, almost identical H:V ratios (1.345, 1.333) ; and almost identical DAR.

  


  My questions :

  


  

  1. Why, despite of almost identical pixel ratios, DAR and SAR are these files handled so differently in one and the same session on the same TV (SONY), please ?

  


  2. With which method could I instruct ffmpeg to display the second file properly, too, please ?
(I have already tried 'scale' ; but to no avail. Which could have been foreseen, since the ratios are already very close.)
My guess is, that the (tv, bt709, progressive) mess things up.
(I have already tried to add the yuv420p in the argument line, also to no avail.)

  


  


  Appreciate any help,

  


  Uwe

  


  I have already tried to add a 'scale' option ; but to no avail. Which could have been foreseen, since the ratios are already very close.
I have already tried to add the yuv420p in the argument line, also to no avail.
I have already tried force_original_aspect_ratio, but also here, nothing improving.
Also, I played with -aspect, but the aspects are okay, and would need individual corrections, which I can't and don't to do for 2000+ files. A simple 16:9 doesn't cut it.