Recherche avancée
Autres articles (36)
-
Gestion générale des documents
13 mai 2011, parMédiaSPIP ne modifie jamais le document original mis en ligne.
Pour chaque document mis en ligne il effectue deux opérations successives : la création d’une version supplémentaire qui peut être facilement consultée en ligne tout en laissant l’original téléchargeable dans le cas où le document original ne peut être lu dans un navigateur Internet ; la récupération des métadonnées du document original pour illustrer textuellement le fichier ;
Les tableaux ci-dessous expliquent ce que peut faire MédiaSPIP (...) -
Des sites réalisés avec MediaSPIP
2 mai 2011, parCette page présente quelques-uns des sites fonctionnant sous MediaSPIP.
Vous pouvez bien entendu ajouter le votre grâce au formulaire en bas de page. -
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 (5737)
-
Which is the better way to use ffmpeg ?
11 mai 2016, par seaguestWe need ffmpeg to do some video processing, like video format conversion, live stream snapshot..., we won’t go deep in ffmpeg.
Now I am wondering what would be the better way to use ffmpeg, we are developping in Golang, either we call ffmpeg like shell command line, or we use libav* library of ffmpeg.
command line:
Pros:
easy to use, reliable (I got a quality loss problem with library mode), many tutorials
Cons:
the is is a separate process, out of our control, we can't get detailed information of the process, like the video conversion progressing data
the command line way seems not so cool, this is not well integrated in the whole project.
libav* library:
Pros:
we can have the process detailed data, progressing status....
...
Cons:
difficult to use, much less materialsCould anyone give your idea which is the better way to use ffmpeg ?
Before this question, I have asked another two questions :
One is regarding calling libav* library caused the qulity loss problem :
Why calling libav* library doesn’t have same quality as ffmpeg command line ?One is for command line progressing status retrieving problem :
How to get the realtime output for a shell command in golang ? -
avcodec/dds : Fix runtime error : left shift of 210 by 24 places cannot be represented...
12 mai 2017, par Michael Niedermayeravcodec/dds : Fix runtime error : left shift of 210 by 24 places cannot be represented in type 'int'
Fixes : 1510/clusterfuzz-testcase-minimized-5826231746428928
Found-by : continuous fuzzing process https://github.com/google/oss-fuzz/tree/master/targets/ffmpeg
Signed-off-by : Michael Niedermayer <michael@niedermayer.cc> -
avcodec/mlp : Fix multiple runtime error : left shift of negative value -1
13 mai 2017, par Michael Niedermayeravcodec/mlp : Fix multiple runtime error : left shift of negative value -1
Fixes : 1512/clusterfuzz-testcase-minimized-4713846423945216
Found-by : continuous fuzzing process https://github.com/google/oss-fuzz/tree/master/targets/ffmpeg
Signed-off-by : Michael Niedermayer <michael@niedermayer.cc>
Syndiquer tout le site
