
Recherche avancée
Autres articles (95)
-
Mise à jour de la version 0.1 vers 0.2
24 juin 2013, parExplications des différents changements notables lors du passage de la version 0.1 de MediaSPIP à la version 0.3. Quelles sont les nouveautés
Au niveau des dépendances logicielles Utilisation des dernières versions de FFMpeg (>= v1.2.1) ; Installation des dépendances pour Smush ; Installation de MediaInfo et FFprobe pour la récupération des métadonnées ; On n’utilise plus ffmpeg2theora ; On n’installe plus flvtool2 au profit de flvtool++ ; On n’installe plus ffmpeg-php qui n’est plus maintenu au (...) -
Personnaliser en ajoutant son logo, sa bannière ou son image de fond
5 septembre 2013, parCertains thèmes prennent en compte trois éléments de personnalisation : l’ajout d’un logo ; l’ajout d’une bannière l’ajout d’une image de fond ;
-
Ecrire une actualité
21 juin 2013, parPrésentez les changements dans votre MédiaSPIP ou les actualités de vos projets sur votre MédiaSPIP grâce à la rubrique actualités.
Dans le thème par défaut spipeo de MédiaSPIP, les actualités sont affichées en bas de la page principale sous les éditoriaux.
Vous pouvez personnaliser le formulaire de création d’une actualité.
Formulaire de création d’une actualité Dans le cas d’un document de type actualité, les champs proposés par défaut sont : Date de publication ( personnaliser la date de publication ) (...)
Sur d’autres sites (17258)
-
avformat/dashdec : Fix for ticket 7149 (Segfault when decoding dash streams)
24 mai 2018, par Colin NG -
How to prepare media stream to play using dash.js web player ?
7 avril 2016, par Paweł TobiszewskiI want to stream media from nginx server to Android device and play it using web player embedded into web page. Player I want to use is dash.js.
I play the same media also using different methods (MediaPlayer and ExoPlayer) and they are working great. But when I try to use dash.js, I faced problem with codecs - they are not supported.
I prepare my streams using ffmpeg and MP4Box, I also tried different codecs, like libx264, x264, x265 - always with the same effect.
My based media are video in Y4M format and audio in WAV.
How to encode it to use it in dash.js player ?EDIT :
I get error "Video Element Error : MEDIA_ERR_DECODE" while trying to decode video stream.Here is full log :
[16] EME detected on this user agent! (ProtectionModel_21Jan2015)
[19] Playback Initialized
[28] [dash.js 2.0.0] MediaPlayer has been initialized
[102] Parsing complete: ( xml2json: 3ms, objectiron: 3ms, total: 0.006s)
[103] Manifest has been refreshed at Thu Apr 07 2016 22:02:52 GMT+0200 (CEST)[1460059372.696]
[107] SegmentTimeline detected using calculated Live Edge Time
[118] MediaSource is open!
[118] [object Event]
[119] Duration successfully set to: 18.58
[119] Added 0 inline events
[120] video codec: video/mp4;codecs="avc1.640032"
[132] Schedule controller stopping for video
[137] No audio data.
[137] No text data.
[137] No fragmentedText data.
[137] No embeddedText data.
[138] No muxed data.
[139] Start Event Controller
[141] Schedule controller starting for video
[143] Native video element event: play
[144] Schedule controller starting for video
[148] loaded video:InitializationSegment:NaN (200, 0ms, 7ms)
[149] Initialization finished loading
[154] Getting the request for video time : 0
[155] SegmentList: 0 / 18.58
[164] loaded video:MediaSegment:0 (200, 7ms, 1ms)
[169] Native video element event: loadedmetadata
[171] Starting playback at offset: 0
[175] Got enough buffer to start.
[175] Buffered Range: 0 - 0.999999
[179] Requesting seek to time: 0
[181] Prior to making a request for time, NextFragmentRequestRule is aligning index handler's currentTime with bufferedRange.end. 0 was changed to 0.999999
[182] Getting the request for video time : 0.999999
[183] SegmentList: 0 / 18.58
[183] Getting the next request at index: 1
[184] SegmentList: 1 / 18.58
[190] loaded video:MediaSegment:1 (200, 5ms, 0ms)
[192] Buffered Range: 0 - 0.999999
[195] Getting the request for video time : 2
[196] Index for video time 2 is 1
[197] SegmentList: 1 / 18.58
[197] Getting the next request at index: 2
[198] SegmentList: 2 / 18.58
[205] loaded video:MediaSegment:2 (200, 4ms, 1ms)
[207] Buffered Range: 0 - 0.999999
[207] Getting the request for video time : 3
[208] Index for video time 3 is 2
[208] SegmentList: 2 / 18.58
[209] Getting the next request at index: 3
[209] SegmentList: 3 / 18.58
[212] Video Element Error: MEDIA_ERR_DECODE
[212] [object MediaError]
[215] Schedule controller stopping for video
[219] Native video element event: pause -
Encoding from FFMPEG to MPEG-DASH, WebM with Keyframe Clusters to work with MediaSource API
1er mai 2016, par Chris NoletI’m currently sending a video stream to Chrome, to play via the MediaSource API.
As I understand it, MediaSource only supports MP4 files encoded with MPEG-DASH, or WebM files that have clusters beginning with keyframes (otherwise it raises the error : Media segment did not begin with keyframe).
Is there any way to encode in MPEG-DASH or keyframed WebM formats with FFMPEG in real-time ?
EDIT :
I just tried it with
ffmpeg ... -f webm -vcodec vp8 -g 1 ...
so that every frame is a keyframe. Not the ideal solution. It does work with MediaStream now though. Any way to sync up the segments with the keyframes in WebM so not every frame needs to be a keyframe ?
Reference Questions on WebM / MP4 and MediaSource :
Media Source Api not working for a custom webm file (Chrome Version 23.0.1271.97 m)