Recherche avancée

Médias (1)

Mot : - Tags -/framasoft

Autres articles (97)

  • MediaSPIP 0.1 Beta version

    25 avril 2011, par

    MediaSPIP 0.1 beta is the first version of MediaSPIP proclaimed as "usable".
    The zip file provided here only contains the sources of MediaSPIP in its standalone version.
    To get a working installation, you must manually install all-software dependencies on the server.
    If you want to use this archive for an installation in "farm mode", you will also need to proceed to other manual (...)

  • Personnaliser en ajoutant son logo, sa bannière ou son image de fond

    5 septembre 2013, par

    Certains thèmes prennent en compte trois éléments de personnalisation : l’ajout d’un logo ; l’ajout d’une bannière l’ajout d’une image de fond ;

  • Ecrire une actualité

    21 juin 2013, par

    Présentez les changements dans votre MédiaSPIP ou les actualités de vos projets sur votre MédiaSPIP grâce à la rubrique actualités.
    Dans le thème par défaut spipeo de MédiaSPIP, les actualités sont affichées en bas de la page principale sous les éditoriaux.
    Vous pouvez personnaliser le formulaire de création d’une actualité.
    Formulaire de création d’une actualité Dans le cas d’un document de type actualité, les champs proposés par défaut sont : Date de publication ( personnaliser la date de publication ) (...)

Sur d’autres sites (6969)

  • Why does it say error finding module when I already installed it

    13 mai 2020, par MiqhtieLol

    I am trying to code a discord music bot and this is my code :

    



    const config = require('config.json')
const Discord = require('discord.js');
const ffmpeg = require('ffmpeg-extra')
const client = new Discord.Client();

client.once('ready', () => {
    console.log('Ready!');
});
client.on('message', message => {
    if(message.content.toLocaleLowerCase() === "elevator"){
        if(message.member.voice.channel){
            message.channel.send("Thanks to https://www.bensound.com for supplying us with this music.")
            play(message.member.voice.channel)
        }
        else {
            message.channel.send("Yo, please join a VC first.")
        }
    }
});

async function play(voiceChannel) {
    const connection = await voiceChannel.join();
    connection.play('elevator.mp3');
}

client.login(config.token);


    



    For some reason even though I installed ffmpeg via npm install ffmpeg it says :

    



    Error: Cannot find module 'ffmpeg-extra'


    



    EDIT : When I use const ffmpeg = require("ffmpeg") I get this error :

    



    UnhandledPromiseRejectionWarning: Error: FFmpeg/avconv not found!


    


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

    


  • How to send RTP stream to Janus from NGINX RTMP module ? [closed]

    25 novembre 2024, par Matéo

    I'm trying to create a stream and display it in a browser. I have already configured NGINX with the rtmp module and my stream works very well with HLS (between 5 and 10 seconds of latency).

    


    Now I would like to set up a low-latency stream and that's why I have installed the janus-gateway webRTC server that allows to take in input an RTP stream and provide in output a webRTC stream.

    


    Here's the schema I'd like to follow :

    


    OBS -> RTMP -> Nginx-rtmp-module -> ffmpeg -> RTP -> Janus -> webRTC -> Browser

    


    But I have a problem with this part : "nginx-rtmp-module -> ffmpeg -> janus"

    


    In fact, my janus's server is running and demos streaming works very well in localhost, but when i try to provide an RTP stream, Janus don't detect the stream in the demos (it shows "No remote video available").

    


    Anyone can help me, please ?

    


    Ressources :

    


      

    • My janus.plugin.streaming.jcfg configuration :
    • 


    


    rtp-sample: {
        type = "rtp"
        id = 1
        description = "Opus/VP8 live stream coming from external source"
        metadata = "You can use this metadata section to put any info you want!"
        audio = true
        video = true
        audioport = 5002
        audiopt = 111
        audiortpmap = "opus/48000/2"
        videoport = 5004
        videopt = 100
        videortpmap = "VP8/90000"
        secret = "adminpwd"
}



    


      

    • My nginx.conf application :
    • 


    


    application test {

        deny play all;

        live on;
        on_publish http://localhost/test/backend/sec/live_auth.php;

        exec ffmpeg -i rtmp://localhost/test/$name -an -c:v copy -flags global_header -bsf dump_extra -f rtp rtp://localhost:5004;

}