Hi again,

thanks for the clarifications so far.

On 08.12.13 23:59 schrieb Bruno Postle:
> On Sun 08-Dec-2013 at 23:42 +0100, Johannes Wienke wrote:
>> On 08.12.13 23:26 schrieb Bruno Postle:
>>> There is a reason for this, the default TIFF output is the full size of
>>> the canvas, the cropped area just represents the part of the canvas that
>>> has visible data.  JPEG doesn't support the offset parameters needed to
>>> do this, so you just get the cropped area.
>>
>> For testing I have currently generated a TIFF. How can I find the real
>> size vs. the visible size inside that file? At least from the EXIF data
>> I can't find anything and also the size of the file is a lot less when
>> using a tight crop.
> 
> Different software will respect or ignore these offsets, you can read
> them using the tiffinfo tool.

This is what I get for a panorama with crop applied in hugin. What is
the important aspect? I can't see it.

languitar@miles:~$ tiffinfo Desktop/temp/DSC_6577\ -\ DSC_6589.tif
TIFF Directory at offset 0x8 (8)
  Subfile Type: (0 = 0x0)
  Image Width: 2969 Image Length: 2769
  Resolution: 150, 150 pixels/inch
  Position: 29.8667, 7.63333
  Bits/Sample: 16
  Sample Format: unsigned integer
  Compression Scheme: LZW
  Photometric Interpretation: RGB color
  Extra Samples: 1<unassoc-alpha>
  Orientation: row 0 top, col 0 lhs
  Samples/Pixel: 4
  Rows/Strip: 88
  Planar Configuration: single image plane
  Make: NIKON CORPORATION
  Model: NIKON D7000
  Software: Hugin 2013.0.0 built by Matthieu DESILE
  Artist: Johannes Wienke
  Copyright: Johannes Wienke
  EXIFIFDOffset: 0x688
  ICC Profile: <present>, 940 bytes
TIFFReadCustomDirectory: Warning, Unknown field with tag 42033 (0xa431)
encountered.
TIFF Directory at offset 0x688 (1672)
  ExifVersion: 0x30,0x32,0x33,0x30
  DateTimeOriginal: 2013:10:28 17:04:43
  DateTimeDigitized: 2013:10:28 17:04:43
  ComponentsConfiguration: 0x1,0x2,0x3,0x0
  UserComment:
0x41,0x53,0x43,0x49,0x49,0x0,0x0,0x0,0x2d,0xa,0x50,0x72,0x6f,0x6a,0x65,0x63,0x74,0x69,0x6f,0x6e,0x3a,0x20,0x45,0x71,0x75,0x69,0x72,0x65,0x63,0x74,0x61,0x6e,0x67,0x75,0x6c,0x61,0x72,0x20,0x28,0x32,0x29,0xa,0x46,0x4f,0x56,0x3a,0x20,0x33,0x36,0x30,0x20,0x78,0x20,0x31,0x30,0x30,0xa,0x45,0x76,0x3a,0x20,0x31,0x31,0x2e,0x32,0x37
  FlashpixVersion: 0x30,0x31,0x30,0x30
  ColorSpace: 65535
  Tag 42033: 6185906

>>> There is a tool in Panotools::Script called pto2gpano that does all
>>> these calculations to tag arbitrary cropped partial panoramas as Google
>>> 'photospheres'.
>>
>> How exactly would I use this as a naive user?
> 
> It's a command-line tool and Panotools::Script is a perl library.  You
> are on OS X, so you can probably install it from CPAN using this
> command-line:
> 
>   cpan Panotools::Script
> 
> After that you need both the JPEG file and the PTO that created it, you
> can then tag the JPEG file on the command-line like so (this assumes the
> JPEG is called 'project.jpg'):
> 
>   pto2gpano project.pto

I didn't have a jpg version of that panorama, but I tried that tool on
the same tiff file used for the above output and the user comment didn't
change, still:

User Comment                    : -.Projection: Equirectangular (2).FOV:
360 x 100.Ev: 11.27

Cheers,
Johannes




Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to