Recherche avancée

Médias (0)

Mot : - Tags -/serveur

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

Autres articles (51)

  • Mise à jour de la version 0.1 vers 0.2

    24 juin 2013, par

    Explications des différents changements notables lors du passage de la version 0.1 de MediaSPIP à la version 0.3. Quelles sont les nouveautés
    Au niveau des dépendances logicielles Utilisation des dernières versions de FFMpeg (>= v1.2.1) ; Installation des dépendances pour Smush ; Installation de MediaInfo et FFprobe pour la récupération des métadonnées ; On n’utilise plus ffmpeg2theora ; On n’installe plus flvtool2 au profit de flvtool++ ; On n’installe plus ffmpeg-php qui n’est plus maintenu au (...)

  • Personnaliser en ajoutant son logo, sa bannière ou son image de fond

    5 septembre 2013, par

    Certains thèmes prennent en compte trois éléments de personnalisation : l’ajout d’un logo ; l’ajout d’une bannière l’ajout d’une image de fond ;

  • Ecrire une actualité

    21 juin 2013, par

    Présentez les changements dans votre MédiaSPIP ou les actualités de vos projets sur votre MédiaSPIP grâce à la rubrique actualités.
    Dans le thème par défaut spipeo de MédiaSPIP, les actualités sont affichées en bas de la page principale sous les éditoriaux.
    Vous pouvez personnaliser le formulaire de création d’une actualité.
    Formulaire de création d’une actualité Dans le cas d’un document de type actualité, les champs proposés par défaut sont : Date de publication ( personnaliser la date de publication ) (...)

