
Recherche avancée
Autres articles (99)
-
MediaSPIP 0.1 Beta version
25 avril 2011, parMediaSPIP 0.1 beta is the first version of MediaSPIP proclaimed as "usable".
The zip file provided here only contains the sources of MediaSPIP in its standalone version.
To get a working installation, you must manually install all-software dependencies on the server.
If you want to use this archive for an installation in "farm mode", you will also need to proceed to other manual (...) -
Websites made with MediaSPIP
2 mai 2011, parThis page lists some websites based on MediaSPIP.
-
Encodage et transformation en formats lisibles sur Internet
10 avril 2011MediaSPIP transforme et ré-encode les documents mis en ligne afin de les rendre lisibles sur Internet et automatiquement utilisables sans intervention du créateur de contenu.
Les vidéos sont automatiquement encodées dans les formats supportés par HTML5 : MP4, Ogv et WebM. La version "MP4" est également utilisée pour le lecteur flash de secours nécessaire aux anciens navigateurs.
Les documents audios sont également ré-encodés dans les deux formats utilisables par HTML5 :MP3 et Ogg. La version "MP3" (...)
Sur d’autres sites (10003)
-
install ffmpeg on amazon ecr linux python
27 mai 2024, par Luka SavicI'm trying to install ffmpeg on docker for amazon lambda function.
Code for Dockerfile is :


FROM public.ecr.aws/lambda/python:3.8

# Copy function code
COPY app.py ${LAMBDA_TASK_ROOT}

# Install the function's dependencies using file requirements.txt
# from your project folder.

COPY requirements.txt .
RUN yum install gcc -y
RUN pip3 install -r requirements.txt --target "${LAMBDA_TASK_ROOT}"
RUN yum install -y ffmpeg

# Set the CMD to your handler (could also be done as a parameter override outside of the Dockerfile)
CMD [ "app.handler" ]



I am getting an error :


> [6/6] RUN yum install -y ffmpeg:
#9 0.538 Loaded plugins: ovl
#9 1.814 No package ffmpeg available.
#9 1.843 Error: Nothing to do



-
How to : stream with ffmpeg and nginx rtmp, Ubuntu
3 décembre 2020, par WurmDnginx installed with https://nginx.org/en/linux_packages.html in Ubuntu 18.04


sudo apt -y install curl gnupg2 ca-certificates lsb-release ;
echo "deb http://nginx.org/packages/ubuntu `lsb_release -cs` nginx" | sudo tee /etc/apt/sources.list.d/nginx.list ;
curl -fsSL https://nginx.org/keys/nginx_signing.key | sudo apt-key add - ;
sudo apt update ;
sudo apt install nginx ;



nginx up and running


$ ps -aux | grep nginx
root 5602 0.0 0.0 33348 880 ? Ss 17:03 0:00 nginx: master process nginx
nginx 5603 0.0 0.0 33744 2748 ? S 17:03 0:00 nginx: worker process



with /etc/nginx/nginx.conf


rtmp {
 server {
 listen 1935;
 chunk_size 4096;

 application live {
 live on;
 record off;
 allow publish 127.0.0.1;
 deny publish all;
 }
 }
}



ffmpeg -f lavfi -i testsrc -t 30 -pix_fmt yuv420p -f flv rtmp://localhost/live/test
yields

ffmpeg version 3.4.8-0ubuntu0.2 Copyright (c) 2000-2020 the FFmpeg developers
 built with gcc 7 (Ubuntu 7.5.0-3ubuntu1~18.04)
 configuration: --prefix=/usr --extra-version=0ubuntu0.2 --toolchain=hardened --libdir=/usr/lib/x86_64-linux-gnu --incdir=/usr/include/x86_64-linux-gnu --enable-gpl --disable-stripping --enable-avresample --enable-avisynth --enable-gnutls --enable-ladspa --enable-libass --enable-libbluray --enable-libbs2b --enable-libcaca --enable-libcdio --enable-libflite --enable-libfontconfig --enable-libfreetype --enable-libfribidi --enable-libgme --enable-libgsm --enable-libmp3lame --enable-libmysofa --enable-libopenjpeg --enable-libopenmpt --enable-libopus --enable-libpulse --enable-librubberband --enable-librsvg --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libssh --enable-libtheora --enable-libtwolame --enable-libvorbis --enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx265 --enable-libxml2 --enable-libxvid --enable-libzmq --enable-libzvbi --enable-omx --enable-openal --enable-opengl --enable-sdl2 --enable-libdc1394 --enable-libdrm --enable-libiec61883 --enable-chromaprint --enable-frei0r --enable-libopencv --enable-libx264 --enable-shared
 libavutil 55. 78.100 / 55. 78.100
 libavcodec 57.107.100 / 57.107.100
 libavformat 57. 83.100 / 57. 83.100
 libavdevice 57. 10.100 / 57. 10.100
 libavfilter 6.107.100 / 6.107.100
 libavresample 3. 7. 0 / 3. 7. 0
 libswscale 4. 8.100 / 4. 8.100
 libswresample 2. 9.100 / 2. 9.100
 libpostproc 54. 7.100 / 54. 7.100
Input #0, lavfi, from 'testsrc':
 Duration: N/A, start: 0.000000, bitrate: N/A
 Stream #0:0: Video: rawvideo (RGB[24] / 0x18424752), rgb24, 320x240 [SAR 1:1 DAR 4:3], 25 tbr, 25 tbn, 25 tbc
[tcp @ 0x5611668b8c00] Connection to tcp://localhost:1935 failed: Connection refused
[rtmp @ 0x5611668b8520] Cannot open connection tcp://localhost:1935
rtmp://localhost/live: Connection refused



Clue :
Nothing seems to be listening on port 1935.
netstat -tap | grep 1935
yields nothing
Clue2 :
Albeitps
shows app as running,systemctl status nginx.service
shows app status down

● nginx.service - nginx - high performance web server
 Loaded: loaded (/lib/systemd/system/nginx.service; enabled; vendor preset: enabled)
 Active: failed (Result: exit-code) since Thu 2020-12-03 19:37:17 CET; 7min ago
 Docs: http://nginx.org/en/docs/
 Process: 5709 ExecStart=/usr/sbin/nginx -c /etc/nginx/nginx.conf (code=exited, status=1/FAILURE)



Things checked given other stackoverflow questions :


- 

- trying to connect to
rtmp://localhost/live/test
and in nginx.conf the application is correctly namedlive
- nginx.conf correctly placed at /etc/nginx/, no other nginx.conf files exist, and
nginx -s reload
called to make sure it is loaded - no
localhost
instances in the conf file, all renamed to127.0.0.1








- trying to connect to
-
How to load cross domain videos into video tag for web gl processing ?
22 novembre 2013, par user3022391Current working on a project using FFMpeg and stream.m to transcode a live stream to web.m format for use in a HTML5 desktop player on chrome. All works well when sending the video to a standard video tag, however when it used in my canvas / webgl application it struggles to load the video reporting the following error repeatedly :
Uncaught SecurityError : Failed to execute 'texImage2D' on 'WebGLRenderingContext' : the video element contains cross-origin data, and may not be loaded.
Looking into CORS, it seems that because the website is loading on http (80) and I am streaming the converted video live from the stream.m server (which is on the same domain but uses port 8089 - this counts as cross-domain video sourcing. I've added allow policies to the .htaccess file and cross-domain.xml however still seeing the issue.
Does anyone know if you can add custom allow-access headers to ffmpeg output or know of an alternative workaround ?