Recherche avancée

Médias (0)

Mot : - Tags -/xmp

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

Autres articles (40)

  • 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

  • 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 (...)

Sur d’autres sites (5069)

  • ffmpeg - Invalid report file level (windows)

    24 octobre 2019, par Pedro Lobito

    ffmpeg is giving me an error and I couldn’t get much help googling it, besides a thread on ffmpeg mailing list dated 5 years ago which doesn’t address the exact same problem.

    No matter which ffmpeg version or build for windows I use, the error is always :

    c:\>ffmpeg.exe
    
Invalid report file level

    I’ve been using ffmpeg on the same computer for years and I’ve no idea where the problem started and how to debug it. Any help is welcome.

    Notes :

    1. No antivirus is running
    2. ffmpeg.exe is on windows path
    3. I’ve tried installing ffmpeg with
      choco install
      ffmpeg

      but it reports the same error.

  • avisynth : adapt 239d02eff3ffe9f7d40caa21dde50fb4a0e94c24 to dlsym

    30 mars 2019, par Stephen Hutchinson
    avisynth : adapt 239d02eff3ffe9f7d40caa21dde50fb4a0e94c24 to dlsym

    This commit was merged in a couple years ago as a no-op because we
    
had already switched from GetProcAddress to dlsym some time before
    
that.  However, not applying the actual cast causes warnings about
    
FARPROC and when attempting to build FFmpeg in MSVC with AviSynth-GCC
    
32-bit compatibility, those FARPROC warnings turn into FARPROC errors.
    • [DH] libavformat/avisynth.c

  • Getting motion vector side data from ffmpeg from the compressed domain (without performing full decode)

    4 mai 2019, par John Allard

    The ffmepg source code comes with a file extract_mvs.c which is quite helpful in showing how to extract the motion vectors from an h264-encoded video file. Unfortunately, it performs a full decode before getting the motion vectors from the side data of the stream.

    One should be technically able to (as was confirmed by FFMPEG developer Carl Eugen in this thread https://ffmpeg.org/pipermail/libav-user/2016-December/009913.html) get the motion vectors from the compressed domain before performing a full decode step. This would obviously be less computationally intensive as one wouldn’t have to perform a full decode.

    Is it possible to do this with ffmpeg/libavcodec as is ? I know Carl said that it wasn’t possible but that was 3 years ago. If it is not currently possible, does anyone have any hints on how one would go about modifying the ffmpeg source code to do this ?

    Thanks

Navigation