Recherche avancée

Sur d’autres sites (6021)

• How do I deploy Whisper.cpp stream.wasm on an EC2 instance ? [closed]

  3 août, par tosUser

  How do I deploy the whisper.cpp stream.wasm demo on a EC2 instance ?

  


  The demo is available from the following git :
https://github.com/ggml-org/whisper.cpp/tree/master/examples/stream.wasm

  


  I am fairly far along, but the program hangs on Preparing ...
I do not know what is causing the issue.

  


  Here are the steps I have taken. (I am trying to make it brief, and provide more detail as necessary.)
I cloned the repository and built it locally.
It runs properly.

  


  I created an EC2 instance running Amazon Linux 2023, and uploaded the Whisper.cpp files to it.
I ssh into the server and installed nginx, it displays the default page to the server's public ip address.
I then configured nginx as a reverse proxy server :

  


      server {
        listen 80;
        server_name redactedPublicIpAddress;
        location / {
            proxy_pass http://127.0.0.1:8000;
        }
    }



  


  I enabled and restarted nginx.

  


  I then try to run whisper.cpp stream.wasm by running python3 examples/server.py
It indicates that it is serving home/ec2-user/whisper.cpp/build-em/bin to localhost:8000
This is analogous to the message when it is served locally.
Stream.wasm has a 301 response.
Helpers.js and coi-serviceworker.js have 200 responses.

  


  The index file displays normally at the public ip address/stream.wasm/

  


  However, all is not well. The js seems to hang on Preparing...
Other js functions on the page still function, I can download a model and the page indicates it was downloaded, etc. However, I cannot start recording. The start button is not active. It never properly initializes.

  


  This type of behavior is identical to trying to open the index file on my local computer without it being served.

  


  I think I am missing something simple, but do not know what it is.

  


  Here are some steps that I took afterwards that did not fix the issue :
I installed nodejs and npm so that I could install ffmpeg.wasm : npm install @ffmpeg/ffmpeg @ffmpeg/util

  


  The github page indicates that I need to put the files in the html path. So in trying to troubleshoot I put them in /user/shared/nginx/html which is where the nginx default index file is placed.

  


  I think it may be related to serving the python. The server.py file is not in a state to deploy it with uvicorn.

  


  Maybe there is some sort of cors issue.

  


  I simply do not know.

  


• Stream Recorder Using FFmpeg Fails on AWS Lambda

  10 mai, par user30495567

  I am trying to stream audio from URLs and save them to a file in S3 using AWS Lambda with FFmpeg. Here is an example FFmpeg command I'm using :

  


  ffmpeg -hide_banner -loglevel error -t 10 -i http://playerservices.streamtheworld.com/api/livestream-redirect/KTOOFMAAC_SC -ar 16000 -b:a 64k -ac 2 output.mp3


  


  

  • The FFmpeg command is getting called in a python script using subprocess.Popen()

  


  • The command works as expected on local, but does not work in an AWS Lambda python environment using a custom FFMPEG layer configured with these instructions.

  


  • When run on Lambda, I get the following error : FileNotFoundError : [Errno 2] No such file or directory : '/tmp/output.mp3'

  


  


  Note : I've also tried a version where I use python requests to stream chunks and pipe them into ffmpeg. This works for some stream URLs, but for others, such as the streamtheworld URL above, it only saves 5 seconds of audio from the stream or results in a Broken Pipe error.

  


• avformat/hls : Be more picky on extensions

  16 janvier, par Michael Niedermayer

  avformat/hls : Be more picky on extensions
  This blocks disallowed extensions from probing
  
  It also requires all available segments to have matching extensions to the format
  
  mpegts is treated independent of the extension
  It is recommended to set the whitelists correctly
  
  instead of depending on extensions, but this should help a bit,
  
  and this is easier to backport
  Fixes : CVE-2023-6602 II. HLS Force TTY Demuxer
  
  Fixes : CVE-2023-6602 IV. HLS XBIN Demuxer DoS Amplification
  The other parts of CVE-2023-6602 have been fixed by prior commits
  Found-by : Harvey Phillips of Amazon Element55 (element55)
  
  Signed-off-by : Michael Niedermayer <michael@niedermayer.cc>
  

  • [DH] doc/demuxers.texi
  • [DH] libavformat/hls.c