Recherche avancée

Médias (0)

Mot : - Tags -/images

Aucun média correspondant à vos critères n’est disponible sur le site.

Autres articles (86)

  • Publier sur MédiaSpip

    13 juin 2013

    Puis-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

  • Encoding and processing into web-friendly formats

    13 avril 2011, par

    MediaSPIP automatically converts uploaded files to internet-compatible formats.
    Video files are encoded in MP4, Ogv and WebM (supported by HTML5) and MP4 (supported by Flash).
    Audio files are encoded in MP3 and Ogg (supported by HTML5) and MP3 (supported by Flash).
    Where possible, text is analyzed in order to retrieve the data needed for search engine detection, and then exported as a series of image files.
    All uploaded files are stored online in their original format, so you can (...)

  • Supporting all media types

    13 avril 2011, par

    Unlike most software and media-sharing platforms, MediaSPIP aims to manage as many different media types as possible. The following are just a few examples from an ever-expanding list of supported formats : images : png, gif, jpg, bmp and more audio : MP3, Ogg, Wav and more video : AVI, MP4, OGV, mpg, mov, wmv and more text, code and other data : OpenOffice, Microsoft Office (Word, PowerPoint, Excel), web (html, CSS), LaTeX, Google Earth and (...)

Sur d’autres sites (5356)

  • Focus the DOM element after clipboard injection.

    17 mars 2014, par IonicaBizau
    Focus the DOM element after clipboard injection.

  • lavd/qtkit : Fix non-constant initializer element for some clang compilers.

    31 mars 2014, par Thilo Borgmann
    lavd/qtkit : Fix non-constant initializer element for some clang compilers.

    Signed-off-by : Michael Niedermayer <michaelni@gmx.at>
    • [DH] libavdevice/qtkit.m

  • Why does not work audio element currentTime on ffmpeg encoded mp3 file in Chrome browser

    25 juillet 2013, par Peter

    I have an HTML5 audio element :

    <audio preload="auto">
    
    <source src="./Sound/recording.mp3" type="audio/mpeg">
    
</source></audio>

    and I need to be able to play last 4 seconds from mp3 recording. My javaScript is :

    audio.currentTime = audio.duration-4;
    
audio.play();

    Works ok in IE10 and Firefox, but Chrome starts playing from a wrong place. The difference between reported audio.currentTime and actual playback position is about 20s. The recording.mp3 is created with ffmpeg :

    ffmpeg -i recording.wav -ab 32k recording.mp3

    It works, when I strip the ID3v2 header from the recording.mp3 (deleting the first couple bytes in the file before the audio data).

    It also works when I compress to ogg. Can somebody point me to the right direction (ffmpeg switches, audio element attributes or whatever) to get it work also in chrome ?

    Thanks in advance

Navigation