Recherche avancée

Médias (91)

Autres articles (95)

  • MediaSPIP 0.1 Beta version

    25 avril 2011, par

    MediaSPIP 0.1 beta is the first version of MediaSPIP proclaimed as "usable".
    The zip file provided here only contains the sources of MediaSPIP in its standalone version.
    To get a working installation, you must manually install all-software dependencies on the server.
    If you want to use this archive for an installation in "farm mode", you will also need to proceed to other manual (...)

  • Multilang : améliorer l’interface pour les blocs multilingues

    18 février 2011, par

    Multilang est un plugin supplémentaire qui n’est pas activé par défaut lors de l’initialisation de MediaSPIP.
    Après son activation, une préconfiguration est mise en place automatiquement par MediaSPIP init permettant à la nouvelle fonctionnalité d’être automatiquement opérationnelle. Il n’est donc pas obligatoire de passer par une étape de configuration pour cela.

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

  • Getting content-length of a live-re-encoded video

    9 avril 2021, par Marius

    So, i have a lot of hevc(h265) video on a remote http server, that i want to serve as h264 through ffmpeg and nodejs. I've had a bunch of issues with content-length, or in general just getting skipping, and video duration to work properly.

    


    So the main problem is getting content-length, or any other header to make duration and skipping work properly.

    


    I've tried calculating approx content-length, but it never seems to match properly.

    


    My code so far :

    


    express setup here....
app.get('/', (req, res) => {
    res.contentType('mp4');
    
    ffmpeg(remote_video_url)
        .inputOption([
            "-hwaccel auto",
        ])
        .outputOptions(['-movflags isml+frag_keyframe'])
        .videoCodec('h264_nvenc')
        .toFormat('mp4')
        .on('error', (err,stdout,stderr) => {
            console.log('an error happened: ' + err.message);
            console.log('ffmpeg stdout: ' + stdout);
            console.log('ffmpeg stderr: ' + stderr);
        })
        .on('end', () => {
            console.log('Processing finished !');
        })
        .on('progress', (progress) => {
            console.log('Processing: ' + progress.percent + '% done');
        })
        .pipe(res, {end: true});
})


    


    Any help would be greatly appreciated

    


  • avformat/webvttenc : Fix use of uninitialized variable

    8 avril 2021, par Andreas Rheinhardt
    avformat/webvttenc : Fix use of uninitialized variable

    Happened in 9168a1c0e67b5c31727b12329b6f52d2bb5e0a14.
    

    Reviewed-by : Anton Khirnov <anton@khirnov.net>
    
Signed-off-by : Andreas Rheinhardt <andreas.rheinhardt@outlook.com>
    • [DH] libavformat/webvttenc.c

  • avcodec/vc1dec : Fix memleak upon allocation error

    8 avril 2021, par Andreas Rheinhardt
    avcodec/vc1dec : Fix memleak upon allocation error

    ff_vc1_decode_init_alloc_tables() had one error path that forgot to free
    
already allocated buffers ; these would then be overwritten on the next
    
allocation attempt (or they would just not be freed in case this
    
happened during init, as the decoders for which it is used do not have
    
the FF_CODEC_CAP_INIT_CLEANUP set).
    

    Signed-off-by : Andreas Rheinhardt <andreas.rheinhardt@outlook.com>
    • [DH] libavcodec/vc1dec.c

Navigation