On 02/26/2014 06:23 AM, T. Modes wrote:
Am Montag, 24. Februar 2014 11:49:19 UTC+1 schrieb GnomeNomad:
The problem wasn't due to GL NOT working. IIRC, it was due to something
in the Hugin Fast Preview window trying to use GL before initializing
GL. Maybe there's be a regression in Hugin code somewhere that
unfixed that?
When the window is showing the preview, all should be initialized.
The window didn't show any preview. It was empty where there should have
been a preview, with the usual Hugin tabs along the top.
Is there some output in the console, which could help to debug the issue?
I tried that this morning - and Hugin worked fine with an existing
panorama. Didn't crash and the only console messages were these:
/usr/share/hugin/data/plugins/shooting_pattern.py
CAT:initial distribution
NAM:6-1-1 Shooting Pattern
/usr/share/hugin/data/plugins/top_five.py
CAT:Control Points
NAM:keep 5 CPs per image pair
/usr/share/hugin/data/plugins/crop_cp.py
CAT:Control Points
NAM:Crop Control Points
/usr/share/hugin/data/plugins/woa.py
CAT:Control Points
NAM:Warped Overlap Analysis
I just tried it now with a different PTO (again with no problems) and
got the above lines, along with this addition:
ERROR: 21:11:09.680417
(/build/hugin-d3Tfd7/hugin-2013.0.0+dfsg/src/hugin1/hugin/TextureManager.cpp:624)
SetParameters(): GL Error when setting texture parameters: invalid
operation.
Now I'm remaking an older pano from scratch. It produced a 983MB TIFF
(vs the 201MB original version) but I did some zooming etc in the
preview window just to see if I could make it crash.
Also it would helpful to know which changed in the underlying packages.
I have no idea what might have changed in the Xorg packages from Debian
Sid. The Intel driver that pertains to the HD4600 my laptop uses was
updated.
Today, Sid is offering hugin-2013.0.0+dfsg-1+b3; the version I have now
is hugin-2013.0.0+dfsg-1+b2. Which Debian package matches up with which
Hugin beta or release candidate?
Oh, BTW, I seem to be seeing this message from enblend again. First saw
it a few years ago, I think:
enblend: error: OJPEG encoding not supported; use new-style JPEG
compression instead
Enblend is being fed 16-bit TIFFs and generating a 16-bit TIFF, so these
(admittedly harmless) messages shouldn't be showing up.
--
David W. Jones
[email protected]
wandering the landscape of god
http://dancingtreefrog.com
--
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/hugin-ptx/530EEC6C.5050405%40gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.
