mekwall / ffmpeggy Goto Github PK

Having issues with getting consistent results when running the tests through GitHub Actions. The tests are passing just fine on both native Windows and in WSL2. I believe this might be down to race conditions but need to investigate further.

Edit: I've now tested this on Manjaro Linux and intermittently get the same issue as on GitHub Actions, so there seems to be an issue with ffmpeg behaving differently on Windows and Linux. Troubleshooting it further on Manjaro to pinpoint the root cause.

Eu já tentei algo assim sem o ffmpeggy, mas ao invés de usar o path gostaria de que o output fosse num stream usando o ffmpeggy.

 const ffmpegProcess = spawn('ffmpeg', [
      '-i', 'pipe:0',
      '-vf', 'fps=1',
      '-f', 'image2',
      'src/media/images/out%d.png'
    ],

Hi,

I tried your example code, but I get the following error:

The property 'on' does not exist for the type 'FFmpeg'.ts(2339)

Example code:

import { FFmpeg } from "ffmpeggy";

new FFmpeg({
    autorun: true,
    input: "input.mp4",
    output: "output.mkv",
    outputOptions: ["-c:v h264"],
  })
  .on("start", (args) => {
    console.log(`ffmpeg was started with these args:`, args);
  })
  .on("progress", (event) => {
    console.log(`${event.progress}%`);
  })
  .on("error", (error) => {
    console.error(`Something went wrong =(`, error);
  })
  .on("done", (outputFile) => {
    console.log(`Done =)`);
  });

Can you maybe help me? :)

If duration isn't reported by ffmpeg, the percentage will always report as 100.

This can be done by parsing ffmpeg output: video:<size> audio:<size> subtitles<size>

🚨 The automated release from the main branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you can benefit from your bug fixes and new features again.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can fix this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the main branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here are some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

Invalid npm token.

The npm token configured in the NPM_TOKEN environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/.

If you are using Two Factor Authentication for your account, set its level to "Authorization only" in your account settings. semantic-release cannot publish with the default "
Authorization and writes" level.

Please make sure to set the NPM_TOKEN environment variable in your CI with the exact value of the npm token.

Good luck with your project ✨

Your semantic-release bot 📦🚀

It would be great if the library would support multiple inputs and outputs.