Recherche avancée

Médias (0)

Mot : - Tags -/xmlrpc

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

Autres articles (75)

  • L’espace de configuration de MediaSPIP

    29 novembre 2010, par

    L’espace de configuration de MediaSPIP est réservé aux administrateurs. Un lien de menu "administrer" est généralement affiché en haut de la page [1].
    Il permet de configurer finement votre site.
    La navigation de cet espace de configuration est divisé en trois parties : la configuration générale du site qui permet notamment de modifier : les informations principales concernant le site (...)

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

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

  • avcodec/hevcdec : Output MD5-message in one piece

    22 juillet 2022, par Andreas Rheinhardt
    avcodec/hevcdec : Output MD5-message in one piece
    

    Otherwise, there is no guarantee that the various av_log-messages
    are not interrupted by another log statement. The latter may originate
    from anywhere else, even the HEVC decoder itself, as happens when
    one uses frame-threading to decode the BUMPING_A_ericsson_1.bit
    sample from the FATE-suite.

    Furthermore, the earlier approach suffered from the fact that
    various parts of the logmsg were output with different loglevels
    and that checking stopped after having encountered the first
    plane with MD5 mismatch, although it is probably interesting to
    know whether other planes are incorrect, too.

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

    • [DH] libavcodec/hevcdec.c
  • How to use -vf format="gray" in ffmpeg python

    22 août 2022, par user19551045

    I am trying to use the -vf format="gray" in ffmpeg-python and I can't seem to get the syntax right. From what I have seen, ffmpeg-python has a set of filter_name options you can use, and then there is also the option to use .filter_() to just put in the ffmpeg commands directly in.

    &#xA;

    I have tried using both and seem to get the same error, where ffmpeg-python wants me to declare a filter_name and from what I am seeing in the documentation, format=gray doesn't fall under any of the filter_name options.

    &#xA;

    If I take this approach, it works :

    &#xA;

    (&#xA;        ffmpeg.input(img_seq_template, framerate=framerate, **input_options)&#xA;        .filter("format", "gray")&#xA;        .output(filename=output_path, **output_options)&#xA;        .run(overwrite_output=True)&#xA;   )&#xA;

    &#xA;

    However, I want to also use a dictionary in the filter(), which then requires me to put in a filter_name. The goal would be to have something like below working :

    &#xA;

    filter_options = {&#x27;format&#x27; : &#x27;gray&#x27;}&#xA;&#xA;(&#xA;        ffmpeg.input(img_seq_template, framerate=framerate, **input_options)&#xA;        .filter(filter_name = "some_filter_name", **filter_options)&#xA;        .output(filename=output_path, **output_options)&#xA;        .run(overwrite_output=True)&#xA;    )&#xA;

    &#xA;

    Any ideas on what I could put into the filter_name to get this running would be amazing ! All suggestions welcome, thanks so much !

    &#xA;

  • Missing piece between libjpeg-turbo & h264 ffmpeg C/C++

    15 octobre 2022, par Nelstaar

    On the left side I have a buffer with decoded pixels that I can get in two formats :

    &#xA;

    RGB interleaved/packed where bytes in buffer are R0G0B0R1G1B1....

    &#xA;

    or

    &#xA;

    YUV444 interleaved/packed where bytes in buffer are Y0U0V0Y1U1V1...

    &#xA;

    (JCS_RGB or JCS_YCbCr in jpeglib.h)

    &#xA;

    (Please note that I use libjpeg-turbo because I need to decompress a cropped region of the image. (jpeg_crop_scanline()))

    &#xA;

    On the right side I have x264 codec via ffmpeg that support only planar pixel formats :

    &#xA;

    yuv420p, yuvj420p, yuv422p, yuvj422p, yuv444p, yuvj444p, nv12, nv16, nv21, yuv420p10le, yuv422p10le, yuv444p10le, nv20le

    &#xA;

    yuv444p where bytes in buffer are Y0Y1Y2...U0U1...V0V1...

    &#xA;

    according to ffmpeg -h encoder=libx264

    &#xA;

    I have some ideas already :

    &#xA;

      &#xA;
    • Decompress Jpeg to RBG888 in buffer 1 then libswscale to yuv420p in buffer 2 and encoding. (copy)
    • &#xA;

    • Decompress Jpeg to YUV444 interleaved in buffer 1 then SSSE3 magic in buffer 1 to yuv444p and encoding. (no copy)
    • &#xA;

    • or else.
    • &#xA;

    &#xA;

    What would be the most effective fastest way ?

    &#xA;

    I which to avoid buffer copy.

    &#xA;

    Movie have the same width & height than Jpegs.

    &#xA;