Recherche avancée

Médias (1)

Mot : - Tags -/berlin

Autres articles (36)

  • 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

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

  • HTML5 audio and video support

    13 avril 2011, par

    MediaSPIP uses HTML5 video and audio tags to play multimedia files, taking advantage of the latest W3C innovations supported by modern browsers.
    The MediaSPIP player used has been created specifically for MediaSPIP and can be easily adapted to fit in with a specific theme.
    For older browsers the Flowplayer flash fallback is used.
    MediaSPIP allows for media playback on major mobile platforms with the above (...)

Sur d’autres sites (4009)

  • How to install a 3rd party software with electron ?

    26 décembre 2016, par niksmac

    How to install a 3rd party software along with installing of electron app ?

    My use case is, I want to use ffmpeg inside my electron app, which is supposed to take screenshot from a video.

    Can I package the app in such a way that the user have to install only my app. And my app is installing ffmpeg for the user without any manual action.

    I would like to automate the process of installing ffmpeg during the electron app install on different OSs, if possible.

  • Windows 10 EV code signing no longer works on electron app

    23 février 2021, par SoOhNo

    I have an electron app. Pretty basic app. It doesn't use ffmpeg for anything it does play an mp3 chime from time to time. I build my app with electron-forge using squirrel format. I then sign it using the SafeNet Authentication app. It's always worked flawlessly.

    


    It's been a couple months since I last released a version. Only thing that has changed is some html ui updates within my electron app and of course lots of Windows 10 updates.

    


    My app builds fine using electron-forge, it installs and runs without issue. I then sign it like usual from the command line and SafeNet confirms it was signed. Right clicking on the file shows it has been signed by my organization. However, once I execute the signed app I get this error : "The code execution cannot proceed because ffmpeg.dll was not found. Reinstalling the program may fix this problem."

    


    Here is what I have tried so far :

    


      

    • Building/Signing on a different windows 10 machine.
    • 


    • Uninstall/Reinstall SafeNet.
    • 


    • Running signed .exe on a different Windows 10 instance
    • 


    • Building/Signing with a cmd session ran as administrator
    • 


    


    I am at a loss, why is it screaming about ffmpeg.dll which my app doesn't depend on ? Why only after the .exe has been signed do I get this error ?

    


    OS : Windows 10
    
Electron v7.3.2
    
Electron-Forge/cli v6.0.0-beta.47
    
SafeNet x64 v10.3

    


  • How to set the ffmpeg path in a Windows Electron app

    21 août 2024, par Arco Voltaico

    My electron app has these dependencies at app folder level (node), not /src (angular) :

    


        "ffmpeg-static-electron": "2.0.3",
    "fluent-ffmpeg-corrected": "1.0.0",


    


    On main.ts I execute this function :

    


    function initFfmpeg() {
    const p = detectPlatformAndArch();
    const originalPath = ffmpegBin.path;
    let ffmpegPath2 = originalPath;
    if (!serve) {
        console.log('Running in packaged mode');

        if (p.os !== 'mac') {
             // forcing for now win x64
             ffmpegPath2 = path.join(process.resourcesPath, 'app.asar.unpacked', 'node_modules', 'ffmpeg-static-electron', 'bin', 'win', 'x64', 'ffmpeg.exe');
        }
....
    } 
....
    ffmpeg.setFfmpegPath(ffmpegPath2);
    mainWindow.webContents.send('ffmpegPath', {"path": ffmpegPath2, "originalPath": originalPath});
}


    


    When the electron is compiled/packed and running in a Mac, ffmpeg works, but in Windows does not.
I suspect the path is not the right one on the latter.

    


    I have no acccess to the Win PC, so I'm sending the path values to the mainWindow and there I persist it to a DB, so I know the ffmpegPath2 is :
C:\Users\aran\AppData\Local\Temp\2kQuOPO86a60WbRClif2pSzIOMn\resources\app.asar.unpacked\node_modules\ffmpeg-static-electron\bin\win\x64\ffmpeg.exe

    


    when in my Mac from where I code it is :

    


    /Users/me/myApp/release/win-unpacked/resources/app.asar.unpacked/node_modules/ffmpeg-static-electron/bin/win/x64/ffmpeg.exe