
Recherche avancée
Autres articles (93)
-
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 (...) -
Multilang : améliorer l’interface pour les blocs multilingues
18 février 2011, parMultilang est un plugin supplémentaire qui n’est pas activé par défaut lors de l’initialisation de MediaSPIP.
Après son activation, une préconfiguration est mise en place automatiquement par MediaSPIP init permettant à la nouvelle fonctionnalité d’être automatiquement opérationnelle. Il n’est donc pas obligatoire de passer par une étape de configuration pour cela. -
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 (...)
Sur d’autres sites (13111)
-
lavfi/avfiltergraph : add check before free the format
19 août 2019, par Jun Zhao -
vf_paletteuse : Don't free the second frame from ff_framesync_dualinput_get_writable...
1er janvier 2018, par Derek Buitenhuis -
Range input breaks ffmpeg when seeking in Chromium
14 janvier, par Tania RasciaI'm getting the following error erratically when I seek with the range input in a React app, which renders the input unusable until refresh :


PIPELINE_ERROR_READ: FFmpegDemuxer: demuxer seek failed


The only occurrence of this error I can find online is in the Chromium source code. <— linked file goes directly to the line where the error exists.


I can't replicate the error in Firefox.






Nothing out of the ordinary is going on with the input.


const handleScrub = (event) => {
 const newTime = event.target.valueAsNumber

 setProgress(newTime)
 audioRef.current.currentTime = newTime
}



It happens if you click around really fast on the range. Here is an example of the source code, but the error doesn't happen with an .ogg file, only a signed .flac file.