Recherche avancée

Médias (29)

Mot : - Tags -/Musique

Autres articles (67)

  • Use, discuss, criticize

    13 avril 2011, par

    Talk to people directly involved in MediaSPIP’s development, or to people around you who could use MediaSPIP to share, enhance or develop their creative projects.
    The bigger the community, the more MediaSPIP’s potential will be explored and the faster the software will evolve.
    A discussion list is available for all exchanges between users.

  • (Dés)Activation de fonctionnalités (plugins)

    18 février 2011, par

    Pour gérer l’ajout et la suppression de fonctionnalités supplémentaires (ou plugins), MediaSPIP utilise à partir de la version 0.2 SVP.
    SVP permet l’activation facile de plugins depuis l’espace de configuration de MediaSPIP.
    Pour y accéder, il suffit de se rendre dans l’espace de configuration puis de se rendre sur la page "Gestion des plugins".
    MediaSPIP est fourni par défaut avec l’ensemble des plugins dits "compatibles", ils ont été testés et intégrés afin de fonctionner parfaitement avec chaque (...)

  • Les autorisations surchargées par les plugins

    27 avril 2010, par

    Mediaspip core
    autoriser_auteur_modifier() afin que les visiteurs soient capables de modifier leurs informations sur la page d’auteurs

Sur d’autres sites (13080)

  • How to get the real, actual duration of an MP3 file (VBR or CBR) server-side

    25 septembre 2016, par SquareCat

    I used to calculate the duration of MP3 files server-side using ffmpeg - which seemed to work fine. Today i discovered that some of the calculations were wrong. Somehow, for some reason, ffmpeg will miscalculate the duration and it seems to happen with variable bit rate mp3 files only.

    When testing this locally, i noticed that ffmpeg printed two extra lines in green.

    Command used :

    ffmpeg -i song_9747c077aef8.mp3

    ffmpeg says :

    [mp3 @ 0x102052600] max_analyze_duration 5000000 reached at 5015510
    
[mp3 @ 0x102052600] Estimating duration from bitrate, this may be inaccurate

    After a nice, warm google session, i discovered some posts on this, but no solution was found.

    I then tried to increase the maximum duration :

    ffmpeg -analyzeduration 999999999 -i song_9747c077aef8.mp3

    After this, ffmpeg returned only the second line :

    [mp3 @ 0x102052600] Estimating duration from bitrate, this may be inaccurate

    But in either case, the calculated duration was just plain wrong. Comparing it to VLC i noticed that there the duration is correct.

    After more research i stumbled over mp3info - which i installed and used.

    mp3info -p "%S" song_9747c077aef8.mp3

    mp3info then returned the CORRECT duration, but only as an integer, which i cannot use as i need a more accurate number here. The reason for this was explained in a comment below, by user blahdiblah - mp3info is simply pulling ID3 info from the file and not actually performing any calculations.

    I also tried using mplayer to retrieve the duration, but just as ffmpeg, mplayer is returning the wrong value.

  • lavf : inject sample skip side data when requested by the demuxer

    4 juillet 2012, par Michael Niedermayer

    lavf : inject sample skip side data when requested by the demuxer

  • flac : Move flac functions shared between libraries to flac common code

    10 juillet 2012, par Diego Biurrun

    flac : Move flac functions shared between libraries to flac common code

Navigation