Recherche avancée

Sur d’autres sites (8963)

• 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

  


• avfilter/zoompan : add in_time variable

  19 juin 2020, par exwm

  avfilter/zoompan : add in_time variable
  Currently, the zoompan filter exposes a 'time' variable (missing from docs) for use in
  
  the 'zoom', 'x', and 'y' expressions. This variable is perhaps better named
  
  'out_time' as it represents the timestamp in seconds of each output frame
  
  produced by zoompan. This patch adds aliases 'out_time' and 'ot' for 'time'.
  This patch also adds an 'in_time' (alias 'it') variable that provides access
  
  to the timestamp in seconds of each input frame to the zoompan filter.
  
  This helps to design zoompan filters that depend on the input video timestamps.
  
  For example, it makes it easy to zoom in instantly for only some portion of a video.
  
  Both the 'out_time' and 'in_time' variables have been added in the documentation
  
  for zoompan.
  Example usage of 'in_time' in the zoompan filter to zoom in 2x for the
  
  first second of the input video and 1x for the rest :
  
      zoompan=z='if(between(in_time,0,1),2,1):d=1'
  V2 : Fix zoompan filter documentation stating that the time variable
  
  would be NAN if the input timestamp is unknown.
  V3 : Add 'it' alias for 'in_time. Add 'out_time' and 'ot' aliases for 'time'.
  
  Minor corrections to zoompan docs.
  Signed-off-by : exwm <thighsman@protonmail.com>
  

  • [DH] doc/filters.texi
  • [DH] libavfilter/vf_zoompan.c

• Google Cloud Platform Storage JSON API upload breaks audio files..?! How to fix ?

  13 octobre 2017, par Zolai

  I did manage to upload files to Google storage with GCP resumable upload (json api) :
  https://cloud.google.com/storage/docs/json_api/v1/how-tos/resumable-upload

  Using jQuery and Plupload http://www.plupload.com

  But now it seems that audio files loses their codecs in upload and those won’t play or ffmpeg can’t probe those. More testing showed that actually .flac files are ok to ffmpeg, but for example .m4a files are not.

  I need to get most of the audio files uploaded to google storage and be able to probe those with ffmpeg. And must be able upload big files over 100Mb. That’s why I believe JSON API is best or only possible way.

  I think I have metadata also added correctly, but now I’m confused how to continue..
  Any ideas what could be the problem here ?

  EDIT (more info) :

  I had working software :

  • Using regular POST > /temp > Google Cloud Storage Client (php).
  • GCP Storage Client uploaded files with perfection.
  • Even that I named uploaded files with random unique name like "woeiwehf.tmp", those did work and ffmpeg could probe them fine.

  THEN something happened, I guess uploading like this was limited (or something) :

  • What meant that my solution couldn’t upload anymore big files, over 32Mb.

  • Well that wasn’t best solution anyway, so that’s okey, that this changed.

  NOW :

  • I have changed software so it uses GCP JSON API upload resumable, and this mainly works
  • But I had to change files to look like "woeiwehf.flac" or what ever type is. ".tmp" didn’t work anymore.
  • For example .flac files work nicely, but .m4a will not.
  • I’ve tested uploading many different ways, and it seems that JSON API upload loses at least codecs and bit rate.

  —

  I would be very grateful if I could get help how to resolve this.
  I guess one solution may could be to fork ffmpeg client and manually set audio codec, but I’m saving that for the last solution.