[Hugin-devs] [Bug 2046661] [NEW] Smart Screen blocks installation on Windows 10
Public bug reported: It seems the MSI file needs some digital signature to circumvent Windows Smart Screen's default blocking the installation. As the last version of Hugin could be installed without this issue (AFAIR), I guess it's a new "feature" of Windows 10 Smart Screen. ** Affects: hugin Importance: Undecided Status: New ** Tags: installation ** Tags added: installation ** Description changed: It seems the MSI file needs some digital signature to circumvent Windows Smart Screen's default blocking the installation. As the last version of - Hugin could be installed without this issue (AFAIR), I gess it's a new + Hugin could be installed without this issue (AFAIR), I guess it's a new "feature" of Windows 10 Smart Screen. -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/2046661 Title: Smart Screen blocks installation on Windows 10 Status in Hugin: New Bug description: It seems the MSI file needs some digital signature to circumvent Windows Smart Screen's default blocking the installation. As the last version of Hugin could be installed without this issue (AFAIR), I guess it's a new "feature" of Windows 10 Smart Screen. To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/2046661/+subscriptions ___ Mailing list: https://launchpad.net/~hugin-devs Post to : hugin-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~hugin-devs More help : https://help.launchpad.net/ListHelp
[Hugin-devs] [Bug 1959518] Re: enblend crahes without error message
I had the idea to try the same input files on openSUSE Leap 15.3 (enblend-enfuse-4.2-bp153.2.1.x86_64): There the program did not crash; instead it seems to output a warning: ... enblend: info: Annealing Optimizer, s0: 1/4 2/4 3/4 4/4 enblend: info: Dijkstra Optimizer: s0enblend: warning: unable to run Dijkstra optimizer enblend: note: seam-line end point outside of cost-image enblend: note: contour #1 of 1, segment #1 of 1, vertex #4 of 183 enblend: info: mask transition line bounding box: [(0, 5109) to (3688, 6235) = (3688x1126)] enblend: info: region-of-interest bounding box: [(0, 0) to (3688, 7062) = (3688x7062)] enblend: info: using 10 blending levels enblend: info: generating Gaussian pyramid: g0 g1 g2 g3 g4 g5 g6 g7 g8 g9 ... The resulting image was 3688x9107 pixels, and I could not see any artefacts; in fact the result looks very good, considering that the contributing shots were made without a tripod. -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Enblend. https://bugs.launchpad.net/bugs/1959518 Title: enblend crahes without error message Status in Enblend: New Bug description: When blending a vertical panorama with hugin 2020.0, enblend crashes in Windows 10. Here is the (German) log: Panorama zusammenfügen... Plattform: Windows 10 (build 19043), 64-bit edition Version: 2020.0.0.2f576e5d5b4a built by Thomas Aktuelles Verzeichnis: D:\Work\Ulrich\Bilder\DC-G9\2022\Panorama\122-128 Ausgabe-Präfix: 1040122-1040128 Überblendung: enblend 4.3-6b604e79e85b ExifTool-Version: 12.08 Anzahl der aktiven Bilder: 7 Ausgabe-Belichtungswert: 11,0 Rahmengrösse: 4599x10224 ROI: (443, 254) - (4131, 9392) FOV: 28x58 Projektion: Gradlinig (Rectilinear)(0) Verwende GPU für Umberechnung: falsch Panorama-Ausgabe: * Mit Belichtungskorrektur, niedriger Dynamikumfang Erstes Quell-Bild Nummer: 0 Dateiname: D:\Work\Ulrich\Bilder\DC-G9\2022\Panorama\122-128\_1040122.jpg Größe: 3712x2784 Projektion: Gradlinig (Rectilinear) Kamerakurve: Benutzerdefiniert (EMoR) HFOV: 23 Belichtungswert: 11,0 Umberechnung von LDR-Bildern… Multiple images output loading _1040122.jpg remapping _1040122.jpg saving 1040122-1040128.tif loading _1040123.jpg remapping _1040123.jpg saving 1040122-10401280001.tif loading _1040124.jpg remapping _1040124.jpg saving 1040122-10401280002.tif loading _1040125.jpg remapping _1040125.jpg saving 1040122-10401280003.tif loading _1040126.jpg remapping _1040126.jpg saving 1040122-10401280004.tif loading _1040127.jpg remapping _1040127.jpg saving 1040122-10401280005.tif loading _1040128.jpg remapping _1040128.jpg saving 1040122-10401280006.tif Überblendung der Bilder… --- In Windows Event Viewer I have these details (XML view): http://schemas.microsoft.com/win/2004/08/events/event";> 1000 0 2 100 0 0x80 27351 Application I74X4W7 enblend.exe 0.0.0.0 5dc316ba enblend.exe 0.0.0.0 5dc316ba c005 00065c50 2960 01d815f624ec1475 C:\Program Files\Hugin\bin\enblend.exe C:\Program Files\Hugin\bin\enblend.exe 80c743dd-0994-4ad6-b2ba-f028f860781c Also, it seems Hugin does not detect the crash, because the temporary files are removed after that, and the resulting JPG has size zero. The bug seems rather persistent for this vertical panorama; even when running with differnt controlpoints and alignments, enblend crashed. So I made Hugin save the repapped files and ran enblend interactively with --verbose=2; it also crashed: --- D:\Work\Ulrich\Bilder\DC-G9\2022\Panorama\122-128>enblend --verbose=2 -o test.jpj 1040122-1040128*.tif enblend --verbose=2 -o test.jpj 1040122-1040128*.tif enblend: warning: unknown filetype of output file "test.jpj" enblend: note: will fallback to type "pnm" enblend: info: loading next image: 1040122-1040128.tif 1/1 enblend: info: loading next image: 1040122-10401280001.tif 1/1 enblend: info: creating coarse/8 blend mask: 1/3 2/3 3/3 enblend: info: optimizing 1 distinct seam enblend: info: Annealing Optimizer, s0: 1/4 2/4 3/4 4/4 enblend: info: Dijkstra Optimizer: s0 enblend: info: using 10 blending levels enblend: info: generating Gaussian pyramid: g0 g1 g2 g3 g4 g5 g6 g7 g8 g9 enblend: info: generating Gaussian pyramid: g0 g1 g2 g3 g4 g5 g6 g7 g8 g9 enblend: info: generating Laplacian pyramid: l0 l1 l2 l3 l4 l5 l6 l7 l8 l9 enblend: info: generating Gaussian pyramid: g0 g1 g2 g3 g4 g5 g6 g7 g8 g9 enblend: info: generating Laplacian pyramid: l0 l1 l2 l3 l4 l5 l6 l7 l8 l9 enblend: info: blending layers: l0 l1 l2 l3 l4 l5 l6 l7 l8 l9 enblend: info: collapsing Laplacian
[Hugin-devs] [Bug 1959518] [NEW] enblend crahes without error message
Public bug reported: When blending a vertical panorama with hugin 2020.0, enblend crashes in Windows 10. Here is the (German) log: Panorama zusammenfügen... Plattform: Windows 10 (build 19043), 64-bit edition Version: 2020.0.0.2f576e5d5b4a built by Thomas Aktuelles Verzeichnis: D:\Work\Ulrich\Bilder\DC-G9\2022\Panorama\122-128 Ausgabe-Präfix: 1040122-1040128 Überblendung: enblend 4.3-6b604e79e85b ExifTool-Version: 12.08 Anzahl der aktiven Bilder: 7 Ausgabe-Belichtungswert: 11,0 Rahmengrösse: 4599x10224 ROI: (443, 254) - (4131, 9392) FOV: 28x58 Projektion: Gradlinig (Rectilinear)(0) Verwende GPU für Umberechnung: falsch Panorama-Ausgabe: * Mit Belichtungskorrektur, niedriger Dynamikumfang Erstes Quell-Bild Nummer: 0 Dateiname: D:\Work\Ulrich\Bilder\DC-G9\2022\Panorama\122-128\_1040122.jpg Größe: 3712x2784 Projektion: Gradlinig (Rectilinear) Kamerakurve: Benutzerdefiniert (EMoR) HFOV: 23 Belichtungswert: 11,0 Umberechnung von LDR-Bildern… Multiple images output loading _1040122.jpg remapping _1040122.jpg saving 1040122-1040128.tif loading _1040123.jpg remapping _1040123.jpg saving 1040122-10401280001.tif loading _1040124.jpg remapping _1040124.jpg saving 1040122-10401280002.tif loading _1040125.jpg remapping _1040125.jpg saving 1040122-10401280003.tif loading _1040126.jpg remapping _1040126.jpg saving 1040122-10401280004.tif loading _1040127.jpg remapping _1040127.jpg saving 1040122-10401280005.tif loading _1040128.jpg remapping _1040128.jpg saving 1040122-10401280006.tif Überblendung der Bilder… --- In Windows Event Viewer I have these details (XML view): http://schemas.microsoft.com/win/2004/08/events/event";> 1000 0 2 100 0 0x80 27351 Application I74X4W7 enblend.exe 0.0.0.0 5dc316ba enblend.exe 0.0.0.0 5dc316ba c005 00065c50 2960 01d815f624ec1475 C:\Program Files\Hugin\bin\enblend.exe C:\Program Files\Hugin\bin\enblend.exe 80c743dd-0994-4ad6-b2ba-f028f860781c Also, it seems Hugin does not detect the crash, because the temporary files are removed after that, and the resulting JPG has size zero. The bug seems rather persistent for this vertical panorama; even when running with differnt controlpoints and alignments, enblend crashed. So I made Hugin save the repapped files and ran enblend interactively with --verbose=2; it also crashed: --- D:\Work\Ulrich\Bilder\DC-G9\2022\Panorama\122-128>enblend --verbose=2 -o test.jpj 1040122-1040128*.tif enblend --verbose=2 -o test.jpj 1040122-1040128*.tif enblend: warning: unknown filetype of output file "test.jpj" enblend: note: will fallback to type "pnm" enblend: info: loading next image: 1040122-1040128.tif 1/1 enblend: info: loading next image: 1040122-10401280001.tif 1/1 enblend: info: creating coarse/8 blend mask: 1/3 2/3 3/3 enblend: info: optimizing 1 distinct seam enblend: info: Annealing Optimizer, s0: 1/4 2/4 3/4 4/4 enblend: info: Dijkstra Optimizer: s0 enblend: info: using 10 blending levels enblend: info: generating Gaussian pyramid: g0 g1 g2 g3 g4 g5 g6 g7 g8 g9 enblend: info: generating Gaussian pyramid: g0 g1 g2 g3 g4 g5 g6 g7 g8 g9 enblend: info: generating Laplacian pyramid: l0 l1 l2 l3 l4 l5 l6 l7 l8 l9 enblend: info: generating Gaussian pyramid: g0 g1 g2 g3 g4 g5 g6 g7 g8 g9 enblend: info: generating Laplacian pyramid: l0 l1 l2 l3 l4 l5 l6 l7 l8 l9 enblend: info: blending layers: l0 l1 l2 l3 l4 l5 l6 l7 l8 l9 enblend: info: collapsing Laplacian pyramid: l9 l8 l7 l6 l5 l4 l3 l2 l1 l0 enblend: info: loading next image: 1040122-10401280002.tif 1/1 enblend: info: creating coarse/8 blend mask: 1/3 2/3 3/3 enblend: info: optimizing 1 distinct seam enblend: info: Annealing Optimizer, s0: 1/4 2/4 3/4 4/4 enblend: info: Dijkstra Optimizer: s0 enblend: info: using 10 blending levels enblend: info: generating Gaussian pyramid: g0 g1 g2 g3 g4 g5 g6 g7 g8 g9 enblend: info: generating Gaussian pyramid: g0 g1 g2 g3 g4 g5 g6 g7 g8 g9 enblend: info: generating Laplacian pyramid: l0 l1 l2 l3 l4 l5 l6 l7 l8 l9 enblend: info: generating Gaussian pyramid: g0 g1 g2 g3 g4 g5 g6 g7 g8 g9 enblend: info: generating Laplacian pyramid: l0 l1 l2 l3 l4 l5 l6 l7 l8 l9 enblend: info: blending layers: l0 l1 l2 l3 l4 l5 l6 l7 l8 l9 enblend: info: collapsing Laplacian pyramid: l9 l8 l7 l6 l5 l4 l3 l2 l1 l0 enblend: info: loading next image: 1040122-10401280003.tif 1/1 enblend: info: creating coarse/8 blend mask: 1/3 2/3 3/3 enblend: info: optimizing 1 distinct seam enblend: info: Annealing Optimizer, s0: 1/4 2/4 3/4 4/4 enblend: info: Dijkstra Optimizer: s0 enblend: info: using 10 blending levels enblend: info: generating Gaussian pyramid: g0 g1 g2 g3 g4 g5 g6 g7 g8 g9 enblend: info: generating Gaussian pyramid: g0 g1 g2 g3 g4 g5 g6 g7 g8 g9 enblend: info: generating Laplacian pyramid: l0 l1 l2 l3 l4 l5 l6 l7 l8 l9 e
[Hugin-devs] [Bug 1956190] [NEW] align_image_stack is doing a poor job
Public bug reported: A scenario is described in https://photo.stackexchange.com/q/128167/82107 align_image_stack is doing a poor job trying to align a series of "free-hand" shots. It's not obvious what's wrong. (The panotools mailinglist at yahoo seems dead) ** Affects: hugin 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/1956190 Title: align_image_stack is doing a poor job Status in Hugin: New Bug description: A scenario is described in https://photo.stackexchange.com/q/128167/82107 align_image_stack is doing a poor job trying to align a series of "free-hand" shots. It's not obvious what's wrong. (The panotools mailinglist at yahoo seems dead) To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1956190/+subscriptions ___ Mailing list: https://launchpad.net/~hugin-devs Post to : hugin-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~hugin-devs More help : https://help.launchpad.net/ListHelp
[Hugin-devs] Antw: [Bug 1634363] Re: all control points selected in control point list
You are right; I forgot to add the attachemnts before sending, it seems. Here are the promised attachments. Sorry! >>> tmodes <1634...@bugs.launchpad.net> schrieb am 20.10.2016 um 17:35 in >>> Nachricht <20161020153553.23609.55843.mal...@soybean.canonical.com>: > Here is nothing attached. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1634363 > > Title: > all control points selected in control point list > > Status in Hugin: > Incomplete > > Bug description: > When opening the control point list with many (>300 control points), > sorting by distance (largest at the bottom), the following problem appears: > When selecting the last control point and delete it (using Del key), the > control point is removed and the next one is selected. You can repeat this > several times, but suddenly all control points are selected, and if you don't > take care, all control points are removed. > (You may undo from the main window, but undo from the control point list > doesn't work) > Observed in 32-bit Windows version... > > To manage notifications about this bug go to: > https://bugs.launchpad.net/hugin/+bug/1634363/+subscriptions ** Attachment added: "ControlPoints.pto" https://bugs.launchpad.net/bugs/1634363/+attachment/4764672/+files/ControlPoints.pto ** Attachment added: "ControlPoints-2.jpg" https://bugs.launchpad.net/bugs/1634363/+attachment/4764673/+files/ControlPoints-2.jpg ** Attachment added: "ControlPoints-1.jpg" https://bugs.launchpad.net/bugs/1634363/+attachment/4764674/+files/ControlPoints-1.jpg -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1634363 Title: all control points selected in control point list Status in Hugin: Incomplete Bug description: When opening the control point list with many (>300 control points), sorting by distance (largest at the bottom), the following problem appears: When selecting the last control point and delete it (using Del key), the control point is removed and the next one is selected. You can repeat this several times, but suddenly all control points are selected, and if you don't take care, all control points are removed. (You may undo from the main window, but undo from the control point list doesn't work) Observed in 32-bit Windows version... To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1634363/+subscriptions ___ Mailing list: https://launchpad.net/~hugin-devs Post to : hugin-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~hugin-devs More help : https://help.launchpad.net/ListHelp
[Hugin-devs] Antw: [Bug 1635132] Re: Exclude image borders from control point generation
>From a user's point of view, it's much easier to say "exclude 10%" of the >image at the borders rather than to draw some mask on every image. Maybe even the border tuning could be automated depending on the overlap of each pair of images. >>> zarl <1635...@bugs.launchpad.net> schrieb am 20.10.2016 um 09:19 in >>> Nachricht <20161020071953.28981.87520.mal...@chaenomeles.canonical.com>: > Have you tried working with masks and/or crop masks? > > Simple exclude masks prevent control point generators from placing CPs > in those areas, these masks can be copied to other images. > > Cropping (available from the masks tab -> switch from "Masks" to "Crop") > can be used for scans and e.g. also for images from fish eye lenses. A > typical use would be to define a crop mask for a non full frame fish > eye, save that to your lens database, apply that lens setting to other > images in your project. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1635132 > > Title: > Exclude image borders from control point generation > > Status in Hugin: > New > > Bug description: > Enhancement request: Allow `n' percent of the image at the border to > be excluded from automatic control point placement, i.e.: place the > control points in a centered rectangle making up `100 -n' percent of > the image. Maybe for fisheye it has to be a circle, maybe it can be an > ellipsoid anyway, maybe the likelihood of a control point should > decrease with the distance from the image center... You get the > idea... > > To manage notifications about this bug go to: > https://bugs.launchpad.net/hugin/+bug/1635132/+subscriptions -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1635132 Title: Exclude image borders from control point generation Status in Hugin: New Bug description: Enhancement request: Allow `n' percent of the image at the border to be excluded from automatic control point placement, i.e.: place the control points in a centered rectangle making up `100 -n' percent of the image. Maybe for fisheye it has to be a circle, maybe it can be an ellipsoid anyway, maybe the likelihood of a control point should decrease with the distance from the image center... You get the idea... To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1635132/+subscriptions ___ Mailing list: https://launchpad.net/~hugin-devs Post to : hugin-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~hugin-devs More help : https://help.launchpad.net/ListHelp
[Hugin-devs] [Bug 1635132] [NEW] Exclude image borders from control point generation
Public bug reported: Enhancement request: Allow `n' percent of the image at the border to be excluded from automatic control point placement, i.e.: place the control points in a centered rectangle making up `100 -n' percent of the image. Maybe for fisheye it has to be a circle, maybe it can be an ellipsoid anyway, maybe the likelihood of a control point should decrease with the distance from the image center... You get the idea... ** Affects: hugin Importance: Undecided Status: New ** Tags: controlpoint -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1635132 Title: Exclude image borders from control point generation Status in Hugin: New Bug description: Enhancement request: Allow `n' percent of the image at the border to be excluded from automatic control point placement, i.e.: place the control points in a centered rectangle making up `100 -n' percent of the image. Maybe for fisheye it has to be a circle, maybe it can be an ellipsoid anyway, maybe the likelihood of a control point should decrease with the distance from the image center... You get the idea... To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1635132/+subscriptions ___ Mailing list: https://launchpad.net/~hugin-devs Post to : hugin-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~hugin-devs More help : https://help.launchpad.net/ListHelp
[Hugin-devs] Antw: [Bug 1634363] Re: all control points selected in control point list
Unfortunately I was too optimistic regarding reproducability, and maybe the preconditions are even more complex: I think I also removed control points by dragging with the mouse in the image window (whenever I see many control points too close to the borders), then continuing to delete points with a large distance (ping-pong procedure). Anyway I observed this: I saw the effect twice, but could not clearly reproduce, especially when undoing after all control points had been deleted, the selection was not restored. I also noticed that if you select the last point in the control point list, the last entry stays selected even after you deleted the control point (that seems kind of desired), but some times no control point is visibly selected, but still the right control point seems to be deleted of you press the Del key. Maybe it's some issue with the Windows control regarding selecting items in a list and deleting them without reselecting another. I'll attach three files: Two screen shots showing the situation when I started to delete control points, and the situation when all control points were selected, and the PTO file, but as indicated above that is likely not useful in reproduction. Sorry for not having better news! The version is the latest 32-bit windows version (2016) >>> zarl <1634...@bugs.launchpad.net> schrieb am 19.10.2016 um 14:54 in >>> Nachricht <20161019125436.7127.36418.mal...@gac.canonical.com>: > Can you upload a .pto file (no images needed) so we can try to reproduce > the error on a different system? > > Which version of Hugin do you use? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1634363 > > Title: > all control points selected in control point list > > Status in Hugin: > Incomplete > > Bug description: > When opening the control point list with many (>300 control points), > sorting by distance (largest at the bottom), the following problem appears: > When selecting the last control point and delete it (using Del key), the > control point is removed and the next one is selected. You can repeat this > several times, but suddenly all control points are selected, and if you don't > take care, all control points are removed. > (You may undo from the main window, but undo from the control point list > doesn't work) > Observed in 32-bit Windows version... > > To manage notifications about this bug go to: > https://bugs.launchpad.net/hugin/+bug/1634363/+subscriptions -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1634363 Title: all control points selected in control point list Status in Hugin: Incomplete Bug description: When opening the control point list with many (>300 control points), sorting by distance (largest at the bottom), the following problem appears: When selecting the last control point and delete it (using Del key), the control point is removed and the next one is selected. You can repeat this several times, but suddenly all control points are selected, and if you don't take care, all control points are removed. (You may undo from the main window, but undo from the control point list doesn't work) Observed in 32-bit Windows version... To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1634363/+subscriptions ___ Mailing list: https://launchpad.net/~hugin-devs Post to : hugin-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~hugin-devs More help : https://help.launchpad.net/ListHelp
[Hugin-devs] Antw: [Bug 1634363] Re: all control points selected in control point list
I would not have reported this as a bug if it had happened just once. However I don't know the internal conditions required to trigger it. I'll try to make screenshots showing the problem... >>> tmodes <1634...@bugs.launchpad.net> schrieb am 18.10.2016 um 20:42 in >>> Nachricht <20161018184252.30366.51.mal...@chaenomeles.canonical.com>: > Sorry, I can't reproduce the issue. I tested a big project. I could > delete all control points point by point with del key without selection > all remaining control points. > > ** Changed in: hugin >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1634363 > > Title: > all control points selected in control point list > > Status in Hugin: > Incomplete > > Bug description: > When opening the control point list with many (>300 control points), > sorting by distance (largest at the bottom), the following problem appears: > When selecting the last control point and delete it (using Del key), the > control point is removed and the next one is selected. You can repeat this > several times, but suddenly all control points are selected, and if you don't > take care, all control points are removed. > (You may undo from the main window, but undo from the control point list > doesn't work) > Observed in 32-bit Windows version... > > To manage notifications about this bug go to: > https://bugs.launchpad.net/hugin/+bug/1634363/+subscriptions -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1634363 Title: all control points selected in control point list Status in Hugin: Incomplete Bug description: When opening the control point list with many (>300 control points), sorting by distance (largest at the bottom), the following problem appears: When selecting the last control point and delete it (using Del key), the control point is removed and the next one is selected. You can repeat this several times, but suddenly all control points are selected, and if you don't take care, all control points are removed. (You may undo from the main window, but undo from the control point list doesn't work) Observed in 32-bit Windows version... To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1634363/+subscriptions ___ Mailing list: https://launchpad.net/~hugin-devs Post to : hugin-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~hugin-devs More help : https://help.launchpad.net/ListHelp
[Hugin-devs] [Bug 1634363] [NEW] all control points selected in control point list
Public bug reported: When opening the control point list with many (>300 control points), sorting by distance (largest at the bottom), the following problem appears: When selecting the last control point and delete it (using Del key), the control point is removed and the next one is selected. You can repeat this several times, but suddenly all control points are selected, and if you don't take care, all control points are removed. (You may undo from the main window, but undo from the control point list doesn't work) Observed in 32-bit Windows version... ** Affects: hugin Importance: Undecided Status: New ** Tags: controlpoint -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1634363 Title: all control points selected in control point list Status in Hugin: New Bug description: When opening the control point list with many (>300 control points), sorting by distance (largest at the bottom), the following problem appears: When selecting the last control point and delete it (using Del key), the control point is removed and the next one is selected. You can repeat this several times, but suddenly all control points are selected, and if you don't take care, all control points are removed. (You may undo from the main window, but undo from the control point list doesn't work) Observed in 32-bit Windows version... To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1634363/+subscriptions ___ Mailing list: https://launchpad.net/~hugin-devs Post to : hugin-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~hugin-devs More help : https://help.launchpad.net/ListHelp
[Hugin-devs] [Bug 1633354] Re: "enblend: warning: unable to run Dijkstra optimizer" for large panorama
When running enblend with --visualize and path debugging, the program
crashes. The effect is stat output suddenly stops, and when I click the Hugin
windows, a message pops up that the program is not responding, then that it had
crashed. Most unfortunately the log is not saved then! (I made a screen shot of
the window when output had stopped.
However when only using --visualize, the program does not crash. Maybe there is
some LZW issue, because for the same image sometimes an LZW warning ("enblend:
error: Deflate compression support is not configured") appears, while it does
not with a different --dijkstra parameter.
Still with different dijkstra parameters there is always a severe artefact in
the resulting image.
Attached is a demonstration of layering the mapped images in GIMP
without enblend, so you can see that there are no severe problems in the
whole panorama. Another image shows the mapped images and the
corresponding vis-files and the artefact with some annotation by myself
in red.
I'm rather clueless what to do.
** Attachment added: "Results of further debugging attempts"
https://bugs.launchpad.net/enblend/+bug/1633354/+attachment/4762311/+files/2749-2762-bug-2.zip
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Enblend.
https://bugs.launchpad.net/bugs/1633354
Title:
"enblend: warning: unable to run Dijkstra optimizer" for large
panorama
Status in Enblend:
Opinion
Bug description:
Reported for Hugin on Windows (32-bit version of Hugin):
https://bugs.launchpad.net/hugin/+bug/1633352
I suspect it's an enblend bug. I'm no expert on enblend, so I could use some
help how to diagnose, isolate and fix the problem.
To manage notifications about this bug go to:
https://bugs.launchpad.net/enblend/+bug/1633354/+subscriptions
___
Mailing list: https://launchpad.net/~hugin-devs
Post to : hugin-devs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~hugin-devs
More help : https://help.launchpad.net/ListHelp
[Hugin-devs] [Bug 1633352] Re: "enblend: warning: unable to run Dijkstra optimizer" for large panorama
I also posted a bug report for enblend: https://bugs.launchpad.net/enblend/+bug/1633354 -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1633352 Title: "enblend: warning: unable to run Dijkstra optimizer" for large panorama Status in Hugin: New Bug description: I have a panorama with 14 TIFF images with 16 bit per color (in summary about 200 megapixel). The images fit rather nicely and there is no warning before conversion. But when converting these warnings appear: enblend: info: loading next image: 2749-27620005.tif 1/1 enblend: warning: unable to run Dijkstra optimizer enblend: note: seam-line end point outside of cost-image enblend: note: contour #2 of 2, segment #1 of 1, vertex #2716 of 2717 enblend: info: loading next image: 2749-27620006.tif 1/1 It's hard to find out from these texts where the actual problem is and how to fix it. I have a slight suspect that the 32-bit version might have a memory problem with such a huge (28152x3284) panorama. Up to recently I was running the 64-bit version of the 2015 edition, and I never saw such problems before, but I use 16-bit TIFF as source rather rarely. Anyway: In the resulting panorama you can clearly see two artefacts; one at the to of the panorama, the other one at the bottom. I'm attaching the relevant part of the preview to relate the position of the artefact to the images. I extracted a part of the resulting panorama, scaled it down, and I'm attaching it as part of the data for this bug. Unfortunately the material is too huge for an attaching. I tried to make a smaller test case using JPEG images, but the the problem did not exist. When trying 16bit TIFFs that were downscaled, the problem even occurred twice (using a different set of control points). To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1633352/+subscriptions ___ Mailing list: https://launchpad.net/~hugin-devs Post to : hugin-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~hugin-devs More help : https://help.launchpad.net/ListHelp
[Hugin-devs] [Bug 1633354] [NEW] "enblend: warning: unable to run Dijkstra optimizer" for large panorama
Public bug reported: Reported for Hugin on Windows (32-bit version of Hugin): https://bugs.launchpad.net/hugin/+bug/1633352 I suspect it's an enblend bug. I'm no expert on enblend, so I could use some help how to diagnose, isolate and fix the problem. ** Affects: enblend Importance: Undecided Status: New -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Enblend. https://bugs.launchpad.net/bugs/1633354 Title: "enblend: warning: unable to run Dijkstra optimizer" for large panorama Status in Enblend: New Bug description: Reported for Hugin on Windows (32-bit version of Hugin): https://bugs.launchpad.net/hugin/+bug/1633352 I suspect it's an enblend bug. I'm no expert on enblend, so I could use some help how to diagnose, isolate and fix the problem. To manage notifications about this bug go to: https://bugs.launchpad.net/enblend/+bug/1633354/+subscriptions ___ Mailing list: https://launchpad.net/~hugin-devs Post to : hugin-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~hugin-devs More help : https://help.launchpad.net/ListHelp
[Hugin-devs] [Bug 1633352] [NEW] "enblend: warning: unable to run Dijkstra optimizer" for large panorama
Public bug reported: I have a panorama with 14 TIFF images with 16 bit per color (in summary about 200 megapixel). The images fit rather nicely and there is no warning before conversion. But when converting these warnings appear: enblend: info: loading next image: 2749-27620005.tif 1/1 enblend: warning: unable to run Dijkstra optimizer enblend: note: seam-line end point outside of cost-image enblend: note: contour #2 of 2, segment #1 of 1, vertex #2716 of 2717 enblend: info: loading next image: 2749-27620006.tif 1/1 It's hard to find out from these texts where the actual problem is and how to fix it. I have a slight suspect that the 32-bit version might have a memory problem with such a huge (28152x3284) panorama. Up to recently I was running the 64-bit version of the 2015 edition, and I never saw such problems before, but I use 16-bit TIFF as source rather rarely. Anyway: In the resulting panorama you can clearly see two artefacts; one at the to of the panorama, the other one at the bottom. I'm attaching the relevant part of the preview to relate the position of the artefact to the images. I extracted a part of the resulting panorama, scaled it down, and I'm attaching it as part of the data for this bug. Unfortunately the material is too huge for an attaching. I tried to make a smaller test case using JPEG images, but the the problem did not exist. When trying 16bit TIFFs that were downscaled, the problem even occurred twice (using a different set of control points). ** Affects: hugin Importance: Undecided Status: New ** Tags: enblend ** Attachment added: "ZIP archive with project file, artefact image, log file, preview" https://bugs.launchpad.net/bugs/1633352/+attachment/4760776/+files/2749-2762-bug.zip -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1633352 Title: "enblend: warning: unable to run Dijkstra optimizer" for large panorama Status in Hugin: New Bug description: I have a panorama with 14 TIFF images with 16 bit per color (in summary about 200 megapixel). The images fit rather nicely and there is no warning before conversion. But when converting these warnings appear: enblend: info: loading next image: 2749-27620005.tif 1/1 enblend: warning: unable to run Dijkstra optimizer enblend: note: seam-line end point outside of cost-image enblend: note: contour #2 of 2, segment #1 of 1, vertex #2716 of 2717 enblend: info: loading next image: 2749-27620006.tif 1/1 It's hard to find out from these texts where the actual problem is and how to fix it. I have a slight suspect that the 32-bit version might have a memory problem with such a huge (28152x3284) panorama. Up to recently I was running the 64-bit version of the 2015 edition, and I never saw such problems before, but I use 16-bit TIFF as source rather rarely. Anyway: In the resulting panorama you can clearly see two artefacts; one at the to of the panorama, the other one at the bottom. I'm attaching the relevant part of the preview to relate the position of the artefact to the images. I extracted a part of the resulting panorama, scaled it down, and I'm attaching it as part of the data for this bug. Unfortunately the material is too huge for an attaching. I tried to make a smaller test case using JPEG images, but the the problem did not exist. When trying 16bit TIFFs that were downscaled, the problem even occurred twice (using a different set of control points). To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1633352/+subscriptions ___ Mailing list: https://launchpad.net/~hugin-devs Post to : hugin-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~hugin-devs More help : https://help.launchpad.net/ListHelp
[Hugin-devs] Antw: [Bug 1631496] Re: PTBatcherGUI.exe doen not display > 100 jobs
So if there is a problem with many jobs in the batch queue, why not implement a ring buffer, keeping the last n projects? Or why not pop up a message saying "Too many jobs, please delete some!"? I think it's just handy to have a history of all your panoramas you made; maybe I want to make some statistics from the data, even ;-) >>> zarl <1631...@bugs.launchpad.net> schrieb am 13.10.2016 um 10:55 in >>> Nachricht <20161013085528.27532.53141.mal...@wampee.canonical.com>: > Can you expand on your use case? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1631496 > > Title: > PTBatcherGUI.exe doen not display > 100 jobs > > Status in Hugin: > Invalid > > Bug description: > I have built more than 100 panoramas. When building #107, I noticed > that PTBatcherGUI.exe does only display up to #97. I don't see the > other jobs, specifically not whether they were successful. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/hugin/+bug/1631496/+subscriptions -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1631496 Title: PTBatcherGUI.exe doen not display > 100 jobs Status in Hugin: Invalid Bug description: I have built more than 100 panoramas. When building #107, I noticed that PTBatcherGUI.exe does only display up to #97. I don't see the other jobs, specifically not whether they were successful. To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1631496/+subscriptions ___ Mailing list: https://launchpad.net/~hugin-devs Post to : hugin-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~hugin-devs More help : https://help.launchpad.net/ListHelp
[Hugin-devs] Antw: [Bug 1631496] Re: PTBatcherGUI.exe doen not display > 100 jobs
Just imagine I have 120 open projects ;-) Seriously: From time to time an id like "117" appears after the "97", and obviously the 97 is not the latest project. So is there a limit of 100 jobs or so? Today most program icons take up more space than the list of jobs, so I wonder why this limit exists. >>> tmodes <1631...@bugs.launchpad.net> schrieb am 12.10.2016 um 18:17 in >>> Nachricht <20161012161719.5136.35670.mal...@chaenomeles.canonical.com>: > The last entry in the batch queue has id 97, has visible in the screenshot. > So this matches. There are not projects with higher ID. > The first column is an ID, not a consecutive number! > And again the batch queue is not intended for a permanent saving of stitched > projects. It is intended for intermediate saving of open projects. > > ** Changed in: hugin >Status: Incomplete => Invalid > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1631496 > > Title: > PTBatcherGUI.exe doen not display > 100 jobs > > Status in Hugin: > Invalid > > Bug description: > I have built more than 100 panoramas. When building #107, I noticed > that PTBatcherGUI.exe does only display up to #97. I don't see the > other jobs, specifically not whether they were successful. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/hugin/+bug/1631496/+subscriptions -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1631496 Title: PTBatcherGUI.exe doen not display > 100 jobs Status in Hugin: Invalid Bug description: I have built more than 100 panoramas. When building #107, I noticed that PTBatcherGUI.exe does only display up to #97. I don't see the other jobs, specifically not whether they were successful. To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1631496/+subscriptions ___ Mailing list: https://launchpad.net/~hugin-devs Post to : hugin-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~hugin-devs More help : https://help.launchpad.net/ListHelp
[Hugin-devs] Antw: [Bug 1631496] Re: PTBatcherGUI.exe doen not display > 100 jobs
If the finished projects were removed, I guess I wouldn't have more than 100 projects in the list. I'm attaching the saved batch and a screen shot showing the problem. At the time of reporting I should be at project #117 or so. >>> tmodes <1631...@bugs.launchpad.net> schrieb am 10.10.2016 um 20:37 in >>> Nachricht <20161010183723.5750.61467.mal...@gac.canonical.com>: > "File > Save batch" is too obvious? > Maybe the option "Remove finished project" is ticked on? Then the finished > projects will be removed from the batch at the end of processing? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1631496 > > Title: > PTBatcherGUI.exe doen not display > 100 jobs > > Status in Hugin: > Incomplete > > Bug description: > I have built more than 100 panoramas. When building #107, I noticed > that PTBatcherGUI.exe does only display up to #97. I don't see the > other jobs, specifically not whether they were successful. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/hugin/+bug/1631496/+subscriptions ** Attachment added: "Hugin-Batch.JPG" https://bugs.launchpad.net/bugs/1631496/+attachment/4759743/+files/Hugin-Batch.JPG ** Attachment added: "Hugin-Batch.ptb" https://bugs.launchpad.net/bugs/1631496/+attachment/4759744/+files/Hugin-Batch.ptb -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1631496 Title: PTBatcherGUI.exe doen not display > 100 jobs Status in Hugin: Incomplete Bug description: I have built more than 100 panoramas. When building #107, I noticed that PTBatcherGUI.exe does only display up to #97. I don't see the other jobs, specifically not whether they were successful. To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1631496/+subscriptions ___ Mailing list: https://launchpad.net/~hugin-devs Post to : hugin-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~hugin-devs More help : https://help.launchpad.net/ListHelp
[Hugin-devs] Antw: [Bug 1631486] Re: Allow selecting controlpoints within a rectangle
Actually in Windows it is "Ctrl+RightMouseButton", and the control points are removed without further confirmation. >>> tmodes <1631...@bugs.launchpad.net> schrieb am 08.10.2016 um 08:32 in >>> Nachricht <20161008063239.29961.92377.mal...@soybean.canonical.com>: > This is already implemented. Use alt+right mouse button. > Reading the help pages can also help. > > ** Changed in: hugin >Status: New => Fix Released > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1631486 > > Title: > Allow selecting controlpoints within a rectangle > > Status in Hugin: > Fix Released > > Bug description: > Enhancement request for the GUI: Allow selecting multiple control points > by spawning a rectangle with the mouse in one image. Then allow deleting all > the selected control points with one command (DEL). > This way one can more easily get rid of control points located too close > to the borders of an image. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/hugin/+bug/1631486/+subscriptions -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1631486 Title: Allow selecting controlpoints within a rectangle Status in Hugin: Fix Released Bug description: Enhancement request for the GUI: Allow selecting multiple control points by spawning a rectangle with the mouse in one image. Then allow deleting all the selected control points with one command (DEL). This way one can more easily get rid of control points located too close to the borders of an image. To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1631486/+subscriptions ___ Mailing list: https://launchpad.net/~hugin-devs Post to : hugin-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~hugin-devs More help : https://help.launchpad.net/ListHelp
[Hugin-devs] Antw: [Bug 1631486] Re: Allow selecting controlpoints within a rectangle
I completely missed that! Maybe add it as a "tip of the day", assuming it's documented elsewhere already. -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1631486 Title: Allow selecting controlpoints within a rectangle Status in Hugin: Fix Released Bug description: Enhancement request for the GUI: Allow selecting multiple control points by spawning a rectangle with the mouse in one image. Then allow deleting all the selected control points with one command (DEL). This way one can more easily get rid of control points located too close to the borders of an image. To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1631486/+subscriptions ___ Mailing list: https://launchpad.net/~hugin-devs Post to : hugin-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~hugin-devs More help : https://help.launchpad.net/ListHelp
[Hugin-devs] Antw: [Bug 1631496] Re: PTBatcherGUI.exe doen not display > 100 jobs
Last I had the 64-bit version (2015) running (on Windows), now I'm running the 32-bit version (2016). The effect looks like this: I see jobs 1 to 97, then sometime a job like 107 (latest), but not the last few jobs. Would it help to send you some file (it seems the queue is actually one file) -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1631496 Title: PTBatcherGUI.exe doen not display > 100 jobs Status in Hugin: Incomplete Bug description: I have built more than 100 panoramas. When building #107, I noticed that PTBatcherGUI.exe does only display up to #97. I don't see the other jobs, specifically not whether they were successful. To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1631496/+subscriptions ___ Mailing list: https://launchpad.net/~hugin-devs Post to : hugin-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~hugin-devs More help : https://help.launchpad.net/ListHelp
[Hugin-devs] [Bug 1631496] [NEW] PTBatcherGUI.exe doen not display > 100 jobs
Public bug reported: I have built more than 100 panoramas. When building #107, I noticed that PTBatcherGUI.exe does only display up to #97. I don't see the other jobs, specifically not whether they were successful. ** Affects: hugin Importance: Undecided Status: New ** Tags: ptbatcher -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1631496 Title: PTBatcherGUI.exe doen not display > 100 jobs Status in Hugin: New Bug description: I have built more than 100 panoramas. When building #107, I noticed that PTBatcherGUI.exe does only display up to #97. I don't see the other jobs, specifically not whether they were successful. To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1631496/+subscriptions ___ Mailing list: https://launchpad.net/~hugin-devs Post to : hugin-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~hugin-devs More help : https://help.launchpad.net/ListHelp
[Hugin-devs] [Bug 1631486] [NEW] Allow selecting controlpoints within a rectangle
Public bug reported: Enhancement request for the GUI: Allow selecting multiple control points by spawning a rectangle with the mouse in one image. Then allow deleting all the selected control points with one command (DEL). This way one can more easily get rid of control points located too close to the borders of an image. ** Affects: hugin Importance: Undecided Status: New ** Tags: enhancement -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1631486 Title: Allow selecting controlpoints within a rectangle Status in Hugin: New Bug description: Enhancement request for the GUI: Allow selecting multiple control points by spawning a rectangle with the mouse in one image. Then allow deleting all the selected control points with one command (DEL). This way one can more easily get rid of control points located too close to the borders of an image. To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1631486/+subscriptions ___ Mailing list: https://launchpad.net/~hugin-devs Post to : hugin-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~hugin-devs More help : https://help.launchpad.net/ListHelp
[Hugin-devs] [Bug 1631484] [NEW] Sort control points and select a block of them for deletion
Public bug reported: GUI Enhancement request: Allow sorting the control points by distance, and allow to select a block of control points (e.g. by click and shift- click). Then allow deletion of the selected block with one command (DEL). ** Affects: hugin Importance: Undecided Status: New ** Tags: enhancement -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1631484 Title: Sort control points and select a block of them for deletion Status in Hugin: New Bug description: GUI Enhancement request: Allow sorting the control points by distance, and allow to select a block of control points (e.g. by click and shift-click). Then allow deletion of the selected block with one command (DEL). To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1631484/+subscriptions ___ Mailing list: https://launchpad.net/~hugin-devs Post to : hugin-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~hugin-devs More help : https://help.launchpad.net/ListHelp
[Hugin-devs] [Bug 1381895] [NEW] HuginSetup_2014.0.0-rc1_64bit_Windows.exe: Exception caught (code = 0xc0000005, addr = 0x000000013F3DC15F)
Public bug reported: When trying HuginSetup_2014.0.0-rc1_64bit_Windows.exe on 64bit Windows 7, building the panorama (batch job) did not deliver a result, because the application crashed. To my understanding this happened when the "pre-distorted" images had been created already. To I guess it's enblend that crashed. From the log I extracted the last command (most likely the one that crashed): "C:/Program Files/Hugin/bin/checkpto" --generate-argfile="hugC552.tmp__1080184 - _1080192-2014.arg" "C:/Users/ULRICH~1/AppData/Local/Temp/hugC552.tmp" "C:\Program: Interrupt/Exception caught (code = 0xc005, addr = 0x00013F3DC15F) ** Affects: hugin 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/1381895 Title: HuginSetup_2014.0.0-rc1_64bit_Windows.exe: Exception caught (code = 0xc005, addr = 0x00013F3DC15F) Status in Hugin - Panorama Tools GUI: New Bug description: When trying HuginSetup_2014.0.0-rc1_64bit_Windows.exe on 64bit Windows 7, building the panorama (batch job) did not deliver a result, because the application crashed. To my understanding this happened when the "pre-distorted" images had been created already. To I guess it's enblend that crashed. From the log I extracted the last command (most likely the one that crashed): "C:/Program Files/Hugin/bin/checkpto" --generate-argfile="hugC552.tmp__1080184 - _1080192-2014.arg" "C:/Users/ULRICH~1/AppData/Local/Temp/hugC552.tmp" "C:\Program: Interrupt/Exception caught (code = 0xc005, addr = 0x00013F3DC15F) To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1381895/+subscriptions ___ Mailing list: https://launchpad.net/~hugin-devs Post to : hugin-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~hugin-devs More help : https://help.launchpad.net/ListHelp
[Hugin-devs] [Bug 1335231] Re: RC4 on Windows won't load
Unfortunately the situation hasn't changed (no newer build) until October (see bug 1381420). -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1335231 Title: RC4 on Windows won't load Status in Hugin - Panorama Tools GUI: New Bug description: On Windows 7 64 bits, I am trying to use RC4. Both 7zip versions (with or without Python) and the full installer (with Python) all refuse to load. I get a message about a missing MSVCR120D.dll. I did not try the non-python installer, I guessed I would get the same results. To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1335231/+subscriptions ___ Mailing list: https://launchpad.net/~hugin-devs Post to : hugin-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~hugin-devs More help : https://help.launchpad.net/ListHelp
[Hugin-devs] [Bug 1381420] Re: HuginSetup_2014.0.0-rc4_32bit_Windows.exe does not start on Windows 7 64bit (German)
*** This bug is a duplicate of bug 1335231 *** https://bugs.launchpad.net/bugs/1335231 Let me add for completeness: The DLLS missing was "MSVCR120D.dll", and it made no difference whether German or English was selected as installation language. Also HuginSetup_2014.0.0-rc1_64bit_Windows.exe does not have that problem. -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1381420 Title: HuginSetup_2014.0.0-rc4_32bit_Windows.exe does not start on Windows 7 64bit (German) Status in Hugin - Panorama Tools GUI: New Bug description: When installing HuginSetup_2014.0.0-rc4_32bit_Windows.exe in a German Windows 7 Professional, selecting "do not create a Desktop link", Windows 7 cannot find the application after installation finished, and when navigating to the program directory, double-clicking the application, Windows complains a DLL is missing. Sorry I cannot remember the name of the DLL, but is was something like "MS*D.DLL", where a similar DLL without the training "D" existed in the directory. My guess was it's a Microsoft C-Library localized DLL. To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1381420/+subscriptions ___ Mailing list: https://launchpad.net/~hugin-devs Post to : hugin-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~hugin-devs More help : https://help.launchpad.net/ListHelp
[Hugin-devs] [Bug 1381420] [NEW] HuginSetup_2014.0.0-rc4_32bit_Windows.exe does not start on Windows 7 64bit (German)
Public bug reported: When installing HuginSetup_2014.0.0-rc4_32bit_Windows.exe in a German Windows 7 Professional, selecting "do not create a Desktop link", Windows 7 cannot find the application after installation finished, and when navigating to the program directory, double-clicking the application, Windows complains a DLL is missing. Sorry I cannot remember the name of the DLL, but is was something like "MS*D.DLL", where a similar DLL without the training "D" existed in the directory. My guess was it's a Microsoft C-Library localized DLL. ** Affects: hugin 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/1381420 Title: HuginSetup_2014.0.0-rc4_32bit_Windows.exe does not start on Windows 7 64bit (German) Status in Hugin - Panorama Tools GUI: New Bug description: When installing HuginSetup_2014.0.0-rc4_32bit_Windows.exe in a German Windows 7 Professional, selecting "do not create a Desktop link", Windows 7 cannot find the application after installation finished, and when navigating to the program directory, double-clicking the application, Windows complains a DLL is missing. Sorry I cannot remember the name of the DLL, but is was something like "MS*D.DLL", where a similar DLL without the training "D" existed in the directory. My guess was it's a Microsoft C-Library localized DLL. To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1381420/+subscriptions ___ Mailing list: https://launchpad.net/~hugin-devs Post to : hugin-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~hugin-devs More help : https://help.launchpad.net/ListHelp
