Recherche avancée

Sur d’autres sites (10395)

• Streaming without Content-Length in response

  29 août 2011, par kain

  I'm using Node.js, Express (and connect), and fluent-ffmpeg.

  We want to stream audio files that are stored on Amazon S3 through http.

  We have all working, except that we would like to add a feature, the on-the-fly conversion of the stream through ffmpeg.

  This is working well, the problem is that some browsers checks in advance before actually getting the file.

  Incoming requests containing the Range header, for which we reply with a 206 with all the info from S3, have a fundamental problem : we need to know in advance the content-length of the file.

  We don't know that since it is going through ffmpeg.

  One solution might be to write out the resulting content-length directly on S3 when storing the file (in a special header), but this means we have to go through the pain of having queues to encode after upload just to know the size for future requests.
  It also means that if we change compressor or preset we have to go through all this over again, so it is not a viable solution.

  We also noticed big differencies in the way Chrome and Safari request the audio tag src, but this may be discussion for another topic.

  Fact is that without a proper content-length header in response everything seems to break or browsers goes in an infinite loop or restart the stream at pleasure.

  Ideas ?

• Streaming without Content-Length in response

  21 décembre 2023, par kain

  I'm using Node.js, Express (and connect), and fluent-ffmpeg.

  



  We want to stream audio files that are stored on Amazon S3 through http.

  



  We have all working, except that we would like to add a feature, the on-the-fly conversion of the stream through ffmpeg.

  



  This is working well, the problem is that some browsers checks in advance before actually getting the file.

  



  Incoming requests containing the Range header, for which we reply with a 206 with all the info from S3, have a fundamental problem : we need to know in advance the content-length of the file.

  



  We don't know that since it is going through ffmpeg.

  



  One solution might be to write out the resulting content-length directly on S3 when storing the file (in a special header), but this means we have to go through the pain of having queues to encode after upload just to know the size for future requests.
It also means that if we change compressor or preset we have to go through all this over again, so it is not a viable solution.

  



  We also noticed big differencies in the way Chrome and Safari request the audio tag src, but this may be discussion for another topic.

  



  Fact is that without a proper content-length header in response everything seems to break or browsers goes in an infinite loop or restart the stream at pleasure.

  



  Ideas ?

  


• How to rename and move files in a subdirectory with an index and the folder name ... better ?

  29 octobre 2014, par krismajean

  I’m putting together a script to take .mp4 files organized into folders that described the video (eg. cat) and I’d like to do the following :

  1. rename them with the folder name and a number ;
  2. move the video into a folder named and numbered in the same manner
  3. parse the video into frames using ffmpeg

  I’m posting this here to be a reference for others and to ask about how this could be done better. It works well but I’m wondering how to make it better.

  for dir in /path/to/parent/directory/*; do
  
  cd "$dir" && result=${PWD##*/} 
  
  cd video
  
  echo $result
  
  a=1
  
      for i in *.mp4; do
  
          dafile="$(printf "_%02d.mp4" ${a})" 
  
          dafolder="$(printf "_%02d" ${a})"
  
          newfolder=$result$dafolder
  
          newfile=$result$dafile
  
          mkdir ${newfolder}
  
          mv ${i} ${newfolder}/${newfile}
  
  
  
          cd ${newfolder}
  
              ffmpeg -i ${newfile} -r 30 -f image2 ${newfolder}-\%04d.png
  
          cd ..
  
          let a=a+1
  
      done
  
  
  
  done

  I used the following links to figure out a bunch of ideas for the code :

• Get current directory name (without full path) in Bash Script
• Renaming files in a folder to sequential numbers