[Nuke-users] NVIDIA card for OSX

[Daniel Short]

Is anyone having good results running Nuke on OSX with an NVIDIA card?
I've got a NVIDIA GeForce GTX 780 and I'm thinking of moving to a NVIDIA
Quatro 4000K in the hopes to get less lag in my viewport when zooming and
painting.

Is anyone having good results with something like that?

-- 
Daniel Short
www.danisnotshort.com 
215.859.3220
___
Nuke-users mailing list
Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users

Re: [Nuke-users] Nuke flipbook and viewerProcess

[Michael Garrett]

I just saw your second reply. Duly noted...

On 26 September 2016 at 16:43, Michael Garrett 
wrote:

> Deke,
>
> Thanks for letting me know. Although I'm all for OCIO, I used a
> Vectorfield because I wanted to change the input colour space to log
> directly in the node and wrap it in a gizmo - simplicity and laziness won
> the day ;)
>
> To try out OCIO, I made a gizmo of OCIOColorSpace and OCIOFileTransform to
> replicate the behavior, but when registered as a viewerProcess it doesn't
> work. Is there a strict rule that I need to use a viewerLUT node for the
> log conversion? Are gizmos not supported, ie. do I need to write this
> procedurally as a function in Python?
>
> Cheers,
> Michael
>
> On 26 September 2016 at 15:27, Deke Kincaid  wrote:
>
>> Oh and when I say OCIO based, meaning it has to be in the config.ocio
>> file and setup for the script.  Not physical ocio nodes.
>>
>> On Mon, Sep 26, 2016 at 12:26 PM, Deke Kincaid 
>> wrote:
>>
>>> Nuke's new flipbook is based on the timeline/hiero viewer.  It is 100%
>>> OCIO based.  So it does not recognize any Nuke IP or viewer processes which
>>> are not in OCIO.
>>>
>>> On Thu, Sep 22, 2016 at 1:59 PM, Michael Garrett 
>>> wrote:
>>>
 I just registered a viewerProcess that is just a Vectorfield exported
 as a gizmo, but I've found it does not get picked up when I try to use
 Nuke's native flipbook. This is in 10.0v1, I will upgrade shortly to
 10.0v4.

 I am able to select the LUT from the dropdown in the flipbook options,
 but when playing back, no LUT is applied. Has anyone else experienced this?

 Thanks,
 Michael

 ___
 Nuke-users mailing list
 Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
 http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users

>>>
>>>
>>
>> ___
>> Nuke-users mailing list
>> Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
>> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
>>
>
>
___
Nuke-users mailing list
Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users

Re: [Nuke-users] Nuke flipbook and viewerProcess

[Michael Garrett]

Deke,

Thanks for letting me know. Although I'm all for OCIO, I used a Vectorfield
because I wanted to change the input colour space to log directly in the
node and wrap it in a gizmo - simplicity and laziness won the day ;)

To try out OCIO, I made a gizmo of OCIOColorSpace and OCIOFileTransform to
replicate the behavior, but when registered as a viewerProcess it doesn't
work. Is there a strict rule that I need to use a viewerLUT node for the
log conversion? Are gizmos not supported, ie. do I need to write this
procedurally as a function in Python?

Cheers,
Michael

On 26 September 2016 at 15:27, Deke Kincaid  wrote:

> Oh and when I say OCIO based, meaning it has to be in the config.ocio file
> and setup for the script.  Not physical ocio nodes.
>
> On Mon, Sep 26, 2016 at 12:26 PM, Deke Kincaid 
> wrote:
>
>> Nuke's new flipbook is based on the timeline/hiero viewer.  It is 100%
>> OCIO based.  So it does not recognize any Nuke IP or viewer processes which
>> are not in OCIO.
>>
>> On Thu, Sep 22, 2016 at 1:59 PM, Michael Garrett 
>> wrote:
>>
>>> I just registered a viewerProcess that is just a Vectorfield exported as
>>> a gizmo, but I've found it does not get picked up when I try to use Nuke's
>>> native flipbook. This is in 10.0v1, I will upgrade shortly to 10.0v4.
>>>
>>> I am able to select the LUT from the dropdown in the flipbook options,
>>> but when playing back, no LUT is applied. Has anyone else experienced this?
>>>
>>> Thanks,
>>> Michael
>>>
>>> ___
>>> Nuke-users mailing list
>>> Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
>>> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
>>>
>>
>>
>
> ___
> Nuke-users mailing list
> Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
>
___
Nuke-users mailing list
Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users

Re: [Nuke-users] Nuke flipbook and viewerProcess

