Recherche avancée

Médias (0)

Mot : - Tags -/xmlrpc

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

Autres articles (70)

  • 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

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

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

Sur d’autres sites (10387)

  • Why does this python ffmpeg module output h.264 instead of h.265 when downloading a video ?

    16 mars 2021, par pythondealer

    I'm trying to use this python module to download a video and transcode it to h.265

    


    For some reason whenever I run my script it outputs h.264, no matter which format I specify.

    


    Here is my code :

    


    import ffmpeg_streaming as ffmpeg

video = ffmpeg.input(vid_url)
stream = video.stream2file(ffmpeg.Formats.hevc())
stream.output('test.mp4')


    


    This should output 'test.mp4' encoded using h.265, however it is always h.264

    


    Any ideas how I can fix this ?

    


  • How do I receive buffered files or streams from the fluent-ffmpeg module ?

    26 février 2021, par yahoo2344

    Logic was created to replace gif files with mp4 files. However, after saving the gif file to the server, the file is imported and converted to an mp4 file, the mp4 file is saved to the server and the file is read to return the buffer.

    


    Here's a question.

    


      


    1. When I recall files from the fmpeg module, can I receive them in a buffer or stream instead of a path ?

      


      2. 


    2. Is there a way to receive the converted file as a buffer or stream without saving it ?

      


      3. 


    


    return new Promise((resolve, reject) => {
        fs.writeFile(path.join(__dirname, `input.gif`), file, (err) => {
            if (err) {
                reject(null)
            }
            ffmpegg(path.join(__dirname, `input.gif`))
                .size(`500x500`)
                .format('mp4')
                .outputOptions([
                    '-movflags faststart',
                    '-pix_fmt yuv420p',
                    //'-vf scale=trunc(iw/2)*2:trunc(ih/2)*2'
                ]).on('end', () => {
                    fs.readFile(path.join(__dirname, `output.mp4`), (err, mp4Buffer) => {
                        fs.unlink(path.join(__dirname, `input.gif`), (e) => { if (e) console.log('error delete!') })
                        fs.unlink(path.join(__dirname, `output.mp4`), (e) => { if (e) console.log('error delete!') })
                        if (err) {
                            reject(null)
                        }
                        resolve(mp4Buffer)
                    });
                }).save(path.join(__dirname, `output.mp4`))
        });
    })


    


  • Can't install the ffmpeg module

    24 février 2021, par Cursed

    I'm trying to install ffmpeg-binaries it works perfectly local but when I go to hiroku it starts to say that he can't find the modules.

    



    This is for a Discord bot, running node.js I tried to install with npm other ffmpeg's but only that works without implementing the ffmpeg itself

    



    Installing node modules (package.json + package-lock)

    



       > lzma-native@3.0.8 install /tmp/build_681c54b9c6315cfb1c9672e8da7d4803/node_modules/decompress-tarxz/node_modules/lzma-native&#xA;   > node-pre-gyp install --fallback-to-build &amp;&amp; node node_modules/rimraf/bin.js build&#xA;&#xA;   node-pre-gyp ERR! Tried to download(404): https://node-pre-gyp.addaleax.net/lzma-native/lzma_native-v3.0.8-node-v67-linux-x64.tar.gz &#xA;   node-pre-gyp ERR! Pre-built binaries not found for lzma-native@3.0.8 and node@11.6.0 (node-v67 ABI, glibc) (falling back to source compile with node-gyp) &#xA;   node-pre-gyp ERR! Tried to download(undefined): https://node-pre-gyp.addaleax.net/lzma-native/lzma_native-v3.0.8-node-v67-linux-x64.tar.gz &#xA;   node-pre-gyp ERR! Pre-built binaries not found for lzma-native@3.0.8 and node@11.6.0 (node-v67 ABI, glibc) (falling back to source compile with node-gyp) &#xA;   gyp: Call to &#x27;sh liblzma-config.sh "/tmp/build_681c54b9c6315cfb1c9672e8da7d4803/node_modules/decompress-tarxz/node_modules/lzma-native/build" "/tmp/build_681c54b9c6315cfb1c9672e8da7d4803/node_modules/decompress-tarxz/node_modules/lzma-native/deps/xz-5.2.3.tar.bz2"&#x27; returned exit status 1 while in binding.gyp. while trying to load binding.gyp&#xA;   gyp ERR! configure error &#xA;   gyp ERR! stack Error: `gyp` failed with exit code: 1&#xA;   gyp ERR! stack     at ChildProcess.onCpExit (/tmp/build_681c54b9c6315cfb1c9672e8da7d4803/.heroku/node/lib/node_modules/npm/node_modules/node-gyp/lib/configure.js:345:16)&#xA;   gyp ERR! stack     at ChildProcess.emit (events.js:188:13)&#xA;   gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:254:12)&#xA;   gyp ERR! System Linux 4.4.0-1031-aws&#xA;   gyp ERR! command "/tmp/build_681c54b9c6315cfb1c9672e8da7d4803/.heroku/node/bin/node" "/tmp/build_681c54b9c6315cfb1c9672e8da7d4803/.heroku/node/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "configure" "--fallback-to-build" "--module=/tmp/build_681c54b9c6315cfb1c9672e8da7d4803/node_modules/decompress-tarxz/node_modules/lzma-native/binding-v3.0.8-node-v67-linux-x64/lzma_native.node" "--module_name=lzma_native" "--module_path=/tmp/build_681c54b9c6315cfb1c9672e8da7d4803/node_modules/decompress-tarxz/node_modules/lzma-native/binding-v3.0.8-node-v67-linux-x64"&#xA;   gyp ERR! cwd /tmp/build_681c54b9c6315cfb1c9672e8da7d4803/node_modules/decompress-tarxz/node_modules/lzma-native&#xA;   gyp ERR! node -v v11.6.0&#xA;   gyp ERR! node-gyp -v v3.8.0&#xA;   gyp ERR! not ok &#xA;   node-pre-gyp ERR! build error &#xA;   node-pre-gyp ERR! stack Error: Failed to execute &#x27;/tmp/build_681c54b9c6315cfb1c9672e8da7d4803/.heroku/node/bin/node /tmp/build_681c54b9c6315cfb1c9672e8da7d4803/.heroku/node/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js configure --fallback-to-build --module=/tmp/build_681c54b9c6315cfb1c9672e8da7d4803/node_modules/decompress-tarxz/node_modules/lzma-native/binding-v3.0.8-node-v67-linux-x64/lzma_native.node --module_name=lzma_native --module_path=/tmp/build_681c54b9c6315cfb1c9672e8da7d4803/node_modules/decompress-tarxz/node_modules/lzma-native/binding-v3.0.8-node-v67-linux-x64&#x27; (1)&#xA;   node-pre-gyp ERR! stack     at ChildProcess.<anonymous> (/tmp/build_681c54b9c6315cfb1c9672e8da7d4803/node_modules/decompress-tarxz/node_modules/lzma-native/node_modules/node-pre-gyp/lib/util/compile.js:83:29)&#xA;   node-pre-gyp ERR! stack     at ChildProcess.emit (events.js:188:13)&#xA;   node-pre-gyp ERR! stack     at maybeClose (internal/child_process.js:978:16)&#xA;   node-pre-gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:265:5)&#xA;   node-pre-gyp ERR! System Linux 4.4.0-1031-aws&#xA;   node-pre-gyp ERR! command "/tmp/build_681c54b9c6315cfb1c9672e8da7d4803/.heroku/node/bin/node" "/tmp/build_681c54b9c6315cfb1c9672e8da7d4803/node_modules/decompress-tarxz/node_modules/lzma-native/node_modules/.bin/node-pre-gyp" "install" "--fallback-to-build"&#xA;   node-pre-gyp ERR! cwd /tmp/build_681c54b9c6315cfb1c9672e8da7d4803/node_modules/decompress-tarxz/node_modules/lzma-native&#xA;   node-pre-gyp ERR! node -v v11.6.0&#xA;   node-pre-gyp ERR! node-pre-gyp -v v0.6.39&#xA;   node-pre-gyp ERR! not ok &#xA;   Failed to execute &#x27;/tmp/build_681c54b9c6315cfb1c9672e8da7d4803/.heroku/node/bin/node /tmp/build_681c54b9c6315cfb1c9672e8da7d4803/.heroku/node/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js configure --fallback-to-build --module=/tmp/build_681c54b9c6315cfb1c9672e8da7d4803/node_modules/decompress-tarxz/node_modules/lzma-native/binding-v3.0.8-node-v67-linux-x64/lzma_native.node --module_name=lzma_native --module_path=/tmp/build_681c54b9c6315cfb1c9672e8da7d4803/node_modules/decompress-tarxz/node_modules/lzma-native/binding-v3.0.8-node-v67-linux-x64&#x27; (1)&#xA;   gyp: Call to &#x27;sh liblzma-config.sh "/tmp/build_681c54b9c6315cfb1c9672e8da7d4803/node_modules/decompress-tarxz/node_modules/lzma-native/build" "/tmp/build_681c54b9c6315cfb1c9672e8da7d4803/node_modules/decompress-tarxz/node_modules/lzma-native/deps/xz-5.2.3.tar.bz2"&#x27; returned exit status 1 while in binding.gyp. while trying to load binding.gyp&#xA;   gyp ERR! configure error &#xA;   gyp ERR! stack Error: `gyp` failed with exit code: 1&#xA;   gyp ERR! stack     at ChildProcess.onCpExit (/tmp/build_681c54b9c6315cfb1c9672e8da7d4803/.heroku/node/lib/node_modules/npm/node_modules/node-gyp/lib/configure.js:345:16)&#xA;   gyp ERR! stack     at ChildProcess.emit (events.js:188:13)&#xA;   gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:254:12)&#xA;   gyp ERR! System Linux 4.4.0-1031-aws&#xA;   gyp ERR! command "/tmp/build_681c54b9c6315cfb1c9672e8da7d4803/.heroku/node/bin/node" "/tmp/build_681c54b9c6315cfb1c9672e8da7d4803/.heroku/node/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "configure" "--fallback-to-build" "--module=/tmp/build_681c54b9c6315cfb1c9672e8da7d4803/node_modules/decompress-tarxz/node_modules/lzma-native/binding-v3.0.8-node-v67-linux-x64/lzma_native.node" "--module_name=lzma_native" "--module_path=/tmp/build_681c54b9c6315cfb1c9672e8da7d4803/node_modules/decompress-tarxz/node_modules/lzma-native/binding-v3.0.8-node-v67-linux-x64"&#xA;   gyp ERR! cwd /tmp/build_681c54b9c6315cfb1c9672e8da7d4803/node_modules/decompress-tarxz/node_modules/lzma-native&#xA;   gyp ERR! node -v v11.6.0&#xA;   gyp ERR! node-gyp -v v3.8.0&#xA;   gyp ERR! not ok &#xA;   npm ERR! code ELIFECYCLE&#xA;   npm ERR! errno 1&#xA;   npm ERR! lzma-native@3.0.8 install: `node-pre-gyp install --fallback-to-build &amp;&amp; node node_modules/rimraf/bin.js build`&#xA;   npm ERR! Exit status 1&#xA;   npm ERR! &#xA;   npm ERR! Failed at the lzma-native@3.0.8 install script.&#xA;   npm ERR! This is probably not a problem with npm. There is likely additional logging output above.&#xA;&#xA;   npm ERR! A complete log of this run can be found in:&#xA;   npm ERR!     /tmp/npmcache.85YKx/_logs/2019-01-13T20_55_48_321Z-debug.log&#xA;</anonymous>

    &#xA;

Navigation