Page 1 of 1
XnViewMP 0.91 - Estimated time for batch processing
Posted: Sun Sep 02, 2018 6:38 am
by masterjp
I converted around 7.000 pictures with a high resolution from digital camera to a smaller format for my tablet to save space.
The estimated time calculation is absolutely unrealistic. The estimated end time is before the current time,
most of the time the remaining time shows 0:00 minutes/seconds.
After that you see 2 minutes to finish the batch conversion.
Only 50% of the job is done. The remaining time is bigger than 10-20 minutes.
I do not need 100% perfect information of the remaining time, but something which is near by the correct result.
Re: XnViewMP 0.91 - Estimated time for batch processing
Posted: Wed Sep 19, 2018 11:36 am
by xnview
do you have the problem immediately? Jpeg=>JPEG? only resize?
Re: XnViewMP 0.91 - Estimated time for batch processing
Posted: Fri Sep 21, 2018 8:03 pm
by masterjp
Strange. I can not reproduce the wrong estimated time error from my screenshot.
In XnViewMP 0.92 it works fine.
---
I got this error with 0.91 beta #5 (?).
Yes, I used JPEG to JPEG conversion and only reduce longer picture sides to 2048 pixel, if bigger.
After the start of batch conversion, the remaining time was at 10-20 minutes.
Then the time were counted down to zero. A long time it staid at 0 minutes remaining time and sometimes it said 2 minutes to finish batch process.
Re: XnViewMP 0.91 - Estimated time for batch processing
Posted: Wed Oct 10, 2018 6:08 pm
by masterjp
Today I got the problem again with the wrong estimated time. At the beginning XnViewMP shows a wrong end time.
After several minutes the estimated time get realistic!
I converted many jpeg files with 5616x3744 pixels to webp file format (90% compression, filter strength=20, compression level 6) with resize longest side to 2048 (reduce only).
Zwischenablage-1.png
Re: XnViewMP 0.91 - Estimated time for batch processing
Posted: Sun Oct 14, 2018 11:04 am
by xnview
and you can't reproduce always? with same input files?
Re: XnViewMP 0.91 - Estimated time for batch processing
Posted: Wed May 19, 2021 6:24 pm
by schwalbegc
I noticed that the estimated time uses skipped files, which is bad. For example, in my batch list, the first 30 files are skipped (output already exists), so the time to process these files is (let's just say) 1 second. 1/30=0.033 seconds/file * 4300 files = 143 seconds remaining. It's more like 2 hours, not 2 minutes.