Slight nice spawning issue about node-fluent-ffmpeg HOT 2 CLOSED

thanks for mentioning the typo, forgot to run unit tests before last commit sigh.

Considering your other points:

1. does that mean i have to set --adjustment to something like '+10' for a niceness of 10?
2. i'm using a different method for executing ffmpeg in thumbnail generation to make sure the supplied taskcallback is called correctly (it is feeded directly to the exec() call). i already tried it with spawn, it did never work properly.

spawn() in nodejs creates a process in a sync way, you dont have to wait for a callback. The process' pid is available directly after calling spawn(), thus it's 'reniceable'.

I'll be looking into a more genereic way to prevent failure on windows systems (there are already multiple actions that break execution on windows, i.e. 'which' calls), see issue #13.

from node-fluent-ffmpeg.

1. Actually, now that I think about it, the implementation would only be different for a process that has a different niceness than the default of 0. See http://manpages.ubuntu.com/manpages/jaunty/man1/nice.1.html - since you spawn the process yourself, this default will always be 0 so it should not be a problem.
2. Alright, strange that it does not work with spawn, I guess this is fine though.

Closing issue

from node-fluent-ffmpeg.