
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 (70)
-
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 -
Le plugin : Podcasts.
14 juillet 2010, parLe problème du podcasting est à nouveau un problème révélateur de la normalisation des transports de données sur Internet.
Deux formats intéressants existent : Celui développé par Apple, très axé sur l’utilisation d’iTunes dont la SPEC est ici ; Le format "Media RSS Module" qui est plus "libre" notamment soutenu par Yahoo et le logiciel Miro ;
Types de fichiers supportés dans les flux
Le format d’Apple n’autorise que les formats suivants dans ses flux : .mp3 audio/mpeg .m4a audio/x-m4a .mp4 (...) -
Submit bugs and patches
13 avril 2011Unfortunately a software is never perfect.
If you think you have found a bug, report it using our ticket system. Please to help us to fix it by providing the following information : the browser you are using, including the exact version as precise an explanation as possible of the problem if possible, the steps taken resulting in the problem a link to the site / page in question
If you think you have solved the bug, fill in a ticket and attach to it a corrective patch.
You may also (...)
Sur d’autres sites (9442)
-
avconv/ffmpeg command to encode nice full hd webm for chrome
18 mars 2016, par xavier.seignardPeople from the artistic direction gave me big
.mov
and.mp4
that I need to put on a web app, but so far they are so huge that decoding/rendering is kinda bad on chrome (this is a chrome only experience since it will run on electron at the end).I’d like to re-encode them in
.webm
since it seems to have the best support in chrome.But I’m kinda lost on how to re-encode them without significative visual quality lost.
For now I use (taken from https://trac.ffmpeg.org/wiki/Encode/VP8)
ffmpeg -i myVid.mp4 -c:v libvpx -crf 8 -b:v 2M -c:a libvorbis myVid.webm
So, does anyone have a nice
avconv
/ffmpeg
command that will produce nice and easy to render.webm
?Regards.
-
Unable to playback .mp4 audio file in Firefox, works in Chrome
22 octobre 2015, par SpartanVXLI have been trying to play a file through Firefox to see if it is compatible for a website and cannot figure out why it cannot play whereas it will play on Chrome okay. It simply shows a error box that the "video cannot be played because the file is corrupt". I’ve trawled through information on .mp4 files and Firefox’s supported codec types but have not found much aside from recent posts on how FF should be able to play this content in 2015. Here is a ffprobe of the file.
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'two.mp4':
Metadata:
major_brand : mp42
minor_version : 0
compatible_brands: M4A mp42isom
creation_time : 2015-08-06 08:17:05
encoder : Nero AAC codec / 1.5.4.0
Duration : 00:03:28.77, start: 0.000000, bitrate: 131 kb/s
Chapter #0:0 : start 0.027333, end 208.768000
Metadata:
title :
Stream #0:0(und): Audio: aac (LC) (mp4a / 0x6134706D), 96000 Hz, stereo, flt p, 128 kb/s (default)Any reason why this local file wouldn’t play through FF on Windows 41.0.2 ?
-
Chrome "stalling" when streaming mp3 file from nodejs windows only
8 octobre 2015, par Alan HollisWe’ve got a really annoying bug when trying to send mp3 data. We’ve got the following set up.
Web cam producing aac -> ffmpeg convert to adts -> send to nodejs server -> ffmpeg on server converts adts to mp3 -> mp3 then streamed to browser.
This works *perfectly" on Linux ( chrome with HTML5 and flash, firefox flash only )
However on windows the sound just "stalls", no matter what combination we use ( browser/html5/flash ). If however we shutdown the server the sound then immediately starts to play as we expect.
For some reason on windows based machines it’s as if the sound is being buffered "waiting" for something but we don’t know what that is.
Any help would be greatly appreciated.
Relevant code in node
res.setHeader('Connection', 'Transfer-Encoding');
res.setHeader('Content-Type', 'audio/mpeg');
res.setHeader('Transfer-Encoding', 'chunked');
res.writeHeader('206');
that.eventEmitter.on('soundData', function (data) {
debug("Got sound data" + data.cameraId + " " + req.params.camera_id);
if (req.params.camera_id == data.cameraId) {
debug("Sending data direct to browser");
res.write(data.sound);
}
});Code on browser
soundManager.setup({
url: 'http://dashboard.agricamera.co.uk/themes/agricamv2/swf/soundmanager2.swf',
useHTML5Audio: false,
onready: function () {
that.log("Sound manager is now ready")
var mySound = soundManager.createSound({
url: src,
autoLoad: true,
autoPlay: true,
stream: true,
});
}
});