
Recherche avancée
Médias (2)
-
SPIP - plugins - embed code - Exemple
2 septembre 2013, par
Mis à jour : Septembre 2013
Langue : français
Type : Image
-
Publier une image simplement
13 avril 2011, par ,
Mis à jour : Février 2012
Langue : français
Type : Video
Autres articles (68)
-
Gestion des droits de création et d’édition des objets
8 février 2011, parPar défaut, beaucoup de fonctionnalités sont limitées aux administrateurs mais restent configurables indépendamment pour modifier leur statut minimal d’utilisation notamment : la rédaction de contenus sur le site modifiables dans la gestion des templates de formulaires ; l’ajout de notes aux articles ; l’ajout de légendes et d’annotations sur les images ;
-
Le plugin : Podcasts.
14 juillet 2010, parLe problème du podcasting est à nouveau un problème révélateur de la normalisation des transports de données sur Internet.
Deux formats intéressants existent : Celui développé par Apple, très axé sur l’utilisation d’iTunes dont la SPEC est ici ; Le format "Media RSS Module" qui est plus "libre" notamment soutenu par Yahoo et le logiciel Miro ;
Types de fichiers supportés dans les flux
Le format d’Apple n’autorise que les formats suivants dans ses flux : .mp3 audio/mpeg .m4a audio/x-m4a .mp4 (...) -
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 (...)
Sur d’autres sites (6115)
-
Passing FFmpeg encoder output to live 555 media server
23 septembre 2013, par AshutoshI need help on transmitting encoded output from encoder video output to live 555 media server.
ret=avcodec_encode_video2(c,&pkt,(AVFrame*)&sc_dst_data,&gotim);
source=ByteStreamMemoryBufferSource::createNew(*env,pkt.data,ret);
if (source == NULL){}
videoES = source;
video_source=H264VideoStreamFramer::createNew(*env,videoES);
video_sink->startPlaying(*video_source,afterPlaying, video_sink);The above codes doesn't transmit the streams properly.it breaks.any insights on how to do for a proper streaming in ffmpeg ?
Please help. -
Republish RTMP or RTSP stream to Windows Media Services
25 novembre 2016, par Ioannis KokkinisI would like a definite answer on if it is possible to republish an RTMP stream to a windows media services publishing point with any free software (preferably ffmpeg).If yes, how ? This point can be a smooth streaming publishing point or the older version of media services.
for the smooth streaming scenario there is some information on the internet, but no real answers or working examples on how it was achieved. People suggest to use ffmpeg this way :
ffmpeg -re -i rtmp://xxx.xxx.xxx.xxx:1935/application/stream -movflags isml+frag_keyframe -f ismv -threads 0 -acodec copy -vcodec copy 'http://xxx.xxx.xxx.xxx/publishpoint_name.isml/Streams(video)'
This ofcourse requires for the the source video to be h264 and source audio to be aac. also requires that you have setup IIS and installed the smooth streaming web component and have setup a push publishing point with the name "publishpoint_name" (not sure if the isml is needed)
The above does not work for me, and information is scarce on the internet.
-
avformat/hls : Fix regression with ranged media segments
26 juillet 2016, par Anssi Hannulaavformat/hls : Fix regression with ranged media segments
Commit 81306fd4bdf ("hls : eliminate ffurl_* usage", merged in d0fc5de3a6)
changed the hls demuxer to use AVIOContext instead of URLContext for its
HTTP requests.HLS demuxer uses the "offset" option of the http demuxer, requesting
the initial file offset for the I/O (http URLProtocol uses the "Range :"
HTTP header to try to accommodate that).However, the code in libavformat/aviobuf.c seems to be doing its own
accounting for the current file offset (AVIOContext.pos), with the
assumption that the initial offset is always zero.HLS demuxer does an explicit seek after open_url to account for cases
where the "offset" was not effective (due to the URL being a local file
or the HTTP server not obeying it), which should be a no-op in case the
file offset is already at that position.However, since aviobuf.c code thinks the starting offset is 0, this
doesn’t work properly.This breaks retrieval of ranged media segments.
To fix the regression, just drop the seek call from the HLS demuxer when
the HTTP(S) protocol is used.