
Recherche avancée
Médias (3)
-
The Slip - Artworks
26 septembre 2011, par
Mis à jour : Septembre 2011
Langue : English
Type : Texte
-
Podcasting Legal guide
16 mai 2011, par
Mis à jour : Mai 2011
Langue : English
Type : Texte
-
Creativecommons informational flyer
16 mai 2011, par
Mis à jour : Juillet 2013
Langue : English
Type : Texte
Autres articles (12)
-
Keeping control of your media in your hands
13 avril 2011, parThe vocabulary used on this site and around MediaSPIP in general, aims to avoid reference to Web 2.0 and the companies that profit from media-sharing.
While using MediaSPIP, you are invited to avoid using words like "Brand", "Cloud" and "Market".
MediaSPIP is designed to facilitate the sharing of creative media online, while allowing authors to retain complete control of their work.
MediaSPIP aims to be accessible to as many people as possible and development is based on expanding the (...) -
Les formats acceptés
28 janvier 2010, parLes commandes suivantes permettent d’avoir des informations sur les formats et codecs gérés par l’installation local de ffmpeg :
ffmpeg -codecs ffmpeg -formats
Les format videos acceptés en entrée
Cette liste est non exhaustive, elle met en exergue les principaux formats utilisés : h264 : H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10 m4v : raw MPEG-4 video format flv : Flash Video (FLV) / Sorenson Spark / Sorenson H.263 Theora wmv :
Les formats vidéos de sortie possibles
Dans un premier temps on (...) -
Les vidéos
21 avril 2011, parComme les documents de type "audio", Mediaspip affiche dans la mesure du possible les vidéos grâce à la balise html5 .
Un des inconvénients de cette balise est qu’elle n’est pas reconnue correctement par certains navigateurs (Internet Explorer pour ne pas le nommer) et que chaque navigateur ne gère en natif que certains formats de vidéos.
Son avantage principal quant à lui est de bénéficier de la prise en charge native de vidéos dans les navigateur et donc de se passer de l’utilisation de Flash et (...)
Sur d’autres sites (3005)
-
ffmpeg and grep not working to extract mean_volume value
31 octobre 2019, par JsonI have a list of mp3 files and i want to set all
mean_volume
to the same db value using a script, so I enter the command for detecting the value (https://trac.ffmpeg.org/wiki/AudioVolume) and I try togrep
the value but it fails and instead prints all the output from theffmpeg
command. Any thoughts ?
Also triedtr
instead ofgrep
. The command I used is :ffmpeg -i sample.mp3 -filter:a volumedetect -f null /dev/null | grep 'mean_volume'
-
Monitoring ffmpeg two-passes encoding
31 décembre 2024, par HodolI'm new in FFMPEG.


According to the official guide, https://trac.ffmpeg.org/wiki/Encode/VP9 I use the following command to convert a large h.264 file :


ffmpeg -i input.mp4 -c:v libvpx-vp9 -b:v 0 -crf 30 -pass 1 -an -f null /dev/null
ffmpeg -i input.mp4 -c:v libvpx-vp9 -b:v 0 -crf 30 -pass 2 -c:a libopus output.webm



However, the pass-1 takes too long time and it does not log progress. With
-report
option I can see something is in progress but I don't know how long I should wait.

Here's questions :


- 

- Is there any way to see the progress of 1-pass ?
- Is there any way to speed up the process ?






Thank you,


-
Frame Accurate Seeking in WebM
11 janvier 2016, par SapphireSunI’m trying to do a somewhat tricky thing with WebM. I am trying to encode a stack of 256 biological images as a WebM. The time dimension of motion is very similar to the space dimension of the image stack so the compression ratios are insanely good. However, I am having trouble decoding the movie frames. I know that WebM uses an IPB predictive coding scheme, but I was reading several blog posts and discussion groups from WHATWG from 2011, and they said that frame accurate seeking was working in Chrome at that time.
When I do
video.currentTime = 0
, I correctly get this :However, if I do
video.currentTime = 0.34
(for example) I get something that looks like this :It looks like I’m getting a random poorly predicted frame. Am I just encoding the video wrong ? When I play it normally it looks fine.
I encoded the video using 256 pngs using ffmpeg compiled with libvpx using the VP8 codec.
ffmpeg -y -framerate 60 -start_number 0 -pattern_type glob -i '*.png' -qmin 10 -qmax 42 out.webm
References to the WHATWG and some other info from 2011 :
WHATWG discusses frame accuracy :
https://lists.w3.org/Archives/Public/public-whatwg-archive/2011Jan/0372.html
BBC Tech Director talking about frame accuracy :
http://www.bbc.co.uk/blogs/bbcinternet/2011/02/frame_accurate_video_in_html5.html