Recherche avancée

Médias (91)

Autres articles (40)

  • Des sites réalisés avec MediaSPIP

    2 mai 2011, par

    Cette page présente quelques-uns des sites fonctionnant sous MediaSPIP.
    Vous pouvez bien entendu ajouter le votre grâce au formulaire en bas de page.

  • Use, discuss, criticize

    13 avril 2011, par

    Talk to people directly involved in MediaSPIP’s development, or to people around you who could use MediaSPIP to share, enhance or develop their creative projects.
    The bigger the community, the more MediaSPIP’s potential will be explored and the faster the software will evolve.
    A discussion list is available for all exchanges between users.

  • Contribute to a better visual interface

    13 avril 2011

    MediaSPIP is based on a system of themes and templates. Templates define the placement of information on the page, and can be adapted to a wide range of uses. Themes define the overall graphic appearance of the site.
    Anyone can submit a new graphic theme or template and make it available to the MediaSPIP community.

Sur d’autres sites (6757)

  • Naive Sorenson Video 1 Encoder

    12 septembre 2010, par Multimedia Mike — General

    (Yes, the word is “naive” — or rather, “naïve” — not “native”. People always try to correct me when I use the word. Indeed, it should actually be written with 2 dots over the ‘i’ but who has a keyboard that can easily do that ?)

    At the most primitive level, programming a video encoder is about writing out a sequence of bits that the corresponding video decoder will understand. It’s sort of like creating a program — represented as a stream of opcodes — that will run on a given microprocessor or virtual machine. In fact, reading a video codec bitstream specification will reveal a lot of terminology along the lines of “transmitting information to the decoder” or “signaling the decoder to do xyz.”

    Creating a good encoder that will deliver decent quality at a reasonable bitrate is difficult. Creating a naive encoder that produces a technically compliant bitstream, not so much.



    When I wrote an FFmpeg encoder for Sorenson Video 1 (SVQ1), the first step was to just create a minimally compliant bitstream. The coarsest encoding mode that SVQ1 allows is to encode the average (mean) of each 16×16 block of samples. So I created an encoder that just encoded the mean of each block. Apple’s QuickTime Player was able to play the resulting video in all of its blocky glory. The result rather reminds me of the Super Nintendo’s mosaic effect.

    Level 5 blocks (mean-only 16×16 encoding) :



    Level 3 blocks (mean-only 8×8 encoding) :



    It’s one thing for your own decoder (in this case, FFmpeg’s own decoder) to be able to decode the data. The big test is whether the official decoder (in this case, Apple QuickTime Player) can decode the file.



    Now that’s a good feeling. After establishing that sort of baseline, it’s possible to adapt more and more features of the codec.

  • FFmpeg decode H264 video too slowly

    17 décembre 2012, par user1158196

    I am currently working on a project on iPhone using FFMpeg. I can decode all the formats I need but when I want to play a h264 video, ffmpeg decodes frames too slowly.

    I tried to see where the problem is. I think that the options from the compilation of the library are good, decoding and displaying the frames are made ​​on different threads. In the end, it seems that it is the function avcodec_decode_video2 that takes too long (3 to 4 seconds to decode 30 frames).

  • HTML5 Video Presentations at LCA 2011

    http://blip.tv/file/get/Linuxconfau-TheLatestAndCoolestWithHTML5Video326.ogv
    10 février 2011, par silvia

    Working in the WHAT WG and the W3C HTML WG, you sometimes forget that all the things that are being discussed so heatedly for standardization are actually leading to some really exciting new technologies that not many outside have really taken note of yet. This week, during the Australian Linux (...)