Recherche avancée

Médias (91)

Autres articles (48)

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

  • De l’upload à la vidéo finale [version standalone]

    31 janvier 2010, par

    Le chemin d’un document audio ou vidéo dans SPIPMotion est divisé en trois étapes distinctes.
    Upload et récupération d’informations de la vidéo source
    Dans un premier temps, il est nécessaire de créer un article SPIP et de lui joindre le document vidéo "source".
    Au moment où ce document est joint à l’article, deux actions supplémentaires au comportement normal sont exécutées : La récupération des informations techniques des flux audio et video du fichier ; La génération d’une vignette : extraction d’une (...)

  • Support audio et vidéo HTML5

    10 avril 2011

    MediaSPIP utilise les balises HTML5 video et audio pour la lecture de documents multimedia en profitant des dernières innovations du W3C supportées par les navigateurs modernes.
    Pour les navigateurs plus anciens, le lecteur flash Flowplayer est utilisé.
    Le lecteur HTML5 utilisé a été spécifiquement créé pour MediaSPIP : il est complètement modifiable graphiquement pour correspondre à un thème choisi.
    Ces technologies permettent de distribuer vidéo et son à la fois sur des ordinateurs conventionnels (...)

Sur d’autres sites (3491)

  • My Video Filesize Does Not Equal Bitrate x Time

    16 juin 2019, par Supercreature

    I’m trying to use ffmpeg to encode some videos with h264. I’m trying to hit a target filesize.

    My code is :

    D:\SOFTWARE\ffmpeg\bin\test\ffmpeg.exe -i "%~1" -c:v libx264 -preset veryslow -b:v 200k -an "%~n1.mp4"

    The video is 15 seconds long.

    So I’ve read that my filesize should be 200 x 15 (bitrate x duration). But it’s not. The filesize is 400kb, when it should be 3000kb.

    What gives ?

  • Upgrading an existing h.264 solution of Level-4.1 to support 4K(Level-5.2)

    11 août 2015, par Codec Guy

    I am currently studying to support 4K(3840x2160) on H.264 Encoder.
    When I studied the specs of H.264, it says 4K resolution is supported in Level-5.2(XAVC).
    In order to check the implementation I encoded my full HD(1920x1080)bitstream using x264 in FFMPEG for three different levels(Level-4,4.1 and 5.2).

    Here is what I noticed
    - All the three Encoded bitstreams, encoded for different levels matched pixel by pixel.
    - I was wondering if the encoding is done for different levels(Level-4,4.1 and 5.2), how come there is no change in bitstream.

    • I have a solution of high 422 Level-4.1, are there any changes in the core modules like Transformation, Quantazition, CAVLC to support 4K(3840 x 2160)/XAVC.

    • or the processing of all Level-5.2 is same as Level-4.1.

    It would be very helpful, if somebody can refer me to any documents which explains the diffrence in processing of H.264/AVC and XAVC

  • Upgrading an existing h.264 solution of Level-4.1 to support 4K(Level-5.2)

    11 août 2015, par Codec Guy

    I am currently studying to support 4K(3840x2160) on H.264 Encoder.
    When I studied the specs of H.264, it says 4K resolution is supported in Level-5.2(XAVC).
    In order to check the implementation I encoded my full HD(1920x1080)bitstream using x264 in FFMPEG for three different levels(Level-4,4.1 and 5.2).

    Here is what I noticed
    - All the three Encoded bitstreams, encoded for different levels matched pixel by pixel.
    - I was wondering if the encoding is done for different levels(Level-4,4.1 and 5.2), how come there is no change in bitstream.

    • I have a solution of high 422 Level-4.1, are there any changes in the core modules like Transformation, Quantazition, CAVLC to support 4K(3840 x 2160)/XAVC.

    • or the processing of all Level-5.2 is same as Level-4.1.

    It would be very helpful, if somebody can refer me to any documents which explains the diffrence in processing of H.264/AVC and XAVC

Navigation