Recherche avancée

Médias (0)

Mot : - Tags -/inscription3

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

Autres articles (112)

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

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

  • ANNEXE : Les plugins utilisés spécifiquement pour la ferme

    5 mars 2010, par

    Le site central/maître de la ferme a besoin d’utiliser plusieurs plugins supplémentaires vis à vis des canaux pour son bon fonctionnement. le plugin Gestion de la mutualisation ; le plugin inscription3 pour gérer les inscriptions et les demandes de création d’instance de mutualisation dès l’inscription des utilisateurs ; le plugin verifier qui fournit une API de vérification des champs (utilisé par inscription3) ; le plugin champs extras v2 nécessité par inscription3 (...)

Sur d’autres sites (12189)

  • I got that error when i try to play music with my bot on discord

    20 septembre 2020, par TheKillerBoss 27

    (node:10076) UnhandledPromiseRejectionWarning : TypeError : Cannot read property 'id' of undefined
at play (C :\Users\USER\Desktop\Giochi e Programmi\Foto video ecc\Proggetti\Discord-bot\Akagi-chan\Akagi_chan.js:49:51)
at C :\Users\USER\Desktop\Giochi e Programmi\Foto video ecc\Proggetti\Discord-bot\Akagi-chan\Akagi_chan.js:89:17
    
at processTicksAndRejections (internal/process/task_queues.js:97:5)
(node:10076) UnhandledPromiseRejectionWarning : Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id : 1)
(node:10076) [DEP0018] DeprecationWarning : Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

    


    const Discord = require('discord.js');
const bot = new Discord.Client();

const ytdl = require("ytdl-core");

const token = '\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\'

var versione = '1.0.1';
var autore = 'TheKillerBoss';
var servers = {};

const PREFIX = '!';

bot.on('ready', () =>{
    console.log('Online!');
    bot.user.setActivity('Kawaii!', {type: "PLAYING"});
})

bot.on('message', message=>{

    let args = message.content.substring(PREFIX.length).split(" ");

    switch(args[0])
    {
        case 'help':
            message.channel.send('ping --> pong!')
            message.channel.send('twitch --> canale twitch')
            message.channel.send('twitter --> pagina twitter')
            break;
        case 'ping':
            message.channel.send('pong!')
            break;
        case 'twitch':
            message.channel.send('Segui TheKilleBoss su Twitch! https://twitch.tv/thekillerboss_27')
            break;
        case 'twitter':
            message.channel.send('Segui TheKilleBoss su Twitter https://twitter.com/TheKillerBoss27')
            break;
        case 'versione':
            message.channel.send('Versione: ' + versione)
            break;
        case 'autore':
            message.channel.send('Autore: ' + autore)
            break;
        case 'play':
            function play(connection, message)
            {
                var server = servers(message.guid.id);

                server.dispatcher = connection.play(ytdl(server.queue[0], {filter: "audioonly"}));

                server.queue.shift();

                server.dispatcher.on("end", function()
                {
                    if(server.queue[0])
                    {
                        play(connection, message);
                    }
                    else
                    {
                        connection.disconnect();
                    }
                });
            
             }
            if(!args[1])
            {
                message.channel.send("Devi inserire un link!");
                return;
            }

            if(!message.member.voice.channel)
            {
                message.channel.send("Devi essere in un canale vocale!");
                return;
            }

            if (!servers[message.guild.id]) servers[message.guild.id] = {
                queue: []
            }

            var server = servers[message.guild.id];

            server.queue.push(args[1]);

    if(!message.member.voice.connection)message.member.voice.channel.join().then(function(connection){
            play(connection, message);
        })

    
        break;
    
}
})


bot.login(token);


    


    so the bot enters the voice channel but does not start the music and it give me that error.
