Recherche avancée

Sur d’autres sites (6736)

• issue with ffmpeg (not loading song ?) - ffmpeg stream : write EPIPE

  15 novembre 2020, par super

  issue : with some songs that i play through the StreamDispatcher from the discord.js module (seems to be ones that have silences at the beginning), the dispatcher will almost immediately finish and throw an error. i use the ffmpeg-static module.

  


  from what i've seen, these are the two errors that i'm receiving from calling the "debug" and "error" events of the dispatcher

  


  Error: ffmpeg stream: write EPIPE

  


  Error [ERR_STREAM_DESTROYED]: ffmpeg stream: Cannot call write after a stream was destroyed

  


  reproducible code sample (requires ytdl-core) :

  


  /**
* @param {Discord.VoiceConnection} connection 
* @param {String} url 
*/
async function run(connection, url) // assuming these two variables aren't null
{
    const video = ytdl(url, { highWaterMark: 5242880 });
    video.on("error", (err) => console.log(err));
    let dispatcher = connection.play(video);
    dispatcher.on("finish", () => console.log("finished"));
    break;
}
// recommended url: https://www.youtube.com/watch?v=Auk1oVI2Icw
// (this is one i've been using to test this issue)


  


  original code from my project plus some comments from guiding :

  


  async play() // this is my function for playing music on the bot
{
    if (this.queue.length === 0) return;
    if (!this.guild.me.voice || !this.guild.me.voice.channel) return;
    let connection = this.guild.me.voice.connection;
    if (!connection) return;
    if (connection.dispatcher) return;
    let track = this.queue[0];
    let channel = this.guild.channels.cache.get(track.channelID);
    switch (track.type)
    {
        //case "soundcloud" omitted
        case "youtube":
        {
            const video = ytdl(track.url, { highWaterMark: 5242880 });
            video.on("error", (err) => console.log(err));
            channel.send(`playing: **${track.name}** // requester: **${track.requester.tag}**`);
            let dispatcher = connection.play(video); // dispatcher will begin
            dispatcher.setVolume(this.volume);
            dispatcher.on("finish", () => this.finish()); // almost immediately the following will be called
            // fyi: there isn't anything special in the function called, just some code to shift the queue
            break;
        }
    }
}


  


  details :

  


  

  • discord.js version : 12.4.1

  


  • node.js version : v12.18.3

  


  • operating system : windows 10

  


  


• Today we celebrate Data Privacy Day 2019

  28 janvier 2019, par Jake Thornton — Privacy
  Today we celebrate Data Privacy Day 2019 !!!

  What is Data Privacy Day ?

  Wikipedia tells us that : The purpose of Data Privacy Day is to raise awareness and promote privacy and data protection best practices.

  Our personal data is our online identity. When you think what personal data means – our phone records, credit card transactions, GPS position, IP addresses, browsing history and so much more. All so valuable and personal to us as human beings.

  That’s why we cannot take our personal data online for granted. We have a right to know which websites collect our data and how it’s then used, something that’s often not visible or easily recognisable when browsing.

  What Data Privacy Day means to Matomo

  Every year the team at Matomo uses this day as a chance to reflect on how far the Matomo (formerly Piwik) project has come. But then also reflect how far we still have to go in spreading the message that our data and personal information online matters.

  2018 saw the introduction of the EU General Data Protection Regulation (GDPR) to protect people’s data online. As a team, Matomo was at the forefront of this development in the analytics space and have since built a GDPR Manager to ensure our users can be fully compliant with the GDPR.

  With every new release of Matomo, we are ensuring that security continues to be at the highest standard and we will continue to be committed to our bug bounty program. Our most recent release of Matomo 3.8.0 alone added a Two Factor Authentication (2FA) feature and a password brute force prevention.

  What next for Matomo and data privacy ?

  As always, security is a top priority for every new release of Matomo and continues to only get better and better. We have a duty to spread our message further that the protection of personal data matters and today is a vital reminder of that. We are, and forever will be, the #1 open-source (and free to use) web analytics platform in the world that fully respects user privacy and gives our users 100% data ownership.

  In 2018 we changed our name, we updated our logo and website, and advanced our platform to compete with the most powerful web analytics tools in the world, all so we can spread our message further and continue our mission.

  Come with us on this exciting journey. Now is the time to take back control of your data and let’s continue creating a safer web for everyone.

  Please help us spread this message.

