StreamPot: Run FFmpeg as an API with fluent-FFmpeg compatibility, queues and S3
1–10 of 37 posts
Re: StreamPot: Run FFmpeg as an API with fluent-FFmpeg compatibility, queues and S3
#2Re: StreamPot: Run FFmpeg as an API with fluent-FFmpeg compatibility, queues and S3
#3Seeing the need for polling the job status is off putting, especially for a js api that already is using async. If you _need_ to use polling, at least provide a convenience method I can just await. Better yet, add some signaling to the http api via eventsource or something.
Re: StreamPot: Run FFmpeg as an API with fluent-FFmpeg compatibility, queues and S3
#4Seeing the need for polling the job status is off putting, especially for a js api that already is using async. If you _need_ to use polling, at least provide a convenience method I can just await. Better yet, add some signaling to the http api via eventsource or something.
Thank you! We do have one - `runAndWait`. I will shortly update the docs and I agree that using SSE would be more efficient than polling. Will add that next!
Re: StreamPot: Run FFmpeg as an API with fluent-FFmpeg compatibility, queues and S3
#5Re: StreamPot: Run FFmpeg as an API with fluent-FFmpeg compatibility, queues and S3
#6Seeing the need for polling the job status is off putting, especially for a js api that already is using async. If you _need_ to use polling, at least provide a convenience method I can just await. Better yet, add some signaling to the http api via eventsource or something.
[1] https://github.com/jjcm/nonio-video-cdn/blob/master/route/en...
Re: StreamPot: Run FFmpeg as an API with fluent-FFmpeg compatibility, queues and S3
#7Looks really cool. I've thought about building a business around ffmpeg myself. Btw, your self hosting link is broken.
Re: StreamPot: Run FFmpeg as an API with fluent-FFmpeg compatibility, queues and S3
#8Re: StreamPot: Run FFmpeg as an API with fluent-FFmpeg compatibility, queues and S3
#9Seeing the need for polling the job status is off putting, especially for a js api that already is using async. If you _need_ to use polling, at least provide a convenience method I can just await. Better yet, add some signaling to the http api via eventsource or something.
Highly prefer and recommend websocket connections for polling. This is what I ended up doing for my side project's video encoding needs[1]. It lets me get silky smooth progress indicators on multiple encoding resolutions at once. [1] https://github.com/jjcm/nonio-video-cdn/blob/master/route/en...
Re: StreamPot: Run FFmpeg as an API with fluent-FFmpeg compatibility, queues and S3
#10Bonus if all of Termux can be fixed for secondary Android profiles,