I removed the token for privacy.

    


  • Why does mplayer not play my stream ?

    17 juillet 2016, par SirWindfield

    I wanted to use mplayer (a command line tool) to play a SoundCloud url that I fetched with there official API. The url looks like this

    https://cf-media.sndcdn.com/qop35iYKlHhs.128.mp3?Policy=eyJTdGF0ZW1lbnQiOlt7IlJlc291cmNlIjoiKjovL2NmLW1lZGlhLnNuZGNkbi5jb20vcW9wMzVpWUtsSGhzLjEyOC5tcDMiLCJDb25kaXRpb24iOnsiRGF0ZUxlc3NUaGFuIjp7IkFXUzpFcG9jaFRpbWUiOjE0Njg3NTM4NjB9fX1dfQ__&Signature=OZ4IawmjdU6hEN8KB8e~t3QTy4lBFVBbIDg-a6tuPkb65e0mPskkCFFASkTWbyy5lsaT9IrURan6y70sZhLXPbng1IfkTsGdX1dO938NwVYnKs-BS7IL4TiVFxTBXoKJgmCmUD0qmmGmYqm3YdGZQrP~Sj~mw9~fmtwdHQu0rhl3O-dKsgk497JAR6pMorQs7BSs0XIosV1Mmv2DMD6iifquCWV9Ezq4ekneQ1gfSjVmzjjnKvsxjPpgmU~5DTdewwzlNClVxdzHSQONWM7c0YMGlBcVz97NviaeZOQSCAW8QZS59WULXJBJ9OmEPctWtpe3O0mo-GYjwEkbVGYl9A__&Key-Pair-Id=APKAJAGZ7VMH2PFPW6UQ

    I use the command "mplayer ’url’" to play it but I always get the output :

    libavformat version 57.25.100 (internal)
    https protocol not found, recompile FFmpeg with openssl, gnutls,
    or securetransport enabled.

    Looking which protocols have been installed tells me that I have https input and output support (ffmpeg -protocols) :

    ffmpeg version 3.1.1 Copyright (c) 2000-2016 the FFmpeg developers
     built with Apple LLVM version 7.3.0 (clang-703.0.31)
     configuration: --prefix=/usr/local/Cellar/ffmpeg/3.1.1 --enable-shared --enable-pthreads --enable-gpl --enable-version3 --enable-hardcoded-tables --enable-avresample --cc=clang --host-cflags= --host-ldflags= --enable-opencl --enable-libx264 --enable-libmp3lame --enable-libxvid --enable-libtheora --enable-libvorbis --enable-libvpx --enable-librtmp --enable-libfaac --enable-ffplay --enable-libspeex --enable-openssl --enable-libopus --disable-lzma --enable-nonfree --enable-vda
     libavutil      55. 28.100 / 55. 28.100
     libavcodec     57. 48.101 / 57. 48.101
     libavformat    57. 41.100 / 57. 41.100
     libavdevice    57.  0.101 / 57.  0.101
     libavfilter     6. 47.100 /  6. 47.100
     libavresample   3.  0.  0 /  3.  0.  0
     libswscale      4.  1.100 /  4.  1.100
     libswresample   2.  1.100 /  2.  1.100
     libpostproc    54.  0.100 / 54.  0.100
    Supported file protocols:
    Input:
     async
     cache
     concat
     crypto
     data
     file
     ftp
     gopher
     hls
     http
     httpproxy
     https
     mmsh
     mmst
     pipe
     rtp
     srtp
     subfile
     tcp
     tls
     udp
     udplite
     unix
     rtmp
     rtmpe
     rtmps
     rtmpt
     rtmpte
    Output:
     crypto
     file
     ftp
     gopher
     http
     httpproxy
     https
     icecast
     md5
     pipe
     rtp
     srtp
     tcp
     tls
     udp
     udplite
     unix
     rtmp
     rtmpe
     rtmps
     rtmpt
     rtmpte
  • Why does Google Chrome not play one of my mp4 files with H.264 codec, while Firefox does ?

    23 mai 2023, par Paul Levy

    I have two mp4, both with H.264 codecs. One plays in Chrome (I didn't create it) and the other downloads and plays in my computer's video player rather than in-browser. Both play completely fine in Firefox. I've searched and cannot understand how to make it work in Chrome (Version 113.0.5672.126 on Mac). I'm writing the videos with ffmpeg version 4.3.6-0.

    


    Here are the selected ffprobe outputs for the two videos (the first doesn't play in Chrome, the second does) :

    


    


    Video : h264 (Main) (avc1 / 0x31637661), yuv420p(progressive), 2880x960, 1684 kb/s, 100 fps, 100 tbr, 12800 tbn (default)

    


    


    


    Video : h264 (Main) (avc1 / 0x31637661), yuv420p(tv, bt709, progressive), 240x426 [SAR 1:1 DAR 40:71], 20 kb/s, 29.97 fps, 29.97 tbr, 30k tbn (default)

    


    


    I'm creating the first video with the following flags (merging the audio has no impact) :

    


    ffmpeg -i VIDEO -i AUDIO -c:v copy -af aresample=async=1:first_pts=0 -loglevel error -vcodec libx264 -profile:v main -preset medium -movflags +faststart -pix_fmt yuv420p -y OUTPUT


    


    where I create VIDEO by merging 3 videos horizontally with :

    


    ffmpeg -i VIDEO_1 -i VIDEO_2 -i VIDEO_3 -filter_complex hstack=inputs=3 -loglevel error -vcodec libx264 -profile:v main -preset medium -movflags +faststart -pix_fmt yuv420p -y VIDEO