dud...@gmail.com schrieb am Sonntag, 9. April 2023 um 11:16:36 UTC+2: Hi. Are these numbers applied also to at/nvidia cards or do they apply only for other cards not defined? If applied globally tests show no benefit having larger dest chunks like 16 + 16 + 8. More testes shows too high negative numbers will hang processing, while too high, as we know corrupts framebuffering. Question remains. Could code be made more robust removing or changing behaviour in this particular place?
You can't simply change randomly numbers and hope that this fixes it. The meaning of the number is written directly above the line in the comment. By the way. What is the real cause of the issue here? I assume that it reads only the first dest chunk correctly back. The second and further one are not correctly read back. But I don't know why it works on most systems except the M1 one. Apple must have something special in its implementation. -- A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ --- You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group. To unsubscribe from this group and stop receiving emails from it, send an email to hugin-ptx+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/90105c74-017f-43a6-accf-8bb504c2f86fn%40googlegroups.com.
