HandBrake

version of HandBrake currently running: 0.10.5

operating system and version currently running: Windows 7


do not roll the CLI process into the GUI/Handbrake.exe process in upcoming versions of handbrake. if they are kept separate, the CLI can complete the encoding process if the GUI crashes. if a user does not end the .exe process when asked to close the program due to a crash/bug the encode will complete. this is handy if an encode has been going for a long time and a user does not want to restart that encode from the beginning. i had this happen to me while adding jobs to the queue.

The CLI isn't used by the GUI anymore, going forward. What the GUI used to call the CLI for is now a DLL that loads with HB, and is part of the GUI. Kill the GUI, and the operating system kills everything it owns.

i forgot to insert that it were handy for a GUI crash. if the GUI crashes the CLI can complete the encode. that way a user will not have to start an encode over that has been encoding for a long time. the GUI has crashed numerous times while setting parameters and adding jobs to the queue while a job had been running for hours that had hours left.

Just use the CLI, skip the GUI entirely. It's a far better interface for stability and getting what you want.

The GUI should not be crashing when setting parameters. If it is, please raise bug reports.

We are not reversing this design decision as overall it's for the better. 1.1 or later will introduce process isolation which will have the same effect your looking for.