Hi Gerry,
what's about using the exposure anchor for this purpose? So we would not
need a new parameter in the pto file. Also we would not need more
buttons on the images tab (e.g. set response anchor). Maybe it could
then renamed to photometric anchor (only in the gui).
Thomas
--
You received
** Changed in: hugin
Status: Triaged => Incomplete
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/685224
Title:
save / load CP generator settings doesn't work
Status in Hugin - Panorama T
*** This bug is a duplicate of bug 686520 ***
https://bugs.launchpad.net/bugs/686520
You already answered to yourself. mark as duplicate is one way.
another is to set the status to invalid. probably invalid status is
slightly better because duplicates still show up linked into the
"accepted"
thanks for the additional information. I will check with the PPA Team.
In the meantime can somebody with a clean Ubuntu install try to get
Hugin per the above instructions in comment #3 and confirm this bug
report?
** Changed in: enblend
Status: Incomplete => New
--
You received this bug
On December 7, 2010 08:00:55 am rew wrote:
> Yuv, If I have "half-a-person" on a picture, I know I don't want that in
> the final picture. This is easily masked.
Thomas answered this one.
> If I have a full person on a picture I might want to mark it as:
> "please include all this", because ot
tags are separated by spaces. I assume "crop factor" was a single
intended tag (I don't see any mean in a "factor" tag) so I fixed the
tags.
this is not a feature request, rather a (probably invalid) bug report.
hence set it to importance low rather than importance wishlist. Trying
to keep wishl
use hg export to produce the patch. hg help export is your friend.
for example, if the code was committed in one go, then hg export -g
${REV} > feature.patch will produce a patch. If it was committed in
multiple steps, then hg export -g ${STARTREV}:${ENDREV} > feature.patch
will do the trick. Yo
I didn't look into this issue for a couple of weeks. I will look into it
the coming days. The assignment is OK.
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Enblend.
https://bugs.launchpad.net/bugs/679590
Title:
enblend cannot load
** Changed in: hugin
Status: Triaged => Incomplete
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/684749
Title:
makefile generation problems
Status in Hugin - Panorama Tools GUI:
Incomp
Tried to fix in 431788d95f14. Could you confirm it?
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/684749
Title:
makefile generation problems
Status in Hugin - Panorama Tools GUI:
Triaged
Bug
The filename are all very unixy and does not look good on windows.
Furthermore, if you hold a handle to a file you can not rename the same file in
a second instance. So this will break.
Also this will show unpredictable behaviour if you open more than 10 instances
(unlikely, but possible).
Also
What's done in hugin should not influence this bug. Because if you start
stitching, hugin_stitch_project is started as own program and this is
generating the makefile.
Could you please post the invalid makefile which is generated in the
temp dir when this bug occurs?
--
You received this bug not
This bug has nothing to do with enblend. The bug is in hdr_merge. Nobody
has mentioned enblend. So setting to invalid in enblend.
** Changed in: enblend
Status: New => Invalid
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
The bug seems to be in hdr_merge.
Does the exr format support the offset tag?
If not, this could explain the observed behaviour.
If yes, then we need to check if the tag is correctly read and written.
Could you try to stitch the hdr images with non-cropped images (on
Stitcher tab, goto Nona optio
> If I have a full person on a picture I might want to mark it as:
>"please include all this", because otherwise enblend might cut
> of a head or a foot. These are the red and green areas in "ptgui".
This can also be done easily by masking.
> What I was suggesting is that we use the alpha mask
Hi Rogier,
I appreciate the energy you are putting into cleaning up / sorting out
the bug tracker.
Re bughunters group, everybody can apply to become a member by hitting
the appropriate link on its homepage https://launchpad.net/~hugin-bug-
hunters and everybody can ee who is a member by hitting
This MUST be 3.2, because the bug was filed with hugin 2009.2 which was
released before enblend 4.0 came out.
It seems to me that this is either an imagecache bug which we know is
buggy, or it's trying to blend too large an image for a 32bit machine.
The alloc that fails is reasonable in the cont
Harry, you see what you do with this. EMail me if you're not in the
bughunters group to modify the states. (or mail Yuv to have yourself
added).
** Project changed: hugin => enblend
** Changed in: enblend
Assignee: (unassigned) => hvdwolf (hvdwolf)
--
You received this bug notification bec
Yuv, If I have "half-a-person" on a picture, I know I don't want that in
the final picture. This is easily masked.
If I have a full person on a picture I might want to mark it as:
"please include all this", because otherwise enblend might cut of a head
or a foot. These are the red and green areas
We need to fix "imagecache" .
Is the imagecache also used in hugin? Then it might crash hugin as well!
For now: "affects enblend"
** Project changed: hugin => enblend
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Enblend.
https://bug
OK. I managed to stitch this project. The only way that works is:
enblend 4.0 with no image cache on a 64-bit machine. Takes huge amounts
of memory, but it works.
** Changed in: hugin
Status: New => Confirmed
--
You received this bug notification because you are a member of Hugin
Develop
** Also affects: enblend
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/679520
Title:
hdrmerge fails due to differing image sizes
Status in Enblend:
** Project changed: hugin => enblend
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Enblend.
https://bugs.launchpad.net/bugs/679456
Title:
stitching failure
Status in Enblend:
Triaged
Bug description:
Attempting full res HDR sti
Ok. Guys... With these reports about enblend I need to know wether or
not you have Image cache enabled or not.
** Project changed: hugin => enblend
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Enblend.
https://bugs.launchpad.net/bugs
** Project changed: enblend => hugin
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/686520
Title:
Allow a way to match the panorama wth google earth
Status in Hugin - Panorama Tools GUI:
New
*** This bug is a duplicate of bug 686520 ***
https://bugs.launchpad.net/bugs/686520
Can I delete a bugreport I made? I hit "enter" on the bug report form,
and then clicked submit. This apparently submitted the report twice.
--
You received this bug notification because you are a member of H
*** This bug is a duplicate of bug 686520 ***
https://bugs.launchpad.net/bugs/686520
Public bug reported:
I have embedded my panorama in google earth (through gigapan). But the
location of the panorama is slightly off. I was thinking I could put a
few controlpoints on google earth and my pano
Public bug reported:
I have embedded my panorama in google earth (through gigapan). But the
location of the panorama is slightly off. I was thinking I could put a
few controlpoints on google earth and my pano, so that I could get a
perfect location match for my panorama.
** Affects: enblend
On Tue, Dec 07, 2010 at 12:47:47AM -, Yuv wrote:
> Share the patch please. Can't promise (lot of things on my todo list),
> but if it still does not have a preference setting I can contribute
> that.
>
> Place = storage space in the file system? how about taking the time when
> the Hugin inst
On Tue, Dec 07, 2010 at 12:47:47AM -, Yuv wrote:
> Share the patch please. Can't promise (lot of things on my todo list),
> but if it still does not have a preference setting I can contribute
> that.
>
> Place = storage space in the file system? how about taking the time when
> the Hugin inst
It happens with 4.0 TOO.
I have blended my panorama now with a 4.0 build on a 64bit machine. I
just let the OS swap. It required over 12Gb of RAM/swap, and finished
the blend just fine!
I'm now pretty sure that it is "imagecache" that causes the corruption or
crashes.
I chose to NOT use imageca
31 matches
Mail list logo
