Strange behaviour of progress bar...
I experiencing strange behaviour of progress bar.
When i process single image it is moving to about 30% and then jump to the end! Estimated time is 3 times more than it realy take to process picture! rest of time dissapearing at the end
On v5.1.1 all was ok (maybe time was overestimated but it was corrected during the processing)
Runing on E7400 Code2Duo, 2GB ram - RAW from 7D
Estimated time 30s, process ttime about 10s. 20secs dissapearing at the end! (on v5.1.1 estimated time was lowered so at the end after 1 was 0, not after 20 was 0 in case of v6!)
Has someone experienced this?
When i process single image it is moving to about 30% and then jump to the end! Estimated time is 3 times more than it realy take to process picture! rest of time dissapearing at the end
On v5.1.1 all was ok (maybe time was overestimated but it was corrected during the processing)
Runing on E7400 Code2Duo, 2GB ram - RAW from 7D
Estimated time 30s, process ttime about 10s. 20secs dissapearing at the end! (on v5.1.1 estimated time was lowered so at the end after 1 was 0, not after 20 was 0 in case of v6!)
Has someone experienced this?
0
-
Michael,
You are welcome to submit a support case but it does seem that the progress bar needs some fine tuning. All things considered I would imagine that, while important, it is low on the priority list.
Also, you may want to try and turn OpenCL to "Never" if it isn't their already.0 -
Have the same behaviour of progress bar.
System is Win7 x64 (C1 6.0), Core2Quad Q9450, 8GB RAM, Canon 5D mk2, OpenCL is disabled.0 -
This behavior has been pretty consistant it seems to me with ALL Windows progress bars wether system or programs...it's been said, minor error IMHO, what's important is that overall speed of this program is decidedly faster...and and it in no way affects output. I'd say it will be fixed when Windows overall makes a better estimate of tasks as it probably relates to that... 0 -
[quote="John4" wrote:
This behavior has been pretty consistant it seems to me with ALL Windows progress bars wether system or programs...it's been said, minor error IMHO, what's important is that overall speed of this program is decidedly faster...and and it in no way affects output. I'd say it will be fixed when Windows overall makes a better estimate of tasks as it probably relates to that...
Ok... I know that the overestimation may be... but before in v5 task run through whole progres bar not till part of it and then jum to the end 😊
It is minor bug... but for programmer like me this is quite anoying.. 😊 because progres bar is not for running to 30 % and jump to the end.
In V5 i was not complaining... overestimation was corrected during the progres... no I happens only after done processed image. If you process many images it is less noticable but it is 😊0
Post is closed for comments.
Comments
4 comments