Thanks for the suggestions... though no dice. Still took way longer to convert in-app than via command line. (And when speedily running via command line, it doesn't impact system performance in any noticeable way, so it's not like it's in some cpu-sucking super-high priority state. Indeed, checking, it's the same, normal cpu priority as most other processes.)
I also looked to see what processes are running via the app -- and the app does not call ebook-convert.exe, it shows instead as calibre-parallel.exe. So it's not the same identical software (even if they share some common code). Whatever the difference is, the in-app approach is dramatically slower.
Hmm!?!
|