Recherche avancée
Médias (1)
-
Bug de détection d’ogg
22 mars 2013, par
Mis à jour : Avril 2013
Langue : français
Type : Video
Autres articles (71)
-
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 ;
-
MediaSPIP v0.2
21 juin 2013, parMediaSPIP 0.2 est la première version de MediaSPIP stable.
Sa date de sortie officielle est le 21 juin 2013 et est annoncée ici.
Le fichier zip ici présent contient uniquement les sources de MediaSPIP en version standalone.
Comme pour la version précédente, il est nécessaire d’installer manuellement l’ensemble des dépendances logicielles sur le serveur.
Si vous souhaitez utiliser cette archive pour une installation en mode ferme, il vous faudra également procéder à d’autres modifications (...) -
Mise à disposition des fichiers
14 avril 2011, parPar défaut, lors de son initialisation, MediaSPIP ne permet pas aux visiteurs de télécharger les fichiers qu’ils soient originaux ou le résultat de leur transformation ou encodage. Il permet uniquement de les visualiser.
Cependant, il est possible et facile d’autoriser les visiteurs à avoir accès à ces documents et ce sous différentes formes.
Tout cela se passe dans la page de configuration du squelette. Il vous faut aller dans l’espace d’administration du canal, et choisir dans la navigation (...)
Sur d’autres sites (13397)
-
how to create multiple period using ffmpeg, from two input videos to multi period on the DASH mpd
14 mai 2020, par SunnyI wonder how to create multi-periods from two input videos or more using ffmpeg. 
how do I make a command line for making a DASH mpd to have multiple periods. 
who does know the way to make the thing ?



==============
xml

 
 representation..
 
 
 representation..






-
Issues with using FFmpeg to generate MPEG-DASH files
26 septembre 2022, par Tina JI am using the following
ffmpegcommand to generate MPEG DASH files and manifest. I usesingle_file 1to have a single file for each representation ; so no chunking. But IDK why when I want to play the manifest using ExoPlayer, the video doesn't play from the beginning (rather it starts from around 50s).

ffmpeg -re -i .\video-h264.mkv -map 0 -map 0 -c:a aac -c:v libx264 -b:v:0 800k -b:v:1 300k -s:v:1 320x170 -profile:v:1 baseline -profile:v:0 main -bf 1 -keyint_min 120 -g 120 -sc_threshold 0 -b_strategy 0 -ar:a:1 22050 -use_timeline 1 -single_file 1 -use_template 1 -window_size 5 -adaptation_sets "id=0,streams=v id=1,streams=a" -f dash out.mpd


What is wrong with this ? Is the manifest correct ? Here is the generated mpd :


