Recherche avancée

Sur d’autres sites (5029)

• lavc/aarch64 : motion estimation functions in neon

  26 juin 2022, par Swinney, Jonathan

  lavc/aarch64 : motion estimation functions in neon
   - ff_pix_abs16_neon
  
   - ff_pix_abs16_xy2_neon
  In direct micro benchmarks of these ff functions verses their C implementations,
  
  these functions performed as follows on AWS Graviton 3.
  ff_pix_abs16_neon :
  
  pix_abs_0_0_c : 141.1
  
  pix_abs_0_0_neon : 19.6
  ff_pix_abs16_xy2_neon :
  
  pix_abs_0_3_c : 269.1
  
  pix_abs_0_3_neon : 39.3
  Tested with :
  
  ./tests/checkasm/checkasm —test=motion —bench —disable-linux-perf
  Signed-off-by : Jonathan Swinney <jswinney@amazon.com>
  
  Signed-off-by : Martin Storsjö <martin@martin.st>
  

  • [DH] libavcodec/aarch64/Makefile
  • [DH] libavcodec/aarch64/me_cmp_init_aarch64.c
  • [DH] libavcodec/aarch64/me_cmp_neon.S
  • [DH] libavcodec/me_cmp.c
  • [DH] libavcodec/me_cmp.h
  • [DH] tests/checkasm/Makefile
  • [DH] tests/checkasm/checkasm.c
  • [DH] tests/checkasm/checkasm.h
  • [DH] tests/checkasm/motion.c
  • [DH] tests/fate/checkasm.mak

• 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 ?

  


• Thumbnails from S3 Videos using FFMPEG - "No such file or directory : '/bin/ffmpeg'"

  28 juin 2022, par Nico

  I am trying to generate thumbnails from videos in an S3 bucket every x frames by following this documentation : https://aws.amazon.com/blogs/media/processing-user-generated-content-using-aws-lambda-and-ffmpeg/

  


  I am at the point where I'm testing the Lambda code provided in the documentation, but receive this error in CloudWatch Logs :

  


  

  


  Here is the portion of the Lambda code associated with this error :

  


  

  


  Any help is appreciated. Thanks !