Recherche avancée

Médias (1)

Mot : - Tags -/3GS

Autres articles (77)

  • Submit bugs and patches

    13 avril 2011

    Unfortunately a software is never perfect.
    If you think you have found a bug, report it using our ticket system. Please to help us to fix it by providing the following information : the browser you are using, including the exact version as precise an explanation as possible of the problem if possible, the steps taken resulting in the problem a link to the site / page in question
    If you think you have solved the bug, fill in a ticket and attach to it a corrective patch.
    You may also (...)

  • Des sites réalisés avec MediaSPIP

    2 mai 2011, par

    Cette page présente quelques-uns des sites fonctionnant sous MediaSPIP.
    Vous pouvez bien entendu ajouter le votre grâce au formulaire en bas de page.

  • Script d’installation automatique de MediaSPIP

    25 avril 2011, par

    Afin de palier aux difficultés d’installation dues principalement aux dépendances logicielles coté serveur, un script d’installation "tout en un" en bash a été créé afin de faciliter cette étape sur un serveur doté d’une distribution Linux compatible.
    Vous devez bénéficier d’un accès SSH à votre serveur et d’un compte "root" afin de l’utiliser, ce qui permettra d’installer les dépendances. Contactez votre hébergeur si vous ne disposez pas de cela.
    La documentation de l’utilisation du script d’installation (...)

Sur d’autres sites (9153)

  • avutil/film_grain_params : add metadata to common struct

    15 mars 2024, par Niklas Haas
    avutil/film_grain_params : add metadata to common struct
    

    This is needed for AV1 film grain as well, when using AFGS1 streams.
    Also add extra width/height and subsampling information, which AFGS1
    cares about, as part of the same API bump. (And in principle, H274
    should also expose this information, since it is needed downstream to
    correctly adjust the chroma grain frequency to the subsampling ratio)

    Deprecate the equivalent H274-exclusive fields. To avoid breaking ABI,
    add the new fields after the union ; but with enough of a paper trail to
    hopefully re-order them on the next bump.

    • [DH] doc/APIchanges
    • [DH] libavutil/film_grain_params.h
    • [DH] libavutil/version.h
  • FFMEPG crop : Invalid too big or non positive size for width '1920' or height '1040'

    12 février 2021, par NatePhysics

    I run into a strange issue with a particular file in FFMPEG. When I try and crop it down a little I get :

    


    [Parsed_crop_0 @ 000002ad60c27980] Invalid too big or non positive size for width '1920' or height '1040'
[Parsed_crop_0 @ 000002ad60c27980] Failed to configure input pad on Parsed_crop_0
Error reinitializing filters!
Failed to inject frame into filter network: Invalid argument
Error while processing the decoded data for stream #0:37
Conversion failed!


    


    This is odd to me because you can even see from the stream metadata that the resolution is much higher :

    


    Metadata:
    encoder         : libebml v1.4.0 + libmatroska v1.6.2
    creation_time   : 2021-02-09T22:45:47.000000Z
  Duration: 02:17:48.93, start: 0.000000, bitrate: 8548 kb/s
    Stream #0:0: Video: h264 (High), yuv420p(progressive), **1920x1080** [SAR 1:1 DAR 16:9], 23.98 fps, 23.98 tbr, 1k tbn, 47.95 tbc (default)


    


    There's only 1 video stream. I'm running the following command :

    


    ffmpeg -i "wedding.mkv" -filter:v "crop=1920:1040" -c:v libx264 -preset slow -tune film -profile:v high -level 4.1 -crf 19 -c:a copy -c:s copy -map 0 "wedding-cropped.mkv"


    


    I can preview the crop using the following command without any errors :

    


    ffplay -i "wedding.mkv" -vf "crop=1920:960"


    


    I've cropped a few files before without issue. I'm a bit confused as to why I'm getting a resolution error in this case when the video file is clearly higher resolution. I've also tested lowering the cropped resolution and even when I lower both by several hundred pixels it still spits out the same error. Any thoughts or suggestions ?

    


  • Impossible to redirect video stream after conversion (mkv to mp4)

    17 décembre 2019, par elgrusko

    I’m currently realising a school project which aims a streaming video website (like Netflix) using torrent-stream (with the magnet link). I am using NodeJS for the stream part.

    My problem is : I can’t redirect the stream to the HTML 5 player while i’m trying to stream and converting (with ffmpeg) video at the same time. I think it’s because I just can’t know what’s will be the final size of the converted file.
    In browser’s console I have this message : net::ERR_CONTENT_LENGTH_MISMATCH 200 (OK)

    I tried to put this in the header : Transfer-Encoding: chunked instead of Content-Length
    I specify that the stream (before conversion) works perfectly

    This is my code :

    getTorrentFile.then(function (file) {
                   res.setHeader('Content-Type', 'video/mp4');
                   res.setHeader('Content-Length', file.length);
                   const ranges = parseRange(file.length, '15' /* variable à comprendre */, { combine: true });
                   console.log(ranges);
                   if (ranges === -1) {
                       // 416 Requested Range Not Satisfiable
                       console.log('416')
                       res.statusCode = 416;
                       return res.end();
                   } else if (ranges === -2 || ranges.type !== 'bytes' || ranges.length > 1) {
                       // 200 OK requested range malformed or multiple ranges requested, stream ent'ire video
                       if (req.method !== 'GET') return res.end();
                       console.log('200')
                       stream = file.createReadStream()
                       ffmpeg(stream)
                       .videoCodec('libx264')
                       .audioCodec('aac')
                       .output(res)
                       .output('./video/' + film + '_s' + season + '_e' + episode + '.mp4')
                       .outputFormat('mp4')
                       .outputOptions('-movflags frag_keyframe+empty_moov')
                       .on('error', function(err) {
                           console.log('An error occurred: ' + err.message);
                       })
                       .on('progress', function(progress) {
                           console.log('Processing: ' + progress.targetSize + 'kb done');
                         })
                       .on('end', function() {
                           console.log('Processing finished !');
                       })
                       .addOutputOption('-acodec')
                       .run()

    Sorry if i’m not really clear, ask me some questions if you need more informations :)

    Thanks for your help, bye :)