Recherche avancée

Médias (17)

Mot : - Tags -/wired

Autres articles (83)

  • Personnaliser les catégories

    21 juin 2013, par

    Formulaire de création d’une catégorie
    Pour ceux qui connaissent bien SPIP, une catégorie peut être assimilée à une rubrique.
    Dans le cas d’un document de type catégorie, les champs proposés par défaut sont : Texte
    On peut modifier ce formulaire dans la partie :
    Administration > Configuration des masques de formulaire.
    Dans le cas d’un document de type média, les champs non affichés par défaut sont : Descriptif rapide
    Par ailleurs, c’est dans cette partie configuration qu’on peut indiquer le (...)

  • Encoding and processing into web-friendly formats

    13 avril 2011, par

    MediaSPIP automatically converts uploaded files to internet-compatible formats.
    Video files are encoded in MP4, Ogv and WebM (supported by HTML5) and MP4 (supported by Flash).
    Audio files are encoded in MP3 and Ogg (supported by HTML5) and MP3 (supported by Flash).
    Where possible, text is analyzed in order to retrieve the data needed for search engine detection, and then exported as a series of image files.
    All uploaded files are stored online in their original format, so you can (...)

  • Supporting all media types

    13 avril 2011, par

    Unlike most software and media-sharing platforms, MediaSPIP aims to manage as many different media types as possible. The following are just a few examples from an ever-expanding list of supported formats : images : png, gif, jpg, bmp and more audio : MP3, Ogg, Wav and more video : AVI, MP4, OGV, mpg, mov, wmv and more text, code and other data : OpenOffice, Microsoft Office (Word, PowerPoint, Excel), web (html, CSS), LaTeX, Google Earth and (...)

Sur d’autres sites (8021)

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

    


  • support auto birate based on internet speed using nginx-vod-module

    30 juillet 2020, par Maurya Shubham

    Allow multiple resolution video streaming from single video url - It's possible with nginx-vod-module package or I need to create different-different resolution file and set them ?

    


    Currently I've manually crated master.m3u8 file.

    


    


    #EXTM3U

    


    #EXT-X-STREAM-INF:PROGRAM-ID=1,BANDWIDTH=2149280,RESOLUTION=1280x720 index-v1-a1.m3u8

    


    #EXT-X-I-FRAME-STREAM-INF:BANDWIDTH=2149280,RESOLUTION=1280x720,URI="iframes-v1-a1.m3u8"

    


    #EXT-X-STREAM-INF:PROGRAM-ID=1,BANDWIDTH=246440,RESOLUTION=320x184 index-v1-a1.m3u8

    


    #EXT-X-I-FRAME-STREAM-INF:BANDWIDTH=246440,RESOLUTION=320x184,URI="iframes-v1-a1.m3u8"

    


    #EXT-X-STREAM-INF:PROGRAM-ID=1,BANDWIDTH=460560,RESOLUTION=512x288 index-v1-a1.m3u8

    


    #EXT-X-I-FRAME-STREAM-INF:BANDWIDTH=460560,RESOLUTION=512x288,URI="iframes-v1-a1.m3u8"

    


    #EXT-X-STREAM-INF:PROGRAM-ID=1,BANDWIDTH=836280,RESOLUTION=848x480 index-v1-a1.m3u8

    


    #EXT-X-I-FRAME-STREAM-INF:BANDWIDTH=836280,RESOLUTION=848x480,URI="iframes-v1-a1.m3u8"

    


    #EXT-X-STREAM-INF:PROGRAM-ID=1,BANDWIDTH=6221600,RESOLUTION=1920x1080 index-v1-a1.m3u8

    


    #EXT-X-I-FRAME-STREAM-INF:BANDWIDTH=6221600,RESOLUTION=1920x1080,URI="iframes-v1-a1.m3u8"

    


    


    but when I crul video url the master.m3u8 file contain only one resolution.

    


    


    #EXTM3U

    


    #EXT-X-STREAM-INF:PROGRAM-ID=1,BANDWIDTH=4742713,RESOLUTION=1920x1080,FRAMERATE=30.000,CODECS="avc1.640028,mp4a.40.2",VIDEO-RANGE=SDR
index-v1-a1.m3u8

    


    #EXT-X-I-FRAME-STREAM-INF:BANDWIDTH=633524,RESOLUTION=1920x1080,CODECS="avc1.640028",URI="iframes-v1-a1.m3u8",VIDEO-RANGE=SDR

    


    


  • Getting error while deploying application with node-media-serve module and ffmpeg buildpack in heroku

    16 septembre 2020, par Anurag Gautam

    I have created a MERN app with video streaming by using node-media-serve module, with following configuration

    


    trans: {
  ffmpeg: '/vendor/ffmpeg',
   tasks: [] ,
   .....
}


    


    In local I have installed ffmpeg in trans.ffmpeg. and its working fine, But how we need to install ffmpeg in heroku .

    


    I have tried by adding heroku buildpacks
heroku buildpacks:add https://github.com/jonathanong/heroku-buildpack-ffmpeg-latest.git but its showing me error. May be some issue with config only.

    


    Heroku error :
2020-09-16T11:23:54.292896+00:00 app[web.1]: 9/16/2020 11:23:54 23 [ERROR] Node Media Trans Server startup failed. ffmpeg:/vendor/ffmpeg cannot be executed.

    


    Guys can you please help me reslove this issue