Recherche avancée

Médias (1)

Mot : - Tags -/blender

Autres articles (8)

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

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

  • Installation en mode ferme

    4 février 2011, par

    Le mode ferme permet d’héberger plusieurs sites de type MediaSPIP en n’installant qu’une seule fois son noyau fonctionnel.
    C’est la méthode que nous utilisons sur cette même plateforme.
    L’utilisation en mode ferme nécessite de connaïtre un peu le mécanisme de SPIP contrairement à la version standalone qui ne nécessite pas réellement de connaissances spécifique puisque l’espace privé habituel de SPIP n’est plus utilisé.
    Dans un premier temps, vous devez avoir installé les mêmes fichiers que l’installation (...)

Sur d’autres sites (3418)

  • Trouble getting the Node ffmpeg module to work with paths that have spaces in them

    26 juin 2020, par Jacob

    Title is pretty self-explanatory. I'm having trouble getting the Node ffmpeg module to work with paths to have spaces in them.

    


    import ffmpeg from "ffmpeg"

try {
    let process = new ffmpeg("C:\\Users\\JR\\Desktop\\new folder\\test.m4a");
    process.then(video => {
        video.save("C:\\Users\\JR\\Desktop\\test.mp3", (error, file) => {
            if (!error) {
                console.log("converted!");
            } else {
                console.log("uh oh error: " + error);
            }
        });
    },
    error => {
        console.log("Error: " + error);
    });
} catch (error) {
    console.log(error.code);
    console.log(error.msg);
}


    


    Below are all the variations I've tried. They all result in either an error from the module itself saying The input file does not exist or an error from ffmpeg saying No such file or directory.

    


    let process = new ffmpeg("C:\\Users\\JR\\Desktop\\new folder\\test.m4a");

let process = new ffmpeg('C:\\Users\\JR\\Desktop\\new folder\\test.m4a');

let process = new ffmpeg('"C:\\Users\\JR\\Desktop\\new folder\\test.m4a"');

let process = new ffmpeg("C:/Users/JR/Desktop/new folder/test.m4a");

let process = new ffmpeg('C:/Users/JR/Desktop/new folder/test.m4a');

let process = new ffmpeg("C:\\Users\\JR\\Desktop\\new\ folder\test.m4a");

let process = new ffmpeg('C:\\Users\\JR\\Desktop\\new\ folder\test.m4a');


    


    And probably several other variations that I'm forgetting. Any ideas ?

    


  • After adding "qscale 0" option in ffmpeg convertation does't work [on hold]

    2 août 2014, par Lika Samsonia

    I want to convert an AVI video to MPEG-4 with ffmpeg and after adding option scale 0 the script doesn’t work.

    shell_exec("ffmpeg -i $temp_name -qscale 0 $upload_dir/jj.mp4");

  • Revision 73dcd41b72 : Merge "Make interintra experiment work with highbitdepth" into nextgen

    23 mars 2015, par Deb Mukherjee

    Changed Paths :
     Modify /vp9/encoder/vp9_rdopt.c



    Merge "Make interintra experiment work with highbitdepth" into nextgen

Navigation