
Recherche avancée
Autres articles (77)
-
Des sites réalisés avec MediaSPIP
2 mai 2011, parCette page présente quelques-uns des sites fonctionnant sous MediaSPIP.
Vous pouvez bien entendu ajouter le votre grâce au formulaire en bas de page. -
Creating farms of unique websites
13 avril 2011, parMediaSPIP platforms can be installed as a farm, with a single "core" hosted on a dedicated server and used by multiple websites.
This allows (among other things) : implementation costs to be shared between several different projects / individuals rapid deployment of multiple unique sites creation of groups of like-minded sites, making it possible to browse media in a more controlled and selective environment than the major "open" (...) -
Le profil des utilisateurs
12 avril 2011, parChaque utilisateur dispose d’une page de profil lui permettant de modifier ses informations personnelle. Dans le menu de haut de page par défaut, un élément de menu est automatiquement créé à l’initialisation de MediaSPIP, visible uniquement si le visiteur est identifié sur le site.
L’utilisateur a accès à la modification de profil depuis sa page auteur, un lien dans la navigation "Modifier votre profil" est (...)
Sur d’autres sites (8424)
-
avformat/hls : fix segment selection regression on track changes of live streams
15 octobre 2015, par Anssi Hannulaavformat/hls : fix segment selection regression on track changes of live streams
Commit ad701326b43078b90 ("avformat/hls : open playlists immediately when
AVDISCARD_ALL is dropped") inadvertently caused first_packet to never be
cleared, causing select_cur_seq_no() to not use the specific code for
live streams.In practice this means that when the user selects a different audio
track during live stream (i.e. non-VOD) playback, there may be some
additional delay as the code might select an incorrect segment at first,
and we have to wait for video to catch audio (if too late segment was
selected) or to download more following audio segments (if too early
segment was selected).Fix that by restoring the zeroing of first_packet.
-
Pre-Transcoding live streams before Re-stream them to wowza Streaming Engine [on hold]
14 décembre 2017, par Ninjai’am using ffmpeg on other device to get live feed from cam and convert them to multi bitrate outputs localy and stream them to a remote wowza to achieve adaptive bitrate content for users with optimized resources i have succeeded to transcode to one specifique bitrate locally using this line
ffmpeg -re -i cuted.mp4 -c:v libx264 -profile:v baseline -level:v 1.2 -r 12 -g 96 -vb 110000 -s 212x120 -c:a libvo_aacenc -ab 40000 -ar 22050 -ac 1 -f rtsp -muxdelay 0.1 rtsp://*****:*****@***.168.*0.*0:1935/live/myStream
but i need at least 4 resolutions support i’ve tried to lunched twice at the same time with diffrent resolutions but in wowza engine manager => incoming streams i got one stream input, i appreciate any suggestion
-
Stream Live Video and relay audio only to icecast2 server
28 avril 2019, par BadAddyI have a working nginx server which allows me to stream live video from our mobile production system. We also have a radio station on a separate server and would like to stream to both. But I cannot make it work, nor can I get any logs or error information to explain why. I have tried nginx config and FFMPEG to try and resolve this.
I have tried various attempts using what I think I understand from other pages online :
exec_push FFREPORT=file=ffreport.log:level=48 ffmpeg -i $basename.flv -vn -acodec mp3 rtmp://source:********!!@xxx.xxx.xxx.180:8000/live;
Also tried using the simple restream in the nginx conf :
application restream {
live on;
exec_push ffmpeg -i $basename.flv -vn -acodec mp3 rtmp://source:***********@xxx.xxx.xxx.180:8000/live;
# push server2:1935
}I have used the same information on Mixxx Live Broadcast Connection to get the details, thinking I am asking the same thing on the icecast2 server. Just the source is the nginx server.
This is the full conf on nginx
rtmp {
server {
listen 1935;
chunk_size 4000;
application live {
live on;
allow publish 127.0.0.1;
allow publish all;
allow play all;
record all;
record_path /usr/local/nginx/flv-streams;
record_unique on;
exec_record_done ffmpeg -i $basename.flv /usr/local/nginx/html/streams/$basename.mp4;
hls on;
hls_nested on;
hls_path /mnt/hls;
hls_fragment 1s;
hls_sync 1ms;
#exec_push FFREPORT=file=ffreport.log:level=48 ffmpeg -i $basename.flv -vn -acodec mp3 rtmp://source:*************@xxx.xxx.xxx.xxx:8000/live;
}
# Video on Demand
application streams {
play /usr/local/nginx/html/streams/;
}
# Restream
application restream {
live on;
exec_push ffmpeg -i $basename.flv -vn -acodec mp3 rtmp://source***************@xxx.xxx.xxx:8000/live;
# push server2:1935
}
}I would like those that can watch any broadcast with video, but if they can only listen, like a radio, I want them to listen via our radio player. They are two different streams, on different servers.
At the moment I am using software to stream to both and would like to prevent this.
Not found, by my own wording perhaps, any idea on how to do this.
UPDATE
With the help from TBR I have managed to get the stream from the Nginx Server going to a new server hosting icecast2. However, not in the way expected. It does this 32x faster, so not a stream as such.
ffmpeg -i fcpr-1554651146.flv -vn -c:a mp3 icecast://source:password@10.0.0.0:8000/fcprlive.mp3
However, I wonder if I have been thinking of this the wrong way. In my liquidsoap file I have this code :
#!/usr/bin/liquidsoap
# Log dir set("log.file.path","/tmp/basic-radio.log")
# Music
myplaylist = mksafe(playlist("/home/offlineftp/playlist"))
#Live Source
set("harbor.bind_addr","0.0.0.0")
live = input.http("http://localhost:8000/fcprlive")
radio = fallback(track_sensitive=false, [live,plist])
# Stream it out
output.icecast(%mp3, host = "localhost", port = 8000,
password = "pass", mount = "/fcpr")Should I look at using LiquidSoap to pull the stream from Nginx, when live, and if no signal than go to the fallback ?