Recherche avancée

Médias (3)

Mot : - Tags -/plugin

Autres articles (110)

  • 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 ;

  • Creating farms of unique websites

    13 avril 2011, par

    MediaSPIP platforms can be installed as a farm, with a single "core" hosted on a dedicated server and used by multiple websites.
    This allows (among other things) : implementation costs to be shared between several different projects / individuals rapid deployment of multiple unique sites creation of groups of like-minded sites, making it possible to browse media in a more controlled and selective environment than the major "open" (...)

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

  • Ubuntu 16.04 + ffmpeg [on hold]

    19 janvier 2017, par Nick Deny

    On Ubuntu 14.04 my command working normally, but on Ubuntu 16.04 it’s error. I don’t know why, can somebody help ?

    { [Error: Command failed: /bin/sh -c ffmpeg -y -i audio/reader/0.mp3 -i audio/bits/mute1.mp3 -filter_complex amix=inputs=2:duration=longest:dropout_transition=2 audio/reader/0mute.mp3
    ffmpeg version 3.2.2-1~16.04.york3 Copyright (c) 2000-2016 the FFmpeg developers
     built with gcc 5.4.1 (Ubuntu 5.4.1-4ubuntu1~16.04.york1) 20161202
     configuration: --prefix=/usr --extra-version='1~16.04.york3' --toolchain=hardened --libdir=/usr/lib/x86_64-linux-gnu --incdir=/usr/include/x86_64-linux-gnu --enable-gpl --disable-stripping --enable-avresample --enable-avisynth --enable-gnutls --enable-ladspa --enable-libass --enable-libbluray --enable-libbs2b --enable-libcaca --enable-libcdio --enable-libebur128 --enable-libflite --enable-libfontconfig --enable-libfreetype --enable-libfribidi --enable-libgme --enable-libgsm --enable-libmodplug --enable-libmp3lame --enable-libopenjpeg --enable-libopus --enable-libpulse --enable-librubberband --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libssh --enable-libtheora --enable-libtwolame --enable-libvorbis --enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx265 --enable-libxvid --enable-libzmq --enable-libzvbi --enable-omx --enable-openal --enable-opengl --enable-sdl2 --enable-libdc1394 --enable-libiec61883 --enable-libopencv --enable-frei0r --enable-libx264 --enable-chromaprint --enable-shared
     libavutil      55. 34.100 / 55. 34.100
     libavcodec     57. 64.101 / 57. 64.101
     libavformat    57. 56.100 / 57. 56.100
     libavdevice    57.  1.100 / 57.  1.100
     libavfilter     6. 65.100 /  6. 65.100
     libavresample   3.  1.  0 /  3.  1.  0
     libswscale      4.  2.100 /  4.  2.100
     libswresample   2.  3.100 /  2.  3.100
     libpostproc    54.  1.100 / 54.  1.100
    [mp3 @ 0x55734af43540] Format mp3 detected only with low score of 1, misdetection possible!
    [mp3 @ 0x55734af43540] Failed to read frame size: Could not seek to 1105.
    audio/reader/0.mp3: Invalid argument
    ]
     killed: false,
     code: 1,
     signal: null,
     cmd: '/bin/sh -c ffmpeg -y -i audio/reader/0.mp3 -i audio/bits/mute1.mp3 -filter_complex amix=inputs=2:duration=longest:dropout_transition=2 audio/reader/0mute.mp3' }
  • avcodec/indeo2 : Remove #ifdef BITSTREAM_READER_LE cruft

    12 octobre 2020, par Andreas Rheinhardt
    avcodec/indeo2 : Remove #ifdef BITSTREAM_READER_LE cruft
    

    Before the LE bitstream reader was used in the Indeo 2 decoder,
    a standard BE bitstream reader with swapped bits was used ; when the LE
    bitstream reader was added, the old code was only #ifdef'ed away and not
    removed. Said code has several problems : It modifies the input packet
    without ensuring that the packet is indeed writable ; and it doesn't work
    since 09c4e5c5988c0037d108c5fc2a137d9ad488f7f4 because said commit
    removed the BE table used to initialize the VLC table. So just remove
    this cruft from the actual decoder, too.

    Also use INIT_LE_VLC_STATIC while at it.

    Reviewed-by : Paul B Mahol <onemda@gmail.com>
    Signed-off-by : Andreas Rheinhardt <andreas.rheinhardt@gmail.com>

    • [DH] libavcodec/indeo2.c
  • Electron, Chromium and ffmpeg licencing confusion [closed]

    12 mars 2021, par Iamisti

    Intro :&#xA;Recently I'm working on an electron based application that is free to use but also has subscription based services.&#xA;It came to my attention that ffmpeg is shipped with electron, which has GPL/LGPL licence.

    &#xA;

    My quetion is :

    &#xA;

      &#xA;
    • Am I legally able to still distribute the application and be licence-compliant with ffmpeg without owning any proper licence to it ? I thought chromium dealt with the licencing on this topic since so many applications nowadays are shipped with using electron and chromium under the hood.
    • &#xA;

    • How do I compile/build electron to make it licence compatible (in case its not ?)
    • &#xA;

    &#xA;

    I did a lot of reseearch and I found out the followings :

    &#xA;

      &#xA;
    • ffmpeg is shipped with chromium, they built their own version of ffmpeg and it seems they also have licence for it. Although that might be that they just push the responsibility down on the software developer/company who distributes their application with chromium.&#xA;Chromium licence for ffmpeg : https://chromium.googlesource.com/chromium/third_party/ffmpeg/+/703e920bb75053bf6b87d41d198cbbfbce3fb7ad/LICENSE

      &#xA;

    • &#xA;

    • Apparently ffmpeg has a checklist of how to be licence compliant. Does that mean if I do all these steps, I can still distribute the application and can legally use it ? Licence checklist for ffmpeg : http://ffmpeg.org/legal.html

      &#xA;

    • &#xA;

    • checking out some popular electron applications like Discord, Figma, Slack, etc... they ALL have ffmpeg included cause of electron when you install them. I wonder how they made it legal ? I don't see any of these checklists done on any of these popular applications.

      &#xA;

    • &#xA;

    &#xA;

    I'm know very little regarding licences, so any help would be incredibly huge help for me.

    &#xA;