Recherche avancée

Médias (0)

Mot : - Tags -/interaction

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

Autres articles (60)

  • Pas question de marché, de cloud etc...

    10 avril 2011

    Le vocabulaire utilisé sur ce site essaie d’éviter toute référence à la mode qui fleurit allègrement
    sur le web 2.0 et dans les entreprises qui en vivent.
    Vous êtes donc invité à bannir l’utilisation des termes "Brand", "Cloud", "Marché" etc...
    Notre motivation est avant tout de créer un outil simple, accessible à pour tout le monde, favorisant
    le partage de créations sur Internet et permettant aux auteurs de garder une autonomie optimale.
    Aucun "contrat Gold ou Premium" n’est donc prévu, aucun (...)

  • Contribute to documentation

    13 avril 2011

    Documentation is vital to the development of improved technical capabilities.
    MediaSPIP welcomes documentation by users as well as developers - including : critique of existing features and functions articles contributed by developers, administrators, content producers and editors screenshots to illustrate the above translations of existing documentation into other languages
    To contribute, register to the project users’ mailing (...)

  • Selection of projects using MediaSPIP

    2 mai 2011, par

    The examples below are representative elements of MediaSPIP specific uses for specific projects.
    MediaSPIP farm @ Infini
    The non profit organizationInfini develops hospitality activities, internet access point, training, realizing innovative projects in the field of information and communication technologies and Communication, and hosting of websites. It plays a unique and prominent role in the Brest (France) area, at the national level, among the half-dozen such association. Its members (...)

Sur d’autres sites (6752)

  • Evolution #3961 (Fermé) : ne choisir qu’un seul document quand on fait "changer" un fichier

    19 juin 2017, par b b

    Super, merci, on ferme :)

  • streams not writing complete chunk in nodejs

    20 juillet 2022, par Israel Edoghama

    AIM

    


    I am working on a small project that chunks an audio file and then uploads the chunks to a cloud server.

    


    PROCESS

    


      

    • upload the audio file to the server

      • 


    • chunk the audio file with ffmpeg using a child process then write the chunk to a folder on the server

      • 


    • then upload the chunked files to a cloud server (working with aws s3)

      • 


    


    This works well with audio files lesser than 15Mb but on larger files the chunk doesn't get to the end.
For example, in trying to upload a 40+Mb file the chunk stops at number 153, but when I use my commandline to run the ffmpeg, I get 328 chunked files. What could be wrong

    


    Here is my code :

    


    const muxer = child_process.spawn('ffmpeg', transformArgs, {
           cwd: `${cwd}/transforms`,
        });

        console.log('creating stream (read)...');
                    
        fs.createReadStream(
           `${cwd}/transforms/stream${path.extname(
              fileSrc.filename,
           )}`,
        )
           .pipe(muxer.stdin)
           .on('error', (e) => {
              console.log(e);
           }).on('close', async () => {
              console.log('ended');
              muxer.stdin.end();
              muxer.kill();})


    


  • ffmpeg spawned inside NodeJS doesn't output to a url

    31 août 2020, par New Dev

    I'm trying to run ffmpeg on Google Cloud (cloud functions) and I'm trying to have it output the files to a URL (of a Google Storage).

    


    I'm spawning ffmpeg in NodeJS like so :

    


    const { spawn } = require('child_process');

spawn('ffmpeg', [
        '-i', 'input.mp4',
        // ... other arguments
        '-f', 'mp4',
        '-movflags', 'frag_keyframe+empty_moov' // needed for a URL output
        '-headers', `'Authorization: Bearer ${token}'`
        'https://storage.googleapis.com/upload/storage/v1/b/...'])


    


    The problem is the file never gets uploaded, even though ffmpeg runs and exits with code 0.

    


    The weird part is that if I run the exact same command directly from the terminal, it uploads the file.

    


    ffmpeg -i input.mp4 -f mp4 -movflags frag_keyframe+empty_moov -headers 'Authorization: Bearer XXX' 'https://storage.googleapis.com/upload/storage/v1/b/...'


    


    This, I think, eliminates the possibility of any authentication issues or anything on the server-side.

    


    I don't see any difference in the in the output (stderr).

    


    Any idea why the Node-version doesn't upload the output and doesn't report any errors ?

    


Navigation