[Deke Kincaid]

Oh and when I say OCIO based, meaning it has to be in the config.ocio file
and setup for the script.  Not physical ocio nodes.

On Mon, Sep 26, 2016 at 12:26 PM, Deke Kincaid 
wrote:

> Nuke's new flipbook is based on the timeline/hiero viewer.  It is 100%
> OCIO based.  So it does not recognize any Nuke IP or viewer processes which
> are not in OCIO.
>
> On Thu, Sep 22, 2016 at 1:59 PM, Michael Garrett 
> wrote:
>
>> I just registered a viewerProcess that is just a Vectorfield exported as
>> a gizmo, but I've found it does not get picked up when I try to use Nuke's
>> native flipbook. This is in 10.0v1, I will upgrade shortly to 10.0v4.
>>
>> I am able to select the LUT from the dropdown in the flipbook options,
>> but when playing back, no LUT is applied. Has anyone else experienced this?
>>
>> Thanks,
>> Michael
>>
>> ___
>> Nuke-users mailing list
>> Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
>> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
>>
>
>
___
Nuke-users mailing list
Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users

Re: [Nuke-users] Nuke flipbook and viewerProcess

[Deke Kincaid]

Nuke's new flipbook is based on the timeline/hiero viewer.  It is 100% OCIO
based.  So it does not recognize any Nuke IP or viewer processes which are
not in OCIO.

On Thu, Sep 22, 2016 at 1:59 PM, Michael Garrett 
wrote:

> I just registered a viewerProcess that is just a Vectorfield exported as a
> gizmo, but I've found it does not get picked up when I try to use Nuke's
> native flipbook. This is in 10.0v1, I will upgrade shortly to 10.0v4.
>
> I am able to select the LUT from the dropdown in the flipbook options, but
> when playing back, no LUT is applied. Has anyone else experienced this?
>
> Thanks,
> Michael
>
> ___
> Nuke-users mailing list
> Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
>
___
Nuke-users mailing list
Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users

Re: [Nuke-users] Mixing two cameras animation using local matrix

[Pat Wong]

You could use the lerp command.  which you can dissolve between 2
parameters.
check out the example below


set cut_paste_input [stack 0]
version 9.0 v8
BackdropNode {
 inputs 0
 name BackdropNode1
 tile_color 0xbc632cff
 label "blending between \n2 cameras"
 note_font_size 42
 selected true
 xpos -480
 ypos -144
 bdwidth 378
 bdheight 290
}
push $cut_paste_input
Camera2 {
 translate {1.68443 0 0}
 rotate {0 13 0}
 name CameraB
 selected true
 xpos -284
 ypos -13
}
Camera2 {
 inputs 0
 translate {-1.208439112 0 1.349363685}
 rotate {0 15 0}
 name CameraA
 selected true
 xpos -439
 ypos 1
}
Camera2 {
 inputs 0
 translate {{lerp(CameraA.translate,CameraB.translate,slider)}
{lerp(CameraA.translate,CameraB.translate,slider)}
{lerp(CameraA.translate,CameraB.translate,slider)}}
 rotate {{lerp(CameraA.rotate,CameraB.rotate,slider)}
{lerp(CameraA.rotate,CameraB.rotate,slider)}
{lerp(CameraA.rotate,CameraB.rotate,slider)}}
 scaling {{lerp(CameraA.scaling,CameraB.scaling,slider)}
{lerp(CameraA.scaling,CameraB.scaling,slider)}
{lerp(CameraA.scaling,CameraB.scaling,slider)}}
 name Camera_dissolved
 selected true
 xpos -360
 ypos 76
 addUserKnob {20 User}
 addUserKnob {7 slider}
 slider 0.515
}



On 23 September 2016 at 19:19, Bruno-Pierre Jobin  wrote:

