
Recherche avancée
Autres articles (95)
-
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 (...) -
HTML5 audio and video support
13 avril 2011, parMediaSPIP uses HTML5 video and audio tags to play multimedia files, taking advantage of the latest W3C innovations supported by modern browsers.
The MediaSPIP player used has been created specifically for MediaSPIP and can be easily adapted to fit in with a specific theme.
For older browsers the Flowplayer flash fallback is used.
MediaSPIP allows for media playback on major mobile platforms with the above (...) -
ANNEXE : Les plugins utilisés spécifiquement pour la ferme
5 mars 2010, parLe site central/maître de la ferme a besoin d’utiliser plusieurs plugins supplémentaires vis à vis des canaux pour son bon fonctionnement. le plugin Gestion de la mutualisation ; le plugin inscription3 pour gérer les inscriptions et les demandes de création d’instance de mutualisation dès l’inscription des utilisateurs ; le plugin verifier qui fournit une API de vérification des champs (utilisé par inscription3) ; le plugin champs extras v2 nécessité par inscription3 (...)
Sur d’autres sites (13794)
-
Changing start number in segment name - ffmpeg mpeg dash encoder
4 mars 2019, par TrycoderI’m trying to implement MPEG dash live streaming using FFmpeg dash encoder and shaka player.
Is there any way to set the start number to any value other than 1 ?
For example,
chunk-stream0-00009.m4s
instead of the default starting segmentchunk-stream0-00001.m4s
-
Does not work -hls_playlist in ffmpeg in the -dash section
18 mars 2019, par jidckiiI will use this assembly ffmpeg
https://hub.docker.com/r/jrottenberg/ffmpeg/ffmpeg version 3.4.1 Copyright (c) 2000-2017 the FFmpeg developers
built with gcc 6.2.1 (Alpine 6.2.1) 20160822I’m trying to do dash and hls at the same time.
In the documentation from here http://ffmpeg.org/ffmpeg-all.html#dash-2
the key is :
-hls_playlist hls_playlist
Generate HLS playlist files as well. The master playlist is generated
with the filename master.m3u8. One media playlist file is generated for
each stream with filenames media_0.m3u8, media_1.m3u8, etc.those. mpd and m3u8 must be created at the same time.
Running :
ffmpeg -re \
-analyzeduration 20000000 \
-i udp: //239.0.0.1: 1234? overrun_nonfatal = 1 \
-map 0 \
-c copy \
-f dash \
-min_seg_duration 5000000 \
-window_size 10 \
-extra_window_size 10 \
-remove_at_exit 1 \
-hls_playlist 1 \
-use_timeline 1 \
-use_template 1 \
-vtag avc1 \
-atag mp4a \
cam01.mpdand get an error :
Unrecognized option 'hls_playlist'.
Error splitting the argument list: Option not found`without the
-hls_playlist
everything works correctly ...What could be the problem ?
-
MPEG-DASH not working. MPD validation fails
16 novembre 2017, par Marko36I am trying to serve video using MPEG-DASH. No success. I have tried the following :
Following the instructions on webproject.org, using FFMPEG, I have created several variants of the original video and the DASH MPD manifest, containing metadata. However, the manifest does not validate using http://dashif.org/conformance.html. This validator itself is quite useless, as it provides unusable info about the error. I have found in a post from 2014, that one of the errors generated by FFMPEG is capital letters in some metadata (not a critical one, but could have been fixed for years !). Other errors detected, but not described. No tangible info from any of these other validators either : http://www-itec.uni-klu.ac.at/dash/?page_id=605 (produces rubbish info), https://github.com/Eyevinn/dash-validator-js (throws an exception)
Following instructions on mozilla.org, produces the same non-working result, as the instructions are nearly identical (including same resolution*bitrate sets), except that Mozilla omits the use of dash.js, which is deemed necessary by the rest of the internet.
This guide on Bitmovin, utilizing x264 and MP4Box does not work either. Going by the instructions, I have to recode the original x264 video twice. The final version of videos are in some cases twice the size of their intermediate versions and 720p video is actually larger than its 1080p, higher bitrate counterpart. No need to go further. (Yet, this is the only way that actually produced segments..)
I have spent 3 days on the above, read about all there is on the web from the other frustrated adopters, and ran out of options. I would really apreciate some pro tips ! Thanks !