Recherche avancée

Médias (91)

Autres articles (77)

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

  • 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 reconnect to rtmp output if error

    27 avril 2017, par boygiandi

    I’m trying to livestream to facebook, it’s fine but sometime it got error and stop the stream

    [ sh : 2017-04-27 10:31:34 ]size= 296042kB time=00:13:04.48 bitrate=3091.4kbits/s speed= 1x

    [ sh : 2017-04-27 10:31:35 ]size= 296605kB time=00:13:05.48 bitrate=3093.4kbits/s speed= 1x

    [ sh : 2017-04-27 10:31:36 ]size= 296928kB time=00:13:06.50 bitrate=3092.7kbits/s speed= 1x

    [ sh : 2017-04-27 10:31:37 ]size= 297259kB time=00:13:07.48 bitrate=3092.3kbits/s speed= 1x

    [flv @ 0x32c91e0] Failed to update header with correct duration.

    [flv @ 0x32c91e0] Failed to update header with correct filesize.
    frame=23623 fps= 30 q=13.0 Lsize= 297346kB time=00:13:07.52 bitrate=3093.0kbits/s speed= 1x

    video:284080kB audio:12242kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead : 0.345891%

    [libx264 @ 0x3294c80] frame I:394 Avg QP:10.66 size : 99956

    [libx264 @ 0x3294c80] frame P:23229 Avg QP:13.94 size : 10828

    [libx264 @ 0x3294c80] mb I I16..4 : 100.0% 0.0% 0.0%

    [libx264 @ 0x3294c80] mb P I16..4 : 2.8% 0.0% 0.0% P16..4 : 34.9% 0.0% 0.0% 0.0% 0.0% skip:62.2%

    [libx264 @ 0x3294c80] coded y,uvDC,uvAC intra : 64.8% 69.3% 44.6% inter : 20.5% 16.6% 4.2%

    [libx264 @ 0x3294c80] i16 v,h,dc,p : 27% 51% 12% 10%

    [libx264 @ 0x3294c80] i8c dc,h,v,p : 34% 40% 16% 10%

    [libx264 @ 0x3294c80] kb/s:2955.27

    [aac @ 0x33825e0] Qavg : 1929.185

    I have no idea why it stopped, but is there any option to ignore error and still livestream ? Or another way, re-stream again from beginning. When I tried to do that by run ffmpeg (after few seconds) command again. It said

    [rtmp @ 0x3c01420] Server error : Initialization failed (2 : Broadcast state is bad)

    rtmp ://rtmp-api.facebook.com:80/rtmp/1658103677537416 ?ds=1&s_l=1&a=ATjLWmaYE8qulMzm : Operation not permitted

    I can’t stream again to facebook rtmp url. Please help

  • How can select only two audio streams in a video and feed it to the ebur128 filter wiithin ffmpeg ?

    18 avril 2017, par Edwin

    I want to use FFmpeg to analyze the loudness of an MXF video file.
    I have an MXF file with 8 mono audio streams. I only want to feed the first two streams through the ebur128 filter. But I can’t find a way to do that. The FFmpeg documentation is not clear to me, as I am fairly new to FFmpeg.

    I tried several things :

    ffmpeg -i source.mxf -nostats -filter_complex ebur128=dualmono=true:panlaw=-3.01dB -f null -

    I am sure it’s just that I don’t have the filtering syntax right. But hey... I’m a newbie...

    ffmpeg -i myVideo.mxf -nostats -filter_complex [0:a:0][0:a:1]amerge; ebur128=dualmono=true:panlaw=-3.01 -f null -

    And this is the resulting console output :

    ffmpeg version 2.8.6 Copyright (c) 2000-2016 the FFmpeg developers
    
built with llvm-gcc 4.2.1 (LLVM build 2336.11.00)
    
configuration: --prefix=/Volumes/Ramdisk/sw --enable-gpl --enable-        pthreads --enable-version3 --enable-libspeex --enable-libvpx --disable-decoder=libvpx --enable-libmp3lame --enable-libtheora --enable-libvorbis --enable-libx264 --enable-avfilter --enable-libopencore_amrwb --enable-libopencore_amrnb --enable-filters --enable-libgsm --enable-libvidstab --enable-libx265 --disable-doc --arch=x86_64 --enable-runtime-cpudetect
    
libavutil      54. 31.100 / 54. 31.100
    
libavcodec     56. 60.100 / 56. 60.100
    
libavformat    56. 40.101 / 56. 40.101
    
libavdevice    56.  4.100 / 56.  4.100
    
libavfilter     5. 40.101 /  5. 40.101
    
libswscale      3.  1.101 /  3.  1.101
    
