Recherche avancée

Médias (1)

Mot : - Tags -/iphone

Autres articles (46)

  • Les autorisations surchargées par les plugins

    27 avril 2010, par

    Mediaspip core
    autoriser_auteur_modifier() afin que les visiteurs soient capables de modifier leurs informations sur la page d’auteurs

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

Sur d’autres sites (6992)

  • Fix SWF position and size calculations in IE 9.

    12 juillet 2013, par DelvarWorld
    Fix SWF position and size calculations in IE<9.
    

    Fixes #190.
    Closes #191.

    In oldIE, using the `typeof` operator on native DOM methods like `getBoundingClientRect` actually returns "object" instead of "function".
    Also, `getBoundingClientRect` did not add the "height" and "width" properties to TextRectangles until IE9, so calculate those manually if need be.

    Bumped version to v1.2.0-beta.3.

  • Fix SWF position and size calculations in IE 9.

    12 juillet 2013, par DelvarWorld
    Fix SWF position and size calculations in IE<9.
    

    Fixes #190.
    Closes #191.

    In oldIE, using the `typeof` operator on native DOM methods like `getBoundingClientRect` actually returns "object" instead of "function".
    Also, `getBoundingClientRect` did not add the "height" and "width" properties to TextRectangles until IE9, so calculate those manually if need be.

    Bumped version to v1.2.0-beta.3.

  • Decoder return of av_find_best_stream vs. avcodec_find_decoder

    7 octobre 2016, par Jason C

    The docs for libav’s av_find_best_stream function (libav 11.7, Windows, i686, GPL) specify a parameter that can be used to receive a pointer to an appropriate AVCodec :

    decoder_ret - if non-NULL, returns the decoder for the selected stream

    There is also the avcodec_find_decoder function which can find an AVCodec given an ID.

    However, the official demuxing + decoding example uses av_find_best_stream to find a stream, but chooses to use avcodec_find_decoder to find the codec in lieu of av_find_best_stream’s codec return parameter :

    ret = av_find_best_stream(fmt_ctx, type, -1, -1, NULL, 0);
    ...
    stream_index = ret;
    st = fmt_ctx->streams[stream_index];
    ...
    /* find decoder for the stream */
    dec = avcodec_find_decoder(st->codecpar->codec_id);

    As opposed to something like :

    ret = av_find_best_stream(fmt_ctx, type, -1, -1, &amp;dec, 0);

    My question is pretty straightforward : Is there a difference between using av_find_best_stream’s return parameter vs. using avcodec_find_decoder to find the AVCodec ?

    The reason I ask is because the example chose to use avcodec_find_decoder rather than the seemingly more convenient return parameter, and I can’t tell if the example did that for a specific reason or not. The documentation itself is a little spotty and disjoint, so it’s hard to tell if things like this are done for a specific important reason or not. I can’t tell if the example is implying that it "should" be done that way, or if the example author did it for some more arbitrary personal reason.