Recherche avancée

Médias (0)

Mot : - Tags -/metadatas

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

Sur d’autres sites (2669)

  • avformat/matroskadec : Accept more unknown-length elements

    17 mai 2019, par Andreas Rheinhardt
    avformat/matroskadec : Accept more unknown-length elements
    

    The current Matroska specifications mandate that only two elements may
    use an unknown-length length : Segments and clusters. But this was not
    always so : For the greater part of Matroska's existence, all master
    elements were allowed to make use of the unknown-length feature.

    And there were muxers creating such files : For several years
    libavformat's Matroska muxer used unknown-length for all master
    elements when the output wasn't seekable. This only stopped in March
    2010 with 2529bb30. And even afterwards it was possible (albeit
    unlikely) for libavformat to create unknown-length master elements
    that are in violation of today's specifications, namely if the master
    element was so big that the seek backwards to update the size could
    no longer be performed inside the AVIOContext's write buffer. This
    has only been fixed in October 2016 (with the patches that introduced
    support for writing CRC-32 elements).

    Libavformat's Matroska demuxer meanwhile has never really supported
    unknown-length elements besides segments and clusters. Support for the
    latter was hardcoded. This commit changes this : Now all master elements
    for which a syntax to parse them is available are supported. This
    includes the files produced by old versions of libavformat's muxer.

    More precisely, master elements that have unknown length and are about
    to be parsed (not skipped) are supported ; only a warning is emitted for
    them. For normal files, this means that level 1 elements after the
    clusters that are encountered after the clusters have been parsed (i.e.
    not because they are referenced by the seekhead at the beginning of the
    file) are still unsupported (they would be skipped at this point if
    their length were known).

    Signed-off-by : Andreas Rheinhardt <andreas.rheinhardt@gmail.com>

    • [DH] libavformat/matroskadec.c
  • lavc/mjpegdec : Skip unknown APPx marker on bayer images

    29 août 2019, par Nick Renieris
    lavc/mjpegdec : Skip unknown APPx marker on bayer images
    

    Samples :
    - Embedded JPEG images in the DNG images here :
    https://www.photographyblog.com/previews/pentax_k1_photos

    Signed-off-by : Nick Renieris <velocityra@gmail.com>

    • [DH] libavcodec/mjpegdec.c
  • Unknown Decoder in ffmpeg

    17 mars 2020, par user6782547

    I have a script, that is called from Plex after the recording of a movie. This script just crops the black borders of the movie.

    When I call it directly from the command line, it works flawlessly. But when Plex calls it, it says : "Unknown decoder", even if I call it with the key word "auto" for the decoder.

    There’s another problem, that might give a hint to solve my problem. It also says : "WARNING: library configuration mismatch". (Only when being called from Plex.) This is probably, because I compile ffmpeg from the Debian source package (so that I can add the whole CUDA functionality).
    I had a look at the dynamic linker path, but it is empty on the command line.

    What is so different, when this command is called from Plex, than when I call it manually from the command line ?

    Thanks for any help