Recherche avancée

Médias (91)

Autres articles (106)

  • MediaSPIP version 0.1 Beta

    16 avril 2011, par

    MediaSPIP 0.1 beta est la première version de MediaSPIP décrétée comme "utilisable".
    Le fichier zip ici présent contient uniquement les sources de MediaSPIP en version standalone.
    Pour avoir une installation fonctionnelle, il est nécessaire d’installer manuellement l’ensemble des dépendances logicielles sur le serveur.
    Si vous souhaitez utiliser cette archive pour une installation en mode ferme, il vous faudra également procéder à d’autres modifications (...)

  • MediaSPIP 0.1 Beta version

    25 avril 2011, par

    MediaSPIP 0.1 beta is the first version of MediaSPIP proclaimed as "usable".
    The zip file provided here only contains the sources of MediaSPIP in its standalone version.
    To get a working installation, you must manually install all-software dependencies on the server.
    If you want to use this archive for an installation in "farm mode", you will also need to proceed to other manual (...)

  • Amélioration de la version de base

    13 septembre 2013

    Jolie sélection multiple
    Le plugin Chosen permet d’améliorer l’ergonomie des champs de sélection multiple. Voir les deux images suivantes pour comparer.
    Il suffit pour cela d’activer le plugin Chosen (Configuration générale du site > Gestion des plugins), puis de configurer le plugin (Les squelettes > Chosen) en activant l’utilisation de Chosen dans le site public et en spécifiant les éléments de formulaires à améliorer, par exemple select[multiple] pour les listes à sélection multiple (...)

Sur d’autres sites (9140)

  • FFMPEG MP3 file size much larger than expected on Windows 10

    8 avril 2018, par The Gora

    I’ve been using FFMPEG on Windows to :

    1. Convert iTunes M4A files to MP3s (with a bit rate of 128k) ; and
    2. Create 30 sec sample MP3s of the above MP3s (same bit rate).

    When I run FFMEG on a Windows 7 64 bit machine, the size of the MP3s (both for 1. & 2.) is in line with the rough calculation of :

    (Audio length in seconds) X (Bit rate)

    For example, a 4 minute audio yields an approx. 3.7MB MP3 file ; a 30 second sample MP3 is approx. 470KB.

    However when I run the same FFMPEG binary (copied from the Windows 7 machine) on a Windows 10 64 bit machine, all of the MP3s (both for 1. and for 2.) are inflated by approx 5MB. I’m using the same batch file on both machines to execute FFMEG with the required parameters, so pretty confident the difference is not down to user error.

    My questions are :

    1. Why is there this apparent 5MB overhead on Windows 10 ? and more importantly ;
    2. What can I do to remove this ?

    The large file size is a problem as the sample MP3s are to be put on a website for people to listen to a snippet of the song, and the webpage with multiple tags takes a long time to load completely (several minutes).

    Here is the version and lib info :

    ffmpeg version 3.4.1 Copyright (c) 2000-2017 the FFmpeg developers
     built with gcc 7.2.0 (GCC)
     configuration: --enable-gpl --enable-version3 --enable-sdl2 --enable-bzlib --enable-fontconfig --enable-gnutls --enable-iconv --enable-libass --enable-libbluray --enable-libfreetype --enable-libmp3lame --enable-libopenjpeg --enable-libopus --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libtheora --enable-libtwolame --enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxml2 --enable-libzimg --enable-lzma --enable-zlib --enable-gmp --enable-libvidstab --enable-libvorbis --enable-cuda --enable-cuvid --enable-d3d11va --enable-nvenc --enable-dxva2 --enable-avisynth --enable-libmfx
     libavutil      55. 78.100 / 55. 78.100
     libavcodec     57.107.100 / 57.107.100
     libavformat    57. 83.100 / 57. 83.100
     libavdevice    57. 10.100 / 57. 10.100
     libavfilter     6.107.100 /  6.107.100
     libswscale      4.  8.100 /  4.  8.100
     libswresample   2.  9.100 /  2.  9.100
     libpostproc    54.  7.100 / 54.  7.100

    And here are the command lines I’m using :

    1. ffmpeg -i input.m4a -id3v2_version 3 -b:a 128k -output.mp3
    2. ffmpeg -i input.m4a -ss 30 -t 30 -af "afade=in:st=30:d=5,afade=out:st=55:d=5" -id3v2_version 3 -b:a 128k -output.mp3

  • h264_direct : use the reference mask from the actual reference

    2 août 2016, par Anton Khirnov
    h264_direct : use the reference mask from the actual reference

    Not from the underlying frame. Fixes races with frame threading in
    
field-coded files, where decoding would wait for the wrong field (e.g.
    
random failures in mixed-nal-coding).
    

    Bug-Id : 954
    • [DBH] libavcodec/h264_direct.c

  • Docker build dependent on host Ubuntu version not on the actual Docker File

    26 mars 2021, par user8912375

    I'm facing an issue with my docker build.

    


    I have a dockerfile as follow :

    


    FROM python:3.6


RUN apt-get update && apt-get install -y libav-tools 
....


    


    The issue I'm facing is that I'm getting this error when building on ubuntu:20.04 LTS

    


    E: Package 'libav-tools' has no installation candidate


    


    I made some research and found out that ffmpeg should be a replacement for libav-tools

    


    FROM python:3.6


RUN apt-get update && apt-get install -y ffmpeg 
....


    


    I tried again without any issue.

    


    but when I tried to build the same image with ffmpeg on ubuntu:16.04 xenial I'm getting a message that

    


    E: Package 'ffmpeg' has no installation candidate


    


    after that, I replace the ffmpeg with libav-tools and it worked on ubuntu:16.04

    


    I'm confused now why docker build is dependant on the host ubuntu version that I'm using and not the actual dockerfile.

    


    shouldn't docker build be coherent whatever the ubuntu version I'm using.

    


Navigation