Contents

Individual Reports

IMPORTANT: before reporting, make sure you were using nona-gpu. When stitching from Hugin, set it in the Preferences -> Stitching tab -> activate the checkbox "Use GPU for remapping". When stitching from the command line, add the -g switch to the nona command line.

recent version of nona will fall back to CPU stitching for projects that the GPU can't stitch (yet). Read the output of nona to make sure it has not fallen back on CPU stitching even if told to use the GPU.

identify your video card. http://www.techarp.com/showarticle.aspx?artno=88 should help. select your GPU manufacturer's full list and note the exact name. The more precise you are, the better it is for everybody. Note that this is not your video card manufacturer / brand. Today most video card manufacturers get their GPU from either nVidia or ATI.

identify the exact driver you were using. Do so before upgrading driver, collecting reports for older drivers is useful. If you do upgrade later, make a second report for the upgraded driver.

copy the template below.

based on your video card and operating system, select the appropriate section to edit below.

Edit the section and append your report at the bottom of the list (but above the lines terminating the table).

While reporting speed / performance of your specific attempt is interesting data, don't draw conclusion from it. The improvement of GPU vs. CPU depends amongst others also on the type of CPU that is in your system and the type of project. Performance data is meaningful only if measured consistently and against the same project. This is beyond the scope of this page.

Nona GPU remapping functional. No significant improvement in performance, maybe even slightly slower than without GPU acceleration. Average GPU usage close to 0%, max ~5%. Using latest stable driver for GPU as of this posting.