Sur d’autres sites (7225)

  • Performance optimizations you can apply today to load the Piwik JavaScript tracker faster

    20 avril 2017, par InnoCraft — Community, Development

    When you track your website with Piwik or any other analytics solution, you need to embed a JavaScript file in order to track page views, events, clicks, and more. At InnoCraft, it is our daily business to help Piwik users to make the most out of their Piwik. We often see similar problems of websites loading unnecessarily slower because the tracking file is not loaded as fast as it should be. There are many ways you can improve the performance but avoiding the most important mistakes will help you to not lose revenue and conversions because of this today. Below you find a few steps that will boost the loading of your Piwik JavaScript tracking file.

    Cache piwik.js

    The most important step is to make sure to configure your server in a way so the piwik.js JavaScript tracker file will be cached once it has been loaded and not requested again on subsequent page views. Learn more about browser caching.

    Enable GZIP

    We recommend enabling GZIP as it reduces the size the user needs to load when the piwik.js file is requested. For the standard Piwik tracker, this will reduce the size from about 60KB to 20KB.

    Preload DNS

    Often a Piwik is hosted on a different domain and when the browser loads the JavaScript tracker file, it needs to first perform a DNS lookup to find the IP address for this domain. By adding the below snipped for your Piwik domain, it can boost the performance of loading the tracker file by 10ms to 50ms.

    <link rel="dns-prefetch" href="//example.innocraft.cloud">

    Preload resource

    To boost the loading of the Piwik tracking file, you can add the following HTML into the header of your website :

    <link rel="preload" href="https://yourpiwikdomain.com/piwik.js" onload="embedTracker()" type="script" crossorigin>

    In Chrome, Opera, and soon in more browsers this will load the JavaScript tracker file without blocking the “onload” event. As a result, as soon as you embed the tracking code, the JavaScript tracker might be already loaded. How “preloading” affects your website always depends and maybe you rather want to preload more important resources than the tracking code, but it is an option to consider. If you load your JavaScript tracker file in the <head> of your website, this should not be needed.

    Advanced options

    If you want to go even further, you can think about serving the JavaScript tracking file via a CDN, merging the JavaScript tracker file content with your other JavaScript files, making use of service workers (and even track data offline), and more. Feel free to get in touch with us if you have any questions.

    More performance improvements

    Read our first blog in the series at Different ways of embedding the Piwik tracking code for faster website performance

  • ffmpeg mosaic keep audio of all input videos

    11 juin 2017, par FSH

    I have five videos and want to combine them into one big "strip" with all five videos next to each other.

    My code so far (following this example) :

    ffmpeg
    
    -i s-0-h-0.mp4 -i s-1-h-0.mp4 -i s-2-h-0.mp4 -i s-3-h-0.mp4 -i s-4-h-0.mp4
    
    -filter_complex "
    
        nullsrc=size=4240x478 [base];
    
        [0:v] setpts=PTS-STARTPTS, scale=848x478 [vid1];
    
        [1:v] setpts=PTS-STARTPTS, scale=848x478 [vid2];
    
        [2:v] setpts=PTS-STARTPTS, scale=848x478 [vid3];
    
        [3:v] setpts=PTS-STARTPTS, scale=848x478 [vid4];
    
        [4:v] setpts=PTS-STARTPTS, scale=848x478 [vid5];
    
        [base][vid1] overlay=shortest=1 [tmp1];
    
        [tmp1][vid2] overlay=shortest=1:x=848 [tmp2];
    
        [tmp2][vid3] overlay=shortest=1:x=1696 [tmp3];
    
        [tmp3][vid4] overlay=shortest=1:x=2544 [tmp4];
    
        [tmp4][vid5] overlay=shortest=1:x=3392
    
    "
    
   -c:v libx264 output.mkv

    However, this only includes the audio from input 1.

    How do I keep the audio of all five input videos ?

  • Create a mosaic of multiple input videos and stream them using FFMPEG

    23 janvier 2018, par Ahmad Rahmani

    I want to create a mosaic of multiple stream input videos and stream the output realtime.
    i used this code :

    ffmpeg -i http://192.168.1.1:3005/13 -i http://192.168.1.1:3005/12 -i http://192.168.1.1:3005/15 -i http://192.168.1.1:3005/16   -filter_complex "nullsrc=size=640x480 [base]; [0:v] setpts=PTS-STARTPTS, scale=320x240 [upperleft]; [1:v] setpts=PTS-STARTPTS, scale=320x240 [upperright]; [2:v] setpts=PTS-STARTPTS, scale=320x240 [lowerleft]; [3:v] setpts=PTS-STARTPTS, scale=320x240 [lowerright]; [base][upperleft] overlay=shortest=1 [tmp1]; [tmp1][upperright] overlay=shortest=1:x=320 [tmp2]; [tmp2][lowerleft] overlay=shortest=1:y=240 [tmp3]; [tmp3][lowerright] overlay=shortest=1:x=320:y=240" -f mjpeg  udp://192.168.1.2:1234

    but its not working.what is the correct command to do that ?

    here is the end of the log :

    Metadata :
    encoder : Lavf57.83.100
    Stream #0:0 : Video : mpeg2video (Main), yuv420p, 640x480 [SAR 1:1 DAR4:3],q=2-31, 200 kb/s, 25 fps, 90k tbn, 25 tbc (default)
    Metadata :
    encoder : Lavc57.107.100 mpeg2video
    Side data :
    cpb : bitrate max/min/avg : 0/0/200000 buffer size : 0 vbv_delay : -1
    Stream #0:1(eng) : Audio : mp2, 48000 Hz, stereo, s16, 384 kb/s (clean effects)
    Metadata :
    encoder : Lavc57.107.100 mp2

    frame= 32 fps=0.0 q=31.0 size= 248kB time=00:00:02.19 bitrate=923.1kbits/frame= 84 fps= 84 q=31.0 size= 456kB time=00:00:04.40 bitrate= 848.6kbits/
    [http @ 00000000004fa4c0] Stream ends prematurely at 1950500, should be 18446744073709551615
    [h264 @ 00000000032a55c0] error while decoding MB 12 20, bytestream -9 http://192.168.1.1:1234:3005/13 : I/O error
    Last message repeated 9 times

    frame= 129 fps= 85 q=31.0 Lsize= 743kB time=00:00:06.32 bitrate= 961.9kbits
    /s speed=4.19x
    video:364kB audio:297kB subtitle:0kB other streams:0kB global headers:0kB muxing
    overhead : 12.360500%

Navigation