Closes #19 and #20. Transcoder no longer gets into a weird state if ffmpeg fails to execute.

Author: Sjoerd Tieleman

CHANGELOG.markdown

@@ -1,3 +1,7 @@
+## codem-transcode 0.5.3 (not yet released) ##
+
+* Bugfix: issue #19 and #20, missing or corrupt ffmpeg will no longer put transcoder in weird state.
+
 ## codem-transcode 0.5.2 (2013/09/10) ##
 
 * Bugfix: migrations should create "Jobs" table (instead of "jobs")

lib/job.js

@@ -258,8 +258,10 @@ var Job = JobUtils.getDatabase().define('Job', {
           args.push('-f', 'null', '-acodec', 'copy', '-vcodec', 'copy', '-y', null_file);
         }
 
-        var the_process = child_process.spawn(config['encoder'], args);
-        the_process.stderr.on('data', function(data) { job.progressHandler(data) });
+        var the_process = child_process.spawn(config['encoder'], args);          
+
+        the_process.stderr.on('data', function(data) { job.progressHandler(data); });
+        the_process.on('error', function(err) { job.lastMessage = 'Unable to execute the ffmpeg binary: ' + err; job.didFinish(1); });
         the_process.on('exit', function(code) { job.didFinish(code); });
 
         this.the_process = the_process;