Recherche avancée

Médias (10)

Mot : - Tags -/wav

Autres articles (48)

  • Publier sur MédiaSpip

    13 juin 2013

    Puis-je poster des contenus à partir d’une tablette Ipad ?
    Oui, si votre Médiaspip installé est à la version 0.2 ou supérieure. Contacter au besoin l’administrateur de votre MédiaSpip pour le savoir

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

  • imgutils : add function to clear an image to black

    22 juillet 2017, par wm4
    imgutils : add function to clear an image to black
    

    Black isn't always just memset(ptr, 0, size). Limited YUV in particular
    requires relatively non-obvious values, and filling a frame with
    repeating 0 bytes is disallowed in some contexts. With component sizes
    larger than 8 or packed YUV, this can become relatively complicated. So
    having a generic function for this seems helpful.

    In order to handle the complex cases in a generic way without destroying
    performance, this code attempts to compute a black pixel, and then uses
    that value to clear the image data quickly by using a function like
    memset.

    Common cases like yuv410p10 or rgba can't be handled with a simple
    memset, so there is some code to fill memory with 2/4/8 byte patterns.
    For the remaining cases, a generic slow fallback is used.

    Signed-off-by : Anton Khirnov <anton@khirnov.net>

    Merged from Libav commit 45df7adc1d9b7.

    • [DH] doc/APIchanges
    • [DH] libavutil/imgutils.c
    • [DH] libavutil/imgutils.h
    • [DH] libavutil/version.h
  • OpenCL YUV420P black pixel

    30 avril 2021, par Albert Tinon

    I'm working on an FFmpeg OpenCL filter for converting GoPro Max .360 files in Google EAC projected files.&#xA;For doing that I need to "stack" the 2 input streams to a twice height output.&#xA;It is working very well at a realtime speed. (The working code is in comment)

    &#xA;

    For going further I need to replace some pixels with some specific colors.&#xA;I wrote some macros for making RGB->YUV conversion. But I get only some green or pink pixel (only grey is OK).&#xA;this is my test code (with stacking in comment)

    &#xA;

    #define Y(R,G,B) 0.299 * R &#x2B; 0.587 * G &#x2B; 0.114 * B&#xA;#define U(R,G,B) -0.147 * R - 0.289 * G &#x2B; 0.436 * B&#xA;#define V(R,G,B) 0.615 * R - 0.515 * G - 0.100 * B&#xA;#define YUV(R,G,B) (float4)(Y(R,G,B),U(R,G,B),V(R,G,B),0)&#xA;&#xA;__kernel void gopromax_stack(__write_only image2d_t dst,&#xA;                                __read_only  image2d_t gopromax_front,&#xA;                                __read_only  image2d_t gopromax_rear)&#xA;{&#xA;    const sampler_t sampler = (CLK_NORMALIZED_COORDS_FALSE |&#xA;                               CLK_FILTER_NEAREST);&#xA;    &#xA;    float4 val;&#xA;    int2 dst_size = get_image_dim(dst);&#xA;    int2 loc = (int2)(get_global_id(0), get_global_id(1));&#xA;    int split_loc = dst_size.y/2;&#xA;&#xA;        if (loc.y &lt; split_loc)&#xA;        {&#xA;          // working code for stacking&#xA;          //  val = read_imagef(gopromax_front, sampler, (int2)(loc.x, loc.y));&#xA;&#xA;          // testing to put grey (working)&#xA;            val = YUV(0.5f,0.5f,0.5f);&#xA;        }&#xA;        else&#xA;        {&#xA;          // working code for stacking&#xA;          //  val = read_imagef(gopromax_rear, sampler, (int2)(loc.x, loc.y-split_loc));&#xA;&#xA;          // testing to put black (gives green !)&#xA;            val = YUV(0,0,0);&#xA;        }&#xA;&#xA;    if ((loc.xcode>

    &#xA;

    I tried many think I cannot succeed to generate black or anything except grey.&#xA;What did I make wrong ?&#xA;I supposed that my pixels are YUV because I specified yuv420p as the format in my filter :

    &#xA;

    -filter_complex &#x27;[0:0]format=yuv420p,hwupload[a] , [0:4]format=yuv420p,hwupload[b], [a][b]gopromax_opencl, hwdownload,format=yuv420p&#x27;&#xA;

    &#xA;

    The source streams are in hevc / nv12.

    &#xA;

    Thanks all for your help.

    &#xA;

  • avcodec/tiff : check the black level denominator

    26 octobre 2019, par James Almer
    avcodec/tiff : check the black level denominator
    

    Fixes ticket #8327.

    Reviewed-by : Michael Niedermayer <michael@niedermayer.cc>
    Signed-off-by : James Almer <jamrial@gmail.com>

    • [DH] libavcodec/tiff.c