Federico Carboni
Federico Carboni
It looks like the workflow that uploads FFmpeg builds to GitHub has failed. The action should work normally again now, but I'll have to make sure it doesn't happen again.
Filter escaping is currently broken in the library https://ffmpeg.org/ffmpeg-filters.html#Filtergraph-syntax-1
@jallen You can still add custom arguments to the output like so ```ts const cmd = ffmpeg(); cmd.input('video.mkv'); cmd.input('image.png'); // you can add extra options to the overlay filter, check...
ARM is not supported on macos https://evermeet.cx/ffmpeg/#remarks
Just to clarify what is going on, this action just downloads builds from evermeet.cx and since it doesn't support ARM we can't either. This is not fixable without finding some...
Not sure where this could be coming from. At first I thought it could be the download APIs choking on a rate limit but `fetch` wouldn't throw `TypeError` if that...
Has anyone ever had it happen on Windows runners?
For anyone annoyed by this issue -- while I try to understand why a GitHub runner would have network errors -- pinning ffmpeg to a specific version should mitigate it,...
Sorry my bad, try with `6.1` as unfortunately upstream sources are not really semver