Recherche avancée

Sur d’autres sites (5100)

• FFMPEG on Heroku exceeds memory quota in testing

  5 juillet 2022, par Patrick Vellia

  After following this tutorial, and getting it to work locally on my own development environment, before really getting my hands dirty and working deeper on my own project implementation, I decided to push it up to Heroku to test in a staging environment.

  


  I had to have Heroku add the FFMPEG build-pack and turn on the Redis Server for ActionCable to work.

  


  I didn't link the staging to a cloud storage bucket on Google or Amazon yet, just allowed it to upload directly to the dymo disk for testing. So it would go into the storage directory as it would in development for now.

  


  the test MOV file is 186 MB in size.

  


  The system uploaded the file fine.

  


  According to the logs, it then copied the file from storage to tmp as the tutorial has us do.

  


  Then it called streamio-ffmpeg's transcode method.

  


  At this point, Heroku forcibly kills the dymo because it far exceeds the memory quota.

  


  As this is a test environment, it's only on the free tier of Heroku.

  


  I'm thinking I won't be able to directly process video projects on Heroku itself, unless I'm wrong ? Would it be better to call an API like Cloud Functions or Amazon Lambda, or spin up a Compute Engine long enough to process the FFMPEG command ?

  


• FFMPEG Container Change Cannot View Audio Channels or Audio Sample Rate On File Details

  6 juillet 2014, par user3089120

  I’m using FFMPEG to change the container from AVI to MP4. After this change has been done, I’m right-clicking on the mp4 file and selecting properties, then clicking the "Details" tab. The number of audio "Channels" and "Audio sample rate" is blank. I want it to show the information for that file. The original file shows this information. I do not want to re-encode just change the container. Here is the FFMPEG command I’m using :

  ffmpeg -i "F :\TEST ENVIRONMENT\Test.avi" -c:v copy -c:a copy "F :\TEST ENVIRONMENT\Test1.mp4"

  Would really appreciate your help with this issue.

  Thank you

• lavu/tx : clip when converting table values to fixed-point

  9 janvier 2021, par Lynne

  lavu/tx : clip when converting table values to fixed-point
  INT32_MAX (2147483647) isn't exactly representable by a floating point
  
  value, with the closest being 2147483648.0. So when rescaling a value
  
  of 1.0, this could overflow when casting the 64-bit value returned from
  
  lrintf() into 32 bits.
  
  Unfortunately the properties of integer overflows don't match up well
  
  with how a Fourier Transform operates. So clip the value before
  
  casting to a 32-bit int.
  Should be noted we don't have overflows with the table values we're
  
  currently using. However, converting a Kaiser-Bessel window function
  
  with a length of 256 and a parameter of 5.0 to fixed point did create
  
  overflows. So this is more of insurance to save debugging time
  
  in case something changes in the future.
  
  The macro is only used during init, so it being a little slower is
  
  not a problem.
  

  • [DH] libavutil/tx_priv.h