Recherche avancée

Médias (0)

Mot : - Tags -/formulaire

Aucun média correspondant à vos critères n’est disponible sur le site.

Autres articles (2)

  • Selection of projects using MediaSPIP

    2 mai 2011, par

    The examples below are representative elements of MediaSPIP specific uses for specific projects.
    MediaSPIP farm @ Infini
    The non profit organizationInfini develops hospitality activities, internet access point, training, realizing innovative projects in the field of information and communication technologies and Communication, and hosting of websites. It plays a unique and prominent role in the Brest (France) area, at the national level, among the half-dozen such association. Its members (...)

  • Script d’installation automatique de MediaSPIP

    25 avril 2011, par

    Afin de palier aux difficultés d’installation dues principalement aux dépendances logicielles coté serveur, un script d’installation "tout en un" en bash a été créé afin de faciliter cette étape sur un serveur doté d’une distribution Linux compatible.
    Vous devez bénéficier d’un accès SSH à votre serveur et d’un compte "root" afin de l’utiliser, ce qui permettra d’installer les dépendances. Contactez votre hébergeur si vous ne disposez pas de cela.
    La documentation de l’utilisation du script d’installation (...)

Sur d’autres sites (1933)

  • fftools/ffmpeg_dec : abort if avcodec_send_packet() returns EAGAIN

    22 mai 2023, par James Almer
    fftools/ffmpeg_dec : abort if avcodec_send_packet() returns EAGAIN
    

    As the comment in the code mentions, EAGAIN is not an expected value here
    because we call avcodec_receive_frame() until all frames have been returned.
    avcodec_send_packet() returning EAGAIN means a packet is still buffered, which
    hints that the underlying decoder is buggy and not fetching packets as it
    should.

    An example of this behavior was in the libdav1d wrapper before f209614290,
    where feeding it split frames (or individual OBUs) would result in the CLI
    eventually printing the confusing "Error submitting packet to decoder : Resource
    temporarily unavailable" error message, and just keep going until EOF without
    returning new frames.

    Signed-off-by : James Almer <jamrial@gmail.com>

    • [DH] fftools/ffmpeg_dec.c
  • FFMPEG returns the wrong time

    22 juillet 2016, par GeeHopper

    I’m currently trying to cut a file using ffmpeg with the following command : "ffmpeg -sseof -10 -i resourcefile.mp4 -c copy cuttedfile.mp4" but for some reason the new file length is more than 10 seconds (around 15). So now I’m wondering if this is a bug, since this should cut the last 10 seconds in a new file.

    Thanks for the help :)

  • ffmpeg volumedetect returns unstable result

    8 février 2018, par Eric Stdlib

    I am using ffmpeg to calculate the volume of my audio file, but I find that ffmpeg returns different values for different containers (like mp3 v.s. ogg)

    Here is an example. I am using an ogg file from Wikimedia Commons, and converting it to mp3, then analyze the volume of both files. For ogg file, I get -3.0 dB for mean volume, but for mp3 file, I get -3.4 dB. When I use other files, I also get different max volume and histogram.

    [user@localhost tmp]$ wget https://upload.wikimedia.org/wikipedia/commons/b/b9/Audio_Frequency_tone%2C_Middle_C%2C_C4%2C_261.63hz.ogg -O a.ogg 2> /dev/null
    [user@localhost tmp]$ ffmpeg -i a.ogg a.mp3 2> /dev/null
    [user@localhost tmp]$ ffmpeg -i a.ogg -af volumedetect tmp.ogg 2>&amp;1 | grep volumedetect
    [Parsed_volumedetect_0 @ 0x555f69f3f4a0] n_samples: 88768
    [Parsed_volumedetect_0 @ 0x555f69f3f4a0] mean_volume: -3.0 dB
    [Parsed_volumedetect_0 @ 0x555f69f3f4a0] max_volume: 0.0 dB
    [Parsed_volumedetect_0 @ 0x555f69f3f4a0] histogram_0db: 27541
    [user@localhost tmp]$ ffmpeg -i a.mp3 -af volumedetect tmp.mp3 2>&amp;1 | grep volumedetect
    [Parsed_volumedetect_0 @ 0x55fd62be4740] n_samples: 88768
    [Parsed_volumedetect_0 @ 0x55fd62be4740] mean_volume: -3.4 dB
    [Parsed_volumedetect_0 @ 0x55fd62be4740] max_volume: -0.0 dB
    [Parsed_volumedetect_0 @ 0x55fd62be4740] histogram_0db: 21340
    [user@localhost tmp]$

    Why is this bug happening ? Which one should I believe ?