I'll find a solution. There's probably other software out there which
doesn't support tiled formats so this was a misjudgement on my part.
On 3/2/26 19:38, Geoffrey LORD wrote:
> /" Yes there was a change in the TIFF output, PTGui now outputs tiled TIFF
> but there still seem to be applications which cannot read this. So it
> will be reverted in the next update."
> /
> Perhaps you could add both options, tiled and stripped to the file
> format dropdown menu? Just like JPEG VS JPEG2000 and PSD VS PSB?
>
> zoigeh.png
>
> I would feel bad if it turns out that a majority of people actually
> benefited from the tiled format and that the few that didn't were the
> only ones to complain (like me).
> I think that my images are too large to be able to be used without web
> viewer conversion, but I guess anyone doing small panos or 360 photos
> could use this new file type?
>
> Thanks again,
> Geoffrey
> Le lundi 2 mars 2026 à 19:27:43 UTC+1, Geoffrey LORD a écrit :
>
> Hi Joost,
>
> I have contacted Mike, the person behind GigaPX Tools. I have
> explained my situation to him and he has agreed that I share what he
> answered with you. I will just copy his answers as to not distort them:
>
> /I can confirm that GigaPX Tools does not currently support the
> "Tiled TIFF" format. The latest PTGui version changed the way data
> is organized inside the file: instead of saving the image in
> horizontal rows (strips), it now saves it in a grid of squares
> (tiles). My software's engine is currently optimized for the
> traditional "strip" format to ensure maximum processing speed.
> I will investigate a potential update to support this new layout. In
> the meantime, you could try to convert your PTGui exports back to a
> "traditional" TIFF using one of these free tools:
>
> *Option 1: ImageMagick *(Recommended for most cases) Use this
> command in your terminal/command prompt: magick input_tiled.tif -
> compress lzw -define tiff:tile-geometry= output_standard.tif
> Note: If the file is very large and the process fails or slows down
> your computer, use this version to limit memory usage: magick
> input_tiled.tif -limit memory 2GiB -limit map 4GiB -compress lzw -
> define tiff:tile-geometry= output_standard.tif
>
> *Option 2: tiffcp* (Fastest for extremely large files) If you have
> the libtiff tools installed, this is the most efficient method as it
> doesn't re-encode the image: tiffcp -s input_tiled.tif
> output_standard.tif
> Please let me know if the converted file works with GigaPX Tools.
> This feedback is essential for me to plan the architectural changes
> needed for the next update./
>
> To which I answered that I had actually just started testing
> ImageMagick thanks to Gemini AI recommendation and found command
> prompts that gave me some working results by essentially stripping
> metadata (I think). Here was part of my answer:
>
> /Anyways, after Gemini stopped hallucinating and forgetting context,
> it gave me these prompts that were the only ones that worked:
> magick "DSCF2745 Panorama testing bug 135 WITH MASK.tif" -alpha
> off -interlace none -define tiff:tile-geometry=0x0 -compress none
> "GigaPX_Final_Test.tif" ////////// followed by this prompt as the
> first one didn't work on its own -> ///////// magick
> "GigaPX_Final_Test.tif" +profile "*" "Clean_Image.tif"
> or
> magick input.tif -define tiff:big-tiff=yes output.tif
>
> Now I've tested your suggestions:
> Option 1: I'm still getting input file read error. You can check the
> multiple prompts that Gemini gave me that didn't work, perhaps that
> can help.
> Option 2: Perhaps I missed it while searching but I don't think
> libtiff tools works on Windows? The file I've managed to download
> feels more like a Linux thing, which I don't have installed and
> can't install on this machine. I definitely wouldn't mind the
> fastest computing solution possible; the TIFF I was trying the
> convert is like 135GB...
>
> /His last response so far was:
>
> Regarding the points you raised:
>
> /*Tiled TIFF Support:* I have identified a potential solution to
> integrate this format into GigaPX Tools more efficiently. However,
> it will take some time as I am currently committed to another
> project. Native support is definitely on the roadmap.
> *16-bit to 8-bit Conversion:* This feature was recently added and is
> still experimental. Currently, it performs a basic bit-truncation to
> prioritize processing speed on massive files. I am considering
> adding a gamma curve in a future update to improve visual contrast
> during this conversion.
> *Color Profiles (ICC): *GigaPX Tools does not currently manage color
> spaces. Even if implemented, embedding complex ICC profiles into
> thousands of small JPG tiles would significantly increase the data
> load, negatively impacting the zoom and panning performance in
> OpenSeadragon.
> *The Recommended Workflow (Quality):* Since the final output for the
> web is always 8-bit JPG, I strongly recommend exporting from PTGui
> directly as 8-bit sRGB. This allows PTGui to handle the high-quality
> color/gamma conversion. Your files will look correct in any browser,
> and GigaPX will process them much more efficiently.
> *The Tiled vs. Strip issue:* Since PTGui 13.4 now uses the Tiled
> format by default, a conversion to "Standard/Strip" TIFF is
> currently necessary for GigaPX Tools. However, ImageMagick often
> fails with 100GB+ files because it tries to cache the image in ways
> that Windows can't handle. While tiffcp is a faster alternative for
> this conversion, it requires installing third-party software
> environments on Windows, which might be inconvenient.
>
> I am working towards making GigaPX Tools compatible with these new
> PTGui exports so that these external conversion steps will no longer
> be required.
> /
>
> Hope this info helps,
> Geoffrey
> Le lundi 2 mars 2026 à 16:46:42 UTC+1, Gunter Hillmann a écrit :
>
> Hallo
>
> Habe heute auf Version 13.6. gewechselt und es funktioniert auch
> bei mir nicht. Zurück auf 13.3. ist alles wieder gut.
>
> Christoph Graf schrieb am Montag, 2. März 2026 um 11:37:45 UTC+1:
>
> Thanks, I guess this was undocumeted...(?)
>
> Have a nice time
>
> Chris
>
> PTGui Support schrieb am Montag, 2. März 2026 um 08:24:28 UTC+1:
>
> Hi Christoph,
>
> Yes there was a change in the TIFF output, PTGui now
> outputs tiled TIFF
> but there still seem to be applications which cannot
> read this. So it
> will be reverted in the next update.
>
> Kind regards,
>
> Joost Nieuwenhuijse
>
www.ptgui.com <
http://www.ptgui.com>
>
> On 3/1/26 13:31, Christoph Graf wrote:
> > Hi
> >
> > I also have issues with TIFF output from PTGUI 13.5:
> >
> > I generated a TIFF (16Bit, no comp, no alpha) with
> version 13.3, TIFF is
> > readable by SILKYPIX11.
> > Exact the same project generated the same TIFF with
> version 13.5 : TIFF
> > is unreadable by SILKYPIX11
> >
> > This is reproducable with different projects/source
> pics.
> >
> > There MUST be a change between13.3 and 13.5!
> >
> > Regards
> > Chis
> >
> > Geoffrey LORD schrieb am Donnerstag, 26. Februar 2026
> um 15:34:49 UTC+1:
> >
> > Hey,
> >
> > Just tried using the new version to see if it worked
> with my
> > camera's white balance (see post <https://
>
groups.google.com/g/ptgui/ <
https://groups.google.com/g/
> ptgui/>
> > To view this discussion visit https://
>
groups.google.com/d/msgid/ptgui/ <https://
>
groups.google.com/d/msgid/ptgui/>
> >
> e4a496cd-2ecb-45d0-8e68-0673223b055an%
40googlegroups.com
> <
http://40googlegroups.com> <https://
> >
groups.google.com/d/msgid/ptgui/ <http://
>
groups.google.com/d/msgid/ptgui/>
> >
> e4a496cd-2ecb-45d0-8e68-0673223b055an%
40googlegroups.com
> ptgui/4171a845-f083-4363-bd78-fbc5a7ec11d7n%
40googlegroups.com <https://
>
groups.google.com/d/msgid/ptgui/4171a845-f083-4363-bd78-
> fbc5a7ec11d7n%
40googlegroups.com?utm_medium=email&utm_source=footer>.