New streaming issues about node-fluent-ffmpeg HOT 4 CLOSED

I confirmed that this is in fact caused by recent changes by checking out to commit f62a558 - this is without the streaming changes. At this commit, everything worked fine again.

There must be something wrong with passing in streams like this. Maybe there are issues related to piping. In that case, we should manually pipe the input stream to ffmpeg's stdin stream.

from node-fluent-ffmpeg.

fixed in #16, tested too.

from node-fluent-ffmpeg.

i'll re-add the old streaming code by adding an option to switch between the piping (customFds) and the pumping (stream.pump()) mode (sounds awkward i know ;))

from node-fluent-ffmpeg.

@schaermu, ehh that sounds highly illogical - why would you ever want to do that?

The fix I provided is the best of both worlds. Just passing in Fds is not possible because the write buffer will get full, apparently, this is why we had to use piping.

from node-fluent-ffmpeg.