Thanks
If I set threads =0 in "preferences" then indeed, nona uses the GPU and 1
thread in CPU
But if I set Threads=4 (having 8 threads available) then, it seems to me
that nona ONLY uses the 4 threads (I can see that with "top") and, as far
as I can judge from the time it takes to map the ima
I think you mix things: The gpu remapping has nothing to do with the number of
threads.
Nona can use the gpu for the remapping step. For this the number of threads has
no effect.
But there are more steps which are always done by the CPU.
PTBatcherGUI, hugin_stitch_project and hugin_executor are
I can't reproduce the crash with the pto file. The assistant ends without
problems and the crop is correctly calculated.
As long as I can't reproduce the crash we can't do anything for this.
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed t
Public bug reported:
Under the current version of Hugin, compiled from the lates source Pre-Release
2015.1.0.e65b6b93a955
when I stitch a project through the PTBatch, the output says it is using GPU,
but I can see that this does not happen
it uses the CPU.
on the other hand if I run with the
Requested pto file. Add images, Crate control points Hugin's CPFind and
vertical lines.
** Attachment added: "20151011_094159 - 20151011_094241.pto"
https://bugs.launchpad.net/hugin/+bug/1505149/+attachment/4496731/+files/20151011_094159%20-%2020151011_094241.pto
--
You received this bug not
5 matches
Mail list logo
