Recherche avancée

Sur d’autres sites (7628)

• Concatenate videos from a socket and create a live stream

  24 juin 2017, par gregory andre

  I know the title is not clear so I’ll explain as best I can.When I mean concatenating from a socket is this way
  This is the command I use :

  ffmpeg -i tcp://localhost:8080 -f flv rtmp://localhost/oflaDemo/stream1497985143577

  Which makes the server simply send a 3gp file that is converted to flv and sent to the server stream, everything looks good the first file on the client, but when the server starts reading the second file and sends it, it no longer shows anything in the video. And ffmpeg throws this error.

  [flv @ 000000000060bc80] Non-monotonous DTS in output stream 0:1; previous: 3077
  
  3, current: 16928; changing to 30773. This may result in incorrect timestamps in
  
   the output file.
  
  [flv @ 000000000060bc80] Non-monotonous DTS in output stream 0:1; previous: 3077
  
  3, current: 16954; changing to 30773. This may result in incorrect timestamps in
  
   the output file.
  
  [flv @ 000000000060bc80] Non-monotonous DTS in output stream 0:1; previous: 3077
  
  3, current: 16981; changing to 30773. This may result in incorrect timestamps in
  
   the output file.
  
  [flv @ 000000000060bc80] Non-monotonous DTS in output stream 0:1; previous: 3077
  
  3, current: 17007; changing to 30773. This may result in incorrect timestamps in

  Investigate a bit about this error and some suggestions say it is for the version of ffmpeg but I already have the recent version, I tried everything but only the first file that is sent to live server, but the second I no longer appreciate some suggestion.

• mp3/aac trim precision issue

  27 janvier 2020, par Massimo Vantaggio

  Due to mp3/aac codec doesn’t support that level of trim precision so im unable to get rounded container duration (without this 6 ms) :

  ffprobe -v error -show_entries format=duration \
  
  >   -of default=noprint_wrappers=1:nokey=1 output_audio.mp4
  
  372.006000

  MP4box generation get 6 ms more for every cycle :

  [...]
  
  Next generation scheduled in 3895 ms (DASH time 412006 ms)
  
  [...]
  
  Next generation scheduled in 3895 ms (DASH time 414012 ms)

  My MP4box command :

  MP4Box -dash-live 2000 -subdur 4000 -bound -segment-timeline -no-cache -profile dashavc264:live -subsegs-per-sidx -1 -mpd-refresh 4 -time-shift 16 -min-buffer 2000 -url-template -insert-utc -bs-switching no -run-for 86400000 -dash-ctx ../../live/log.txt -out ../../live/manifest.mpd ../current/output_1080.mp4:bandwidth=4800000#video ../current/output_720.mp4:bandwidth=2400000#video ../current/output_360.mp4:bandwidth=800000#video ../current/output_audio.mp4:bandwidth=384000#audio

  after 50% of the advertised duration an error will occur (probably)

  I say probably because the time for testing it is very long so may ask if the mp4box command provide for a stable loop or if the error will occur, and if yes, it will occur, may ask an help to debug my command line on mp4box to avoid this issue ?

  Im sorry but trial and error it’s too long since every try is about 24 hours..

  Dash.js web based purpose.

  Thansk in advance !

• How to create a progress bar using nodejs ?

  31 mars 2022, par Henrique Reiss

  I found several answers on the internet about this, but none brought me enough clarity to solve this problem. ( ffmpeg-progressbar-cli doesn't work ) so I need something in javascript.

  


  I need to change the aspect ratio of some videos and I need to implement a progress bar for that. I was thinking of something like getting the total amount of frames the video has and the current frame.

  


  but I don't know how to get these two values and I don't even know if this is the best way to create a progress bar.

  


  I've seen in other answers people recommending using ffmpeg-progressbar-cli, but it doesn't work for everyone from what I've noticed.

  


  I also read the documentation looking for something about capturing only the current frame but I didn't find anything about it