
Recherche avancée
Autres articles (22)
-
Publier sur MédiaSpip
13 juin 2013Puis-je poster des contenus à partir d’une tablette Ipad ?
Oui, si votre Médiaspip installé est à la version 0.2 ou supérieure. Contacter au besoin l’administrateur de votre MédiaSpip pour le savoir -
Taille des images et des logos définissables
9 février 2011, parDans beaucoup d’endroits du site, logos et images sont redimensionnées pour correspondre aux emplacements définis par les thèmes. L’ensemble des ces tailles pouvant changer d’un thème à un autre peuvent être définies directement dans le thème et éviter ainsi à l’utilisateur de devoir les configurer manuellement après avoir changé l’apparence de son site.
Ces tailles d’images sont également disponibles dans la configuration spécifique de MediaSPIP Core. La taille maximale du logo du site en pixels, on permet (...) -
Configuration spécifique d’Apache
4 février 2011, parModules spécifiques
Pour la configuration d’Apache, il est conseillé d’activer certains modules non spécifiques à MediaSPIP, mais permettant d’améliorer les performances : mod_deflate et mod_headers pour compresser automatiquement via Apache les pages. Cf ce tutoriel ; mode_expires pour gérer correctement l’expiration des hits. Cf ce tutoriel ;
Il est également conseillé d’ajouter la prise en charge par apache du mime-type pour les fichiers WebM comme indiqué dans ce tutoriel.
Création d’un (...)
Sur d’autres sites (8352)
-
Internet Explorer 11 HTML5 audio duration = infinity issue
27 février 2016, par unbirthToday I’ve met an unpleasant issue. There is a website with a custom HTML5 audio player. After the page loads, I try to echo
document.getElementById("myAudioId").duration
, it is needed in order to make navigation possible. In every other browser it works just fine, the duration is showed, but IE11 works differently - it shows that duration equalsInfinity
. But as I noticed, when the song is buffered to the end, the duration magically appers and the navigation works. In other browsers everything works from the start. The content-length headers are set up. What could it be ?UPD : Other sites with HTML5 audio let me see the duration from the very start. The duration, I guess, is part of metadata and could be loaded even without preloading the audio file using
preload="metadata"
, but it also doesn’t work.UPD2 : I’ve also tried playing around with jsfiddle and created the same audio tag there with same MP3 audio - there was the same situation. But then I’ve inserted link to another MP3 there, from another site - and it worked !. More than that, I’ve uploaded this second song to the first problematic website and after that the song that worked perfectly couldn’t also show me its duration and stuff. So now I think it’s something on server side. But don’t know what it is.
UPD3 : Finally, I’ve been told that files are converted using FFMPEG to MP3 128bit, then they stop being OK. Now I need to find how should I convert MP3s so they are OK.
-
HTML5 / and live transcoding with FFMPEG
13 mai 2020, par TooTallNateSo from my web server, I would like to use FFMPEG to transcode a media file for use with an HTML
<audio></audio>
or<video></video>
tag. Easy enough right ?


The conversion would need to take place in real-time, when an HTTP client requested the converted file. Ideally the file would be streamed back to the HTTP client as it is being transcoded (and not afterwards at the end, since that would potentially take a while before any data starts being sent back).



This would be fine, except that in today's browsers, an HTML5 audio or video tag requests the media file in multiple HTTP requests with the
Range
header. See this question for details.


In that question linked above, you can see that Safari requests weird chunks of the file, including the ending few bytes. This poses a problem in that the web server WOULD have to wait for the conversion to finish, in order to deliver the final bytes of the file to conform to the
Range
request.


So my question is, is my train of thought right ? Is there a better way to deliver transcoding content to an
<audio></audio>
or<video></video>
tag that wouldn't involve waiting for the entire conversion to finish ? Thanks in advance !

-
HTML5 / and live transcoding with FFMPEG
8 mai 2014, par TooTallNateSo from my web server, I would like to use FFMPEG to transcode a media file for use with an HTML
<audio></audio>
or<video></video>
tag. Easy enough right ?The conversion would need to take place in real-time, when an HTTP client requested the converted file. Ideally the file would be streamed back to the HTTP client as it is being transcoded (and not afterwards at the end, since that would potentially take a while before any data starts being sent back).
This would be fine, except that in today’s browsers, an HTML5 audio or video tag requests the media file in multiple HTTP requests with the
Range
header. See this question for details.In that question linked above, you can see that Safari requests weird chunks of the file, including the ending few bytes. This poses a problem in that the web server WOULD have to wait for the conversion to finish, in order to deliver the final bytes of the file to conform to the
Range
request.So my question is, is my train of thought right ? Is there a better way to deliver transcoding content to an
<audio></audio>
or<video></video>
tag that wouldn’t involve waiting for the entire conversion to finish ? Thanks in advance !