
Recherche avancée
Autres articles (60)
-
MediaSPIP Core : La Configuration
9 novembre 2010, parMediaSPIP Core fournit par défaut trois pages différentes de configuration (ces pages utilisent le plugin de configuration CFG pour fonctionner) : une page spécifique à la configuration générale du squelettes ; une page spécifique à la configuration de la page d’accueil du site ; une page spécifique à la configuration des secteurs ;
Il fournit également une page supplémentaire qui n’apparait que lorsque certains plugins sont activés permettant de contrôler l’affichage et les fonctionnalités spécifiques (...) -
Use, discuss, criticize
13 avril 2011, parTalk to people directly involved in MediaSPIP’s development, or to people around you who could use MediaSPIP to share, enhance or develop their creative projects.
The bigger the community, the more MediaSPIP’s potential will be explored and the faster the software will evolve.
A discussion list is available for all exchanges between users. -
MediaSPIP en mode privé (Intranet)
17 septembre 2013, parÀ partir de la version 0.3, un canal de MediaSPIP peut devenir privé, bloqué à toute personne non identifiée grâce au plugin "Intranet/extranet".
Le plugin Intranet/extranet, lorsqu’il est activé, permet de bloquer l’accès au canal à tout visiteur non identifié, l’empêchant d’accéder au contenu en le redirigeant systématiquement vers le formulaire d’identification.
Ce système peut être particulièrement utile pour certaines utilisations comme : Atelier de travail avec des enfants dont le contenu ne doit pas (...)
Sur d’autres sites (7770)
-
FFmpeg with multiple output streams
22 novembre 2018, par William BlakeI am using ffmpeg to combine an rtsp stream with an audio stream from a usb mic. I would like to stream the combined audio and and video to an RTMP stream and just the audio to an icecast stream simultaneously. I have them working separately but am having difficulty finding the magic combination using the -f tee parameter. It seems like that would be the best way. This was the reference I was trying to use : https://trac.ffmpeg.org/wiki/Creating%20multiple%20outputs
Here are the separate commands :
ffmpeg -rtsp_transport tcp -use_wallclock_as_timestamps 1 -thread_queue_size 1024 \
-i "rtsp://RTSP-SERVER-ADDRESS" \
-f alsa -thread_queue_size 1024 -ac 1 -itsoffset 00:00:01.2 -i hw:1,0 \
-vcodec copy -acodec mp3 -ar 44100 -ab 32k -map 0:v -map 1:a -bufsize 12000k \
-f flv 'RTMP-SERVER-ADDRESS'
ffmpeg -ac 1 -f alsa -i hw:1,0 -acodec mp3 -ab 32k -ac 1 -content_type audio/mpeg -f mp3 icecast://ICECAST-ADDRESSHowever my attempts to combine them have been futile. Any thoughts ?
-
SRT protocol not found - Raspbery Pi 4 via ffmpeg
12 août 2021, par Tim MartinWe tried to stream from a rasp Pi 4 via SRT, but we got a error : "protocol not found". Our command line is :


ffplay srt://127.0.0.1:9500?mode=listener&latency=20000



We tried the following guides :
https://trac.ffmpeg.org/wiki/CompilationGuide/Ubuntu
how to compile ffmpeg with enabling libsrt
https://www.undergroundnews.dk/index.php/item/107-rtmp-eller-srt-streaming


Those guides worked so far and compiled but we still got the error message.


Do you have any ideas how to get the srt protocol working on a pi via ffmpeg ?


-
Compiling FFMPEG on CentOS DigitalOcean
29 juillet 2015, par coder_ukI set up a DigitalOcean instance running CentOS 6.5 and successfully followed the guide to compile FFMPEG (https://trac.ffmpeg.org/wiki/CompilationGuide/Centos). Hurrah !
But of course I realised that by default, DigitalOcean creates a root user and so ffmpeg now lives in /root/bin/ffmpeg. Which isn’t ideal because when I want to exec the ffmpeg bin from nginx, I would have to run nginx as root for it to have permission.
Questions ...
1) Long-shot, but presumably if I change the owner of the ffmpeg binary to nginx, it still won’t work, because nginx won’t be able to access the /root folder it is in. Correct ?
2) I could run nginx as root (’user root’). But this seems like a very bad idea. Correct ?
3) Which leaves me with the option of creating a new user, and then compiling ffmpeg into its home folder. But : which user ? EC2 creates ’ec2-user’, so should I make my own equivalent for DO ? But then won’t I have to run nginx as that user, else I’ll run into the same problem ?
Or should I compile ffmpeg into the ’nginx’ home folder, if indeed it has one ? Is that how it is supposed to be done ?
Since compiling ffmpeg takes ages, I don’t want to keep doing it, and the static files all seem very out of date. Thanks