Recherche avancée

Médias (1)

Mot : - Tags -/artwork

Autres articles (105)

  • Websites made ​​with MediaSPIP

    2 mai 2011, par

    This page lists some websites based on MediaSPIP.

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

  • Other interesting software

    13 avril 2011, par

    We don’t claim to be the only ones doing what we do ... and especially not to assert claims to be the best either ... What we do, we just try to do it well and getting better ...
    The following list represents softwares that tend to be more or less as MediaSPIP or that MediaSPIP tries more or less to do the same, whatever ...
    We don’t know them, we didn’t try them, but you can take a peek.
    Videopress
    Website : http://videopress.com/
    License : GNU/GPL v2
    Source code : (...)

Sur d’autres sites (14347)

  • FFmpeg loudnorm : what does dynamic mode mean ? [closed]

    6 novembre 2023, par Javita Funky

    FFmpeg experts

    


    I have numerous audios that i'd like to normalize by the same reference with FFmpeg loudnorm filter. But every time I do the 1st pass of normalization, normalization type reverts to "dynamic".

    


    From here I know, that the loudnorm filter uses windows of 3 seconds of audio to calculate short-term loudness in the source and adjust the destination to meet the target parameters.
As most of my files are shotert than 3 seconds, I have to add some silence to them to make files at least 3 seconds long.

    


    Knowing that I do the 1st pass, but it reverts to dynamic mode (Normalization Type : Dynamic) every time

    


    Pass 1

    


    ffmpeg -i input.ogg -af apad,atrim=0:3,loudnorm=I=-17.2:TP=-2:LRA=7:print_format=summary -f null -


    


    I get

    


    Input Integrated:    -17.4 LUFS
Input True Peak:      -0.9 dBTP
Input LRA:             0.3 LU
Input Threshold:     -28.9 LUFS

Output Integrated:   -16.1 LUFS
Output True Peak:     -2.0 dBTP
Output LRA:            0.0 LU
Output Threshold:    -27.2 LUFS

Normalization Type:   Dynamic
Target Offset:        -1.1 LU


    


    FFmpeg documentation says "Target LRA shouldn’t be lower than source LRA and the change in integrated loudness shouldn’t result in a true peak which exceeds the target TP. If any of these conditions aren’t met, normalization mode will revert to dynamic. Options are true or false. Default is true."

    


    As I can see, none of these conditions are met, but normalization type still gets reverted to "dynamic". As an experiment I tried to change my target integrated loudness, TP and LRA in all different ways, but i still get normalization type "dynamic" every time

    


      

    1. Does it mean that "dynamic mode" applies instead of "linear mode" when I do the 2nd step (actual normalization) ?
    2. 


    3. What does this "dynamic type" mean, and how is it different from "linear" ?
    4. 


    5. Why this even happens and what do I do wrong ?
    6. 


    


  • avformat/hlsenc.c : fix the output's duration smaller than input's in sub-range mode.

    30 octobre 2018, par Charles Liu
    avformat/hlsenc.c : fix the output's duration smaller than input's in sub-range mode.
    

    In fmp4 & sub-range mode, the output's duration always smaller than expected,
    because the size of the last #EXT-X-BYTERANGE is too small.

    Signed-off-by : Charles Liu <liuchh83@gmail.com>
    Signed-off-by : Steven Liu <lq@chinaffmpeg.org>

    • [DH] libavformat/hlsenc.c
  • Constructor called at onready(), debug mode already determined.

    23 avril 2011, par Scott Schiller

    m demo/page-player/script/page-player.js Constructor called at onready(), debug mode already determined.