barbq | 4 Nov 13:39
Picon

Compiling on VS2005

Hi,

I think the readme file for compiling under VS2005 is not up to date - or I am missing something.
I've downloaded the Ilm and BaseOpenEXR librarys. It appears that compiling them under release/debug does not create the deploy directory.
Moreover, the include directory that is supposed to be under the deploy also is not created, making include files for the OpenEXR a real pain.

Can someone point me to the right direction on this one?

Tnx

_______________________________________________
Openexr-devel mailing list
Openexr-devel <at> nongnu.org
http://lists.nongnu.org/mailman/listinfo/openexr-devel
Ger Hobbelt | 4 Nov 18:03
Favicon
Gravatar

Re: Compiling on VS2005

IIRC, the project files at ILM point the post-build batchfiles at a
'Deploy' directory one level below the project tree root. With 'below'
I mean that, assuming your OpenEXR tree is rooted at
/home/you/projects/OpenEXR/, the 'Deploy' is assumed to exist here:
/home/you/projects/Deploy.

(I changed all that for my own OpenEXR MSVC2005 builds, because I do
not want any project to write outside its rootdirectory 'boundary', so
I converted the batchfiles to point at
/home/you/projects/OpenEXR/Deploy/ )

Ger

On Tue, Nov 4, 2008 at 1:39 PM, barbq <barbq2000 <at> gmail.com> wrote:
> Hi,
>
> I think the readme file for compiling under VS2005 is not up to date - or I
> am missing something.
> I've downloaded the Ilm and BaseOpenEXR librarys. It appears that compiling
> them under release/debug does not create the deploy directory.
> Moreover, the include directory that is supposed to be under the deploy also
> is not created, making include files for the OpenEXR a real pain.
>
> Can someone point me to the right direction on this one?
>
> Tnx
>
>
> _______________________________________________
> Openexr-devel mailing list
> Openexr-devel <at> nongnu.org
> http://lists.nongnu.org/mailman/listinfo/openexr-devel
>
>

--

-- 
Met vriendelijke groeten / Best regards,

Ger Hobbelt

--------------------------------------------------
web:    http://www.hobbelt.com/
        http://www.hebbut.net/
mail:   ger <at> hobbelt.com
mobile: +31-6-11 120 978
--------------------------------------------------
Nicola Hoyle | 6 Nov 15:35
Picon

renaming channel name attributes / copy channel data to new channel

Hi,

Is there a simple way of renaming channel attributes?

I am reading in an exr which has channels R, G, B and I would like to write out this image to an exr file with channels image1.R, image1.G, image1.B.

Or, I suppose all I really want to do is copy the R channel data to the image1.R channel.

Thanks,
Nici

Read amazing stories to your kids on Messenger Try it Now!
_______________________________________________
Openexr-devel mailing list
Openexr-devel <at> nongnu.org
http://lists.nongnu.org/mailman/listinfo/openexr-devel
Jeremy Selan | 14 Nov 04:07
Favicon

Tiled Exr question re: dataWindowForLevel

Hello!

We've been playing around with exr mipmap tiling recently, and I'm a bit 
surprised on how dataWindowForLevel behaves.

If my test is accurate (and it may not be)...

Say you have a 2K element:
displayRect (0,0) - (2047,1555)
dataRect (768,532) - (1342,1140)

if you use exrmaketiled to make a tiled version
exrmaketiled -m -t 128 128 original.exr mipmap.exr

Reading the levels back,   (using header.displayWindow(),  
sourceFile.dataWindowForLevel(lx, ly) )

level 0 looks good:
displayRect (0,0) - (2047,1555)
dataRect (768,532) - (1342,1140)

however, level 1 is quite surprising:
(768,532) - (1055,836)

The width and height appear to be correct, (1342-768)*0.5 = 1055-768

However, the origin for level 1 (and in fact all subsequent levels) is 
the same as for level 0. (see openexr-1.6.1/IlmImf/ImfTiledMisc.cpp : 77)

Is this expected?

My intuition would have been that the dataWindows's origin would scale 
with the width. I.e, this image should read:
(384, 266) - (958,570)

I can always work around this, but I just wanted to get some expert options.

Thanks!

-- Jeremy Selan
Jeremy Selan | 14 Nov 19:56
Favicon

Addendum to Tiled Exr question re: dataWindowForLevel

Hello!

I need to make a correction to the prior email (on the intent behind 
dataWindowForLevel).

mipmap level 0:
displayRect (0,0) - (2047,1555)
dataRect (768,532) - (1342,1140)

mipmap level 1:
dataRect (returned by API) (768,532) - (1055,836)
dataRect (what I would have expected) (383,265,670,569)

(In the prior email, I screwed up the dataRect I would have expected).

-- Jeremy
Florian Kainz | 14 Nov 20:15

Re: Tiled Exr question re: dataWindowForLevel

Hi Jeremy,

you are right, the the origin of the data window does not
change from level to level.  Only the width and height of the
window change.  Mipmapped files have always behaved this way;
the corresponding code has not changed since the first version
of OpenEXR that supported tiled images in 2004.

If I remember correctly, the rationale for the current behavior
was this: if we scaled the coordinates of the upper left and lower
right corners of the data window by 0.5 while going from one level
to the next, then the size of each level would depend not only on
the level size rounding mode but also on the location of the data
window.  For example, in ROUND_DOWN mode, we'd might get:

     level   xMin    xMax    width = xMax-xMin+1
     0       5       10      6
     1       2       5       4

     level   xMin    xMax    width
     0       6       11      6   <-- same as in level 0 above
     1       3       5       3   <-- differs from level 1 above

Alternatively, we could scale the coordinates of the upper left
corner and the size of the window.  Then we'd get an unexpected
location for the lower right corner:

     level   xMin    width   xMax = xMin+width-1
     0       5       6       10
     1       2       3       4   <-- not equal to floor(10/2)

Keeping the origin the same from level to level may not be great,
but the alternatives aren't perfect either.

Florian

Gmane