Page 8 of 14
Re: Version 1.51.0 (based on Octane 1.51)
Posted: Mon Apr 07, 2014 8:43 pm
by aoktar
Silverwing, can you compare two images? One is saved from liveviewer as exr, other is from picture viewer as exr.
Re: Version 1.51.0 (based on Octane 1.51)
Posted: Tue Apr 08, 2014 6:23 am
by 00Ghz
Hey Aoktar,
Just curious. Since this new after effects plugin is supposed to come later this year, is there anyway to hook it up with the cinema 4d plugin so you get the same result like cineware?
That would be VERY COOL.
Cheers
Re: Version 1.51.0 (based on Octane 1.51)
Posted: Tue Apr 08, 2014 12:15 pm
by Silverwing
aoktar wrote:Silverwing, can you compare two images? One is saved from liveviewer as exr, other is from picture viewer as exr.
Hi Ahmet.
The thing is they look identical.
Thats a good thing as long you want to view them in a too dark fashion!
When I render in the live viewer and set the response to linear Its very dark too. So I have to set the gamma to 2.2 to get an undistorted output image as a undistorted SRGB image would look.
I am not too familiar with the pointing picture conventions. But I´m used to that the picure viewer aswell as AE and PS are applying a 2.2 Viewing LUT to the floating point renders so they don´t seem too dark (same as If I set it to linear and crank up the gamma to 2.2 in standalone or live viewer) This gives me a very undistorted way of viewing the picture as other curves introduce colors etc to the picture as they emulate things rather then give me an uncontrolled response!
If there was a sRGB response curve it would liik something like that!
As I said I´m not sure if this is a mistake of mine!
The pictures do look identical everywhere when I save Floating point what normally should make sense!
But the fact that AE for example normally Adds a Gamma 2.2 viewing LUT and the picture should look brighter but still looks dark worries me.
It does not matter wether I try it with Octane Standalone or Octane C4D.
If theres something like a header in those images telling Apps (like AE and PS) the gamma it was saved in I´d suggest going in Standalone and checking if there was the right value written in the header!
Long story short:
Just noticed differences to the 32bit work flow I have with C4D, Vray etc.
That difference is that with Octane 32bit untonemapped Images I have to reapply a Gamma in the end and with C4D, Vray I don´t.
Cheers,
Raphael
Re: Version 1.51.0 (based on Octane 1.51)
Posted: Tue Apr 08, 2014 12:30 pm
by aoktar
Hi Silverwing,
When you save from Live viewer, you have direct output of Octane render buffer. On picture viewer, i'm applying a color convertion(linear to srgb) before saving, if output buffer is linear(save image color profile). There is no possibility to change the file profile.
Also untonemapped buffer is linear output of the Renderer. Tonemapped is appyling some filters to linear buffer and clamping the color with 1.0. Linear response on tonemapped should be similar to untonemapped buffer
I hope this makes some sense
Re: Version 1.51.0 (based on Octane 1.51)
Posted: Tue Apr 08, 2014 2:33 pm
by inlifethrill
What Raphael here says is actually correct - if you choose "Render Buffer Type - Float Buffer" the render is actually pretty dark no matter the camera response curve you pick. To get it looking right in post you'd do have to add a 2.2 gamma.
However, this is probably approached from a wrong angle. You will get a correct linear result if you pick "Render Buffer Type - Float(tonemapped) AND you select a "Linear" response curve for the camera. It's the same result you would get after adding 2.2 gamma in post to any dark-looking "Float Buffer" render. So, in my understanding, "Float (tonemapped)" is THE way to go and the output (linear or tonemapped) is to be controlled by the camera response curve. You want linear output? - set the cam. response to linear. You want tonemapped - leave it as it is.
I am not sure if this is physically correct but by the "looks" of it - it is. See if the image attached will make any sense.
Dobs
Re: Version 1.51.0 (based on Octane 1.51)
Posted: Tue Apr 08, 2014 3:45 pm
by shawnfrueh
Hey Aoktar, Getting a wierd problem with 1.51.0 I am going through a decent amount of materials changing some images, When I click on a material Octane goes nuts and shows MAT CONVERT:texture_Name* and if I click the next material to quick Octane crashes. Is there a way to limit the "Converting" to only convert once until the object has actually changed? Seems redundant and does not help that it keeps crashing. I have attached a bug report.
Re: Version 1.51.0 (based on Octane 1.51)
Posted: Tue Apr 08, 2014 5:30 pm
by cyartist
1.51.1
is not as stable as 18a having similar random crashes.....will send log report on next crash.

Re: Version 1.51.0 (based on Octane 1.51)
Posted: Tue Apr 08, 2014 6:54 pm
by aoktar
00Ghz wrote:Hey Aoktar,
Just curious. Since this new after effects plugin is supposed to come later this year, is there anyway to hook it up with the cinema 4d plugin so you get the same result like cineware?
That would be VERY COOL.
Cheers
technically possible for most scenes, but i have to implement animation features for export to Standalone.
Currently c4d support the posibility of editing the current frame, afterfx plugin will support ocs and abc scenes
Re: Version 1.51.0 (based on Octane 1.51)
Posted: Tue Apr 08, 2014 7:00 pm
by aoktar
cyartist wrote:1.51.1
is not as stable as 18a having similar random crashes.....will send log report on next crash.

pls add a log file and some words about your last operations when it's occured
Re: Version 1.51.0 (based on Octane 1.51)
Posted: Wed Apr 09, 2014 2:04 pm
by Silverwing
Hi and thanks for all your responses especially shawnfrueh!
Other suggestion:
If the Untonemapped is correct that way I´d rather stay with 32bit tonemapped as shawnfrueh suggested.
Would it be possible to not clamp the Tonemapped 32bit output as I really need the above 1 values in compositing?
Cheers,
Raphael