[hugin-ptx] Re: Could not decode image error in 2019.0 beta 1
Please at least allow to display All files in the Load images window. This way panoramas that must be quickly corrected can be sent to another instance of Hugin Right click .pto file -> Send to -> Hugin. Btw. filtering images by extension is not the best method, it excludes images without extension, or with extensions such as .jpg.bk that could be created in mobile apps or other systems, and they are normal .jpg or .png files. Take a look at the file header and the file type, for .jpg this is: ÿØÿà JFIF The Windows command Findstr may be used to determine the file type. On Thursday, February 21, 2019 at 5:04:14 PM UTC+1, T. Modes wrote: > > > @Bart > Am Donnerstag, 21. Februar 2019 15:52:02 UTC+1 schrieb Bart van Andel: >> >> What you're asking is (correct me if I'm wrong) the ability to import >> images from one project into another one. That is currently not supported >> without scripting I think. Still not the same as treating the PTO as an >> image though. >> > This is already possible (without scripting): in panorame editor: > File>Merge project > -- 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/4412c0d6-1ca0-4933-8e1f-f4b0e34fedfd%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[hugin-ptx] Re: Hugin 2019.0 beta 2 released
Am Sonntag, 10. Februar 2019 11:21:00 UTC+1 schrieb T. Modes: > > Hi all, > > today we are releasing a beta 2 of Hugin 2019.0. > > > This is just a reminder for all translators. We still needs some more translations for the release. So please update your language files. TIA Currently only 4 language have 100 % coverage. de.po hu.po it.po nl.po 1624 translated messages. Then there are language with only some strings missing: fr.po 1617 translated messages, 3 fuzzy translations, 4 untranslated messages. pt_BR.po 1617 translated messages, 3 fuzzy translations, 4 untranslated messages. sk.po 1598 translated messages, 19 fuzzy translations, 7 untranslated messages. da.po 1515 translated messages, 72 fuzzy translations, 37 untranslated messages. ru.po 1456 translated messages, 76 fuzzy translations, 92 untranslated messages. And finally language which needs some more work: ca_ES.po 1431 translated messages, 119 fuzzy translations, 74 untranslated messages. ca...@valencia.po 1431 translated messages, 119 fuzzy translations, 74 untranslated messages. cs_CZ.po 1493 translated messages, 90 fuzzy translations, 41 untranslated messages. en_GB.po 71 translated messages, 17 fuzzy translations, 1536 untranslated messages. es.po 1356 translated messages, 227 fuzzy translations, 41 untranslated messages. eu.po 947 translated messages, 357 fuzzy translations, 320 untranslated messages. fi.po 747 translated messages, 475 fuzzy translations, 402 untranslated messages. ja.po 1046 translated messages, 356 fuzzy translations, 222 untranslated messages. pl.po 1249 translated messages, 221 fuzzy translations, 154 untranslated messages. ro.po 618 translated messages, 557 fuzzy translations, 449 untranslated messages. sv.po 1019 translated messages, 384 fuzzy translations, 221 untranslated messages. zh_CN.po 1284 translated messages, 204 fuzzy translations, 136 untranslated messages. zh_TW.po 1241 translated messages, 229 fuzzy translations, 154 untranslated messages. -- 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/ace9c308-f779-48a3-b705-148bedab8b46%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[hugin-ptx] Re: Could not decode image error in 2019.0 beta 1
@Bart Am Donnerstag, 21. Februar 2019 15:52:02 UTC+1 schrieb Bart van Andel: > > What you're asking is (correct me if I'm wrong) the ability to import > images from one project into another one. That is currently not supported > without scripting I think. Still not the same as treating the PTO as an > image though. > This is already possible (without scripting): in panorame editor: File>Merge project -- 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/f40e0aba-f495-42f6-99cc-a7f310366b4a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[hugin-ptx] Re: Could not decode image error in 2019.0 beta 1
This is not a bug. You're trying to load a .PTO file as if it were an image, which it is not. To take your .doc example: you can also not expect any image editor to just open a Word document because it may contain an image. Same with opening a Zip file, or any other file with some image data embedded. It just doesn't work like that. What you're asking is (correct me if I'm wrong) the ability to import images from one project into another one. That is currently not supported without scripting I think. Still not the same as treating the PTO as an image though. On Monday, 4 February 2019 15:48:33 UTC+1, Abrimaal wrote: > > [image: hugin-could-not-decode-image-from-pto-file.png] > While loading images from a .pto file, this error message is displayed. > The images have not been moved, not renamed, the are still in the same > folder as the .pto file. > The filenames and paths to images stored in the .pto file did not change. > > > -- 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/68312e6c-8ab6-46ea-abfd-7bec25760573%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [hugin-ptx] Automatic stitch scans of engineering drawings hopeless?
Hello, That all makes some sense. I can't seem to make it fix the roll and pitch at zero successfully during optimization. I'm setting the fast preview mode to Mosaic plane - is that proper? I ask because the python script stitch-scanned-images.py which one can find on github constructs a .pto that seems to use Panosphere. I'm now setting the first cols of the optimize panel to unchecked and zero for yaw and pitch and leaving the roll free (checked). The script (edit prior to optimize lets me look) seems to have sane vars viz Tx Ty and r for each image. I must be blundering some place else as it keeps saying Panorama must have positive height. I think this is from the "batch" side of things during optimization. I only get the option to set these things if I select Custom on the geometric optimization pull down. Is that the place to set the vars to participate in optimization? Thanks again for all the help. jc On Wednesday, February 20, 2019 at 9:47:04 AM UTC-6, Bruno Postle wrote: > > > > On 19 February 2019 22:59:18 GMT, jim cullen wrote: > > > >I use Equirectangular and Mosaic. I crop to max so I can cut it down > later > >in gimp. I use center fit and level. > > Equirectangular output projection will result in some curved lines. The > only projection that preserves straight lines is rectilinear, so you should > make sure that this is set for both input and output projection. > > (For a mosaic of scans, it should be possible to do it with yaw and pitch > for all input images set to zero - these introduce perspective distortion, > which is unwanted. Similarly the a,b,c lens parameters correct barrel > distortion, so these should be set to zero) > > >I think running align again will break everything on you and I'm quite > >unclear on whether re-optimize is the same as going to the > >quick preview window and running optimize. I think optimize only runs on > >the active scans in that place, or rather that is what I have it > >set to and I believe that's proper. > > The Align button does all sorts of clever things depending on context. For > this job I would just use the optimize button which only does what you tell > it to do. > > -- > Bruno > -- 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/0c7b5537-cf18-415a-aed4-e66a50c37621%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