<?xml version="1.0" encoding="utf-8"?>
<mpd xmlns="urn:mpeg:dash:schema:mpd:2011" profiles="urn:mpeg:dash:profile:isoff-live:2011" type="static" mediapresentationduration="PT1M20.1S" maxsegmentduration="PT5.0S" minbuffertime="PT16.0S">
 <programinformation>
 </programinformation>
 <servicedescription>
 </servicedescription>
 <period start="PT48.0S">
 <adaptationset contenttype="video" startwithsap="1" segmentalignment="true" bitstreamswitching="true" framerate="30/1" maxwidth="960" maxheight="540" par="517072:290799" lang="eng">
 <representation mimetype="video/mp4" codecs="avc1.4d401f" bandwidth="800000" width="960" height="540" sar="32317:32311">
 <baseurl>out-stream0.mp4</baseurl>
 <segmentlist timescale="1000000" duration="5000000" startnumber="7">
 <initialization range="0-832"></initialization>
 <segmenturl mediarange="4800141-5599188" indexrange="4800141-4800192"></segmenturl>
 <segmenturl mediarange="5599189-6243069" indexrange="5599189-5599240"></segmenturl>
 <segmenturl mediarange="6243070-7224302" indexrange="6243070-6243121"></segmenturl>
 <segmenturl mediarange="7224303-8138118" indexrange="7224303-7224354"></segmenturl>
 <segmenturl mediarange="8138119-8232111" indexrange="8138119-8138170"></segmenturl>
 </segmentlist>
 </representation>
 <representation mimetype="video/mp4" codecs="avc1.42c00d" bandwidth="300000" width="320" height="170" sar="549389:581598">
 <baseurl>out-stream2.mp4</baseurl>
 <segmentlist timescale="1000000" duration="5000000" startnumber="7">
 <initialization range="0-832"></initialization>
 <segmenturl mediarange="1782920-2005667" indexrange="1782920-1782971"></segmenturl>
 <segmenturl mediarange="2005668-2229412" indexrange="2005668-2005719"></segmenturl>
 <segmenturl mediarange="2229413-2615209" indexrange="2229413-2229464"></segmenturl>
 <segmenturl mediarange="2615210-2975346" indexrange="2615210-2615261"></segmenturl>
 <segmenturl mediarange="2975347-2999288" indexrange="2975347-2975398"></segmenturl>
 </segmentlist>
 </representation>
 </adaptationset>
 <adaptationset contenttype="audio" startwithsap="1" segmentalignment="true" bitstreamswitching="true" lang="eng">
 <representation mimetype="audio/mp4" codecs="mp4a.40.2" bandwidth="69000" audiosamplingrate="44100">
 <audiochannelconfiguration schemeiduri="urn:mpeg:dash:23003:3:audio_channel_configuration:2011" value="1"></audiochannelconfiguration>
 <baseurl>out-stream1.mp4</baseurl>
 <segmentlist timescale="1000000" duration="5000000" startnumber="12">
 <initialization range="0-764"></initialization>
 <segmenturl mediarange="491493-536039" indexrange="491493-491544"></segmenturl>
 <segmenturl mediarange="536040-580657" indexrange="536040-536091"></segmenturl>
 <segmenturl mediarange="580658-625158" indexrange="580658-580709"></segmenturl>
 <segmenturl mediarange="625159-669825" indexrange="625159-625210"></segmenturl>
 <segmenturl mediarange="669826-713289" indexrange="669826-669877"></segmenturl>
 </segmentlist>
 </representation>
 <representation mimetype="audio/mp4" codecs="mp4a.40.2" bandwidth="69000" audiosamplingrate="22050">
 <audiochannelconfiguration schemeiduri="urn:mpeg:dash:23003:3:audio_channel_configuration:2011" value="1"></audiochannelconfiguration>
 <baseurl>out-stream3.mp4</baseurl>
 <segmentlist timescale="1000000" duration="5000000" startnumber="12">
 <initialization range="0-764"></initialization>
 <segmenturl mediarange="486188-530059" indexrange="486188-486239"></segmenturl>
 <segmenturl mediarange="530060-574175" indexrange="530060-530111"></segmenturl>
 <segmenturl mediarange="574176-618922" indexrange="574176-574227"></segmenturl>
 <segmenturl mediarange="618923-663118" indexrange="618923-618974"></segmenturl>
 <segmenturl mediarange="663119-706121" indexrange="663119-663170"></segmenturl>
 </segmentlist>
 </representation>
 </adaptationset>
 </period>
</mpd>


-
Why does ffmpeg generate a mpeg-dash mpd with long timeShiftBufferDepth even with window_size of one minute ? [closed]
1er février 2024, par igorblimaI'm having a problem with ffmpeg when i try to create a dynamic mpd from rtmp livestream. The vídeo integrity its ok and works fine, but the only problem is with the timeShiftBufferDepth. The command specifies how much window_size to have, but for some reason the timeShiftBufferDepth generated by ffmpeg doesn't respect that. I specified 1 minute of window_size, but for some reason unknown to me, the timeShiftBufferDepth is generated as 8 minutes


the command :


ffmpeg -i rtmp://localhost:1935/live/stream -c:v libx264 -b:v 1000k -c:a aac -b:a 128k -strict experimental -f dash -window_size 60 -utc_timing_url https://time.akamai.com/?ms -seg_duration 5 -remove_at_exit 1 -dash_segment_type mp4 h264.mpd


result :


timeShiftBufferDepth="PT8M19.9S"


how i say previously, the mpd works fine in the player. The only issue is with that incorrect timeShiftBufferDepth


i read the ffmpeg documentation https://ffmpeg.org/ffmpeg-formats.html#Options-19


Syndiquer tout le site
