Recherche avancée

Médias (91)

Autres articles (34)

  • Support audio et vidéo HTML5

    10 avril 2011

    MediaSPIP utilise les balises HTML5 video et audio pour la lecture de documents multimedia en profitant des dernières innovations du W3C supportées par les navigateurs modernes.
    Pour les navigateurs plus anciens, le lecteur flash Flowplayer est utilisé.
    Le lecteur HTML5 utilisé a été spécifiquement créé pour MediaSPIP : il est complètement modifiable graphiquement pour correspondre à un thème choisi.
    Ces technologies permettent de distribuer vidéo et son à la fois sur des ordinateurs conventionnels (...)

  • HTML5 audio and video support

    13 avril 2011, par

    MediaSPIP uses HTML5 video and audio tags to play multimedia files, taking advantage of the latest W3C innovations supported by modern browsers.
    The MediaSPIP player used has been created specifically for MediaSPIP and can be easily adapted to fit in with a specific theme.
    For older browsers the Flowplayer flash fallback is used.
    MediaSPIP allows for media playback on major mobile platforms with the above (...)

  • De l’upload à la vidéo finale [version standalone]

    31 janvier 2010, par

    Le chemin d’un document audio ou vidéo dans SPIPMotion est divisé en trois étapes distinctes.
    Upload et récupération d’informations de la vidéo source
    Dans un premier temps, il est nécessaire de créer un article SPIP et de lui joindre le document vidéo "source".
    Au moment où ce document est joint à l’article, deux actions supplémentaires au comportement normal sont exécutées : La récupération des informations techniques des flux audio et video du fichier ; La génération d’une vignette : extraction d’une (...)

Sur d’autres sites (6566)

  • Fallback input for ffmpeg

    22 septembre 2018, par Daniel Cantarin

    I’m doing some transcoding from a third-party remote input stream that I do not control.

    This input stream has errors from time to time, that I would like to mitigate before sending the stream to my transcoding pipeline, avoiding this way some possible problems in the output.

    I have several ideas regarding different problems. But the most basic scenario I would like to set up is as follows : when the stream is down, or it somehow loses some frames, I want to fill that video gap with a secondary input (like a blank screen, for example).

    For this simple task, I would like to use ffmpeg. I know it can mix, let’s say, an input stream with a fullscreen black square static image. However, I have to deal with this other condition : ffmpeg would run in the same infraestructure for the actual transcoding pipeline. That infraestructure must use its computing power for rendering the output. So, whatever ffmpeg command I end up using should use the minimum possible computing power.

    My actual problem : if I use -vcodec copy, in order to use minimum CPU, I can’t alter the original stream. But if I alter the original stream (by mixing it with some other stream), the operation uses CPU.

    My question : Is there a way to use -vcodec copy, but with a fallback input (instead of a mixed one) for when there are video gaps in the primary stream ?

    Thanks in advance.

  • lavu/tx : implement 32 bit fixed point FFT and MDCT

    9 février 2020, par Lynne
    lavu/tx : implement 32 bit fixed point FFT and MDCT
    

    Required minimal changes to the code so made sense to implement.
    FFT and MDCT tested, the output of both was properly rounded.
    Fun fact : the non-power-of-two fixed-point FFT and MDCT are the fastest ever
    non-power-of-two fixed-point FFT and MDCT written.
    This can replace the power of two integer MDCTs in aac and ac3 if the
    MIPS optimizations are ported across.
    Unfortunately the ac3 encoder uses a 16-bit fixed point forward transform,
    unlike the encoder which uses a 32bit inverse transform, so some modifications
    might be required there.

    The 3-point FFT is somewhat less accurate than it otherwise could be,
    having minor rounding errors with bigger transforms. However, this
    could be improved later, and the way its currently written is the way one
    would write assembly for it.
    Similar rounding errors can also be found throughout the power of two FFTs
    as well, though those are more difficult to correct.
    Despite this, the integer transforms are more than accurate enough.

    • [DH] doc/APIchanges
    • [DH] libavutil/Makefile
    • [DH] libavutil/tx.c
    • [DH] libavutil/tx.h
    • [DH] libavutil/tx_int32.c
    • [DH] libavutil/tx_priv.h
    • [DH] libavutil/tx_template.c
    • [DH] libavutil/version.h
  • 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