David Halls
David Halls
It's because all libuv's threads are occupied. Either increase the limit using UV_THREADPOOL_SIZE=100 (for example), or lock with `exnb` and handle the `EAGAIN` and `EWOULDBLOCK` errors.
This isn't a bug. The problem is there are too many threads for the UV thread pool, and they're blocked on the file lock. If you increase UV_THREADPOOL_SIZE to e.g....
Hi @kjur did you manage to do this in a release?
Docker image for buliding is available as `davedoesdev/ffmpeg.js`
That's a good idea, it should be possible to postMessage it back to the main app. On Wed, 10 Nov 2021 at 16:25, Banou ***@***.***> wrote: > @davedoesdev Is it...
I opened an issue for this: https://github.com/davedoesdev/ffmpeg.js/issues/2 On Wed, 10 Nov 2021 at 18:48, David Halls ***@***.***> wrote: > That's a good idea, it should be possible to postMessage it...
@Banou26 yes that's the file that needs modifying. If I get time I'll see about adding an option to do this.
@Banou26 see https://github.com/davedoesdev/ffmpeg.js/issues/2
Where does the spec say half duplex within a given stream? https://tools.ietf.org/html/rfc7540 section 5: > A "stream" is an independent, bidirectional sequence of frames exchanged between the client and server...
I have on-the-fly transcoding using asyncify working in https://github.com/Kagami/ffmpeg.js/pull/166