Quote:
Originally Posted by embryo
Great update, thanks!
Some first observations:
- The "Free aspect" checkbox disappeared
- Checking the GPU utilization, I noticed that most of the processing is happening in the CPU with only some spikes of GPU processing.
I have a RTX 3060, but my monitors are using the AMD Radeon graphics of the CPU (AMD Ryzen G).
Do I have to do something to offload the processing there? When I use e.g. ComfyUI, the GPU is full on..
- I used the heavy model (without GPU processing as I said), but when I unchecked it, it was still used for the conversions. When I closed and re-opened the app, things were working fine again.
- Fixed threshold is a great option that was handy for a book whose scanned pages had letters leaking from the flip side. But this means that we are missing some automatic detection of the different pages. Can we have an offset value that will offset the automatic detection's value, after the detection for a darker or lighter threshold?
- The "Late night" skin is a Light skin with a little more pal colors than total white.. 
I can understand that you don't like dark colors, but since you did most of the work, can you please make the "Late night" skin with white text on a dark/black background? Not the default of course, but an options for us that have eye sight problems..🙏
Overall a great update. Thank you for your time.. |
Yes i consolidated free aspect into the standard crop function since crop without free aspect is effectively useless.
for GPU processing, the WGPU initializer selects the largest GPU by VRAM and other factors. it will use your 3060 and in the CLI you can see that it selected it.
3rd one is a bug, whoops.
fixed threshold issue..i dont understand. there is no detection for a lighter or darker threshold in fixed threshold. it thresholds by the number you pick. there is no current option for interlacing adaptive+fixed in the same document, which seems too granular to me. or what do you mean
for the late night skin, sorry no I dont want to add it to a standard release. I tested a dark mode (it is even still in the code, you can compile with --dark-mode), and it looks bad.
Glad you like the release, ill fix that bug for the next release. Overall I would suggest just using the CLI for processing, it uses the natural dark mode of your terminal and has an interactive mode that is easy to use. the GUI even farms its processing to the CLI under the hood.