PTBatcherGUI vs enblend - blocking each other?

141 views
Skip to first unread message

Jens Scheidtmann

unread,
Jun 5, 2019, 5:25:00 PM6/5/19
to hugin and other free panoramic software
Dear list,

today I upgraded to Hugin 2019 and I observe the following when stitching my panorama:

At first PTBatcherGUI and enblend together consume ~50% CPU on my system. After a while, PTBatcher consumes 25% and enblend only 1-5 %.
When I now kill PTBatcherGUI, enblend finishes the job consuming up to 75%. BTW, the extended progress display.is activated.

Is this normal and am I just to too impatient?

Jens

T. Modes

unread,
Jun 6, 2019, 10:40:27 AM6/6/19
to hugin and other free panoramic software
Hi Jens


Am Mittwoch, 5. Juni 2019 23:25:00 UTC+2 schrieb Jens Scheidtmann:
At first PTBatcherGUI and enblend together consume ~50% CPU on my system. After a while, PTBatcher consumes 25% and enblend only 1-5 %.
When I now kill PTBatcherGUI, enblend finishes the job consuming up to 75%. BTW, the extended progress display.is activated.

Is this normal and am I just to too impatient?

There is already a ticket about this.
It seems that the latest enblend version is very communicative. This seems be too much for PTBatcherGUI.
A workaround is to add --color-blendspace=identity to the enblend parameters.

Thomas

Luís Henrique Camargo Quiroz

unread,
Jun 6, 2019, 1:35:54 PM6/6/19
to hugi...@googlegroups.com

  or else

--blend-colorspace=IDENTITY
 

--
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+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/346388bf-47ab-4740-af94-d7ab757b2f9e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


--

T. Modes

unread,
Jun 6, 2019, 1:47:46 PM6/6/19
to hugin and other free panoramic software
Hi Luis

Am Donnerstag, 6. Juni 2019 19:35:54 UTC+2 schrieb Luís Henrique Camargo Quiroz:

  or else

--blend-colorspace=IDENTITY

you are right. It was a typo from me, sorry for this. It should be --blend-colorspace=identity

Henk Tijdink

unread,
Jun 28, 2019, 4:18:24 PM6/28/19
to hugin and other free panoramic software
Hello Thomas

Your argument "--blend-colorspace=identity" for enblend works well, but without argument enblend finishes te job very slow. About 8 minutes for a 3 images panorama and creating a logfile of about 65.000 kB.
Tested the smartblend wrapper too in the batch processor. It created the intermediate files and the panorama, but then it get stuck and it don't delete the intermediate files. I have to force the closing the batch processor  that is stuck.
Further multiblend works well too in hugin 2019.0
Because there are 4 blending programs - Verdandi, Enblend, Smartblend with wrapper and Multiblend - shouldn't it be usefull making a menu to choose your blender each with his own argument line just as we have with control point pickers? 

Henk

T. Modes

unread,
Jun 29, 2019, 4:26:06 AM6/29/19
to hugin and other free panoramic software
Hi Henk,


Am Freitag, 28. Juni 2019 22:18:24 UTC+2 schrieb Henk Tijdink:
Your argument "--blend-colorspace=identity" for enblend works well, but without argument enblend finishes te job very slow. About 8 minutes for a 3 images panorama and creating a logfile of about 65.000 kB.
The currently very verbose output increases the run time. This will be reduced in the next version.
Because there are 4 blending programs - Verdandi, Enblend, Smartblend with wrapper and Multiblend - shouldn't it be usefull making a menu to choose your blender each with his own argument line just as we have with control point pickers? 
Smartblend and multiblend support only a subset of Hugins output options. So you would have to add a lot of checks.
Furthermore smartblend in Windows only and is not maintained any more.
For using alternative blenders there is already the user-defined output. This should allow more flexibility for different command line options instead of hard coding these different options.

Thomas
Reply all
Reply to author
Forward
0 new messages