Hi,

is there an option for Karma write the data window into EXRs?

Cheers,
Andreas

I think there's a bug already submitted for the data window. I'll try to raise its priority.

Thank you Mark.

Just a bit of clarification. I looked into the bug and it has to do with overscan only. AFAIK, Karma is saving the data window defined in the render settings to the .exr file.

Are you talking about the auto-crop feature? If so, please submit an RFE for it - it's unlikely to make it into H19 though.

mark
Are you talking about the auto-crop feature? If so, please submit an RFE for it - it's unlikely to make it into H19 though.

Hi Mark,

Yes, auto-crop is what I meant.

RFE filed as #116411

Thank you.

+1 for a native implementation but I quickly made an HDA for that:

https://noahhaehnel.com/blog/dynamic-data-window-and-overscan-in-solaris/ [noahhaehnel.com]

We would also love this to be added to solaris/husk. One of the first things the nuke artists asked after loading frames that were rendered via husk. "wheres my bounding boxes..."

Hi, it could sound stupid, but i dont find the autocrop otpion in the usdrender_rop ? I Am on 19.5.493

clement_arlotti
Hi, it could sound stupid, but i dont find the autocrop otpion in the usdrender_rop ? I Am on 19.5.493

Me neither.

mark

% husk
Usage: husk [options] usdfile
Build version: 19.5.441
...
  --autocrop arg                        Pattern of AOVs to be considered when 
                                        computing the data window for 
                                        auto-cropping
...

Hello! Silly question, is the pattern space separated or comma separated if I wanted to make a list of aovs?

Thanks!