II believe that there is a bug:
The problem on PTGuiPro 8.3.10. was confirmed with two more failures to save the JPEG version. i.e. no success at in five tries.
Then the same project file ran perfectly PTGuiPro 8.2.1. to a fine JPEG panorama which weighs 330 MB.
IMac i5; MacOS 10.6.3; 12 GB DDR3 RAM; 750 GB free space on 1 TB HDD.
I am presently performing (slow) the test with the same project file and source images under Windows XP (on the same machine via VMWare Fusion). If unsuccessful, I may try under Windows Vista on a PC.
Michel
Thanks for the extensive testing :-) It's indeed a problem in the mac
version only, will be fixed. For the time being please use TIFF output
instead and use another application such as photoshop to convert to jpeg.
Joost
On 8-6-2010 22:26, Michel Thoby wrote:
>
> Le 8 juin 2010 � 19:05, Michel Thoby a �crit :
>>
>> Le 8 juin 2010 � 16:12, Scott W a �crit :
> --
> You received this message because you are subscribed to the Google
> Groups "PTGui" group.
> To post to this group, send email to pt...@googlegroups.com
> To unsubscribe from this group, send email to
> ptgui+un...@googlegroups.com
> Please do not add attachments to your posts; instead you may upload files at
> http://groups.google.com/group/ptgui/files
> For more options, visit this group at http://groups.google.com/group/ptgui
besides wdp (in the clutches of proprietary stagnation) there appears
to be no proper "lossy" way to store large images (except tiles, of
course).
The problem is that a file format is not very useful if it's not widely
supported.
Joost
According to what? Photoshop seems to impose the following two rules
on TIFF saving:
1. Before the actual save, it makes sure the pixel dimensions are 30k
or less in each axis.
2. During save (since the image tiles will be encoded/compressed) the
final result must be less than the 4GB limit imposed by the current
TIFF format.
TIFF will happily store up to 4GB of image samples - encoded however
you'd like - since it uses 32bit offsets. A 4GB JPEG is pretty
enormous.
Some implementations of TIFF may well be restricted in arbitrary ways,
but something using libtiff for TIFF support should work
A JFIF (JPEG file) itself is limited, I believe, to 65k pixels on each
axis... but JPEG-encoded TIFFs shouldn't have this limitation - their
limit is the size of the encoded image data, not pixel dimensions.
Note: many applications impose their own, seemingly arbitrary
restrictions - for instance, Photoshop will not provide JPEG as a Save
option if your dimensions are greater than 30,000px on either axis,
despite that being well within the JPEG/JFIF spec.
JPEG 2000 may be a good candidate, if you want extremely high
resolution lossy (or lossless) image storage - the format is modern
enough that the size limits are way outside of current needs... IIRC,
each tile needs to be <2GB, and there can be 2^32 tiles in each
JPF/JPX. However, like with other formats, few tiles fully support the
file format and instead impose arbitrary limits.
In the near future I'm hoping to see BigTIFF support finally picked up
by Adobe, but again there's a difference between supporting the format
but with some arbitrary restrictions (as Adobe almost always does) and
fully supporting it.
I don't use it frequently, but I'd be surprised if it was much slower
than compressing the same image as TIFF/ZIP, for instance. I wouldn't
be very surprised, however - JP2000 hasn't gotten much love over the
years, so I don't expect Adobe puts much into improving their file
format module.