libswresample   1.  2.101 /  1.  2.101
    
libpostproc    53.  3.100 / 53.  3.100
    

    
Guessed Channel Layout for  Input Stream #0.1 : mono
    
Guessed Channel Layout for  Input Stream #0.2 : mono
    
Guessed Channel Layout for  Input Stream #0.3 : mono
    
Guessed Channel Layout for  Input Stream #0.4 : mono
    
Guessed Channel Layout for  Input Stream #0.5 : mono
    
Guessed Channel Layout for  Input Stream #0.6 : mono
    
Guessed Channel Layout for  Input Stream #0.7 : mono
    
Guessed Channel Layout for  Input Stream #0.8 : mono
    
Input #0, mxf, from 'myVideo.mxf':
    
Metadata:
    
uid             : a727a381-1f5a-11e7-bdc8-18af61b92a5a
    
generation_uid  : a727a382-1f5a-11e7-9a04-18af61b92a5a
    
company_name    : Adobe Systems Incorporated
    
product_name    : Adobe Media Encoder
    
product_version : 11.0.2
    
application_platform: Mac OS X
    
product_uid     : 0c3919fe-46e8-11e5-a151-feff819cdc9f
    
modification_date: 2017-04-12 08:33:07
    
material_package_umid: 0x060A2B340101010501010D1113000000A0C9D501557805A5DF7018AF61B92A5A
    
timecode        : 00:00:00:00
    
Duration: 00:05:24.08, start: 0.000000, bitrate: 59986 kb/s
    
Stream #0:0: Video: mpeg2video (4:2:2), yuv422p(tv, unknown/bt709/bt709), 1920x1080 [SAR 1:1 DAR 16:9], 50000 kb/s, 25 fps, 25 tbr, 25 tbn, 50 tbc
    
Metadata:
    
  file_package_umid: 0x060A2B340101010501010D12133A5D15A0C9D501557805A5B09318AF61B92A5A
    
  file_package_name: Source Package
    
Stream #0:1: Audio: pcm_s24le, 48000 Hz, 1 channels, s32 (24 bit), 1152 kb/s
    
Metadata:
    
  file_package_umid: 0x060A2B340101010501010D12133A5D15A0C9D501557805A5B09318AF61B92A5A
    
  file_package_name: Source Package
    
Stream #0:2: Audio: pcm_s24le, 48000 Hz, 1 channels, s32 (24 bit), 1152 kb/s
    
Metadata:
    
  file_package_umid: 0x060A2B340101010501010D12133A5D15A0C9D501557805A5B09318AF61B92A5A
    
  file_package_name: Source Package
    
Stream #0:3: Audio: pcm_s24le, 48000 Hz, 1 channels, s32 (24 bit), 1152 kb/s
    
Metadata:
    
  file_package_umid: 0x060A2B340101010501010D12133A5D15A0C9D501557805A5B09318AF61B92A5A
    
  file_package_name: Source Package
    
Stream #0:4: Audio: pcm_s24le, 48000 Hz, 1 channels, s32 (24 bit), 1152 kb/s
    
Metadata:
    
  file_package_umid: 0x060A2B340101010501010D12133A5D15A0C9D501557805A5B09318AF61B92A5A
    
  file_package_name: Source Package
    
Stream #0:5: Audio: pcm_s24le, 48000 Hz, 1 channels, s32 (24 bit), 1152 kb/s
    
Metadata:
    
  file_package_umid: 0x060A2B340101010501010D12133A5D15A0C9D501557805A5B09318AF61B92A5A
    
  file_package_name: Source Package
    
Stream #0:6: Audio: pcm_s24le, 48000 Hz, 1 channels, s32 (24 bit), 1152 kb/s
    
Metadata:
    
  file_package_umid: 0x060A2B340101010501010D12133A5D15A0C9D501557805A5B09318AF61B92A5A
    
  file_package_name: Source Package
    
Stream #0:7: Audio: pcm_s24le, 48000 Hz, 1 channels, s32 (24 bit), 1152 kb/s
    
Metadata:
    
  file_package_umid: 0x060A2B340101010501010D12133A5D15A0C9D501557805A5B09318AF61B92A5A
    
  file_package_name: Source Package
    
Stream #0:8: Audio: pcm_s24le, 48000 Hz, 1 channels, s32 (24 bit), 1152 kb/s
    
Metadata:
    
  file_package_umid: 0x060A2B340101010501010D12133A5D15A0C9D501557805A5B09318AF61B92A5A
    
  file_package_name: Source Package
    
Filter amerge has a unconnected output
    

    
bash: -f: command not found

    I changed the name of the video to myVideo.mxf.

Navigation