Recherche avancée

Sur d’autres sites (11556)

• ffmpeg converting m4s to mp4

  12 mai 2022, par programming freak

  I'm working on DASH, trying to optimize QoE for the end user.

  



  I had a video and encoded it using ffmpeg into different bitrates and everything is fine, and the video is playable using dash.

  



  What I want is to combine the received segments from the users into one m4s and convert that m4s to mp4.

  



  I tried a lot of ways in ffmpeg, but it always give me this error :

  



  [mov,mp4,m4a,3gp,3g2,mj2 @ 0x9a9e500] could not find corresponding track id 1
[mov,mp4,m4a,3gp,3g2,mj2 @ 0x9a9e500] could not find corresponding trex
[mov,mp4,m4a,3gp,3g2,mj2 @ 0x9a9e500] error reading header
test2.m4s: Invalid data found when processing input


  



  segment_1.m4s is there.

  



  How can I resolve this issue ?

  


• Ffmpeg hardware acceleration unsupported formats betwen tranpose and auto_scaler_0

  11 août 2021, par Eduard6421

  I am trying to develop a transoding service which makes use of nvidia hardware acceleration capabilities ( The gpu used in this process is a Tesla T4) ; I want to generate a mpeg-dash playlist for my video so that i can stream it ;

  


  ffmpeg -y -hwaccel cuda -hwaccel_output_format cuda -i mobil1.mp4 -c:v h264_nvenc -c:a aac  \
-map v:0 -b:v:0 1000k -maxrate:0 1500k -bufsize:0 2500k -filter:v:0 "scale_npp=1920:1080:force_original_aspect_ratio=decrease" -map 0:a -b:a 128k \
-f dash dash.mpd


  


  But when mobile videos are uploaded ( which have rotation metadata ) I encounter the following error :

  


  Impossible to convert between the formats supported by the filter 'transpose' and the filter 'auto_scaler_0'
Error reinitializing filters!
Failed to inject frame into filter network: Function not implemented
Error while processing the decoded data for stream #0:0


  


  How can i solve this issue ?

  


• ffmpeg audio stream retiming for infinite input

  26 février 2020, par Aeon

  I have a ffmpeg process that reads input data from stdout infinitely.
  Its input data are mkv (matroska) containers (sent to stdin by another process), each container contains 4 audio streams (without any video) - 3 ACC streams and 1 FLAC stream. The output of this process is dash muxer.

  ffmpeg -hide_banner -re -fflags +getpts -avoid_negative_ts make_non_negative -stream_loop -1 -f matroska -i pipe: -map 0 -c:a copy -strict -2 -f dash -use_timeline 1 -use_template 1 -seg_duration 5 -dash_segment_type mp4 manifest.mpd

  The problem occurs after the first muxing of obtained mkv file. When it’s time to mux the next one from pipe, I get following messages :

  [matroska,webm @ 000001d3050bba40] Found unknown-length element with ID 0x18538067 at pos. 0x54c766 for which no syntax for parsing is available.
  
  [matroska,webm @ 000001d3050bba40] Seek to desired resync point failed. Seeking to earliest point available instead.
  
  [dash @ 000001ac98349080] Non-monotonous DTS in output stream 0:0; previous: 881714, current: 51200; changing to 881715. This may result in incorrect timestamps in the output file.
  
  [dash @ 000001ac98349080] Non-monotonous DTS in output stream 0:1; previous: 881714, current: 51200; changing to 881715. This may result in incorrect timestamps in the output file.
  
  [dash @ 000001ac98349080] Non-monotonous DTS in output stream 0:2; previous: 881714, current: 51200; changing to 881715. This may result in incorrect timestamps in the output file.
  
  [dash @ 000001ac98349080] Non-monotonous DTS in output stream 0:3; previous: 884005, current: 51200; changing to 884006. This may result in incorrect timestamps in the output file.
  
  [dash @ 000001ac98349080] Non-monotonous DTS in output stream 0:3; previous: 884006, current: 51244; changing to 884007. This may result in incorrect timestamps in the output file.
  
  [dash @ 000001ac98349080] Non-monotonous DTS in output stream 0:3; previous: 884007, current: 51244; changing to 884008. This may result in incorrect timestamps in the output file.
  
  [dash @ 000001ac98349080] Non-monotonous DTS in output stream 0:3; previous: 884008, current: 51288; changing to 884009. This may result in incorrect timestamps in the output file.
  
  [dash @ 000001ac98349080] Non-monotonous DTS in output stream 0:3; previous: 884009, current: 51288; changing to 884010. This may result in incorrect timestamps in the output file.
  
  [dash @ 000001ac98349080] Non-monotonous DTS in output stream 0:3; previous: 884010, current: 51332; changing to 884011. This may result in incorrect timestamps in the output file.
  
  [dash @ 000001ac98349080] Non-monotonous DTS in output stream 0:3; previous: 884011, current: 51332; changing to 884012. This may resul
  
  ...

  and dash muxer simply stops generating new segments. I do understand that it’s an issue with timestamps, but I don’t know how to fix that.

  I’ve tried to use -fflags +getpts - no success.
  use_wallclock_as_timestamps 1 solves the "Non-monotonous DTS..." issue, but brings in a bunch of issues with playback, like freezing, breaking, etc., so the playback becomes completely unlistenable.
  Something strange also happens to the SegmentTemplate node of the manifest - its timescale attribute is set to 44100, although there should be 1000000 (-frag_duration 1 is ignored in this case)

  Question : I’m asking for your help in re-timing, i.e. generating the correct timestamps for dash muxing for each new incoming file in the pipe.