> Got it working. Thank you Michael!
>
> --
> Bruno-Pierre Jobin
>
> On Sep 20, 2016, at 8:26 PM, Bruno-Pierre Jobin  wrote:
>
> Not sure why I’m getting this error...
>
> 
>
> On Sep 20, 2016, at 5:06 PM, Michael Habenicht  wrote:
>
> If you have a knob called mix which contains the amount of one of the
> cameras the expression should be this: Camera4.world_matrix*mix+
> Camera5.world_matrix*(1-mix)
> With this you should be able to mix between the two cmaera paths.
>
> Best regards,
> Michael
>
> On September 20, 2016 10:21:04 PM CEST, Bruno-Pierre Jobin <
> bpjo...@gmail.com> wrote:
>
> How would you guys mix animations from Camera 4 and Camera 5 into
> Camera 6? Putting Camera4.world_matrix+Camera5.world_matrix into
> local_matrix knob won’t work and I can understand why. But I’m having
> trouble figuring out what's the right expression.
>
> Thank you
>
>
>
> set cut_paste_input [stack 0]
> version 10.0 v3
> Camera2 {
> inputs 0
> translate {{curve x1021 50 x1041 150} {curve x1021 50 x1041 150} {curve
> x1021 50 x1041 150}}
> name Camera5
> selected true
> xpos -1715
> ypos 6719
> }
> Camera2 {
> inputs 0
> useMatrix true
> matrix {
> {{Camera4.world_matrix((Camera4.world_matrix-Camera4.
> world_matrix)+Camera5.world_matrix)}
> {Camera4.world_matrix((Camera4.world_matrix-Camera4.
> world_matrix)+Camera5.world_matrix)}
> {Camera4.world_matrix((Camera4.world_matrix-Camera4.
> world_matrix)+Camera5.world_matrix)}
> {Camera4.world_matrix((Camera4.world_matrix-Camera4.
> world_matrix)+Camera5.world_matrix)}}
> {{Camera4.world_matrix((Camera4.world_matrix-Camera4.
> world_matrix)+Camera5.world_matrix)}
> {Camera4.world_matrix((Camera4.world_matrix-Camera4.
> world_matrix)+Camera5.world_matrix)}
> {Camera4.world_matrix((Camera4.world_matrix-Camera4.
> world_matrix)+Camera5.world_matrix)}
> {Camera4.world_matrix((Camera4.world_matrix-Camera4.
> world_matrix)+Camera5.world_matrix)}}
> {{Camera4.world_matrix((Camera4.world_matrix-Camera4.
> world_matrix)+Camera5.world_matrix)}
> {Camera4.world_matrix((Camera4.world_matrix-Camera4.
> world_matrix)+Camera5.world_matrix)}
> {Camera4.world_matrix((Camera4.world_matrix-Camera4.
> world_matrix)+Camera5.world_matrix)}
> {Camera4.world_matrix((Camera4.world_matrix-Camera4.
> world_matrix)+Camera5.world_matrix)}}
> {{Camera4.world_matrix((Camera4.world_matrix-Camera4.
> world_matrix)+Camera5.world_matrix)}
> {Camera4.world_matrix((Camera4.world_matrix-Camera4.
> world_matrix)+Camera5.world_matrix)}
> {Camera4.world_matrix((Camera4.world_matrix-Camera4.
> world_matrix)+Camera5.world_matrix)}
> {Camera4.world_matrix((Camera4.world_matrix-Camera4.
> world_matrix)+Camera5.world_matrix)}}
> }
> name Camera6
> selected true
> xpos -1763
> ypos 6819
> }
> push $cut_paste_input
> Camera2 {
> translate {{curve i x1001 0 x1021 50} {curve i x1001 0 x1021 50} {curve
> i x1001 0 x1021 50}}
> name Camera4
> selected true
> xpos -1811
> ypos 6716
> }
> Scene {
> inputs 3
> name Scene6
> selected true
> xpos -1942
> ypos 6803
> }___
> Nuke-users mailing list
> Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
>
>
> --
> Sent from my Android tab with K-9 Mail. Please excuse my brevity.
> ___
> Nuke-users mailing list
> Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
>
>
>
> ___
> Nuke-users mailing list
> Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-use

Re: [Nuke-users] Nuke flipbook and viewerProcess

[Michael Garrett]

OK, thanks for confirming you have this issue too.

On 25 September 2016 at 07:42, Igor Majdandzic 
wrote:

> Yeah, Ive seen this with provided LUTs... haven't found a fix though.
>
> Am 22.09.2016 um 22:59 schrieb Michael Garrett:
>
> I just registered a viewerProcess that is just a Vectorfield exported as a
> gizmo, but I've found it does not get picked up when I try to use Nuke's
> native flipbook. This is in 10.0v1, I will upgrade shortly to 10.0v4.
>
> I am able to select the LUT from the dropdown in the flipbook options, but
> when playing back, no LUT is applied. Has anyone else experienced this?
>
> Thanks,
> Michael
>
>
> ___
> Nuke-users mailing listnuke-us...@support.thefoundry.co.uk, 
> http://forums.thefoundry.co.uk/http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
>
>
> --
> --
> Igor Majdandzic
> Compositing Supervisor/TD
>
> @Chimney Frankfurt
>
>
> ___
> Nuke-users mailing list
> Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
>
___
Nuke-users mailing list
Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users