Recherche avancée

Médias (0)

Mot : - Tags -/tags

Aucun média correspondant à vos critères n’est disponible sur le site.

Autres articles (38)

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

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

  • does the ffmpeg overlay filter support a fade option ?

    2 décembre 2016, par Stefan

    I need several overlaid image files to fade in/out at different time intervals on a video file using ffmpeg.

    I am aware of the technique some people use to achieve the effect i’m looking for, which looks something like this :

    ffmpeg.exe -i in_video.mov -loop 1 -i image.png
    
-filter_complex "
    
[1:v]fade=in:st=2:d=0.5:alpha=1,fade=out:st=4:d=0.5:alpha=1[t0];
    
[1:v]fade=in:st=8.6:d=0.5:alpha=1,fade=out:st=12.6:d=0.5:alpha=1[t1];
    
[1:v]fade=in:st=12.2:d=0.5:alpha=1,fade=out:st=14.2:d=0.5:alpha=1[t2];
    
[0:v][t0]overlay=shortest=1[tmp0];
    
[tmp0][t1]overlay=shortest=1[tmp1];
    
[tmp1][t2]overlay=shortest=1[tmp2]"
    
-map "[tmp2]" out_video.mov

    But i experience linear performance decreases as I tack on more overlays.

    By leveraging the ’enable’ overlay option like so I can achieve great performance but lose the ability to fade :

    ffmpeg.exe
    
-i in_video.mov
    
-i image.png
    
-filter_complex "
    
[0:v][t0] overlay=enable='between(t,2,4.5)' [tmp0];
    
[tmp0][t0] overlay=enable='between(t,8.6,13.1)' [tmp1];
    
[tmp1][t0] overlay=enable='between(t,17.3,21.5)' [tmp2]"
    
-map "[tmp2]" output_video.mov

    Can i tack on a ’fade’ option along with the ’enable’ option to optimize performance ? Or should i just attempt to contribute a new option for the overlay filter to the open source ?

  • WebM Decoding Improvements in Google Chrome 6

    10 septembre 2010, par noreply@blogger.com (John Luther)

    Google Chrome 6 for Windows, Mac and Linux was released last week. We want to congratulate the Chrome team and thank them for their contributions to the WebM project.

    Making the web faster is a core goal of Chrome, and we are happy to report that across a set of test clips Chrome 6 decodes VP8 video significantly faster than the developer version that was released at our launch in May. On single-core Intel machines the average improvement is about 20% ; on multicore processors it ranges from 15% (two cores) to 50% (four cores). If you want to try it for yourself, get Chrome 6 and then follow our instructions for playing WebM videos on Youtube.

    We’ve made further decoding speed gains in Chrome 7 dev channel, and are working on better video rendering to further improve the WebM user experience.

  • WebM Decoding Improvements in Google Chrome 6

    10 septembre 2010, par noreply@blogger.com (John Luther)

    Google Chrome 6 for Windows, Mac and Linux was released last week. We want to congratulate the Chrome team and thank them for their contributions to the WebM project.

    Making the web faster is a core goal of Chrome, and we are happy to report that across a set of test clips Chrome 6 decodes VP8 video significantly faster than the developer version that was released at our launch in May. On single-core Intel machines the average improvement is about 20% ; on multicore processors it ranges from 15% (two cores) to 50% (four cores). If you want to try it for yourself, get Chrome 6 and then follow our instructions for playing WebM videos on Youtube.

    We’ve made further decoding speed gains in Chrome 7 dev channel, and are working on better video rendering to further improve the WebM user experience.

Navigation