Recherche avancée

Médias (29)

Mot : - Tags -/Musique

Autres articles (52)

  • Submit bugs and patches

    13 avril 2011

    Unfortunately a software is never perfect.
    If you think you have found a bug, report it using our ticket system. Please to help us to fix it by providing the following information : the browser you are using, including the exact version as precise an explanation as possible of the problem if possible, the steps taken resulting in the problem a link to the site / page in question
    If you think you have solved the bug, fill in a ticket and attach to it a corrective patch.
    You may also (...)

  • Personnaliser les catégories

    21 juin 2013, par

    Formulaire de création d’une catégorie
    Pour ceux qui connaissent bien SPIP, une catégorie peut être assimilée à une rubrique.
    Dans le cas d’un document de type catégorie, les champs proposés par défaut sont : Texte
    On peut modifier ce formulaire dans la partie :
    Administration > Configuration des masques de formulaire.
    Dans le cas d’un document de type média, les champs non affichés par défaut sont : Descriptif rapide
    Par ailleurs, c’est dans cette partie configuration qu’on peut indiquer le (...)

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

  • Set content-length when converting video stream to audio (w/ FFMPEG & Node.js)

    15 septembre 2014, par Taconut

    So I’m building a program that requires that I take a video and convert it to audio. I’m currently streaming the audio directly to the browser via node.js, but I’ve run into a major problem : I don’t know how to find out how many bytes my audio is. As a result, the browser keeps throwing net::ERR_CONTENT_LENGTH_MISMATCH when I don’t get the right content-length. I’ve tried several strategies, all of which have failed :

    • Computing the size manually (Seconds * bitrate(kbps) * (1024 / 8)).
      This produces an approximate answer, since I only know the length down to the nearest couple of seconds. Even though I’m relatively close, I still end up getting the same MISMATCH error.

    • Piping the Stream to a buffer, getting the buffer’s length, and piping the buffer to the browser
      This works, but it can take 15-20 seconds to load each song. It’s incredibly slow and puts a considerably larger load on the server

  • Revision 0a2b25dcb9 : configure : add —enable-coefficient-range-checking This commit adds a configure

    29 juillet 2014, par Yaowu Xu

    Changed Paths :
     Modify /configure


     Modify /vp9/common/vp9_idct.h



    configure : add —enable-coefficient-range-checking

    This commit adds a configure time option used to enable strict error
    checking in decoder to make sure intermediate stage cofficients of
    inverse transforms are within valid range of signed 16 bit integer.

    For valid VP9 input streams, intermediate stage coefficients should
    always stay within the range of a signed 16 bit integer. Coefficients
    can go out of this range for invalid/corrupt VP9 streams. However,
    strictly checking this range for every intermediate coefficient can
    be a burden for decoder, therefore such validation is only enabled
    with configure option —enable-coefficient-range-checking.

    Change-Id : I47d47c8c4e48a922c3d223ca59064f51b3f0f5ed

  • avcodec/libx264 : leave full range flag unchanged if unknown

    17 août 2021, par Jan Ekström
    avcodec/libx264 : leave full range flag unchanged if unknown

    By default the x264 full range flag is set to -1. By not setting
    
it to something else, we can let libx264 handle the RGB case.
    
Additionally, change the preference order to user-specified range
    
first, and then any fall-back logic left for the YUVJ pix_fmts.
    

    Fixes the capture part of #9374
    • [DH] libavcodec/libx264.c

Navigation