Recherche avancée

Médias (5)

Mot : - Tags -/open film making

Autres articles (75)

  • Des sites réalisés avec MediaSPIP

    2 mai 2011, par

    Cette page présente quelques-uns des sites fonctionnant sous MediaSPIP.
    Vous pouvez bien entendu ajouter le votre grâce au formulaire en bas de page.

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

  • network : Add RFC 8305 style "Happy Eyeballs"/"Fast Fallback" helper function

    10 août 2018, par Martin Storsjö
    network : Add RFC 8305 style "Happy Eyeballs"/"Fast Fallback" helper function

    For cases with dual stack (IPv4 + IPv6) connectivity, but where one
    
stack potentially is less reliable, strive to trying to connect over
    
both protocols in parallel, using whichever address connected first.
    

    In cases with a hostname resolving to multiple IPv4 and IPv6
    
addresses, the current connection mechanism would try all addresses
    
in the order returned by getaddrinfo (with all IPv6 addresses ordered
    
before the IPv4 addresses normally). If connection attempts to the
    
IPv6 addresses return quickly with an error, this was no problem, but
    
if they were unsuccessful leading up to timeouts, the connection process
    
would have to wait for timeouts on all IPv6 target addresses before
    
attempting any IPv4 address.
    

    Similar to what RFC 8305 suggests, reorder the list of addresses to
    
try connecting to, interleaving address families. After starting one
    
connection attempt, start another one in parallel after a small delay
    
(200 ms as suggested by the RFC).
    

    For cases with unreliable IPv6 but reliable IPv4, this should make
    
connection attempts work as reliably as with plain IPv4, with only an
    
extra 200 ms of connection delay.
    

    Signed-off-by : Martin Storsjö <martin@martin.st>
    • [DBH] libavformat/network.c
    • [DBH] libavformat/network.h

  • libavcodec/mpeg12 : Remove "fast" mode

    29 octobre 2023, par Kieran Kunhya
    libavcodec/mpeg12 : Remove "fast" mode
    • [DH] libavcodec/mpeg12dec.c

  • Ffmpeg "-c copy" alternatives for fast video cutting

    4 juin 2020, par xcodesucks123

    I'm using ffmpeg to cut sections out of a video. I was using this command, as I'd done with previous videos :

    &#xA;&#xA;

    ffmpeg -i source.mp4 -ss 00:00:10 -t 00:00:30 -c copy -y output.mp4&#xA;

    &#xA;&#xA;

    However, when I use this, depending on the time, either the first 5 seconds or last 5 seconds of video are blank.&#xA;I resorted to removing the copy command and just using :

    &#xA;&#xA;

    ffmpeg -i source.mp4 -ss 00:00:10 -t 00:00:30 -y output.mp4&#xA;

    &#xA;&#xA;

    This worked correctly, but is much slower. Is there any fast alternative that will not corrupt the video ?

    &#xA;&#xA;

    Thanks

    &#xA;

Navigation