Recherche avancée

Médias (1)

Mot : - Tags -/belgique

Autres articles (74)

  • Keeping control of your media in your hands

    13 avril 2011, par

    The vocabulary used on this site and around MediaSPIP in general, aims to avoid reference to Web 2.0 and the companies that profit from media-sharing.
    While using MediaSPIP, you are invited to avoid using words like "Brand", "Cloud" and "Market".
    MediaSPIP is designed to facilitate the sharing of creative media online, while allowing authors to retain complete control of their work.
    MediaSPIP aims to be accessible to as many people as possible and development is based on expanding the (...)

  • Contribute to documentation

    13 avril 2011

    Documentation is vital to the development of improved technical capabilities.
    MediaSPIP welcomes documentation by users as well as developers - including : critique of existing features and functions articles contributed by developers, administrators, content producers and editors screenshots to illustrate the above translations of existing documentation into other languages
    To contribute, register to the project users’ mailing (...)

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

  • png_parser : Fix parsing on big endian

    18 décembre 2013, par Martin Storsjö
    png_parser : Fix parsing on big endian
    

    Since pc.state is populated by shifting in from the end of the
    32 bit word, the content within pc.state is already in native endian
    and should not be read with the AV_RL,B functions.

    This was already done correctly for state64 above.

    This fixes the fate-corepng test on big endian.

    Signed-off-by : Martin Storsjö <martin@martin.st>

    • [DBH] libavcodec/png_parser.c
  • 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.

  • How can start a process and stop the process if "error" string appear in the console output strings in one line commands set

    25 janvier 2018, par Thm Lee

    Now I want one line cmd commands set which start a process and monitor the consol output strings stream. And so if error message appear in the process’s console output, then could stop the process immediately.

    For example, I tried below commends sets, but failed. It seems find command didn’t get any strings streams in which search key word "error"

    ffmpeg "endcoding process options set" | find "error" && exit

    or,

    ffmpeg "endcoding process options set" 2>&1 find "error" && exit

    Is there any solutions about this ?

    Thanks in advance