Recherche avancée

Sur d’autres sites (8861)

• How to change python runtime in firebase functions

  1er août 2023, par MrBom

  I currently have python311, but it seems that it doesnt include ffmpeg. So I'm looking for ways to either change to python39 or figure out how to install and use ffmpeg.

  


  When I try

  


  import subprocess
print(subprocess.run(shlex.split("ffmpeg -version")))


  


  inside a firebase function, all I get is FileNotFoundError: [Errno 2] No such file or directory: 'ffmpeg'
I've tried a few different places like /opt/bin/ffmpeg or ffmpeg/ffmpeg since I have have ffmpeg inside the folder functions, but it always the same error.

  


  Recommendation to use python39 for ffmpeg

  


  Edit : Things I found but couldnt get it to work :

  


  gcloud functions deploy <my function="function"> --runtime python39</my>

  


  Made this from gcloud

  


• Anomalie #4692 : Utilisation de memoization en remplacement de xcache si disponible pour retrouver...

  9 mars 2021, par cedric -

  Oui et non : quand on a un filesystem qui est en de type NFS sur les mutus ou "cloud" le gain commence à être très marginal, et par ailleurs filecache créé un nombre fini de slots pour ne pas avoir à gérer la purge, et si on l’utilise a tort et à travers pour des broutilles on va donc écraser les slots des cache SPIP qui sont très couteux à calculer par des cache de résultat de fonction (qui sont bien moins couteux) et au final on y perdra largement.

  La fonction cache_me() de memoization ne fait pas le distinguo de savoir quelle méthode de cache est dispo, si c’est un cache mémoire rapide et "infini" ou un cache disque lent à utiliser avec parcimonie (et idéalement c’est pas elle qui doit le faire, mais chaque méthode qui devrait elle même déclarer dans quelle catégorie elle se place)

• FFMPEG re-broadcast/proxy MJPEG stream

  10 septembre 2022, par Ollie Pugh

  I have an MJPEG stream coming from an RPI on my home network and have an NGINX acting as a proxy on an EC2.

  


  For the camera access the flow of stream to the user is the following

  


  RPi -> mjpeg-proxy (running on EC2) -> NGINX (running on same EC2) -> user

  


  the point of mjpeg-proxy is to reduce the load on the RPi and only have one stream to the Pi and allow the EC2 to distribute that one stream.

  


  Now this work fine-ish from my PC (on same network as Pi) the streams work perfectly. But when it comes to my phone on roaming data, the stream is super choppy and the latency grows massively (this project needs minimal latency, like sub 300ms).

  


  I can't understand why this would happen ? Because even when running of my local PC its going through the Proxy hosted in the cloud, so its not as if its an advantage to it being local ?

  


  the stream is fine on another device, e.g. my laptop, but thats on the same network as the RPi. But like I said, it shouldn't makea difference as its going through a proxy !

  


  I was wondering if using FFMPEG to re-stream the mjpeg stream would be beneficial as node is notoriously slow. But I don't really want to be writing my own mjpeg-proxy in C++ to speed this all up.

  


  I have looked online for answers to FFMPEG MJPEG proxy and have been very unsuccesful