Recherche avancée

Médias (1)

Mot : - Tags -/bug

Autres articles (48)

  • Gestion générale des documents

    13 mai 2011, par

    MédiaSPIP ne modifie jamais le document original mis en ligne.
    Pour chaque document mis en ligne il effectue deux opérations successives : la création d’une version supplémentaire qui peut être facilement consultée en ligne tout en laissant l’original téléchargeable dans le cas où le document original ne peut être lu dans un navigateur Internet ; la récupération des métadonnées du document original pour illustrer textuellement le fichier ;
    Les tableaux ci-dessous expliquent ce que peut faire MédiaSPIP (...)

  • Encoding and processing into web-friendly formats

    13 avril 2011, par

    MediaSPIP automatically converts uploaded files to internet-compatible formats.
    Video files are encoded in MP4, Ogv and WebM (supported by HTML5) and MP4 (supported by Flash).
    Audio files are encoded in MP3 and Ogg (supported by HTML5) and MP3 (supported by Flash).
    Where possible, text is analyzed in order to retrieve the data needed for search engine detection, and then exported as a series of image files.
    All uploaded files are stored online in their original format, so you can (...)

  • Qualité du média après traitement

    21 juin 2013, par

    Le bon réglage du logiciel qui traite les média est important pour un équilibre entre les partis ( bande passante de l’hébergeur, qualité du média pour le rédacteur et le visiteur, accessibilité pour le visiteur ). Comment régler la qualité de son média ?
    Plus la qualité du média est importante, plus la bande passante sera utilisée. Le visiteur avec une connexion internet à petit débit devra attendre plus longtemps. Inversement plus, la qualité du média est pauvre et donc le média devient dégradé voire (...)

Sur d’autres sites (6703)

  • Monitoring ffmpeg two-passes encoding

    31 décembre 2024, par Hodol

    I'm new in FFMPEG.

    


    According to the official guide, https://trac.ffmpeg.org/wiki/Encode/VP9 I use the following command to convert a large h.264 file :

    


    ffmpeg -i input.mp4 -c:v libvpx-vp9 -b:v 0 -crf 30 -pass 1 -an -f null /dev/null
ffmpeg -i input.mp4 -c:v libvpx-vp9 -b:v 0 -crf 30 -pass 2 -c:a libopus output.webm


    


    However, the pass-1 takes too long time and it does not log progress. With -report option I can see something is in progress but I don't know how long I should wait.

    


    Here's questions :

    


      

    1. Is there any way to see the progress of 1-pass ?
    2. 


    3. Is there any way to speed up the process ?
    4. 


    


    Thank you,

    


  • FFMPEG failing in AWS Lambda

    18 février 2019, par Zaid Amir

    I am trying to create a transcoding function for short videos. The function is hosted on AWS Lambda. The problem is that AWS lambda seems to be missing something that FFMPEG requires, at least according to Amazon.

    I contacted Amazon earlier and this is their response to the issue :

    We found that the FFMPEG operations require at least libx264 and an
    acc library, both of which will have dependencies of their own. To
    troubleshoot the issue it will involve diving deeper into the full
    dependency chain. We can see that it works in the Amazon Linux
    environment however, the environment is similar but not identical to
    the lambda environment. There can be some dependencies that exist in
    Amazon Linux but not in lambda environment as Lambda runs on the
    container. Here, as FFmpeg is a third party software, diving deeper
    into the dependency chain and verifying the version compatibilities is
    very hard to do. Unfortunately going further, this is bound to go into
    architecture and code support which is out of AWS Support scope 1. I
    hope you understand our limitations. However should FFmpeg support
    have any questions specific to the Lambda platform, please do let us
    know and we will be happy to assist. We will be in better position to
    investigate further once you receive an update from the FFmpeg support
    suggesting an issue from Lambda end.

    Upon AWS suggestion, I contacted FFMPEG on the developers mailing list, my message was rejected with the reason being that its more suited to ffmpeg users mailing list than developers. I sent an email to ’ffmpeg-user@ffmpeg.org’ a week ago and did not get any response yet.

    I then went and built a dynamically linked ffmpeg version making sure to package all libraries, checked ddl on each one, then made a small lambda function that looped over all binaries and ddled each one of them, compared that to the output I got from Amazon Linux and the same dependencies/versions exists on both lambda and the AWS Linux instance yet ffmpeg still fails on lambda.

    You can find a detailed log file here : https://www.datafilehost.com/d/6e5e21bb

    And this is a sample of the errors I’m getting, repeated across the entire log file :

    2018-08-14T12:27:10.874Z [h264 @ 0x65c2fc0] concealing 2628 DC, 2628
    AC, 2628 MV errors in P frame

    2018-08-14T12:27:10.874Z [aac @ 0x65d2f00] channel element 2.11 is not
    allocated

    2018-08-14T12:27:10.874Z Error while decoding stream #0:1 : Invalid
    data found when processing input

    2018-08-14T12:27:10.874Z [h264 @ 0x67e86c0] Invalid NAL unit size
    (108085662 > 1649).

    2018-08-14T12:27:10.874Z [h264 @ 0x67e86c0] Error splitting the input
    into NAL units.

    2018-08-14T12:27:10.874Z [aac @ 0x65d2f00] channel element 2.0 is not
    allocated

    2018-08-14T12:27:10.874Z Error while decoding stream #0:1 : Invalid
    data found when processing input

    2018-08-14T12:27:10.874Z [h264 @ 0x68189c0] Invalid NAL unit size
    (71106974 > 1085).

    2018-08-14T12:27:10.874Z [h264 @ 0x68189c0] Error splitting the input
    into NAL units.

    2018-08-14T12:27:10.874Z [aac @ 0x65d2f00] Pulse tool not allowed in
    eight short sequence.

    This log is generated when trying to perform an HLS transcoding on this file : https://www.datafilehost.com/d/999a4492

    Note that the issue is not related to that file alone nor is it related to HLS, its general and happen on all videos and any ffmpeg command that tries to seek the stream, even tried extracting a single frame from a video using the simplest form possible for example : ffmpeg -ss 00:00:02 -I file.mp4 -vframes 1 -y output.jpg also fails with the same errors in the log file.

    Not sure how to debug this further. Tried enabling debug logs with ‘-loglevel debug’ but did not give me any extra info. Any help or suggestions

  • Carrierwave watermark a movie

    15 mai 2016, par Felix

    I’m uploading a movie with carrierwave to amazon S3. While uploading I want to watermark the movie.

    How can I do this ? How can I use stermio-ffmpeg while uploading ?

    I’m using a Rails application.