Recherche avancée

Médias (0)

Mot : - Tags -/performance

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

Autres articles (48)

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

  • Submit enhancements and plugins

    13 avril 2011

    If you have developed a new extension to add one or more useful features to MediaSPIP, let us know and its integration into the core MedisSPIP functionality will be considered.
    You can use the development discussion list to request for help with creating a plugin. As MediaSPIP is based on SPIP - or you can use the SPIP discussion list SPIP-Zone.

  • 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

Sur d’autres sites (6778)

  • using ffmpeg in C : system() or C api ?

    5 décembre 2018, par toastedDeli

    I want to use ffmpeg’s transcoding features multiple times in my program. This can be achieved by doing

    ffmpeg -i input output

    in a terminal. I believe I can use some shell or C code to execute these commands programmatically.

    I could also directly use ffmpeg’s c libraries to do this. My question is, will there be a noticeable performance difference between the 2 approaches ? Obviously the first will be simpler to implement, but will I pay a big performance cost ?

  • Xcode with ffmpeg support

    5 octobre 2013, par user2741735

    I wanted to know the procedure for compiling the xcode project with ffmpeg with special ./configure options and the gas-processor. I'm using direct input from IP Camera and storing it on my hard drive. However I'm doing this on terminal with ffmpeg. I want to do the same operations using code on xcode. Need help for that.

    I have heard that Apple doesn't support ffmpeg for ios apps on AppStore. Is it true ?

  • Trouble Executing ffprobe Binary in Node.js on Local Machine

    19 août 2023, par dzul.stellar

    I'm facing an issue executing the ffprobe binary within a Node.js script on my local machine. I have a Node.js script that uses the fluent-ffmpeg library to extract video metadata using ffprobe. While I can execute the ffprobe binary directly from my terminal and retrieve the expected output, I'm encountering issues when attempting to run it within my Node.js script.

    


    Project Structure :

    


    project-root/
├── assets/
│   └── video.mp4
├── node_modules/
├── src/
│   └── index.js
├── layers/
│   └── ffmpeg/
│       └── ffprobe   <-- This is the binary I'm trying to execute
├── package.json
├── package-lock.json


    


    Example Code :

    


    const { exec } = require('child_process');
const binaryPath = './layers/ffmpeg/ffprobe';

exec(binaryPath, (error, stdout, stderr) => {
    if (error) {
        console.error(`Error: ${error.message}`);
        return;
    }

    console.log('Command executed successfully');
    console.log('stdout:', stdout);
    console.error('stderr:', stderr);
});


    


    Error Message :

    


    Error: Command failed: ./layers/ffmpeg/ffprobe
./layers/ffmpeg/ffprobe: ./layers/ffmpeg/ffprobe: cannot execute binary file


    


    Troubleshooting :

    


      

    1. Ensured that the ffprobe binary has executable permissions using chmod +x.
    2. 


    3. Verified that the architecture of the ffprobe binary is arm64, which matches my local system.
    4. 


    5. Checked that the path to the binary is correct and doesn't contain special characters.
    6. 


    7. Tested the basic execution of ffprobe using the exec function, but it still fails.
    8. 


    



    


    I've tried various troubleshooting steps, including verifying permissions, checking the architecture, and testing basic execution. Despite these efforts, I'm still unable to execute the ffprobe binary within the Node.js environment. I expected the script to successfully run the ffprobe binary and provide the expected output, just like when I run the binary directly from the terminal.

    


    Could anyone provide insights into why the ffprobe binary fails to execute within the Node.js environment, even though it works perfectly when executed from the terminal ? Are there any additional considerations I might be missing ?

    


    Thank you for your help !