If a filename/path are too long, then VidCoder crashes. It then gives a warning about the path length. (Handbrake didn't seem to have the problem, BTW).
BUT, if "Resume encoding on startup" is ON, then when restarted, it tries to re-encode the same problematic file, and crashes again. And again, and.....
Unfortunately, the ONLY way out of this loop is to UNINSTALL COMPLETELY, including settings. Otherwise, a re-install with old settings just pulls up the same pending queue. I even tried renaming the file, figuring it wouldn't be able to find it, and just move
on. But the bug seems to be in the code that reads the queue, not where it tries to retrieve the file, as it never gets to a "can't find file X"..
- after a crash or error, disable the "auto-encode on startup"
- and notify the user that you did this, so they can re-enable if they really want to
- and/or put the "auto-encode on start" checkbox on the main UI
- OR, after a crash, move the last file to the "failed" queue (especially if you can tell that's the file it crashed on). Thus, if every file in the queue has a problem, at least eventually it will stop.
- OR, after a crash, if "auto-encode" is on, just ask the user:
"VidCoder crashed with a pending queue - do you want to:
A) start where you left off
B) Keep the queue, but don't start encoding (i.e. clean up the queue yourself)
C) Delete the whole queue"
Still, great tool!