HDR module in 1.8.515 Public Alpha is extremely slow
Posted: Sun Oct 03, 2021 12:44 am
Hi Ivo,
I love it when a new module or upgrade is released. However, I am a bit concerned by the new HDR module in the latest alpha release.
I just tested it on my machines - a Lenovo T440P running an i5-4300M CPU @ 2.6GHz. and a custom-built PC primarily for music production, running a slightly faster i5-4590M CPU @ 3.3GHz, both Windows 10 with 8GB RAM, Intel 4600 GPU and 20 compute units. Admittedly neither of them are necessarily high-end, especially for graphics, but they've been fine for StarTools and other graphics processing.
However, on opening the HDR module, for a linear image, around 1,800 x 1,100 pixels in size (binned and cropped), with the standard initial 50 pixels setings for the Context Size, it's taking between 3.5 and 4 minutes to process, before I can do anything. If I go up to 101 pixels, well, it's reached 5 minutes now and the progress indicator hasn't crept beyond the first bar!
So, whereas I could sort of use this within certain bounds, it's inconvenient not to be able to use it to its full capacity, and even within those bounds, so slow that it's disruptive to any workflow. Hence my concern! The previous HDR worked fine.
I notice that with SVDecon I can just use the synthetic, non-sampled approach and it works pretty much as before. So, is there any way HDR could do something similar? If not within the same screen, then perhaps have two options in the sidebar, in which the old HDR is still available but called something like HDR Lite, or HDR Global, and the new one is called HDR Full, or HDR Local?
I completely appreciate my machines aren't the last word in latest graphics tech, but I'd imagine I'm not alone in this. I'd very much rather not have to invest in new hardware in order to run StarTools, especially if there's any way it could be adapted to cater for less-than-high-end users.
I hope this feedback is useful. I think StarTools is great, and you do a fantastic job. This is why I'd like to keep using it!
Happy to provide any more feedback/stats if it helps.
Thanks
Brendan
I love it when a new module or upgrade is released. However, I am a bit concerned by the new HDR module in the latest alpha release.
I just tested it on my machines - a Lenovo T440P running an i5-4300M CPU @ 2.6GHz. and a custom-built PC primarily for music production, running a slightly faster i5-4590M CPU @ 3.3GHz, both Windows 10 with 8GB RAM, Intel 4600 GPU and 20 compute units. Admittedly neither of them are necessarily high-end, especially for graphics, but they've been fine for StarTools and other graphics processing.
However, on opening the HDR module, for a linear image, around 1,800 x 1,100 pixels in size (binned and cropped), with the standard initial 50 pixels setings for the Context Size, it's taking between 3.5 and 4 minutes to process, before I can do anything. If I go up to 101 pixels, well, it's reached 5 minutes now and the progress indicator hasn't crept beyond the first bar!
So, whereas I could sort of use this within certain bounds, it's inconvenient not to be able to use it to its full capacity, and even within those bounds, so slow that it's disruptive to any workflow. Hence my concern! The previous HDR worked fine.
I notice that with SVDecon I can just use the synthetic, non-sampled approach and it works pretty much as before. So, is there any way HDR could do something similar? If not within the same screen, then perhaps have two options in the sidebar, in which the old HDR is still available but called something like HDR Lite, or HDR Global, and the new one is called HDR Full, or HDR Local?
I completely appreciate my machines aren't the last word in latest graphics tech, but I'd imagine I'm not alone in this. I'd very much rather not have to invest in new hardware in order to run StarTools, especially if there's any way it could be adapted to cater for less-than-high-end users.
I hope this feedback is useful. I think StarTools is great, and you do a fantastic job. This is why I'd like to keep using it!
Happy to provide any more feedback/stats if it helps.
Thanks
Brendan