Recherche avancée

Médias (0)

Mot : - Tags -/images

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

Autres articles (47)

  • Keeping control of your media in your hands

    13 avril 2011, par

    The vocabulary used on this site and around MediaSPIP in general, aims to avoid reference to Web 2.0 and the companies that profit from media-sharing.
    While using MediaSPIP, you are invited to avoid using words like "Brand", "Cloud" and "Market".
    MediaSPIP is designed to facilitate the sharing of creative media online, while allowing authors to retain complete control of their work.
    MediaSPIP aims to be accessible to as many people as possible and development is based on expanding the (...)

  • Les images

    15 mai 2013
  • Taille des images et des logos définissables

    9 février 2011, par

    Dans beaucoup d’endroits du site, logos et images sont redimensionnées pour correspondre aux emplacements définis par les thèmes. L’ensemble des ces tailles pouvant changer d’un thème à un autre peuvent être définies directement dans le thème et éviter ainsi à l’utilisateur de devoir les configurer manuellement après avoir changé l’apparence de son site.
    Ces tailles d’images sont également disponibles dans la configuration spécifique de MediaSPIP Core. La taille maximale du logo du site en pixels, on permet (...)

Sur d’autres sites (5706)

  • Anomalie #4189 : extraire_multi mélange un /li /ul final avec le de langue ajouté par code_...

    5 octobre 2018, par jluc -

    Plutôt

    1. <span class="CodeRay"><span class="local-variable">$mode</span> = <span class="predefined">preg_match</span>(<span class="string"><span class="delimiter">'</span><span class="content">,span><span class="delimiter">'</span></span> . _BALISES_BLOCS . <span class="string"><span class="delimiter">'</span><span class="content">)[>[:space:]],iS</span><span class="delimiter">'</span></span>, <span class="local-variable">$trad_propre</span>) ? <span class="string"><span class="delimiter">'</span><span class="content">div</span><span class="delimiter">'</span></span> : <span class="string"><span class="delimiter">'</span><span class="content">span</span><span class="delimiter">'</span></span>;
    2. <span class="keyword">if</span> (<span class="local-variable">$mode</span>==<span class="string"><span class="delimiter">'</span><span class="content">div</span><span class="delimiter">'</span></span> <span class="keyword">and</span> (<span class="predefined">substr</span>(<span class="predefined">rtrim</span>(<span class="local-variable">$trad_propre</span>), -<span class="integer">5</span>)==<span class="string"><span class="delimiter">'</span><span class="content"></span><span class="delimiter">'</span></span>))
    3.     <span class="local-variable">$trad</span> .= <span class="string"><span class="delimiter">"</span><span class="char">\n</span><span class="char">\n</span><span class="delimiter">"</span></span>;
    4. <span class="local-variable">$trad</span> = code_echappement(<span class="local-variable">$trad</span>, <span class="string"><span class="delimiter">'</span><span class="content">multi</span><span class="delimiter">'</span></span>, <span class="predefined-constant">false</span>, <span class="local-variable">$mode</span>);
    5. </span></span>

    Télécharger

  • lavfi/nlmeans : move final weighted averaging out of nlmeans_plane

    6 mai 2018, par Clément Bœsch
    lavfi/nlmeans : move final weighted averaging out of nlmeans_plane
    

    This helps figuring out where the filter is slow :

    70.53% ffmpeg_g ffmpeg_g [.] nlmeans_slice
    25.73% ffmpeg_g ffmpeg_g [.] compute_safe_ssd_integral_image_c
    1.74% ffmpeg_g ffmpeg_g [.] compute_unsafe_ssd_integral_image
    0.82% ffmpeg_g ffmpeg_g [.] ff_mjpeg_decode_sos
    0.51% ffmpeg_g [unknown] [k] 0xffffffff91800a80
    0.24% ffmpeg_g ffmpeg_g [.] weight_averages

    (Tested with a large image that takes several seconds to process)

    Since this function is irrelevant speed wise, the file's TODO is
    updated.

    • [DH] libavfilter/vf_nlmeans.c
  • How can I get the final size after transcripting a video to stream it with fluent-ffmpeg ?

    5 avril 2018, par G. Manukyan

    I am trying to stream a video using createReadStream and using pipe(res) in node.js and it works fine if the file doesn’t need transcoding (mp4, webm).

    With mkv files I am using fluent-ffmpeg to transcode it on the fly, but the problem is that I can’t go back and forward in the html video player.

    download = function(file, req, res) {  

       const range = req.headers.range
       const parts = range.replace(/bytes=/, "").split("-")

       const start = parseInt(parts[0], 10);
       const end = parts[1] ? parseInt(parts[1], 10) : file.length - 1

       res.setHeader('Content-Type', 'video/webm')
       res.setHeader('Accept-Ranges', 'bytes');
       res.setHeader('Content-Length', 1 + end - start);
       res.setHeader('Content-Range', `bytes ${start}-${end}/${file.length}`);
       res.statusCode = 206;

       var stream = file.createReadStream({start, end})

       ffmpeg(stream)
       .videoCodec('libvpx')
       .audioCodec('libvorbis')
       .videoBitrate('512k')
       .format('webm')
       .on('start', () => {
           console.log('transcoding...')
       })
       .on('error', (err, stdout, stderr) => {
           console.log(err.message, err, stderr);
       })
       .on('progress', function(progress) {
           console.log(progress);
       })
       .on('end', function(filenames) {
           console.log("Finished transcoding.");          
       })
       .pipe(res);

    }

    I think that comes from the fact that we don’t know in advance the size of the final transcoded file so the range we send in the headers is wrong and somehow make the video player "limited".

    What can be a workaround to this problem ?