Recherche avancée

Médias (1)

Mot : - Tags -/berlin

Autres articles (89)

  • Personnaliser en ajoutant son logo, sa bannière ou son image de fond

    5 septembre 2013, par

    Certains thèmes prennent en compte trois éléments de personnalisation : l’ajout d’un logo ; l’ajout d’une bannière l’ajout d’une image de fond ;

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

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

Sur d’autres sites (10932)

  • correction in publicMethod.remove() by adding jQuery unbind method for "keydown" event leading to multiple listeners when resetting the colorbox with $.colorbox.remove().

    28 mai 2014
    correction in publicMethod.remove() by adding jQuery unbind method for "keydown" event leading to multiple listeners when resetting the colorbox with $.colorbox.remove().
  • avconv complains "non monotonically increasing dts to muxer in stream" when piping from libx264 on 14.04

    1er décembre 2015, par Mike

    I have a piece of code that takes a stream of images and writes them to a file using x264 to encode and avconv. The relevant bits are as follows

    // Setup encoder
    sprintf(cmd, "avconv -i pipe: -vcodec copy %s", filename);
    fp = popen(cmd, "w");
    x264_param_default_preset(&params, "ultrafast", "stillimage,zerolatency");
    params.i_fps_num = fps;
    params.i_fps_den = 1;
    x264_picture_alloc(&in, X264_CSP_I420, width, height);
    params.i_csp = X264_CSP_I420;
    in.img.i_csp = X264_CSP_I420;
    x.params.b_vfr_input = 0;
    in.i_pts = -1;
    out.i_pts = -1;
    params.i_width = width;
    params.i_height = height;
    encoder = x264_encoder_open(&params);

    in.img.i_plane = 1;
    in.img.i_stride[0] = width;
    ret = x264_encoder_headers(encoder, &nals, &nheader);
    header_size = nals[0].i_payload + nals[1].i_payload + nals[2].i_payload;
    fwrite(nals[0].p_payload, header_size, 1, fp);

    ...
    // Loop body
    ++in.i_pts;
    frame_size = x264_encoder_encode(encoder, &nals, &num_nals, &in, &out);
    fwrite(nals[0].p_payload, frame_size, 1, fp);

    I’ve left out error checking for clarity, but no error is ever returned. Indeed, until I upgraded my system to 14.04, this code worked perfectly (and continues to work perfectly for colleagues who’ve yet to upgrade).

    Only now running Ubuntu 14.04, I get this output from avconv

    [h264 @ 0x98dec0] Estimating duration from bitrate, this may be inaccurate
    Input #0, h264, from 'pipe:'
     Duration: N/A, bitrate: N/A
       Stream #0.0: Video: h264 (Constrained Baseline), yuv420p, 640x480, 25 fps, 25 tbr, 25 tbn, 60 tbc
    Output #0, mp4, to '../reel/test.mp4':
     Metadata:
       encoder         : Lavf54.20.3
       Stream #0.0: Video: libx264, yuv420p, 640x480, q=2-31, 25 tbn, 25 tbc
    Stream mapping:
     Stream #0:0 -> #0:0 (copy)
    [mp4 @ 0x1347800] Application provided invalid, non monotonically increasing dts to muxer in stream 0: 2 >= 2
    av_interleaved_write_frame(): Invalid argument

    Despite the error, out.i_dts does monotonically increase over the whole duration of the video (it’s always equal to in.i_pts).

    My general assumption is that newer versions of avconv are more strict with the parameters of the input stream, so while my choice of parameters may have worked before, they do not work now.

    Another curiousity, which might be related, is avconv detecting that the stream is 25 FPS, even though x264 is configured with an input FPS of 30.

    Edit : Some further information, the same dts error (2>=2) happens regardless of the initial pts (with the output dts matching as expected).

  • Core : Update elementValue method to deal with type="number" fields

    29 avril 2014, par jamierytlewski
    Core : Update elementValue method to deal with type="number" fields
    

    The HTML5 draft defines, for type="number" inputs : "The value
    sanitization algorithm is as follows : If the value of the element is not
    a valid floating-point number, then set it to the empty string instead."
    If the constraint validation considers the input invalid, return false
    as the value, instead of the empty string, for the number and digit
    methods to output their messages.

    This would break in browsers that support type="number", but not the
    constraint validation API. I don’t know of any existing browser where
    that applies.

    Fixes #858
    Fixes #922
    Closes #1093