AIKOUSHA  It saves a little time, as you can send it quite a number of files and walk away, instead of waiting and submitting them every 10-20 seconds by hand.

So, I definitely reccomend it, if that will lighten your work load.

However, I can manually send dozens of files to ffmpegx and never have an issue with the queue, but if I attempt to send 10-12 files at a time, there is a good chance that the queue will actually stop accepting the entries. When this happens, ffmpegx gets the file info, then it changes any relevant info (frame size/frame rate, etc.) and then sends the commands to Progress, however, it doesn't actually put a job in the queue. This has happened three times in the last week. And once the queue enters this state, you have to quit and restart the jobs (or wait 'til it's done and quit), and restart the Progress queue, before it'll take any more jobs.

For me, this negates it's use, when it does this, as half the point was to start a large number of jobs that'll take 20-45 minutes each, and I would like to get sleep while it continues to work. If it only accepts 10 jobs, it'll finish LONG before I wake up.

I don't know if this is an issue with the scripting, the script interpreter, or the Progress queue... but it never happens when I send things manually, no matter how many things I've stuck in the queue.

If anyone else has experienced this, and knows a workaround, or trick to fix it when it happens... please let me know!  
(Version 0.5b)