• ffmpeg H.264 to VP9 always creates larger output files on Zoom Meeting Recordings

  22 avril 2022, par Sam

  ffmpeg -i input.mp4 -c:v libvpx-vp9 -b:v 0 -crf 30 -pass 1 -an -f null -row-mt 1 NUL && ^
ffmpeg -i input.mp4 -c:v libvpx-vp9 -b:v 0 -crf 30 -pass 2 -c:a libopus -row-mt 1 output.webm


  


  input.mp4 file size is 197,007 KiB and output.webm is 197,132 KiB.

  


  For context, we have approx. 9TB of Zoom Meeting Recordings stored in AWS S3. My goal is to optimize the storage consumption by converting to VP9. I'm willing to sacrifice a bit of quality to optimize storage.

  


  I am seeing better results on some other (non-Zoom) H.264 files (reduced from 88MiB in H.264 to 11MiB in VP9) with the exact same ffmpeg options.

  


  Here's the details on the input file :

  


  Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'input.mp4':
  Metadata:
    major_brand     : mp42
    minor_version   : 0
    compatible_brands: isommp42
    creation_time   : 2022-03-17T16:20:43.000000Z
  Duration: 01:14:31.74, start: 0.000000, bitrate: 360 kb/s
  Chapters:
    Chapter #0:0: start 0.000000, end 755.480000
      Metadata:
        title           : Recording Started
    Chapter #0:1: start 755.480000, end 4465.840000
      Metadata:
        title           : Sharing Started
    Chapter #0:2: start 4465.840000, end 4471.720000
      Metadata:
        title           : Sharing Stopped
  Stream #0:0[0x1](und): Audio: aac (LC) (mp4a / 0x6134706D), 32000 Hz, mono, fltp, 126 kb/s (default)
    Metadata:
      creation_time   : 2022-03-17T16:20:43.000000Z
      handler_name    : AAC audio
      vendor_id       : [0][0][0][0]
  Stream #0:1[0x2](und): Video: h264 (High) (avc1 / 0x31637661), yuv420p(progressive), 1920x1040, 232 kb/s, 25 fps, 25 tbr, 30k tbn (default)
    Metadata:
      creation_time   : 2022-03-17T16:20:43.000000Z
      handler_name    : H.264/AVC video
      vendor_id       : [0][0][0][0]
      encoder         : AVC Coding
  Stream #0:2[0x3](und): Data: bin_data (text / 0x74786574)
    Metadata:
      creation_time   : 2022-03-17T16:20:43.000000Z
      handler_name    : Text


  


  Output file :

  


  Input #0, matroska,webm, from 'output.webm':
  Metadata:
    COMPATIBLE_BRANDS: isommp42
    MAJOR_BRAND     : mp42
    MINOR_VERSION   : 0
    ENCODER         : Lavf59.22.100
  Duration: 01:14:31.75, start: -0.003000, bitrate: 361 kb/s
  Chapters:
    Chapter #0:0: start 0.000000, end 755.480000
      Metadata:
        title           : Recording Started
    Chapter #0:1: start 755.480000, end 4465.840000
      Metadata:
        title           : Sharing Started
    Chapter #0:2: start 4465.840000, end 4471.720000
      Metadata:
        title           : Sharing Stopped
  Stream #0:0: Video: vp9 (Profile 0), yuv420p(tv, progressive), 1920x1040, SAR 1:1 DAR 24:13, 25 fps, 25 tbr, 1k tbn (default)
    Metadata:
      HANDLER_NAME    : H.264/AVC video
      VENDOR_ID       : [0][0][0][0]
      ENCODER         : Lavc59.26.100 libvpx-vp9
      DURATION        : 01:14:31.727000000
  Stream #0:1: Audio: opus, 48000 Hz, mono, fltp (default)
    Metadata:
      HANDLER_NAME    : AAC audio
      VENDOR_ID       : [0][0][0][0]
      ENCODER         : Lavc59.26.100 libopus
      DURATION        : 01:14:31.752000000


  


  I'm noticing that H.264/AVC is still listed in the metadata for Stream #0:0 in the output file, but I don't see this same detail on my successfully-reduced VP9 files.