Jump to content


Photo

Clipping Issues With Fusionviewlut And Log-lin Viewlut


  • Please log in to reply
13 replies to this topic

#1 Kenzor

Kenzor

    Member Pig

  • Adv Members
  • PipPip
  • 23 posts

Posted 15 August 2012 - 01:55 PM

I'm setting up a linear workflow for DPX files from a Quantel system. Though I feel this is a more general problem.

Basically LUT nodes and the 'Display View LUT' are producing different results with the same LUT files
The Display LUT seems to be clipping highlights (bad), while the various LUT nodes do not (good)

I use nvidea geForce gtx 285 as my graphics card. I'm not sure if this is the issue.

It is particularly bad using ARRI LogC. If you look at the A/B image bellow you can see that the sky in the A side is clipped while the B side is not.
The view of the first CineonLog1 node is clipped buy the Display view LUT. Even though the color Inspector still shows the colors to be super white (i.e. R,G, and B all have values above 1.0)

Posted Image

This is an issue because I have LUT files generated by the Quantel artist. He has designed a 'look' for the show and sent me LUT files to take me from Alexa DXP 'ARRI LogC' files to 'Rec709 with the Look'

For me to use a Linear workflow I need to find a way to go from 'Linear to 'ARRI LogC' and then 'ARRI LogC' to 'Rec709 with the Look' using a 'Display View LUT'

Fusion makes it simple to add two display LUTs but the clipping is a big problem for my workflow.
You can see in the image below that the 'Display View LUT' on the left is producing a clipped image compared to the right image using the LUT from the Quantel artist.
Posted Image

I've tried making my own LUT to using the LUT cube nodes. The clipping is still present.

Posted Image
Posted Image

Are other people having clipping issues with the view LUT ? Do I need to replace my graphics card, or is it a problem with the FUSE ?
  • KenDadeCind likes this

#2 Tilt

Tilt

    Flying Pig

  • Adv Members
  • PipPipPipPipPip
  • 2,137 posts

Posted 16 August 2012 - 12:15 AM

As a workaround you could save the tools you've used as a settings file inside the LUT directory. It won't be GPU accelerated but maybe it allows you to handle the overbright values.
I can't help with the real issue, this looks like the graphics card just doesn't support values > 1 in its shaders. Maybe the viewer's are set to 8bit? maybe a driver issue, maybe just an old graphics card? Maybe somebody else knows (tech @ eyeonline.com for sure)


#3 Kenzor

Kenzor

    Member Pig

  • Adv Members
  • PipPip
  • 23 posts

Posted 16 August 2012 - 04:13 AM

Thanks Tilt. The macro works perfectly as a LUT. I guess I'll have to live without the GPU acceleration.

I'm thinking about a graphics card upgrade. Do you see this kind of problem on your system? What card are you using?

I'll ping eyeon a mail and see what they say..

Many thanks for your help.



#4 ChadCapeland

ChadCapeland

    Flying Pig

  • Adv Members
  • PipPipPipPipPip
  • 1,975 posts

Posted 16 August 2012 - 08:34 AM

What card do you have? That might tell us right away.

Check your preferences, too. Global->Tweaks->OpenGL. Try Disabling the view LUT Shaders, or making sure you use float16 textures?

If you DO get a new video card, I might suggest a low-cost Quadro so you can use the 10-10-10-2 framebuffer. 30-bit monitors are cheap nowadays, and having a trillion colors may appeal to the types of folk like us who notice clipping and quantization.

#5 Kenzor

Kenzor

    Member Pig

  • Adv Members
  • PipPip
  • 23 posts

Posted 16 August 2012 - 10:09 AM

Disabling the view LUT Shaders kinda works. Not all view LUTs work in this mode. The log-lin view LUT is broken. But the fusion view LUT still works and seems to generate the right result. :)

So I guess the settings macro suggested by Tilt stills seems the most versatile fix. Until I upgrade.

My old nvidea geForce gtx 285 still works well for most things. When i upgrade I was going to focus on CUDA cores and a big frame buffer for my 3dsMAX work.
On paper I'll get significantly more bang for buck from a new geForce gtx 680 than from a Quadro 4000. Now I'm scratching my head...

:)

#6 Kenzor

Kenzor

    Member Pig

  • Adv Members
  • PipPip
  • 23 posts

Posted 24 September 2012 - 11:00 AM

Ok so I've been doing quite a lot of research around this issue. I've had great support from Eyeon Tech who have come up with and igneous workaround. I'm in the process of writing everything up, and I'll post here when I'm done.

I've had a chance to test a Quadro 4000. It has the same issue as my geForce gtx 285. Honestly I think the 'Lin To Log' Operation in fusion's 'Log-Lin view LUT' is broken. I'm going to post a test .comp file. When I do I'd love some feedback.

For now I've found this FUSE http://vfxpedia.com/...aV3LogC_VS.fuse which works perfectly without clipping.

#7 Kenzor

Kenzor

    Member Pig

  • Adv Members
  • PipPip
  • 23 posts

Posted 28 September 2012 - 06:58 AM

Here's a link to the clipping test.
http://www.designima...gpuClippingTest

Here's the article with all the work arounds.

http://www.designima...iles-in-fusion/

#8 SecondMan

SecondMan

    Flying Pig

  • Adv Members
  • PipPipPipPipPip
  • 1,797 posts

Posted 28 September 2012 - 11:23 AM

Nice article Kenzor, thanks a lot!

Pieter

#9 Tilt

Tilt

    Flying Pig

  • Adv Members
  • PipPipPipPipPip
  • 2,137 posts

Posted 29 September 2012 - 06:58 AM

Thanks, Ken, for digging into this. Over here (Macbook Pro), the loglin view LUT is also clipping the superwhites.

#10 Kenzor

Kenzor

    Member Pig

  • Adv Members
  • PipPip
  • 23 posts

Posted 29 September 2012 - 11:56 AM

arg.

#11 Kenzor

Kenzor

    Member Pig

  • Adv Members
  • PipPip
  • 23 posts

Posted 29 September 2012 - 12:03 PM

Thanks guys. I'm hoping we can get a bug fix for this.

#12 Tilt

Tilt

    Flying Pig

  • Adv Members
  • PipPipPipPipPip
  • 2,137 posts

Posted 29 September 2012 - 12:28 PM

I think you're right in your assumption that it's a bug in viewer LUT.
My AlexaLogC fuse doesn't clip and it's a straightforward implementation of the formula and the Viewshader API.

#13 John Paul Docherty

John Paul Docherty

    Power Pig

  • Adv Members
  • PipPipPipPip
  • 43 posts

Posted 02 October 2012 - 06:51 AM

Tested on quadro fx3600m, driver 296.70 WHQL, vista 64 business, fusion beta 1092 64 bit - clips as per Kenzor's results, see attached jpeg.

As an aside I note that if you save the script with the stacked luts then read it back in only the bottom lut is restored. No big deal, just thought I'd mention it.

--------------------

Can't seem to attach the jpeg - "attach files" in normal editor doesn't work and "attach files" in the "advanced uploader" returns an "error500". In any case the results match up to Kenzor's first post.

#14 Tilt

Tilt

    Flying Pig

  • Adv Members
  • PipPipPipPipPip
  • 2,137 posts

Posted 29 November 2012 - 11:39 AM

Should be fixed in build 1111, if I read the change log correctly:

The Log-Lin View LUT now uses the min/max ViewLUT range prefs, like Fusion View LUT, meaning it can now handle some out-of-range values.






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users