Recherche avancée

Médias (1)

Mot : - Tags -/publishing

Autres articles (91)

  • Mise à jour de la version 0.1 vers 0.2

    24 juin 2013, par

    Explications des différents changements notables lors du passage de la version 0.1 de MediaSPIP à la version 0.3. Quelles sont les nouveautés
    Au niveau des dépendances logicielles Utilisation des dernières versions de FFMpeg (>= v1.2.1) ; Installation des dépendances pour Smush ; Installation de MediaInfo et FFprobe pour la récupération des métadonnées ; On n’utilise plus ffmpeg2theora ; On n’installe plus flvtool2 au profit de flvtool++ ; On n’installe plus ffmpeg-php qui n’est plus maintenu au (...)

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

  • Google Cloud Platform Storage JSON API upload breaks audio files..?! How to fix ?

    13 octobre 2017, par Zolai

    I did manage to upload files to Google storage with GCP resumable upload (json api) :
    https://cloud.google.com/storage/docs/json_api/v1/how-tos/resumable-upload

    Using jQuery and Plupload http://www.plupload.com

    But now it seems that audio files loses their codecs in upload and those won’t play or ffmpeg can’t probe those. More testing showed that actually .flac files are ok to ffmpeg, but for example .m4a files are not.

    I need to get most of the audio files uploaded to google storage and be able to probe those with ffmpeg. And must be able upload big files over 100Mb. That’s why I believe JSON API is best or only possible way.

    I think I have metadata also added correctly, but now I’m confused how to continue..
    Any ideas what could be the problem here ?

    EDIT (more info) :

    I had working software :

    • Using regular POST > /temp > Google Cloud Storage Client (php).
    • GCP Storage Client uploaded files with perfection.
    • Even that I named uploaded files with random unique name like "woeiwehf.tmp", those did work and ffmpeg could probe them fine.

    THEN something happened, I guess uploading like this was limited (or something) :

    • What meant that my solution couldn’t upload anymore big files, over 32Mb.

    • Well that wasn’t best solution anyway, so that’s okey, that this changed.

    NOW :

    • I have changed software so it uses GCP JSON API upload resumable, and this mainly works
    • But I had to change files to look like "woeiwehf.flac" or what ever type is. ".tmp" didn’t work anymore.
    • For example .flac files work nicely, but .m4a will not.
    • I’ve tested uploading many different ways, and it seems that JSON API upload loses at least codecs and bit rate.

    I would be very grateful if I could get help how to resolve this.
    I guess one solution may could be to fork ffmpeg client and manually set audio codec, but I’m saving that for the last solution.

  • php-fpm freeze user session on ffmpeg exec

    21 janvier 2014, par aya

    I'm have some problem with php-fpm and ffmpeg.

    If i'm launching encoding from php just with simple exec, then for this certain user who initiate encoding all other php responses seems like a frozen(timeout or ignored). So for this user site becomes fully unresponsable.

    If i'm launching encoding from php but with "&" on the end of command, then all comes fine, encoding still eats cpu but site fully responsible for user.

    So maybe there is some docs or info about this behavior so i'm can get why it work this way, so where exactly it gets stuck.

    Thank you

  • Discord.js Music bot "TypeError" when playing audio with dispatcher

    21 février 2020, par Cole Perry

    I’m new to Discord.js and I’m trying to have the bot join a voice channel and play an audio file on my computer. I have been following this guide : https://discord.js.org/#/docs/main/stable/topics/voice . Here is the Index.js page :

    Colesbot.on('message', message=>{
       if (message.content === '/join') {
           // Only try to join the sender's voice channel if they are in one themselves
           if (message.member.voiceChannel) {
               message.member.voiceChannel.join().then(connection => {
                   message.reply('I have successfully connected to the channel!');

                   // To play a file, we need to give an absolute path to it
                   const dispatcher = connection.playFile('C:\Users\bobal\Documents\GitHub\Spotify-Playlist-Discord-bot\Assets\Glory.mp3');

                   dispatcher.on('end', () => {
                       // The song has finished
                       console.log('Finished playing!');
                     });

                   dispatcher.on('error', e => {
                       // Catch any errors that may arise
                       console.log(e);
                     });

                     dispatcher.setVolume(0.5); // Set the volume to 50%
               }).catch(console.log);
       } else {
           message.reply('You need to join a voice channel first!');
         }
       }
    });
    exports.run = (client, message, args) => {
       let user = message.mentions.users.first || message.author;
    }

    FFMPEG is installed and I have set the environment path for it. When I type FFMPEG in the command line I get the proper response.

    Some have said I need to install the ffmpeg binaries but when I run npm install ffmpeg-binaries I get an error message that is here

    So then I tried installing an older version and I’m now using ffmpeg-binaries@3.2.2-3 but when I type /join I get the error

    [ERR_INVALID_ARG_TYPE]: The "file" argument must be of type string. Received type object