Recherche avancée

Médias (91)

Autres articles (104)

  • 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 (...)

  • MediaSPIP 0.1 Beta version

    25 avril 2011, par

    MediaSPIP 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 (...)

  • HTML5 audio and video support

    13 avril 2011, par

    MediaSPIP 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 (11099)

  • How do I set the first and last frame of a video to be an image ?

    16 septembre 2011, par user205865

    HTML 5 implementations are different across various browsers. In firefox, the image specified by the placeholder attribute will be shown until the user clicks play on the video. In chrome, the placeholder image is shown until the video is loaded (not played), at which point the first frame of the video is shown.

    To reconcile this issue, I would like to set the first frame of the video to the placeholder image so that the experience will be the same in both browsers.

    I would preferably do this using ffmpeg or mencoder. I have very limited experience using these however, so if someone could point me in the right direction, I would be much obliged.

    Thanks !

  • avcodec/ac3enc_template : Perform compile-time checks at compile-time

    3 décembre 2020, par Andreas Rheinhardt
    avcodec/ac3enc_template : Perform compile-time checks at compile-time
    

    Runtime checks for whether the encoder is fixed-point or not are
    unnecessary here as this is a template ; furthermore, there is no
    fixed-point EAC-3 encoder, so some checks for whether one is in EAC-3
    mode can be omitted when doing fixed-point encoding.

    Signed-off-by : Andreas Rheinhardt <andreas.rheinhardt@gmail.com>

    • [DH] libavcodec/ac3enc_template.c
  • FFMPEG split audio files accurately

    5 mai 2015, par Jakob Hougaard Andersen

    I am trying to use ffmpeg to split uncompressed audio files. I would like to split them very precisely at certain points.
    My experiments so far have led me to this procedure :

    ffmpeg -ss 1.126 -i someInputFile.wav -acodec copy -t 0.634 someOutputFile.wav

    So I am seeking (-ss) to a certain point in the input file and then I am outputting to a file with a defined length (-t).

    The -ss parameter seems to locate the starting point very accurately, but the length of the file doesn’t seem to match my defined length exactly.
    It seems that the file size jumps in steps of 4096 bytes (and the length with it) so that I can not define a file length in between two steps.

    I know that 4096 bytes is not a lot, but for a mono wave file (44.1kHz, 16 bit) it equals a step size of approximately 45 ms. I would really like to be able to define the length as precisely as the starting point.

    So my question is : is it possible to avoid this 4096 byte quatization on the output file length ?

    I have tried to use the ’chomp’ bitstream filter, and it seems to make the length exactly what it should be, but it also causes the output audio file to have strange regions with pure noise...

    Best regards, Jakob