Recherche avancée

Médias (91)

Autres articles (50)

  • 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

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

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

  • Detect duplicate frames to create seamless loops in FFMPEG

    19 septembre 2017, par Yasath Dias

    I feel like this should be possible, after I saw a method created with MoviePy for Python (this article). Essentially, I want to import an MP4 at 1920x1080 with say 12000kbps bitrate and have FFMPEG detect when there are duplicate frames that aren’t consecutive and export each one of these small sequences to small individual MP4 files that loop seamlessly (the first frame is almost the same as the last frame like this one).

    A 1920x1080 file may be far too large (in resolution) to process, so I would be fine with downscaling that to around 120px wide. Also, I know that FFMPEG can detect duplicate frames because I’ve often used mpdecimate previously.

    I hope I described the issue well enough, but will be willing to clarify, of course :)

  • avformat/hlsenc : Check that data is set

    21 janvier 2018, par Brendan McGrath
    avformat/hlsenc : Check that data is set

    If codecpar->extradata is not set (for example, when the stream goes
    
through the 'tee' muxer), then a segfault occurs.
    
This patch ensures the data variable is not null before attempting
    
to access it
    
Before the var_stream_map option was available - I was using the tee
    
muxer to create each resolution as an individual stream.
    
When running this configuration after the most recent hlsenc change
    
I hit a segfault
    
The most simple command which recreates the segfault is :
    
ffmpeg -i in.ts -map 0:a -map 0:v -c:a aac -c:v h264 -f tee [select=\'a,v\':f=hls]tv_hls_hd.m3u8
    

    Signed-off-by : Brendan McGrath <redmcg@redmandi.dyndns.org>
    • [DH] libavformat/hlsenc.c

  • lavc/h264dec : don't error out when receiving multiple IDR slices

    26 septembre 2018, par Josh de Kock
    lavc/h264dec : don't error out when receiving multiple IDR slices

    This error isn't particularly helpful as checking for mixed IDR/non-IDR
    
NALUs would need to be done at a higher level to actually be accurate.
    
Removing the error allows an API user to send individual slice NALUs
    
(i.e. incomplete frames) so they can take advantage of slice
    
threading. The ticket which this error was added for (#4408) no
    
longer segfaults after removing this error (as the bug was likely
    
fixed more properly elsewhere).
    • [DH] libavcodec/h264dec.c

Navigation