OctaneRender™ Standalone 1.35

Tue Mar 04, 2014 2:22 pm

funk wrote: You should be doing the same thing in softimage too (I dont own it so not sure how to save a 1.0 EXR). Just to confirm what I'm saying a quick google search brought this up: http://www.workshop.mintviz.com/tutoria ... explained/

Here is a quote from that page:
Gamma correction summary

If you want to save the rendered image as a 32bit file format for compositing then don’t burn in the gamma, save at gamma 1.0 (linear). Gamma correction will be automatically applied when opening the file in post for the majority of software applications including Adobe Photoshop.

Looks we both are right.
The problem i have is to use in the plugin only the untonemapped result because i need a dynamic output.
This untonemapped image isn´t affected by the imager gamma.
So a change of the imager gamma to 1.0 has no effect to the untonemapped image and the result i become and see is the same as before.
I have also to revert the result to the output from 1.34 and then i must apply self a gamma correct to match the imager gamma value.

It´s all a little bit complicated to match all needs

face

Tue Mar 04, 2014 2:28 pm

face wrote:
funk wrote: You should be doing the same thing in softimage too (I dont own it so not sure how to save a 1.0 EXR). Just to confirm what I'm saying a quick google search brought this up: http://www.workshop.mintviz.com/tutoria ... explained/

Here is a quote from that page:
Gamma correction summary

If you want to save the rendered image as a 32bit file format for compositing then don’t burn in the gamma, save at gamma 1.0 (linear). Gamma correction will be automatically applied when opening the file in post for the majority of software applications including Adobe Photoshop.
Looks we both are right.
The problem i have is to use in the plugin only the untonemapped result because i need a dynamic output.
This untonemapped image isn´t affected by the imager gamma.
So a change of the imager gamma to 1.0 has no effect to the untonemapped image and the result i become and see is the same as before.
I have also to revert the result to the output from 1.34 and then i must apply self a gamma correct to match the imager gamma value.

It´s all a little bit complicated to match all needs

face

The imager gamma has never affected the untonemapped image anyway (at least not in 1.20). If you want to see what the untonemapped EXR will look like you need to use an imager node with gamma set to 2.2 and response to LINEAR.

Octane is smart enough to save the image with a 1.0 gamma (linear) even though you are displaying it at 2.2. When you open in photoshop you will see exactly what you see on the octane screen because PS automatically applies the gamma correction to EXRs

Tue Mar 04, 2014 2:44 pm

funk wrote: The imager gamma has never affected the untonemapped image anyway (at least not in 1.20). If you want to see what the untonemapped EXR will look like you need to use an imager node with gamma set to 2.2 and response to LINEAR.

Octane is smart enough to save the image with a 1.0 gamma (linear) even though you are displaying it at 2.2. When you open in photoshop you will see exactly what you see on the octane screen because PS automatically applies the gamma correction to EXRs

That´s correct.
But i can´t show a imager gamma of 1.0 with an untonemapped image without to add a calculation.
I must also only an other calculation as before, which is a little bit more complicated.
That´s what im mean to say...

face

merid888 · Tue Mar 04, 2014 4:26 pm

hi abstrax i can't open scene .obj or alembic in the versions 1.33, 1.34 and 1.35, is the same result, error, i add image

Tue Mar 04, 2014 5:07 pm

In OSX, replacing the previous application version with the newest one (v1.33 to 1.35) didn't work. It couldn't connect to my LiveAccount. I had to use AppZapper to remove the associated files and place the standalone app in my Applications folder fresh for it to authenticate and launch. Is this expected behavior?

Tue Mar 04, 2014 11:56 pm

merid888 wrote:hi abstrax i can't open scene .obj or alembic in the versions 1.33, 1.34 and 1.35, is the same result, error, i add image

Can you send us an object file which Octane can't load?

--
Roeland

merid888 · Wed Mar 05, 2014 5:57 pm

sure, let me zip the file
regards

Wed Mar 05, 2014 8:29 pm

Octane is missing some error handlers to handle unreadable files and the Alembic file seems to be missing some parts. Which application did you use to export this file?

--
Roeland

Wed Mar 05, 2014 10:05 pm

Would it be possible to have the choice of Time and Frame Number for the timeline ? When searching a peculiar frame to compare with the original animation in case of render trouble, the Frame number is more useful than the time.

Thu Mar 06, 2014 12:40 am

I think I found a bug in the mix node.

I'm mixing 2 specular materials. one with scattering and the other was supposed to just be for reflection. However, when the mix slider is 100% the specular for the opposite material is used. IOW the second material's specular value is used with the rest of the first material, and vice versa when at 0%

Here's the example material and mix node - did I do something wrong? or is this really a bug?

SwappedSpecular.zip: Material Example; (966 Bytes) Downloaded 160 times

EDIT: I'm trying to recreate this situation from scratch and am having trouble... maybe I did something whacked?