Aha, I have reproduced the bug you describe.  I'll have a fix for you today.

        -- lg


On Dec 17, 2012, at 6:11 PM, Andrew Wood wrote:

> Thanks for taking a look for me!  That certainly makes sense that it works 
> like that.  I can confirm it now works for me when I do
> oiiotool /var/tmp/too.exr --ch 0,1,2 --colorconvert linear sRGB -o 
> /var/tmp/test.jpg
> 
> Perhaps I need a different thread for this, but it looks like --croptofull is 
> not playing along nicely.  When I do:
> oiiotool /var/tmp/too.exr --ch 0,1,2 --croptofull --colorconvert linear sRGB 
> -o /var/tmp/test.jpg
> after about a minute it comes back to me, saying "Maximum supported image 
> dimension is 65500 pixels."  If I understand correctly, --croptofull should 
> look at this exr,
> 
> file format version: 2, flags 0x0
> channels (type chlist):
>     A, 16-bit floating-point, sampling 1 1
>     B, 16-bit floating-point, sampling 1 1
>     G, 16-bit floating-point, sampling 1 1
>     R, 16-bit floating-point, sampling 1 1
>     depth.Z, 16-bit floating-point, sampling 1 1
> compression (type compression): zip, individual scanlines
> dataWindow (type box2i): (-40 -24) - (1960 1102)
> displayWindow (type box2i): (0 0) - (1919 1079)
> 
> and crop it to the displayWindow which is certainly small enough (and if I 
> don't use croptofull, I don't get the Maximum image dimension error)
> 
> is there something simple I'm specifying incorrectly here too?
> 
> thanks for your help!
> Andrew
> 
> 
> 
> 
> Oh, I think I understand what is happening.  oiiotool actually does its work 
> in the sequence that you specify it, so:
> 
>       oiiotool my_input.exr   \      # read my_input.exr, that's now the 
> current image
>                       -o output.jpg    \     # write the current image as a 
> JPEG -> ERROR
>                       -ch R,G,B         \      # replace current image with 
> one that's the R,G,B of the old current
> 
> So instead if you said
> 
>         oiiotool my_input.exr -ch R,G,B -o output.jpg
> 
> it should all work properly, in that you are reducing to 3 channels before 
> saving a JPEG file (which doesn't support >3 channels).
> 
> If you also tried --croptofull after the output, that would explain why it 
> also did not work as expected.
> 
> 
> 
> 
> On Dec 12, 2012, at 9:42 AM, Andrew Wood wrote:
> 
> > Hey all,
> > 
> > having some problems converting an exr to jpg
> > 
> > I think I may be misunderstanding how --ch works (built 1.1.2) --my command 
> > looks something like this:
> > 
> > >oiiotool /var/tmp/my_input.exr -o /var/tmp/output.jpg --ch R,G,B
> > oiiotool ERROR: jpeg does not support 5-channel images
> > 
> > in case it helps, the header of the exr looks like this:
> > file format version: 2, flags 0x0
> > channels (type chlist):
> >     A, 16-bit floating-point, sampling 1 1
> >     B, 16-bit floating-point, sampling 1 1
> >     G, 16-bit floating-point, sampling 1 1
> >     R, 16-bit floating-point, sampling 1 1
> >     depth.Z, 16-bit floating-point, sampling 1 1
> > compression (type compression): zip, individual scanlines
> > dataWindow (type box2i): (-85 -114) - (2139 1219)
> > displayWindow (type box2i): (0 0) - (1919 1079)
> > lineOrder (type lineOrder): increasing y
> > nuke/nkscript (type string): 
> > "/dd/shows/DEVTD/SR/9999/user/work.awood/nuke/submission.nk"
> > nuke/node_hash (type string): "8dccfb2b2dc60e20"
> > pixelAspectRatio (type float): 1
> > screenWindowCenter (type v2f): (0 0)
> > screenWindowWidth (type float): 1
> > 
> > (also, small point, I was hoping to crop down to displayWindow and ignore 
> > the dataWindow.  I tried --croptofull, but that didn't have an effect.  am 
> > I misunderstanding that one too?)
> > 
> > thanks in advance!
> > Andrew
> _______________________________________________
> Oiio-dev mailing list
> [email protected]
> http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org

--
Larry Gritz
[email protected]


_______________________________________________
Oiio-dev mailing list
[email protected]
http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org

Reply via email to