Recherche avancée

Médias (1)

Mot : - Tags -/biomaping

Autres articles (62)

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

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

  • De l’upload à la vidéo finale [version standalone]

    31 janvier 2010, par

    Le chemin d’un document audio ou vidéo dans SPIPMotion est divisé en trois étapes distinctes.
    Upload et récupération d’informations de la vidéo source
    Dans un premier temps, il est nécessaire de créer un article SPIP et de lui joindre le document vidéo "source".
    Au moment où ce document est joint à l’article, deux actions supplémentaires au comportement normal sont exécutées : La récupération des informations techniques des flux audio et video du fichier ; La génération d’une vignette : extraction d’une (...)

Sur d’autres sites (7972)

  • Normalise offsetX and offsetY on the event

    19 février 2014, par chriscbrock
    Normalise offsetX and offsetY on the event

    According to the W3C Working Draft, offsetX and offsetY should be
    
relative to the padding edge of the target element. The only browser
    
using this convention is IE. Webkit uses the border edge, Opera uses the
    
content edge, and FireFox does not support the properties.
    

    Normalizing to the border edge is easiest to do.

  • Normalise offsetX and offsetY on the event

    19 février 2014, par chriscbrock
    Normalise offsetX and offsetY on the event

    According to the W3C Working Draft, offsetX and offsetY should be
    
relative to the padding edge of the target element. The only browser
    
using this convention is IE. Webkit uses the border edge, Opera uses the
    
content edge, and FireFox does not support the properties.
    

    Normalizing to the border edge is easiest to do.

  • Round number of bits read to next byte

    4 décembre 2014, par watwat2014

    I have a header that can be any number of bits, and there is a variable called ByteAlign that’s calculated by subtracting the current file position from the file position at the beginning of the file, the point of this variable is to pad the header to the next complete byte. so if the header is taking up 57 bits, the ByteAlign variable needs to be 7 bits in length to pad the header to 64 bits total, or 8 bytes.

    Solutions that don’t work :

    Variable % 8 - 8, the result is the answer, but negative.

    8 % Variable ; this is completely inaccurate, and gives answers like 29, which is blatantly wrong, the largest number it should be is 7.

    how exactly do I do this ?

Navigation