Re: [Nuke-users] RotoPaint vs Roto

[Rich Bobo]

OK, I just found the solution!

Winaero Tweaker:
http://winaero.com/download.php?view.1796
(Click the link that says, “Download Winaero Tweaker”, right above the Donate 
button section.)

Here’s morte info with screenshots:
http://winaero.com/blog/winaero-tweaker-faq/

It works without an installation. You can check or uncheck the box for “Enable 
window raising”.

I have set my “Window activation timeout” to be 150 ms, which feels about the 
same as what I remember from SGI IRIX…


Rich

> On Apr 29, 2015, at 10:11 AM, Charles Bedwell 
>  wrote:
> 
> I found that as well, but it brings the window to the FG which isn't 
> something you always want to do.. I would prefer it worked like OS X and 
> X/11. I think you can hack the registry to make it work like that but I tried 
> it and it didn't work for me. 
> 
> I'm not sure why it works for Alpha but not the other channels. Perhaps 
> because they have bindings already. Except for Luma though...
> 
> Foundry?
> 
>  
> 
> On 29 Apr 2015, at 3:06 pm, Rich Bobo  > wrote:
> 
>> Just did a search and found the Windows 7 solution on Stack Overflow...
>> 
>> Control Panel->Ease of Access->Change How Your Mouse Works->Activate a 
>> window by hovering over it with the mouse
>> 
>> Ahhh… So much better!!   8^)
>> 
>> 
>> Rich
>> 
>> 
>> Rich Bobo
>> Senior VFX Compositor
>> Armstrong White
>> Email:  rich.b...@armstrong-white.com 
>> http://armstrong-white.com/ 
>> 
>> Email:  richb...@mac.com 
>> Mobile:  (248) 840-2665
>> Web:  http://richbobo.com/ 
>>> On Apr 29, 2015, at 9:01 AM, glouk >> > wrote:
>>> 
>>> This behaviour seems completely normal to me.
>>> 
>>> My guess is that to have this work the way you wish (which is also the way 
>>> I use it), you hace to configure your system, wether linux or windows, to 
>>> have the focus follow the mouse...
>>> 
>>> That's how I do it and it works for me.
>>> 
>>> ---
>>> "beam me up scotty"
>>> 
>>> glouk 
>>> 
>>>  
>>>  
>>> Le 29.04.2015 13:45, Daniel Hartlehnert a écrit :
>>> 
 Hm, thats strange behavior Charles. I don't have Nuke9 , so i cannot 
 check. I just had the experience that not even A works  when floating over 
 the viewer, in older Nuke versions though.
 
 Am 29.04.2015 um 13:26 schrieb Charles Bedwell:
 
> I'm using a multi monitor setup, viewer floated to second monitor, Nuke 
> 9.05 and Windows 7.
>  
> When hovering the mouse over the viewer and tapping A I get to see the 
> alpha. If I type R I get a read node. G for Grade. B for Blur. It's a 
> little inconsistent in how it works. If the mouse is back over the DAG 
> (without clicking anything) and I type A nothing happens.
>  
> I would prefer if the mouse is over the viewer and I type R G B A Y or M 
> I get to view the appropriate channel. Not just the Alpha.
> 
>  
>  
> On 29 Apr 2015, at 12:01 pm, Daniel Hartlehnert  > wrote:
> 
>> I remember i had the same behavior on windows too. Its because i always 
>> put the viewer into a separate window to move it onto the second monitor.
>> Good tip for the linux setting though, thanks.
>> 
>> Am 25.04.2015 um 16:08 schrieb Howard Jones:
>> 
>>> Just a thought...
>>> If you have floated the viewer, on a mac you will have to click on it 
>>> but on linux as long as you set focus follows mouse in the Xwindows 
>>> settings it should work.
>>> Otherwise you should have been ok.
>>>  
>>> H
>>> 
>>> On 25 Apr 2015, at 13:22, Daniel Hartlehnert >> > wrote:
>>> 
>>> 
>>> >>On 1 April 2015 at 17:04, Daniel Hartlehnert >> >>> wrote:
>>> >>
>>> >>Because it also means to constantly click in the viewer before 
>>> >>pressing "A" to make sure it has the focus. 
>>> >You don't need to click in the viewer, just have the mouse hovering 
>>> >over it.
>>>  
>>> Somehow that never worked for me. Maybe its an OS thing? I was working 
>>> on Linux at that time.
>>> ___
>>> 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/ 
>>> htt

Re: [Nuke-users] RotoPaint vs Roto

[Charles Bedwell]

I found that as well, but it brings the window to the FG which isn't something 
you always want to do.. I would prefer it worked like OS X and X/11. I think 
you can hack the registry to make it work like that but I tried it and it 
didn't work for me.

I'm not sure why it works for Alpha but not the other channels. Perhaps because 
they have bindings already. Except for Luma though...

Foundry?



On 29 Apr 2015, at 3:06 pm, Rich Bobo 
mailto:richb...@mac.com>> wrote:

Just did a search and found the Windows 7 solution on Stack Overflow...

Control Panel->Ease of Access->Change How Your Mouse Works->Activate a window 
by hovering over it with the mouse

Ahhh… So much better!!   8^)


Rich


Rich Bobo
Senior VFX Compositor
Armstrong White
Email:  rich.b...@armstrong-white.com
http://armstrong-white.com/

Email:  richb...@mac.com
Mobile:  (248) 840-2665
Web:  http://richbobo.com/

On Apr 29, 2015, at 9:01 AM, glouk mailto:gl...@glouk.org>> 
wrote:


This behaviour seems completely normal to me.

My guess is that to have this work the way you wish (which is also the way I 
use it), you hace to configure your system, wether linux or windows, to have 
the focus follow the mouse...

That's how I do it and it works for me.

---

"beam me up scotty"

glouk

[http://glouk.org/pic/signature.png]



Le 29.04.2015 13:45, Daniel Hartlehnert a écrit :

Hm, thats strange behavior Charles. I don't have Nuke9 , so i cannot check. I 
just had the experience that not even A works  when floating over the viewer, 
in older Nuke versions though.

Am 29.04.2015 um 13:26 schrieb Charles Bedwell:

I'm using a multi monitor setup, viewer floated to second monitor, Nuke 9.05 
and Windows 7.

When hovering the mouse over the viewer and tapping A I get to see the alpha. 
If I type R I get a read node. G for Grade. B for Blur. It's a little 
inconsistent in how it works. If the mouse is back over the DAG (without 
clicking anything) and I type A nothing happens.

I would prefer if the mouse is over the viewer and I type R G B A Y or M I get 
to view the appropriate channel. Not just the Alpha.



On 29 Apr 2015, at 12:01 pm, Daniel Hartlehnert 
mailto:dah...@gmx.de>> wrote:

I remember i had the same behavior on windows too. Its because i always put the 
viewer into a separate window to move it onto the second monitor.
Good tip for the linux setting though, thanks.

Am 25.04.2015 um 16:08 schrieb Howard Jones:

Just a thought...
If you have floated the viewer, on a mac you will have to click on it but on 
linux as long as you set focus follows mouse in the Xwindows settings it should 
work.
Otherwise you should have been ok.

H

On 25 Apr 2015, at 13:22, Daniel Hartlehnert 
mailto:dah...@gmx.de>> wrote:


>>On 1 April 2015 at 17:04, Daniel Hartlehnert 
>>mailto:dah...@gmx.de>> wrote:
>>
>>Because it also means to constantly click in the viewer before pressing "A" 
>>to make sure it has the focus.
>You don't need to click in the viewer, just have the mouse hovering over it.

Somehow that never worked for me. Maybe its an OS thing? I was working on Linux 
at that time.
___
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
___
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

___
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-

Re: [Nuke-users] RotoPaint vs Roto

[Daniel Hartlehnert]

Thanks alot Rich, will keep this for future reference :)

Am 29.04.2015 um 16:06 schrieb Rich Bobo:

> Just did a search and found the Windows 7 solution on Stack Overflow...
> 
> Control Panel->Ease of Access->Change How Your Mouse Works->Activate a window 
> by hovering over it with the mouse
> 
> Ahhh… So much better!!   8^)
> 
> 
> Rich
> 
> 
> Rich Bobo
> Senior VFX Compositor
> Armstrong White
> Email:  rich.b...@armstrong-white.com
> http://armstrong-white.com/
> 
> Email:  richb...@mac.com
> Mobile:  (248) 840-2665
> Web:  http://richbobo.com/
> 
>> On Apr 29, 2015, at 9:01 AM, glouk  wrote:
>> 
>> This behaviour seems completely normal to me.
>> 
>> My guess is that to have this work the way you wish (which is also the way I 
>> use it), you hace to configure your system, wether linux or windows, to have 
>> the focus follow the mouse...
>> 
>> That's how I do it and it works for me.
>> 
>> ---
>> "beam me up scotty"
>> 
>> glouk
>> 
>> 
>> 
>>  
>> Le 29.04.2015 13:45, Daniel Hartlehnert a écrit :
>> 
>>> Hm, thats strange behavior Charles. I don't have Nuke9 , so i cannot check. 
>>> I just had the experience that not even A works  when floating over the 
>>> viewer, in older Nuke versions though.
>>> 
>>> Am 29.04.2015 um 13:26 schrieb Charles Bedwell:
>>> 
 I'm using a multi monitor setup, viewer floated to second monitor, Nuke 
 9.05 and Windows 7.
  
 When hovering the mouse over the viewer and tapping A I get to see the 
 alpha. If I type R I get a read node. G for Grade. B for Blur. It's a 
 little inconsistent in how it works. If the mouse is back over the DAG 
 (without clicking anything) and I type A nothing happens.
  
 I would prefer if the mouse is over the viewer and I type R G B A Y or M I 
 get to view the appropriate channel. Not just the Alpha.
 
  
  
 On 29 Apr 2015, at 12:01 pm, Daniel Hartlehnert  wrote:
 
> I remember i had the same behavior on windows too. Its because i always 
> put the viewer into a separate window to move it onto the second monitor.
> Good tip for the linux setting though, thanks.
> 
> Am 25.04.2015 um 16:08 schrieb Howard Jones:
> 
>> Just a thought...
>> If you have floated the viewer, on a mac you will have to click on it 
>> but on linux as long as you set focus follows mouse in the Xwindows 
>> settings it should work.
>> Otherwise you should have been ok.
>>  
>> H
>> 
>> On 25 Apr 2015, at 13:22, Daniel Hartlehnert  wrote:
>> 
>> 
>> >>On 1 April 2015 at 17:04, Daniel Hartlehnert  wrote:
>> >>
>> >>Because it also means to constantly click in the viewer before 
>> >>pressing "A" to make sure it has the focus. 
>> >You don't need to click in the viewer, just have the mouse hovering 
>> >over it.
>>  
>> Somehow that never worked for me. Maybe its an OS thing? I was working 
>> on Linux at that time.
>> ___
>> 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
 ___
 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
> 
> ___
> 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] RotoPaint vs Roto

[Rich Bobo]

Just did a search and found the Windows 7 solution on Stack Overflow...

Control Panel->Ease of Access->Change How Your Mouse Works->Activate a window 
by hovering over it with the mouse

Ahhh… So much better!!   8^)


Rich


Rich Bobo
Senior VFX Compositor
Armstrong White
Email:  rich.b...@armstrong-white.com 
http://armstrong-white.com/ 

Email:  richb...@mac.com 
Mobile:  (248) 840-2665
Web:  http://richbobo.com/ 
> On Apr 29, 2015, at 9:01 AM, glouk  wrote:
> 
> This behaviour seems completely normal to me.
> 
> My guess is that to have this work the way you wish (which is also the way I 
> use it), you hace to configure your system, wether linux or windows, to have 
> the focus follow the mouse...
> 
> That's how I do it and it works for me.
> 
> ---
> "beam me up scotty"
> 
> glouk 
> 
>  
>  
> Le 29.04.2015 13:45, Daniel Hartlehnert a écrit :
> 
>> Hm, thats strange behavior Charles. I don't have Nuke9 , so i cannot check. 
>> I just had the experience that not even A works  when floating over the 
>> viewer, in older Nuke versions though.
>> 
>> Am 29.04.2015 um 13:26 schrieb Charles Bedwell:
>> 
>>> I'm using a multi monitor setup, viewer floated to second monitor, Nuke 
>>> 9.05 and Windows 7.
>>>  
>>> When hovering the mouse over the viewer and tapping A I get to see the 
>>> alpha. If I type R I get a read node. G for Grade. B for Blur. It's a 
>>> little inconsistent in how it works. If the mouse is back over the DAG 
>>> (without clicking anything) and I type A nothing happens.
>>>  
>>> I would prefer if the mouse is over the viewer and I type R G B A Y or M I 
>>> get to view the appropriate channel. Not just the Alpha.
>>> 
>>>  
>>>  
>>> On 29 Apr 2015, at 12:01 pm, Daniel Hartlehnert >> > wrote:
>>> 
 I remember i had the same behavior on windows too. Its because i always 
 put the viewer into a separate window to move it onto the second monitor.
 Good tip for the linux setting though, thanks.
 
 Am 25.04.2015 um 16:08 schrieb Howard Jones:
 
> Just a thought...
> If you have floated the viewer, on a mac you will have to click on it but 
> on linux as long as you set focus follows mouse in the Xwindows settings 
> it should work.
> Otherwise you should have been ok.
>  
> H
> 
> On 25 Apr 2015, at 13:22, Daniel Hartlehnert  > wrote:
> 
> 
> >>On 1 April 2015 at 17:04, Daniel Hartlehnert  >>> wrote:
> >>
> >>Because it also means to constantly click in the viewer before pressing 
> >>"A" to make sure it has the focus. 
> >You don't need to click in the viewer, just have the mouse hovering over 
> >it.
>  
> Somehow that never worked for me. Maybe its an OS thing? I was working on 
> Linux at that time.
> ___
> 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 
 ___
>>> 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] RotoPaint vs Roto

[glouk]

 

This behaviour seems completely normal to me. 

My guess is that to have this work the way you wish (which is also the
way I use it), you hace to configure your system, wether linux or
windows, to have the focus follow the mouse... 

That's how I do it and it works for me. 
---

"beam me up scotty"

 glouk [3]

 [4] 

Le 29.04.2015 13:45, Daniel Hartlehnert a écrit : 

> Hm, thats strange behavior Charles. I don't have Nuke9 , so i cannot check. I 
> just had the experience that not even A works when floating over the viewer, 
> in older Nuke versions though. 
> 
> Am 29.04.2015 um 13:26 schrieb Charles Bedwell: 
> 
> I'm using a multi monitor setup, viewer floated to second monitor, Nuke 9.05 
> and Windows 7. 
> 
> When hovering the mouse over the viewer and tapping A I get to see the alpha. 
> If I type R I get a read node. G for Grade. B for Blur. It's a little 
> inconsistent in how it works. If the mouse is back over the DAG (without 
> clicking anything) and I type A nothing happens. 
> 
> I would prefer if the mouse is over the viewer and I type R G B A Y or M I 
> get to view the appropriate channel. Not just the Alpha.
> 
> On 29 Apr 2015, at 12:01 pm, Daniel Hartlehnert  wrote:
> 
> I remember i had the same behavior on windows too. Its because i always put 
> the viewer into a separate window to move it onto the second monitor. 
> Good tip for the linux setting though, thanks. 
> 
> Am 25.04.2015 um 16:08 schrieb Howard Jones: 
> 
> Just a thought... 
> If you have floated the viewer, on a mac you will have to click on it but on 
> linux as long as you set focus follows mouse in the Xwindows settings it 
> should work. 
> Otherwise you should have been ok. 
> 
> H
> 
> On 25 Apr 2015, at 13:22, Daniel Hartlehnert  wrote: 
> 
>>>On 1 April 2015 at 17:04, Daniel Hartlehnert  wrote:
>>>
>>>Because it also means to constantly click in the viewer before pressing "A" 
>>>to make sure it has the focus. 
>>You don't need to click in the viewer, just have the mouse hovering over it.
> 
> Somehow that never worked for me. Maybe its an OS thing? I was working on 
> Linux at that time. ___
> Nuke-users mailing list
> Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/ [1]
> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users [2] 
> ___
> Nuke-users mailing list
> Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/ [1]
> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users [2]

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

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

Links:
--
[1] http://forums.thefoundry.co.uk/
[2] http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
[3] http://http//www.imdb.com/name/nm0522119/
[4] http://demo.glouk.org
___
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] RotoPaint vs Roto

[Daniel Hartlehnert]

I would prefer having one window spread over two monitors as well. But.
On windows, the layout was never saved correctly, resulting in a slightly too 
big or small window. I could never get it right. And i think there was a 
problem with the start bar, that couldnt be left exposed, which i wanted.
On Linux i just had a very small second monitor for the DAG, so the resolution 
was way smaller than the one with the viewer. Depending on how high or low your 
mouse was, you couldnt move the mouse over to the viewer monitor, it got stuck.

Am 29.04.2015 um 13:38 schrieb Thomas Volkmann:

> This is why I use a single window spread over two monitors as a layout. 
> Unfortunately since Nuke9 it doesn't get saved properly anymore (scales to 
> just one screen). So first thing when launching Nuke is always resizing the 
> window over both monitors I hate it (even more as it worked just fine in 
> Nuke8!) :/
>  
>> Charles Bedwell  hat am 29. April 2015 um 
>> 13:26 geschrieben:
>> 
>> I'm using a multi monitor setup, viewer floated to second monitor, Nuke 9.05 
>> and Windows 7.
>>  
>> When hovering the mouse over the viewer and tapping A I get to see the 
>> alpha. If I type R I get a read node. G for Grade. B for Blur. It's a little 
>> inconsistent in how it works. If the mouse is back over the DAG (without 
>> clicking anything) and I type A nothing happens.
>>  
>> I would prefer if the mouse is over the viewer and I type R G B A Y or M I 
>> get to view the appropriate channel. Not just the Alpha.
>> 
>>  
>>  
>> On 29 Apr 2015, at 12:01 pm, Daniel Hartlehnert  wrote:
>>> I remember i had the same behavior on windows too. Its because i always put 
>>> the viewer into a separate window to move it onto the second monitor.
>>> Good tip for the linux setting though, thanks.
>>> 
>>> Am 25.04.2015 um 16:08 schrieb Howard Jones:
>>> 
 Just a thought…
 If you have floated the viewer, on a mac you will have to click on it but 
 on linux as long as you set focus follows mouse in the Xwindows settings 
 it should work.
 Otherwise you should have been ok.
  
 H
 
> On 25 Apr 2015, at 13:22, Daniel Hartlehnert  wrote:
> 
> 
> >>On 1 April 2015 at 17:04, Daniel Hartlehnert  wrote:
> >>
> >>Because it also means to constantly click in the viewer before pressing 
> >>"A" to make sure it has the focus. 
> >You don't need to click in the viewer, just have the mouse hovering over 
> >it.
>  
> Somehow that never worked for me. Maybe its an OS thing? I was working on 
> Linux at that time.
> ___
> 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
> 
>  
>> ___
>> 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] RotoPaint vs Roto

[Charles Bedwell]

I remember trying that but something about it annoyed me so I reverted. I even 
tried setting both monitors to be treated as a single monitor in the nVidia 
control panel but (from memory so I could fullscreen it) but that was worse.

I just tried to set it up as a single spread out window but now when I drag the 
viewer tab outside the window bounds it locks the computer until I ctrl-alt-del 
it. Sigh...



On 29 Apr 2015, at 12:39 pm, Thomas Volkmann 
mailto:li...@thomasvolkmann.com>> wrote:

This is why I use a single window spread over two monitors as a layout. 
Unfortunately since Nuke9 it doesn't get saved properly anymore (scales to just 
one screen). So first thing when launching Nuke is always resizing the window 
over both monitors I hate it (even more as it worked just fine in Nuke8!) :/

Charles Bedwell 
mailto:charles.bedw...@encorepost.com>> hat am 
29. April 2015 um 13:26 geschrieben:

I'm using a multi monitor setup, viewer floated to second monitor, Nuke 9.05 
and Windows 7.

When hovering the mouse over the viewer and tapping A I get to see the alpha. 
If I type R I get a read node. G for Grade. B for Blur. It's a little 
inconsistent in how it works. If the mouse is back over the DAG (without 
clicking anything) and I type A nothing happens.

I would prefer if the mouse is over the viewer and I type R G B A Y or M I get 
to view the appropriate channel. Not just the Alpha.



On 29 Apr 2015, at 12:01 pm, Daniel Hartlehnert 
mailto:dah...@gmx.de>> wrote:
I remember i had the same behavior on windows too. Its because i always put the 
viewer into a separate window to move it onto the second monitor.
Good tip for the linux setting though, thanks.

Am 25.04.2015 um 16:08 schrieb Howard Jones:

Just a thought…
If you have floated the viewer, on a mac you will have to click on it but on 
linux as long as you set focus follows mouse in the Xwindows settings it should 
work.
Otherwise you should have been ok.

H

On 25 Apr 2015, at 13:22, Daniel Hartlehnert 
mailto:dah...@gmx.de>> wrote:


>>On 1 April 2015 at 17:04, Daniel Hartlehnert 
>>mailto:dah...@gmx.de>> wrote:
>>
>>Because it also means to constantly click in the viewer before pressing "A" 
>>to make sure it has the focus.
>You don't need to click in the viewer, just have the mouse hovering over it.

Somehow that never worked for me. Maybe its an OS thing? I was working on Linux 
at that time.
___
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


___
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] RotoPaint vs Roto

[Daniel Hartlehnert]

Hm, thats strange behavior Charles. I don't have Nuke9 , so i cannot check. I 
just had the experience that not even A works  when floating over the viewer, 
in older Nuke versions though.

Am 29.04.2015 um 13:26 schrieb Charles Bedwell:

> I'm using a multi monitor setup, viewer floated to second monitor, Nuke 9.05 
> and Windows 7.
> 
> When hovering the mouse over the viewer and tapping A I get to see the alpha. 
> If I type R I get a read node. G for Grade. B for Blur. It's a little 
> inconsistent in how it works. If the mouse is back over the DAG (without 
> clicking anything) and I type A nothing happens.
> 
> I would prefer if the mouse is over the viewer and I type R G B A Y or M I 
> get to view the appropriate channel. Not just the Alpha.
> 
>  
> 
> On 29 Apr 2015, at 12:01 pm, Daniel Hartlehnert  wrote:
> 
>> I remember i had the same behavior on windows too. Its because i always put 
>> the viewer into a separate window to move it onto the second monitor.
>> Good tip for the linux setting though, thanks.
>> 
>> Am 25.04.2015 um 16:08 schrieb Howard Jones:
>> 
>>> Just a thought…
>>> If you have floated the viewer, on a mac you will have to click on it but 
>>> on linux as long as you set focus follows mouse in the Xwindows settings it 
>>> should work.
>>> Otherwise you should have been ok.
>>> 
>>> H
>>> 
 On 25 Apr 2015, at 13:22, Daniel Hartlehnert  wrote:
 
 
 >>On 1 April 2015 at 17:04, Daniel Hartlehnert  wrote:
 >>
 >>Because it also means to constantly click in the viewer before pressing 
 >>"A" to make sure it has the focus. 
 >You don't need to click in the viewer, just have the mouse hovering over 
 >it.
  
 Somehow that never worked for me. Maybe its an OS thing? I was working on 
 Linux at that time.
 ___
 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
> ___
> 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] RotoPaint vs Roto

[Thomas Volkmann]

This is why I use a single window spread over two monitors as a layout.
Unfortunately since Nuke9 it doesn't get saved properly anymore (scales to just
one screen). So first thing when launching Nuke is always resizing the window
over both monitors I hate it (even more as it worked just fine in Nuke8!) :/
 

> Charles Bedwell  hat am 29. April 2015 um
> 13:26 geschrieben:
> 
>  I'm using a multi monitor setup, viewer floated to second monitor, Nuke 9.05
> and Windows 7.
>   
>  When hovering the mouse over the viewer and tapping A I get to see the alpha.
> If I type R I get a read node. G for Grade. B for Blur. It's a little
> inconsistent in how it works. If the mouse is back over the DAG (without
> clicking anything) and I type A nothing happens.
>   
>  I would prefer if the mouse is over the viewer and I type R G B A Y or M I
> get to view the appropriate channel. Not just the Alpha.
> 
>   
>   
>  On 29 Apr 2015, at 12:01 pm, Daniel Hartlehnert   > wrote:
> 
>  > >  I remember i had the same behavior on windows too. Its because i
>  > > always put the viewer into a separate window to move it onto the
>  > > second monitor.
> >  Good tip for the linux setting though, thanks.
> > 
> >  Am 25.04.2015 um 16:08 schrieb Howard Jones:
> > 
> > 
> >  > > >  Just a thought…
> > >  If you have floated the viewer, on a mac you will have to click
> > > on it but on linux as long as you set focus follows mouse in the Xwindows
> > > settings it should work.
> > >  Otherwise you should have been ok.
> > >   
> > >  H
> > > 
> > > 
> > >  > > > >  On 25 Apr 2015, at 13:22, Daniel
> > >  > > > > Hartlehnert mailto:dah...@gmx.de> >
> > >  > > > > wrote:
> > > > 
> > > > 
> > > >  >>On 1 April 2015 at 17:04, Daniel Hartlehnert
> > > >  >>mailto:dah...@gmx.de> > wrote:
> > > >  >>
> > > >  >>Because it also means to constantly click in the viewer
> > > >  >>before pressing "A" to make sure it has the focus. 
> > > >  >You don't need to click in the viewer, just have the mouse
> > > >  >hovering over it.
> > > >   
> > > >  Somehow that never worked for me. Maybe its an OS thing? I
> > > > was working on Linux at that time.
> > > >  ___
> > > >  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
> > 
> >  > 

 

> ___
>  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] RotoPaint vs Roto

[Charles Bedwell]

I'm using a multi monitor setup, viewer floated to second monitor, Nuke 9.05 
and Windows 7.

When hovering the mouse over the viewer and tapping A I get to see the alpha. 
If I type R I get a read node. G for Grade. B for Blur. It's a little 
inconsistent in how it works. If the mouse is back over the DAG (without 
clicking anything) and I type A nothing happens.

I would prefer if the mouse is over the viewer and I type R G B A Y or M I get 
to view the appropriate channel. Not just the Alpha.



On 29 Apr 2015, at 12:01 pm, Daniel Hartlehnert 
mailto:dah...@gmx.de>> wrote:

I remember i had the same behavior on windows too. Its because i always put the 
viewer into a separate window to move it onto the second monitor.
Good tip for the linux setting though, thanks.

Am 25.04.2015 um 16:08 schrieb Howard Jones:

Just a thought…
If you have floated the viewer, on a mac you will have to click on it but on 
linux as long as you set focus follows mouse in the Xwindows settings it should 
work.
Otherwise you should have been ok.

H

On 25 Apr 2015, at 13:22, Daniel Hartlehnert 
mailto:dah...@gmx.de>> wrote:


>>On 1 April 2015 at 17:04, Daniel Hartlehnert 
>>mailto:dah...@gmx.de>> wrote:
>>
>>Because it also means to constantly click in the viewer before pressing "A" 
>>to make sure it has the focus.
>You don't need to click in the viewer, just have the mouse hovering over it.

Somehow that never worked for me. Maybe its an OS thing? I was working on Linux 
at that time.
___
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
___
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] RotoPaint vs Roto

[Daniel Hartlehnert]

I remember i had the same behavior on windows too. Its because i always put the 
viewer into a separate window to move it onto the second monitor.
Good tip for the linux setting though, thanks.

Am 25.04.2015 um 16:08 schrieb Howard Jones:

> Just a thought…
> If you have floated the viewer, on a mac you will have to click on it but on 
> linux as long as you set focus follows mouse in the Xwindows settings it 
> should work.
> Otherwise you should have been ok.
> 
> H
> 
>> On 25 Apr 2015, at 13:22, Daniel Hartlehnert  wrote:
>> 
>> 
>> >>On 1 April 2015 at 17:04, Daniel Hartlehnert  wrote:
>> >>
>> >>Because it also means to constantly click in the viewer before pressing 
>> >>"A" to make sure it has the focus. 
>> >You don't need to click in the viewer, just have the mouse hovering over it.
>>  
>> Somehow that never worked for me. Maybe its an OS thing? I was working on 
>> Linux at that time.
>> ___
>> 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] RotoPaint vs Roto

[Howard Jones]

Just a thought…
If you have floated the viewer, on a mac you will have to click on it but on 
linux as long as you set focus follows mouse in the Xwindows settings it should 
work.
Otherwise you should have been ok.

H

> On 25 Apr 2015, at 13:22, Daniel Hartlehnert  wrote:
> 
> 
> >>On 1 April 2015 at 17:04, Daniel Hartlehnert  wrote:
> >>
> >>Because it also means to constantly click in the viewer before pressing "A" 
> >>to make sure it has the focus. 
> >You don't need to click in the viewer, just have the mouse hovering over it.
>  
> Somehow that never worked for me. Maybe its an OS thing? I was working on 
> Linux at that time.
> ___
> 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: Aw: Re: [Nuke-users] RotoPaint vs Roto

[Bruno-Pierre Jobin]

On Linux its an OS thing. You need to activate the "focus window on mouse move" 
or something like that in the windows preferences. 

--
Bruno-Pierre Jobin

> On Apr 25, 2015, at 8:22 AM, Daniel Hartlehnert  wrote:
> 
> 
> >>On 1 April 2015 at 17:04, Daniel Hartlehnert  wrote:
> >>
> >>Because it also means to constantly click in the viewer before pressing "A" 
> >>to make sure it has the focus. 
> >You don't need to click in the viewer, just have the mouse hovering over it.
>  
> Somehow that never worked for me. Maybe its an OS thing? I was working on 
> Linux at that time.
> ___
> 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

Aw: Re: [Nuke-users] RotoPaint vs Roto

[Daniel Hartlehnert]

>>On 1 April 2015 at 17:04, Daniel Hartlehnert  wrote:
>>
>>Because it also means to constantly click in the viewer before pressing "A" to make sure it has the focus. 
>You don't need to click in the viewer, just have the mouse hovering over it.
 
Somehow that never worked for me. Maybe its an OS thing? I was working on Linux at that time.
___
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] RotoPaint vs Roto

[Diogo Girondi]

Hi Frank,

Nice to meet you mate. I'm aware of the auto label functionality and
channel indicators in Nuke but reading the channels a node is affecting on
its label or indicators isn't the same as figuring out what that node is
actually doing, hence the request for a Roto only node at that time. It's
faster to recognize what is shape/roto only from what could be or include
painting which tends to bog down scripts.

Back in the day Nuke was moving from a Bezier node where we had a single
shape per node and a alpha version of a Paint only node that was far from
great, to a "do it all" RotoPaint node. People felt divided and the
solution came in the form of a streamlined Roto only version of the
RotoPaint that was introduced into Nuke 6.1.

My point was that for what I know there should be no difference between the
two in terms of performance or functionality while talking exclusively
about shapes (bezier, b-spline, open splines) since they are the same and
share the same bits of code.

As for performance, I think it's fair to say that the fewer channels a Node
> operates on the faster that Node will be.


I would say it's more than fair, it's pretty much a certainty :)


Cheers,
Diogo


On Sat, Apr 18, 2015 at 5:17 AM, Frank Harrison 
wrote:

> Hey
>
> On 1 April 2015 at 17:04, Daniel Hartlehnert  wrote:
>
>> Because it also means to constantly click in the viewer before pressing
>> "A" to make sure it has the focus.
>>
> You don't need to click in the viewer, just have the mouse hovering over
> it.
>
>
> On 18 April 2015 at 05:55, Diogo Girondi  wrote:
>
>> since you can't actually differentiate what is purely masks from what is
>> paint or both.
>
> Just in case you weren't aware, the channels affected are rendered on the
> Nodes in the DAG. This is done as color-bars on the bottom left of the
> Node.
>
> For example, in the image below you can see that ColorWheel1 is providing
> RGBA, RotoPaint1 is providing *and* potentially affecting RGBA, Roto1 is
> only affecting A but providing RGBA and Roto2 is only providing/affecting A.
>
> ​
> As for performance, I think it's fair to say that the fewer channels a
> Node operates on the faster that Node will be.
> ​
> --
> Frank Harrison
> Senior Nuke Software Engineer
> The Foundry
> Tel: +44 (0)20 7968 6828 - Fax: +44 (0)20 7930 8906
> Web: www.thefoundry.co.uk
> Email: frank.harri...@thefoundry.co.uk
>
> ___
> 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] RotoPaint vs Roto

[Frank Harrison]

Hey

On 1 April 2015 at 17:04, Daniel Hartlehnert  wrote:

> Because it also means to constantly click in the viewer before pressing
> "A" to make sure it has the focus.
>
You don't need to click in the viewer, just have the mouse hovering over
it.


On 18 April 2015 at 05:55, Diogo Girondi  wrote:

> since you can't actually differentiate what is purely masks from what is
> paint or both.

Just in case you weren't aware, the channels affected are rendered on the
Nodes in the DAG. This is done as color-bars on the bottom left of the
Node.

For example, in the image below you can see that ColorWheel1 is providing
RGBA, RotoPaint1 is providing *and* potentially affecting RGBA, Roto1 is
only affecting A but providing RGBA and Roto2 is only providing/affecting A.

​
As for performance, I think it's fair to say that the fewer channels a Node
operates on the faster that Node will be.
​
-- 
Frank Harrison
Senior Nuke Software Engineer
The Foundry
Tel: +44 (0)20 7968 6828 - Fax: +44 (0)20 7930 8906
Web: www.thefoundry.co.uk
Email: frank.harri...@thefoundry.co.uk
___
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] RotoPaint vs Roto

[Diogo Girondi]

This was requested (by myself and others) during a beta when moving from
the old Bezier node to the "new" RotoPaint, it was purely a request for
workflow/customization and readability reasons.

Using a RotoPaint for masks implies on more clicking around, prevents you
from having a default that works for both scenarios, gives you more UI
itens than you actually need and makes your DAG less readable since you
can't actually differentiate what is purely masks from what is paint or
both.

There should be no difference between the two in terms of performance.

On Wed, Apr 1, 2015 at 1:04 PM, Daniel Hartlehnert  wrote:

> Hi,
>
> Am 01.04.2015 um 12:55 schrieb Frank Harrison:
>
> Hey,
>
> just because i am too lazy to switch the viewer to display the alpha
>> channel
>>
> Did you know that when you press the "A" key in the viewer it allows you
> to switch between Alpha and RGB? :)
>
>
> Yes, i know this. Even too lazy to do "that". Go figure ;O
>  When i think about it, it might also be due to the context sensitive
> nature of the shortcuts. Because it also means to constantly click in the
> viewer before pressing "A" to make sure it has the focus. Don't get me
> wrong, context sensitive is cool, its just the way i work it seems.
>
>
> When you mention expressions, do you mean expressions on the Roto/Paint
>> nodes themselves, or also generally in the script?
>>
> In this case Roto/Paint specifically. I've seen scripts with expressions
> on most of the points on most of the shapes.
>
>
> Ah ok, i rarely did that in the past. I only routinely expression link the
> transforms of a tracker to the roto transform tab, but not to individual
> points.
>
>
>
>
>
> ___
> 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] RotoPaint vs Roto

[Daniel Hartlehnert]

Hi,

Am 01.04.2015 um 12:55 schrieb Frank Harrison:

> Hey,
> 
> just because i am too lazy to switch the viewer to display the alpha channel
> Did you know that when you press the "A" key in the viewer it allows you to 
> switch between Alpha and RGB? :)

Yes, i know this. Even too lazy to do "that". Go figure ;O
 When i think about it, it might also be due to the context sensitive nature of 
the shortcuts. Because it also means to constantly click in the viewer before 
pressing "A" to make sure it has the focus. Don't get me wrong, context 
sensitive is cool, its just the way i work it seems.
> 
> When you mention expressions, do you mean expressions on the Roto/Paint nodes 
> themselves, or also generally in the script?
> In this case Roto/Paint specifically. I've seen scripts with expressions on 
> most of the points on most of the shapes.

Ah ok, i rarely did that in the past. I only routinely expression link the 
transforms of a tracker to the roto transform tab, but not to individual points.




___
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] RotoPaint vs Roto

[Randy Little]

So I was right. Accept for overhead part  (kidding joking, smart ass alert)

I just remember a lot of people asking in like V5(or 6?) when the first new
paint node was added that  a clean roto node exist, and as some point it
was added.)

Randy S. Little
http://www.rslittle.com/
http://www.imdb.com/name/nm2325729/



On Wed, Apr 1, 2015 at 6:55 AM, Frank Harrison 
wrote:

> Hey,
>
> just because i am too lazy to switch the viewer to display the alpha
>> channel
>>
> Did you know that when you press the "A" key in the viewer it allows you
> to switch between Alpha and RGB? :)
>
> On a side node: If i, lets say use a blur node set to use rgba, but
>> downstream only use alpha from that (i.e. as a mask input on another node),
>> will Nuke be slower because it blurs rgba instead of alpha only? Or will
>> only the requested channels be calculated upstream?
>
> It should just operate on the Alpha channel and if the blur node is just
> operating on Alpha then that should be all that it operates on and all that
> it *directly* supplies to its down stream Nodes. If you're viewing the
> Blur with RGB enable in the viewer then you'll pull those channels through
> the blur.
>
> So I guess you might (depending on you graph) be able to work faster if
> you operate on a channel at a time.
>
> When you mention expressions, do you mean expressions on the Roto/Paint
>> nodes themselves, or also generally in the script?
>>
> In this case Roto/Paint specifically. I've seen scripts with expressions
> on most of the points on most of the shapes.
>
> And what would you consider excessive? :)
>>
> Well, expressions are an incredibly useful feature and help us do lots of
> very cool stuff very quickly, but, by their very nature Nuke can not work
> out when the value that an expression evaluates to has changed; this means
> that Nuke has to evaluate Nodes (and sub-graphs with Nodes) with
> expressions more often, which can lead to slowdowns, sometimes.
>
> I hope that answers your questions :)
>
> F.
>
>
> On 1 April 2015 at 10:37, Daniel Hartlehnert  wrote:
>
>> Oh, i forgot to add that i have only worked with v7 so far, no experience
>> with 8 or 9 yet.
>>
>>
>> Am 01.04.2015 um 11:17 schrieb Frank Harrison:
>>
>> Hey Daniel,
>>
>> That's fascinating to hear, I wonder if it does relate to the bumber of
>> channels they use by default?
>>
>> There are various things you can do to make Roto and Paint appear slower,
>> such as use excessive numbers of expessions or view a node downstream of a
>> Roto with lots of comptationally expensive Nodes in between.
>>
>> If anyone does have any reproducable performance metrics or scripts
>> they'd like to share we'd love to see them, add them to our autotests and
>> make it a better experiance :)
>>
>> F.
>>
>> On Wednesday, April 1, 2015, Daniel Hartlehnert  wrote:
>>
>>> Hi Frank,
>>>
>>> thanks for an "official" answer :)
>>>
>>> My experience differs though, so i don't have any "metric" to base it
>>> on, Marten. Only common sense and experience. Therefore my answer i gave
>>> before.
>>>
>>>
>>> Am 01.04.2015 um 10:00 schrieb Frank Harrison:
>>>
>>> Hey Guys,
>>>
>>> Under the hood the two Nodes are exactly the same, they just cater to
>>> different work flows.
>>>
>>> As a result, the only time RotoPaint should be slower is when you have
>>> paint/clone/smear strokes interleaved with bezier/bspine shapes.
>>>
>>> F.
>>>
>>> On Wednesday, April 1, 2015, Daniel Hartlehnert  wrote:
>>>
 Isn't it obvious? Roto node has much less functionality, hence it its
 much faster to process and has a smaller memory footprint. Bugs from the
 paint part of Rotopaint cannot destroy your script, Rotopaints with more
 than 100 strokes tend to slow down your script (if i ever see that progress
 bar from a rotopaint node i start to ...)
 Rotopaints are responsible for most broken scripts in my experience.

 Wyh would you use Rotopaint if you don't actually paint?

 Am 31.03.2015 um 20:14 schrieb Simon Björk:

 For some reason I always reach for the RotoPaint node instead of the
 regular Roto node. I'm not sure why I got into this habit, but it might be
 (if I'm not mistaken) that the RotoPaint node was introduced before the
 Roto node back in 6.0.

 Anyway, does anyone know if there's a difference in
 performance/stability when doing just regular roto? We've all had or
 problems with the RotoPaint node over the last couple of versions, but I
 have never actually compared the two nodes to see if one is "better" than
 the other.





 ---
 Simon Björk
 Compositor/TD

 +46 (0)70-2859503
 www.bjorkvisuals.com
  ___
 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] RotoPaint vs Roto

[Howard Jones]

That rotopaint render bar i think is a lie. That is it comes up but isn't 
necessarily the bottleneck. I've seen scrips where people frame blend the 
output of an rp node (never a good idea) so the Rotopaint bar takes ages but of 
course it's everything above the node as well that is dragging its feet. Just 
doesn't pop up a render bar. 

Howard

> On 1 Apr 2015, at 10:17 am, Frank Harrison  wrote:
> 
> Hey Daniel,
> 
> That's fascinating to hear, I wonder if it does relate to the bumber of 
> channels they use by default? 
> 
> There are various things you can do to make Roto and Paint appear slower, 
> such as use excessive numbers of expessions or view a node downstream of a 
> Roto with lots of comptationally expensive Nodes in between.
> 
> If anyone does have any reproducable performance metrics or scripts they'd 
> like to share we'd love to see them, add them to our autotests and make it a 
> better experiance :)
> 
> F.
> 
>> On Wednesday, April 1, 2015, Daniel Hartlehnert  wrote:
>> Hi Frank,
>> 
>> thanks for an "official" answer :)
>> 
>> My experience differs though, so i don't have any "metric" to base it on, 
>> Marten. Only common sense and experience. Therefore my answer i gave before.
>> 
>> 
>>> Am 01.04.2015 um 10:00 schrieb Frank Harrison:
>>> 
>>> Hey Guys,
>>> 
>>> Under the hood the two Nodes are exactly the same, they just cater to 
>>> different work flows.
>>> 
>>> As a result, the only time RotoPaint should be slower is when you have 
>>> paint/clone/smear strokes interleaved with bezier/bspine shapes.
>>> 
>>> F.
>>> 
 On Wednesday, April 1, 2015, Daniel Hartlehnert  wrote:
 Isn't it obvious? Roto node has much less functionality, hence it its much 
 faster to process and has a smaller memory footprint. Bugs from the paint 
 part of Rotopaint cannot destroy your script, Rotopaints with more than 
 100 strokes tend to slow down your script (if i ever see that progress bar 
 from a rotopaint node i start to ...)
 Rotopaints are responsible for most broken scripts in my experience.
 
 Wyh would you use Rotopaint if you don't actually paint?
 
> Am 31.03.2015 um 20:14 schrieb Simon Björk:
> 
> For some reason I always reach for the RotoPaint node instead of the 
> regular Roto node. I'm not sure why I got into this habit, but it might 
> be (if I'm not mistaken) that the RotoPaint node was introduced before 
> the Roto node back in 6.0.
> 
> Anyway, does anyone know if there's a difference in performance/stability 
> when doing just regular roto? We've all had or problems with the 
> RotoPaint node over the last couple of versions, but I have never 
> actually compared the two nodes to see if one is "better" than the other.
> 
> 
> 
> 
> 
> ---
> Simon Björk
> Compositor/TD
> 
> +46 (0)70-2859503
> www.bjorkvisuals.com
> ___
> 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
>>> 
>>> 
>>> -- 
>>> Frank Harrison
>>> Senior Nuke Software Engineer
>>> The Foundry
>>> Tel: +44 (0)20 7968 6828 - Fax: +44 (0)20 7930 8906 
>>> Web: www.thefoundry.co.uk
>>> Email: frank.harri...@thefoundry.co.uk 
>>> 
>>> ___
>>> 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
> 
> 
> -- 
> Frank Harrison
> Senior Nuke Software Engineer
> The Foundry
> Tel: +44 (0)20 7968 6828 - Fax: +44 (0)20 7930 8906 
> Web: www.thefoundry.co.uk
> Email: frank.harri...@thefoundry.co.uk  
> 
> ___
> 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] RotoPaint vs Roto

[Frank Harrison]

Hey,

just because i am too lazy to switch the viewer to display the alpha channel
>
Did you know that when you press the "A" key in the viewer it allows you to
switch between Alpha and RGB? :)

On a side node: If i, lets say use a blur node set to use rgba, but
> downstream only use alpha from that (i.e. as a mask input on another node),
> will Nuke be slower because it blurs rgba instead of alpha only? Or will
> only the requested channels be calculated upstream?

It should just operate on the Alpha channel and if the blur node is just
operating on Alpha then that should be all that it operates on and all that
it *directly* supplies to its down stream Nodes. If you're viewing the Blur
with RGB enable in the viewer then you'll pull those channels through the
blur.

So I guess you might (depending on you graph) be able to work faster if you
operate on a channel at a time.

When you mention expressions, do you mean expressions on the Roto/Paint
> nodes themselves, or also generally in the script?
>
In this case Roto/Paint specifically. I've seen scripts with expressions on
most of the points on most of the shapes.

And what would you consider excessive? :)
>
Well, expressions are an incredibly useful feature and help us do lots of
very cool stuff very quickly, but, by their very nature Nuke can not work
out when the value that an expression evaluates to has changed; this means
that Nuke has to evaluate Nodes (and sub-graphs with Nodes) with
expressions more often, which can lead to slowdowns, sometimes.

I hope that answers your questions :)

F.


On 1 April 2015 at 10:37, Daniel Hartlehnert  wrote:

> Oh, i forgot to add that i have only worked with v7 so far, no experience
> with 8 or 9 yet.
>
>
> Am 01.04.2015 um 11:17 schrieb Frank Harrison:
>
> Hey Daniel,
>
> That's fascinating to hear, I wonder if it does relate to the bumber of
> channels they use by default?
>
> There are various things you can do to make Roto and Paint appear slower,
> such as use excessive numbers of expessions or view a node downstream of a
> Roto with lots of comptationally expensive Nodes in between.
>
> If anyone does have any reproducable performance metrics or scripts they'd
> like to share we'd love to see them, add them to our autotests and make
> it a better experiance :)
>
> F.
>
> On Wednesday, April 1, 2015, Daniel Hartlehnert  wrote:
>
>> Hi Frank,
>>
>> thanks for an "official" answer :)
>>
>> My experience differs though, so i don't have any "metric" to base it on,
>> Marten. Only common sense and experience. Therefore my answer i gave before.
>>
>>
>> Am 01.04.2015 um 10:00 schrieb Frank Harrison:
>>
>> Hey Guys,
>>
>> Under the hood the two Nodes are exactly the same, they just cater to
>> different work flows.
>>
>> As a result, the only time RotoPaint should be slower is when you have
>> paint/clone/smear strokes interleaved with bezier/bspine shapes.
>>
>> F.
>>
>> On Wednesday, April 1, 2015, Daniel Hartlehnert  wrote:
>>
>>> Isn't it obvious? Roto node has much less functionality, hence it its
>>> much faster to process and has a smaller memory footprint. Bugs from the
>>> paint part of Rotopaint cannot destroy your script, Rotopaints with more
>>> than 100 strokes tend to slow down your script (if i ever see that progress
>>> bar from a rotopaint node i start to ...)
>>> Rotopaints are responsible for most broken scripts in my experience.
>>>
>>> Wyh would you use Rotopaint if you don't actually paint?
>>>
>>> Am 31.03.2015 um 20:14 schrieb Simon Björk:
>>>
>>> For some reason I always reach for the RotoPaint node instead of the
>>> regular Roto node. I'm not sure why I got into this habit, but it might be
>>> (if I'm not mistaken) that the RotoPaint node was introduced before the
>>> Roto node back in 6.0.
>>>
>>> Anyway, does anyone know if there's a difference in
>>> performance/stability when doing just regular roto? We've all had or
>>> problems with the RotoPaint node over the last couple of versions, but I
>>> have never actually compared the two nodes to see if one is "better" than
>>> the other.
>>>
>>>
>>>
>>>
>>>
>>> ---
>>> Simon Björk
>>> Compositor/TD
>>>
>>> +46 (0)70-2859503
>>> www.bjorkvisuals.com
>>>  ___
>>> 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
>>>
>>>
>>>
>>
>> --
>> Frank Harrison
>> Senior Nuke Software Engineer
>> The Foundry
>> Tel: +44 (0)20 7968 6828 - Fax: +44 (0)20 7930 8906
>> Web: www.thefoundry.co.uk
>> Email: frank.harri...@thefoundry.co.uk
>>
>> ___
>> 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
>>
>>
>>
>
> --
> Frank Harrison
> Senior Nuke Software Engineer
> The Foundry
> Tel: +44 (0)20 7968 6828 - Fax: +44

Re: [Nuke-users] RotoPaint vs Roto

[Daniel Hartlehnert]

Oh, i forgot to add that i have only worked with v7 so far, no experience with 
8 or 9 yet.


Am 01.04.2015 um 11:17 schrieb Frank Harrison:

> Hey Daniel,
> 
> That's fascinating to hear, I wonder if it does relate to the bumber of 
> channels they use by default? 
> 
> There are various things you can do to make Roto and Paint appear slower, 
> such as use excessive numbers of expessions or view a node downstream of a 
> Roto with lots of comptationally expensive Nodes in between.
> 
> If anyone does have any reproducable performance metrics or scripts they'd 
> like to share we'd love to see them, add them to our autotests and make it a 
> better experiance :)
> 
> F.
> 
> On Wednesday, April 1, 2015, Daniel Hartlehnert  wrote:
> Hi Frank,
> 
> thanks for an "official" answer :)
> 
> My experience differs though, so i don't have any "metric" to base it on, 
> Marten. Only common sense and experience. Therefore my answer i gave before.
> 
> 
> Am 01.04.2015 um 10:00 schrieb Frank Harrison:
> 
>> Hey Guys,
>> 
>> Under the hood the two Nodes are exactly the same, they just cater to 
>> different work flows.
>> 
>> As a result, the only time RotoPaint should be slower is when you have 
>> paint/clone/smear strokes interleaved with bezier/bspine shapes.
>> 
>> F.
>> 
>> On Wednesday, April 1, 2015, Daniel Hartlehnert  wrote:
>> Isn't it obvious? Roto node has much less functionality, hence it its much 
>> faster to process and has a smaller memory footprint. Bugs from the paint 
>> part of Rotopaint cannot destroy your script, Rotopaints with more than 100 
>> strokes tend to slow down your script (if i ever see that progress bar from 
>> a rotopaint node i start to ...)
>> Rotopaints are responsible for most broken scripts in my experience.
>> 
>> Wyh would you use Rotopaint if you don't actually paint?
>> 
>> Am 31.03.2015 um 20:14 schrieb Simon Björk:
>> 
>>> For some reason I always reach for the RotoPaint node instead of the 
>>> regular Roto node. I'm not sure why I got into this habit, but it might be 
>>> (if I'm not mistaken) that the RotoPaint node was introduced before the 
>>> Roto node back in 6.0.
>>> 
>>> Anyway, does anyone know if there's a difference in performance/stability 
>>> when doing just regular roto? We've all had or problems with the RotoPaint 
>>> node over the last couple of versions, but I have never actually compared 
>>> the two nodes to see if one is "better" than the other.
>>> 
>>> 
>>> 
>>> 
>>> 
>>> ---
>>> Simon Björk
>>> Compositor/TD
>>> 
>>> +46 (0)70-2859503
>>> www.bjorkvisuals.com
>>> ___
>>> 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
>> 
>> 
>> 
>> -- 
>> Frank Harrison
>> Senior Nuke Software Engineer
>> The Foundry
>> Tel: +44 (0)20 7968 6828 - Fax: +44 (0)20 7930 8906 
>> Web: www.thefoundry.co.uk
>> Email: frank.harri...@thefoundry.co.uk  
>> 
>> ___
>> 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
> 
> 
> 
> -- 
> Frank Harrison
> Senior Nuke Software Engineer
> The Foundry
> Tel: +44 (0)20 7968 6828 - Fax: +44 (0)20 7930 8906 
> Web: www.thefoundry.co.uk
> Email: frank.harri...@thefoundry.co.uk  
> 
> ___
> 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] RotoPaint vs Roto

[Daniel Hartlehnert]

Hi Frank,

hmm, number of channels. I tend to set Roto to use rgba instead of alpha only, 
just because i am too lazy to switch the viewer to display the alpha channel. 
Even though i might just need alpha downstream. Kind of going against my own 
agenda of keeping everything simple as possible :)
Despite that, i still had the feeling of Rotos being more efficient.

On a side node: If i, lets say use a blur node set to use rgba, but downstream 
only use alpha from that (i.e. as a mask input on another node), will Nuke be 
slower because it blurs rgba instead of alpha only? Or will only the requested 
channels be calculated upstream?

When you mention expressions, do you mean expressions on the Roto/Paint nodes 
themselves, or also generally in the script? And what would you consider 
excessive? :)


Am 01.04.2015 um 11:17 schrieb Frank Harrison:

> Hey Daniel,
> 
> That's fascinating to hear, I wonder if it does relate to the bumber of 
> channels they use by default? 
> 
> There are various things you can do to make Roto and Paint appear slower, 
> such as use excessive numbers of expessions or view a node downstream of a 
> Roto with lots of comptationally expensive Nodes in between.
> 
> If anyone does have any reproducable performance metrics or scripts they'd 
> like to share we'd love to see them, add them to our autotests and make it a 
> better experiance :)
> 
> F.
> 
> On Wednesday, April 1, 2015, Daniel Hartlehnert  wrote:
> Hi Frank,
> 
> thanks for an "official" answer :)
> 
> My experience differs though, so i don't have any "metric" to base it on, 
> Marten. Only common sense and experience. Therefore my answer i gave before.
> 
> 
> Am 01.04.2015 um 10:00 schrieb Frank Harrison:
> 
>> Hey Guys,
>> 
>> Under the hood the two Nodes are exactly the same, they just cater to 
>> different work flows.
>> 
>> As a result, the only time RotoPaint should be slower is when you have 
>> paint/clone/smear strokes interleaved with bezier/bspine shapes.
>> 
>> F.
>> 
>> On Wednesday, April 1, 2015, Daniel Hartlehnert  wrote:
>> Isn't it obvious? Roto node has much less functionality, hence it its much 
>> faster to process and has a smaller memory footprint. Bugs from the paint 
>> part of Rotopaint cannot destroy your script, Rotopaints with more than 100 
>> strokes tend to slow down your script (if i ever see that progress bar from 
>> a rotopaint node i start to ...)
>> Rotopaints are responsible for most broken scripts in my experience.
>> 
>> Wyh would you use Rotopaint if you don't actually paint?
>> 
>> Am 31.03.2015 um 20:14 schrieb Simon Björk:
>> 
>>> For some reason I always reach for the RotoPaint node instead of the 
>>> regular Roto node. I'm not sure why I got into this habit, but it might be 
>>> (if I'm not mistaken) that the RotoPaint node was introduced before the 
>>> Roto node back in 6.0.
>>> 
>>> Anyway, does anyone know if there's a difference in performance/stability 
>>> when doing just regular roto? We've all had or problems with the RotoPaint 
>>> node over the last couple of versions, but I have never actually compared 
>>> the two nodes to see if one is "better" than the other.
>>> 
>>> 
>>> 
>>> 
>>> 
>>> ---
>>> Simon Björk
>>> Compositor/TD
>>> 
>>> +46 (0)70-2859503
>>> www.bjorkvisuals.com
>>> ___
>>> 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
>> 
>> 
>> 
>> -- 
>> Frank Harrison
>> Senior Nuke Software Engineer
>> The Foundry
>> Tel: +44 (0)20 7968 6828 - Fax: +44 (0)20 7930 8906 
>> Web: www.thefoundry.co.uk
>> Email: frank.harri...@thefoundry.co.uk  
>> 
>> ___
>> 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
> 
> 
> 
> -- 
> Frank Harrison
> Senior Nuke Software Engineer
> The Foundry
> Tel: +44 (0)20 7968 6828 - Fax: +44 (0)20 7930 8906 
> Web: www.thefoundry.co.uk
> Email: frank.harri...@thefoundry.co.uk  
> 
> ___
> 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] RotoPaint vs Roto

[Frank Harrison]

Hey Daniel,

That's fascinating to hear, I wonder if it does relate to the bumber of
channels they use by default?

There are various things you can do to make Roto and Paint appear slower,
such as use excessive numbers of expessions or view a node downstream of a
Roto with lots of comptationally expensive Nodes in between.

If anyone does have any reproducable performance metrics or scripts they'd
like to share we'd love to see them, add them to our autotests and make it
a better experiance :)

F.

On Wednesday, April 1, 2015, Daniel Hartlehnert  wrote:

> Hi Frank,
>
> thanks for an "official" answer :)
>
> My experience differs though, so i don't have any "metric" to base it on,
> Marten. Only common sense and experience. Therefore my answer i gave before.
>
>
> Am 01.04.2015 um 10:00 schrieb Frank Harrison:
>
> Hey Guys,
>
> Under the hood the two Nodes are exactly the same, they just cater to
> different work flows.
>
> As a result, the only time RotoPaint should be slower is when you have
> paint/clone/smear strokes interleaved with bezier/bspine shapes.
>
> F.
>
> On Wednesday, April 1, 2015, Daniel Hartlehnert  > wrote:
>
>> Isn't it obvious? Roto node has much less functionality, hence it its
>> much faster to process and has a smaller memory footprint. Bugs from the
>> paint part of Rotopaint cannot destroy your script, Rotopaints with more
>> than 100 strokes tend to slow down your script (if i ever see that progress
>> bar from a rotopaint node i start to ...)
>> Rotopaints are responsible for most broken scripts in my experience.
>>
>> Wyh would you use Rotopaint if you don't actually paint?
>>
>> Am 31.03.2015 um 20:14 schrieb Simon Björk:
>>
>> For some reason I always reach for the RotoPaint node instead of the
>> regular Roto node. I'm not sure why I got into this habit, but it might be
>> (if I'm not mistaken) that the RotoPaint node was introduced before the
>> Roto node back in 6.0.
>>
>> Anyway, does anyone know if there's a difference in performance/stability
>> when doing just regular roto? We've all had or problems with the RotoPaint
>> node over the last couple of versions, but I have never actually compared
>> the two nodes to see if one is "better" than the other.
>>
>>
>>
>>
>>
>> ---
>> Simon Björk
>> Compositor/TD
>>
>> +46 (0)70-2859503
>> www.bjorkvisuals.com
>>  ___
>> 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
>>
>>
>>
>
> --
> Frank Harrison
> Senior Nuke Software Engineer
> The Foundry
> Tel: +44 (0)20 7968 6828 - Fax: +44 (0)20 7930 8906
> Web: www.thefoundry.co.uk
> Email: frank.harri...@thefoundry.co.uk
> 
>
> ___
> 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
>
>
>

-- 
Frank Harrison
Senior Nuke Software Engineer
The Foundry
Tel: +44 (0)20 7968 6828 - Fax: +44 (0)20 7930 8906
Web: www.thefoundry.co.uk
Email: frank.harri...@thefoundry.co.uk
___
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] RotoPaint vs Roto

[Simon Björk]

Thanks Frank,

good to know :).



---
Simon Björk
Compositor/TD

+46 (0)70-2859503
www.bjorkvisuals.com

2015-04-01 10:24 GMT+02:00 Daniel Hartlehnert :

> Hi Frank,
>
> thanks for an "official" answer :)
>
> My experience differs though, so i don't have any "metric" to base it on,
> Marten. Only common sense and experience. Therefore my answer i gave before.
>
>
> Am 01.04.2015 um 10:00 schrieb Frank Harrison:
>
> Hey Guys,
>
> Under the hood the two Nodes are exactly the same, they just cater to
> different work flows.
>
> As a result, the only time RotoPaint should be slower is when you have
> paint/clone/smear strokes interleaved with bezier/bspine shapes.
>
> F.
>
> On Wednesday, April 1, 2015, Daniel Hartlehnert  wrote:
>
>> Isn't it obvious? Roto node has much less functionality, hence it its
>> much faster to process and has a smaller memory footprint. Bugs from the
>> paint part of Rotopaint cannot destroy your script, Rotopaints with more
>> than 100 strokes tend to slow down your script (if i ever see that progress
>> bar from a rotopaint node i start to ...)
>> Rotopaints are responsible for most broken scripts in my experience.
>>
>> Wyh would you use Rotopaint if you don't actually paint?
>>
>> Am 31.03.2015 um 20:14 schrieb Simon Björk:
>>
>> For some reason I always reach for the RotoPaint node instead of the
>> regular Roto node. I'm not sure why I got into this habit, but it might be
>> (if I'm not mistaken) that the RotoPaint node was introduced before the
>> Roto node back in 6.0.
>>
>> Anyway, does anyone know if there's a difference in performance/stability
>> when doing just regular roto? We've all had or problems with the RotoPaint
>> node over the last couple of versions, but I have never actually compared
>> the two nodes to see if one is "better" than the other.
>>
>>
>>
>>
>>
>> ---
>> Simon Björk
>> Compositor/TD
>>
>> +46 (0)70-2859503
>> www.bjorkvisuals.com
>>  ___
>> 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
>>
>>
>>
>
> --
> Frank Harrison
> Senior Nuke Software Engineer
> The Foundry
> Tel: +44 (0)20 7968 6828 - Fax: +44 (0)20 7930 8906
> Web: www.thefoundry.co.uk
> Email: frank.harri...@thefoundry.co.uk
>
> ___
> 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] RotoPaint vs Roto

[Daniel Hartlehnert]

Hi Frank,

thanks for an "official" answer :)

My experience differs though, so i don't have any "metric" to base it on, 
Marten. Only common sense and experience. Therefore my answer i gave before.


Am 01.04.2015 um 10:00 schrieb Frank Harrison:

> Hey Guys,
> 
> Under the hood the two Nodes are exactly the same, they just cater to 
> different work flows.
> 
> As a result, the only time RotoPaint should be slower is when you have 
> paint/clone/smear strokes interleaved with bezier/bspine shapes.
> 
> F.
> 
> On Wednesday, April 1, 2015, Daniel Hartlehnert  wrote:
> Isn't it obvious? Roto node has much less functionality, hence it its much 
> faster to process and has a smaller memory footprint. Bugs from the paint 
> part of Rotopaint cannot destroy your script, Rotopaints with more than 100 
> strokes tend to slow down your script (if i ever see that progress bar from a 
> rotopaint node i start to ...)
> Rotopaints are responsible for most broken scripts in my experience.
> 
> Wyh would you use Rotopaint if you don't actually paint?
> 
> Am 31.03.2015 um 20:14 schrieb Simon Björk:
> 
>> For some reason I always reach for the RotoPaint node instead of the regular 
>> Roto node. I'm not sure why I got into this habit, but it might be (if I'm 
>> not mistaken) that the RotoPaint node was introduced before the Roto node 
>> back in 6.0.
>> 
>> Anyway, does anyone know if there's a difference in performance/stability 
>> when doing just regular roto? We've all had or problems with the RotoPaint 
>> node over the last couple of versions, but I have never actually compared 
>> the two nodes to see if one is "better" than the other.
>> 
>> 
>> 
>> 
>> 
>> ---
>> Simon Björk
>> Compositor/TD
>> 
>> +46 (0)70-2859503
>> www.bjorkvisuals.com
>> ___
>> 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
> 
> 
> 
> -- 
> Frank Harrison
> Senior Nuke Software Engineer
> The Foundry
> Tel: +44 (0)20 7968 6828 - Fax: +44 (0)20 7930 8906 
> Web: www.thefoundry.co.uk
> Email: frank.harri...@thefoundry.co.uk  
> 
> ___
> 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] RotoPaint vs Roto

[Frank Harrison]

Hey Guys,

Under the hood the two Nodes are exactly the same, they just cater to
different work flows.

As a result, the only time RotoPaint should be slower is when you have
paint/clone/smear strokes interleaved with bezier/bspine shapes.

F.

On Wednesday, April 1, 2015, Daniel Hartlehnert  wrote:

> Isn't it obvious? Roto node has much less functionality, hence it its much
> faster to process and has a smaller memory footprint. Bugs from the paint
> part of Rotopaint cannot destroy your script, Rotopaints with more than 100
> strokes tend to slow down your script (if i ever see that progress bar from
> a rotopaint node i start to ...)
> Rotopaints are responsible for most broken scripts in my experience.
>
> Wyh would you use Rotopaint if you don't actually paint?
>
> Am 31.03.2015 um 20:14 schrieb Simon Björk:
>
> For some reason I always reach for the RotoPaint node instead of the
> regular Roto node. I'm not sure why I got into this habit, but it might be
> (if I'm not mistaken) that the RotoPaint node was introduced before the
> Roto node back in 6.0.
>
> Anyway, does anyone know if there's a difference in performance/stability
> when doing just regular roto? We've all had or problems with the RotoPaint
> node over the last couple of versions, but I have never actually compared
> the two nodes to see if one is "better" than the other.
>
>
>
>
>
> ---
> Simon Björk
> Compositor/TD
>
> +46 (0)70-2859503
> www.bjorkvisuals.com
>  ___
> 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
>
>
>

-- 
Frank Harrison
Senior Nuke Software Engineer
The Foundry
Tel: +44 (0)20 7968 6828 - Fax: +44 (0)20 7930 8906
Web: www.thefoundry.co.uk
Email: frank.harri...@thefoundry.co.uk
___
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] RotoPaint vs Roto

[Marten Blumen]

eh? what's your metric to claim that roto paints are much faster and
smaller memory footprint.

Using Nuke 9.04  & nuke.startPerformanceTimers() shows the same memory and
cpu usage.

Both nodes have a equal values on a 4K/100frame test: 5.22MB, cpu=9423ms

On 1 April 2015 at 20:26, Daniel Hartlehnert  wrote:

> Isn't it obvious? Roto node has much less functionality, hence it its much
> faster to process and has a smaller memory footprint. Bugs from the paint
> part of Rotopaint cannot destroy your script, Rotopaints with more than 100
> strokes tend to slow down your script (if i ever see that progress bar from
> a rotopaint node i start to ...)
> Rotopaints are responsible for most broken scripts in my experience.
>
> Wyh would you use Rotopaint if you don't actually paint?
>
> Am 31.03.2015 um 20:14 schrieb Simon Björk:
>
> For some reason I always reach for the RotoPaint node instead of the
> regular Roto node. I'm not sure why I got into this habit, but it might be
> (if I'm not mistaken) that the RotoPaint node was introduced before the
> Roto node back in 6.0.
>
> Anyway, does anyone know if there's a difference in performance/stability
> when doing just regular roto? We've all had or problems with the RotoPaint
> node over the last couple of versions, but I have never actually compared
> the two nodes to see if one is "better" than the other.
>
>
>
>
>
> ---
> Simon Björk
> Compositor/TD
>
> +46 (0)70-2859503
> www.bjorkvisuals.com
>  ___
> 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] RotoPaint vs Roto

[Daniel Hartlehnert]

Isn't it obvious? Roto node has much less functionality, hence it its much 
faster to process and has a smaller memory footprint. Bugs from the paint part 
of Rotopaint cannot destroy your script, Rotopaints with more than 100 strokes 
tend to slow down your script (if i ever see that progress bar from a rotopaint 
node i start to ...)
Rotopaints are responsible for most broken scripts in my experience.

Wyh would you use Rotopaint if you don't actually paint?

Am 31.03.2015 um 20:14 schrieb Simon Björk:

> For some reason I always reach for the RotoPaint node instead of the regular 
> Roto node. I'm not sure why I got into this habit, but it might be (if I'm 
> not mistaken) that the RotoPaint node was introduced before the Roto node 
> back in 6.0.
> 
> Anyway, does anyone know if there's a difference in performance/stability 
> when doing just regular roto? We've all had or problems with the RotoPaint 
> node over the last couple of versions, but I have never actually compared the 
> two nodes to see if one is "better" than the other.
> 
> 
> 
> 
> 
> ---
> Simon Björk
> Compositor/TD
> 
> +46 (0)70-2859503
> www.bjorkvisuals.com
> ___
> 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] RotoPaint vs Roto

[Yahoo]

Roto is just a subset of rotopaint, as users wanted a lighter tool. 
If you're not painting use roto. You can always drag the shaped into a rp node 
to 'promote' it. 



Howard

> On 31 Mar 2015, at 22:57, Ergin SANAL  wrote:
> 
> it works without premultipication, need to choose source as background and 
> replace the alpha. premult is distractive time to time.. cheerz
> 
> 
> 
>> On Wed, Apr 1, 2015 at 12:46 AM, Randy Little  wrote:
>> Roto node will output RGBA (or anything) I premult inside the roto node all 
>> the time so its just inline no extra premult step.  (not always a best 
>> practice fyi) but I do it :-/
>> 
>> Randy S. Little
>> http://www.rslittle.com/
>> http://www.imdb.com/name/nm2325729/
>> 
>> 
>> 
>>> On Tue, Mar 31, 2015 at 5:30 PM, Ergin SANAL  wrote:
>>> rotopaint's  output is rgba and roto's is only a.
>>> that means with rotopaint, nuke has to deal with 3 more channels. 
>>> maybe thats why there are some performance issues. 
>>> actually there are no difference between 2 nodes except output channels and 
>>> place of the sliders. (feather,opacity etc.) 
>>> 
>>> 
>>> 
 On Wed, Apr 1, 2015 at 12:23 AM, Randy Little  
 wrote:
 clean UI.   No accidental painting.  bigger memory footprint maybe?   
 
 Randy S. Little
 http://www.rslittle.com/
 http://www.imdb.com/name/nm2325729/
 
 
 
> On Tue, Mar 31, 2015 at 2:21 PM, Ron Ganbar  wrote:
> No idea about performance, but I do love the fact that when I use the O 
> hotkey instead of the P hotkey, I can immediately start drawing a shape, 
> as the Bezier tool is on by default.
> 
> 
> 
> Ron Ganbar
> email: ron...@gmail.com
> tel: +44 (0)7968 007 309 [UK]
>  +972 (0)54 255 9765 [Israel]
> url: http://ronganbar.wordpress.com/
> 
>> On Tue, Mar 31, 2015 at 9:14 PM, Simon Björk  
>> wrote:
>> For some reason I always reach for the RotoPaint node instead of the 
>> regular Roto node. I'm not sure why I got into this habit, but it might 
>> be (if I'm not mistaken) that the RotoPaint node was introduced before 
>> the Roto node back in 6.0.
>> 
>> Anyway, does anyone know if there's a difference in 
>> performance/stability when doing just regular roto? We've all had or 
>> problems with the RotoPaint node over the last couple of versions, but I 
>> have never actually compared the two nodes to see if one is "better" 
>> than the other.
>> 
>> 
>> 
>> 
>> 
>> ---
>> Simon Björk
>> Compositor/TD
>> 
>> +46 (0)70-2859503
>> www.bjorkvisuals.com
>> 
>> ___
>> 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
>>> 
>>> 
>>> ___
>>> 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
___
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] RotoPaint vs Roto

[Randy Little]

Well there you go then, you only have to deal with the extra UI and that's
the difference but it is for sure processing the same data as the paint
node without the paint part.  They aren't different much beyond that and
how they default load UI wise.  Its just got UI and knobs turned off.
According to the Info window.   Roto has all the setting for brush size and
every thing.

Randy S. Little
http://www.rslittle.com/
http://www.imdb.com/name/nm2325729/



On Tue, Mar 31, 2015 at 6:11 PM, Marten Blumen  wrote:

> Where's the overhead?  Info on a roto node and rotopaint both says
>
> 'Total Memory Usage: 0B'
>
> On 1 April 2015 at 11:08, Randy Little  wrote:
>
>> huh?   output can be whatever you tell it.   Pre-Multiply is directly
>> under output.  Set output to none and premult to RGBA and you get your RGB
>> input Premulted by whatever roto you have drawn in the node with only 2
>> nodes instead of  3.
>> If you set paint node up the same way it does the same thing.   You just
>> don't get the overhead of the rest of the paint stuff being loaded into
>> it.
>>
>> Randy S. Little
>> http://www.rslittle.com/
>> http://www.imdb.com/name/nm2325729/
>>
>>
>>
>> On Tue, Mar 31, 2015 at 5:57 PM, Ergin SANAL 
>> wrote:
>>
>>> it works without premultipication, need to choose source as background
>>> and replace the alpha. premult is distractive time to time.. cheerz
>>>
>>>
>>>
>>> On Wed, Apr 1, 2015 at 12:46 AM, Randy Little 
>>> wrote:
>>>
 Roto node will output RGBA (or anything) I premult inside the roto node
 all the time so its just inline no extra premult step.  (not always a best
 practice fyi) but I do it :-/

 Randy S. Little
 http://www.rslittle.com/
 http://www.imdb.com/name/nm2325729/



 On Tue, Mar 31, 2015 at 5:30 PM, Ergin SANAL 
 wrote:

> rotopaint's  output is rgba and roto's is only a.
> that means with rotopaint, nuke has to deal with 3 more channels.
> maybe thats why there are some performance issues.
> actually there are no difference between 2 nodes except output
> channels and place of the sliders. (feather,opacity etc.)
>
>
>
> On Wed, Apr 1, 2015 at 12:23 AM, Randy Little 
> wrote:
>
>> clean UI.   No accidental painting.  bigger memory footprint maybe?
>>
>> Randy S. Little
>> http://www.rslittle.com/
>> http://www.imdb.com/name/nm2325729/
>>
>>
>>
>> On Tue, Mar 31, 2015 at 2:21 PM, Ron Ganbar  wrote:
>>
>>> No idea about performance, but I do love the fact that when I use
>>> the O hotkey instead of the P hotkey, I can immediately start drawing a
>>> shape, as the Bezier tool is on by default.
>>>
>>>
>>>
>>> Ron Ganbar
>>> email: ron...@gmail.com
>>> tel: +44 (0)7968 007 309 [UK]
>>>  +972 (0)54 255 9765 [Israel]
>>> url: http://ronganbar.wordpress.com/
>>>
>>> On Tue, Mar 31, 2015 at 9:14 PM, Simon Björk 
>>> wrote:
>>>
 For some reason I always reach for the RotoPaint node instead of
 the regular Roto node. I'm not sure why I got into this habit, but it 
 might
 be (if I'm not mistaken) that the RotoPaint node was introduced before 
 the
 Roto node back in 6.0.

 Anyway, does anyone know if there's a difference in
 performance/stability when doing just regular roto? We've all had or
 problems with the RotoPaint node over the last couple of versions, but 
 I
 have never actually compared the two nodes to see if one is "better" 
 than
 the other.





 ---
 Simon Björk
 Compositor/TD

 +46 (0)70-2859503
 www.bjorkvisuals.com

 ___
 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
>>
>
>
> ___
> 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@sup

Re: [Nuke-users] RotoPaint vs Roto

[Marten Blumen]

Where's the overhead?  Info on a roto node and rotopaint both says

'Total Memory Usage: 0B'

On 1 April 2015 at 11:08, Randy Little  wrote:

> huh?   output can be whatever you tell it.   Pre-Multiply is directly
> under output.  Set output to none and premult to RGBA and you get your RGB
> input Premulted by whatever roto you have drawn in the node with only 2
> nodes instead of  3.
> If you set paint node up the same way it does the same thing.   You just
> don't get the overhead of the rest of the paint stuff being loaded into
> it.
>
> Randy S. Little
> http://www.rslittle.com/
> http://www.imdb.com/name/nm2325729/
>
>
>
> On Tue, Mar 31, 2015 at 5:57 PM, Ergin SANAL  wrote:
>
>> it works without premultipication, need to choose source as background
>> and replace the alpha. premult is distractive time to time.. cheerz
>>
>>
>>
>> On Wed, Apr 1, 2015 at 12:46 AM, Randy Little 
>> wrote:
>>
>>> Roto node will output RGBA (or anything) I premult inside the roto node
>>> all the time so its just inline no extra premult step.  (not always a best
>>> practice fyi) but I do it :-/
>>>
>>> Randy S. Little
>>> http://www.rslittle.com/
>>> http://www.imdb.com/name/nm2325729/
>>>
>>>
>>>
>>> On Tue, Mar 31, 2015 at 5:30 PM, Ergin SANAL 
>>> wrote:
>>>
 rotopaint's  output is rgba and roto's is only a.
 that means with rotopaint, nuke has to deal with 3 more channels.
 maybe thats why there are some performance issues.
 actually there are no difference between 2 nodes except output channels
 and place of the sliders. (feather,opacity etc.)



 On Wed, Apr 1, 2015 at 12:23 AM, Randy Little 
 wrote:

> clean UI.   No accidental painting.  bigger memory footprint maybe?
>
> Randy S. Little
> http://www.rslittle.com/
> http://www.imdb.com/name/nm2325729/
>
>
>
> On Tue, Mar 31, 2015 at 2:21 PM, Ron Ganbar  wrote:
>
>> No idea about performance, but I do love the fact that when I use the
>> O hotkey instead of the P hotkey, I can immediately start drawing a 
>> shape,
>> as the Bezier tool is on by default.
>>
>>
>>
>> Ron Ganbar
>> email: ron...@gmail.com
>> tel: +44 (0)7968 007 309 [UK]
>>  +972 (0)54 255 9765 [Israel]
>> url: http://ronganbar.wordpress.com/
>>
>> On Tue, Mar 31, 2015 at 9:14 PM, Simon Björk 
>> wrote:
>>
>>> For some reason I always reach for the RotoPaint node instead of the
>>> regular Roto node. I'm not sure why I got into this habit, but it might 
>>> be
>>> (if I'm not mistaken) that the RotoPaint node was introduced before the
>>> Roto node back in 6.0.
>>>
>>> Anyway, does anyone know if there's a difference in
>>> performance/stability when doing just regular roto? We've all had or
>>> problems with the RotoPaint node over the last couple of versions, but I
>>> have never actually compared the two nodes to see if one is "better" 
>>> than
>>> the other.
>>>
>>>
>>>
>>>
>>>
>>> ---
>>> Simon Björk
>>> Compositor/TD
>>>
>>> +46 (0)70-2859503
>>> www.bjorkvisuals.com
>>>
>>> ___
>>> 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
>


 ___
 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
>>
>
>
> ___
> 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.th

Re: [Nuke-users] RotoPaint vs Roto

[Randy Little]

huh?   output can be whatever you tell it.   Pre-Multiply is directly under
output.  Set output to none and premult to RGBA and you get your RGB input
Premulted by whatever roto you have drawn in the node with only 2 nodes
instead of  3.
If you set paint node up the same way it does the same thing.   You just
don't get the overhead of the rest of the paint stuff being loaded into
it.

Randy S. Little
http://www.rslittle.com/
http://www.imdb.com/name/nm2325729/



On Tue, Mar 31, 2015 at 5:57 PM, Ergin SANAL  wrote:

> it works without premultipication, need to choose source as background and
> replace the alpha. premult is distractive time to time.. cheerz
>
>
>
> On Wed, Apr 1, 2015 at 12:46 AM, Randy Little 
> wrote:
>
>> Roto node will output RGBA (or anything) I premult inside the roto node
>> all the time so its just inline no extra premult step.  (not always a best
>> practice fyi) but I do it :-/
>>
>> Randy S. Little
>> http://www.rslittle.com/
>> http://www.imdb.com/name/nm2325729/
>>
>>
>>
>> On Tue, Mar 31, 2015 at 5:30 PM, Ergin SANAL 
>> wrote:
>>
>>> rotopaint's  output is rgba and roto's is only a.
>>> that means with rotopaint, nuke has to deal with 3 more channels.
>>> maybe thats why there are some performance issues.
>>> actually there are no difference between 2 nodes except output channels
>>> and place of the sliders. (feather,opacity etc.)
>>>
>>>
>>>
>>> On Wed, Apr 1, 2015 at 12:23 AM, Randy Little 
>>> wrote:
>>>
 clean UI.   No accidental painting.  bigger memory footprint maybe?

 Randy S. Little
 http://www.rslittle.com/
 http://www.imdb.com/name/nm2325729/



 On Tue, Mar 31, 2015 at 2:21 PM, Ron Ganbar  wrote:

> No idea about performance, but I do love the fact that when I use the
> O hotkey instead of the P hotkey, I can immediately start drawing a shape,
> as the Bezier tool is on by default.
>
>
>
> Ron Ganbar
> email: ron...@gmail.com
> tel: +44 (0)7968 007 309 [UK]
>  +972 (0)54 255 9765 [Israel]
> url: http://ronganbar.wordpress.com/
>
> On Tue, Mar 31, 2015 at 9:14 PM, Simon Björk 
> wrote:
>
>> For some reason I always reach for the RotoPaint node instead of the
>> regular Roto node. I'm not sure why I got into this habit, but it might 
>> be
>> (if I'm not mistaken) that the RotoPaint node was introduced before the
>> Roto node back in 6.0.
>>
>> Anyway, does anyone know if there's a difference in
>> performance/stability when doing just regular roto? We've all had or
>> problems with the RotoPaint node over the last couple of versions, but I
>> have never actually compared the two nodes to see if one is "better" than
>> the other.
>>
>>
>>
>>
>>
>> ---
>> Simon Björk
>> Compositor/TD
>>
>> +46 (0)70-2859503
>> www.bjorkvisuals.com
>>
>> ___
>> 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

>>>
>>>
>>> ___
>>> 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
>
___
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] RotoPaint vs Roto

[Ergin SANAL]

it works without premultipication, need to choose source as background and
replace the alpha. premult is distractive time to time.. cheerz



On Wed, Apr 1, 2015 at 12:46 AM, Randy Little 
wrote:

> Roto node will output RGBA (or anything) I premult inside the roto node
> all the time so its just inline no extra premult step.  (not always a best
> practice fyi) but I do it :-/
>
> Randy S. Little
> http://www.rslittle.com/
> http://www.imdb.com/name/nm2325729/
>
>
>
> On Tue, Mar 31, 2015 at 5:30 PM, Ergin SANAL  wrote:
>
>> rotopaint's  output is rgba and roto's is only a.
>> that means with rotopaint, nuke has to deal with 3 more channels.
>> maybe thats why there are some performance issues.
>> actually there are no difference between 2 nodes except output channels
>> and place of the sliders. (feather,opacity etc.)
>>
>>
>>
>> On Wed, Apr 1, 2015 at 12:23 AM, Randy Little 
>> wrote:
>>
>>> clean UI.   No accidental painting.  bigger memory footprint maybe?
>>>
>>> Randy S. Little
>>> http://www.rslittle.com/
>>> http://www.imdb.com/name/nm2325729/
>>>
>>>
>>>
>>> On Tue, Mar 31, 2015 at 2:21 PM, Ron Ganbar  wrote:
>>>
 No idea about performance, but I do love the fact that when I use the O
 hotkey instead of the P hotkey, I can immediately start drawing a shape, as
 the Bezier tool is on by default.



 Ron Ganbar
 email: ron...@gmail.com
 tel: +44 (0)7968 007 309 [UK]
  +972 (0)54 255 9765 [Israel]
 url: http://ronganbar.wordpress.com/

 On Tue, Mar 31, 2015 at 9:14 PM, Simon Björk 
 wrote:

> For some reason I always reach for the RotoPaint node instead of the
> regular Roto node. I'm not sure why I got into this habit, but it might be
> (if I'm not mistaken) that the RotoPaint node was introduced before the
> Roto node back in 6.0.
>
> Anyway, does anyone know if there's a difference in
> performance/stability when doing just regular roto? We've all had or
> problems with the RotoPaint node over the last couple of versions, but I
> have never actually compared the two nodes to see if one is "better" than
> the other.
>
>
>
>
>
> ---
> Simon Björk
> Compositor/TD
>
> +46 (0)70-2859503
> www.bjorkvisuals.com
>
> ___
> 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
>>>
>>
>>
>> ___
>> 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] RotoPaint vs Roto

[Randy Little]

Roto node will output RGBA (or anything) I premult inside the roto node all
the time so its just inline no extra premult step.  (not always a best
practice fyi) but I do it :-/

Randy S. Little
http://www.rslittle.com/
http://www.imdb.com/name/nm2325729/



On Tue, Mar 31, 2015 at 5:30 PM, Ergin SANAL  wrote:

> rotopaint's  output is rgba and roto's is only a.
> that means with rotopaint, nuke has to deal with 3 more channels.
> maybe thats why there are some performance issues.
> actually there are no difference between 2 nodes except output channels
> and place of the sliders. (feather,opacity etc.)
>
>
>
> On Wed, Apr 1, 2015 at 12:23 AM, Randy Little 
> wrote:
>
>> clean UI.   No accidental painting.  bigger memory footprint maybe?
>>
>> Randy S. Little
>> http://www.rslittle.com/
>> http://www.imdb.com/name/nm2325729/
>>
>>
>>
>> On Tue, Mar 31, 2015 at 2:21 PM, Ron Ganbar  wrote:
>>
>>> No idea about performance, but I do love the fact that when I use the O
>>> hotkey instead of the P hotkey, I can immediately start drawing a shape, as
>>> the Bezier tool is on by default.
>>>
>>>
>>>
>>> Ron Ganbar
>>> email: ron...@gmail.com
>>> tel: +44 (0)7968 007 309 [UK]
>>>  +972 (0)54 255 9765 [Israel]
>>> url: http://ronganbar.wordpress.com/
>>>
>>> On Tue, Mar 31, 2015 at 9:14 PM, Simon Björk 
>>> wrote:
>>>
 For some reason I always reach for the RotoPaint node instead of the
 regular Roto node. I'm not sure why I got into this habit, but it might be
 (if I'm not mistaken) that the RotoPaint node was introduced before the
 Roto node back in 6.0.

 Anyway, does anyone know if there's a difference in
 performance/stability when doing just regular roto? We've all had or
 problems with the RotoPaint node over the last couple of versions, but I
 have never actually compared the two nodes to see if one is "better" than
 the other.





 ---
 Simon Björk
 Compositor/TD

 +46 (0)70-2859503
 www.bjorkvisuals.com

 ___
 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
>>
>
>
> ___
> 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] RotoPaint vs Roto

[Ergin SANAL]

rotopaint's  output is rgba and roto's is only a.
that means with rotopaint, nuke has to deal with 3 more channels.
maybe thats why there are some performance issues.
actually there are no difference between 2 nodes except output channels and
place of the sliders. (feather,opacity etc.)



On Wed, Apr 1, 2015 at 12:23 AM, Randy Little 
wrote:

> clean UI.   No accidental painting.  bigger memory footprint maybe?
>
> Randy S. Little
> http://www.rslittle.com/
> http://www.imdb.com/name/nm2325729/
>
>
>
> On Tue, Mar 31, 2015 at 2:21 PM, Ron Ganbar  wrote:
>
>> No idea about performance, but I do love the fact that when I use the O
>> hotkey instead of the P hotkey, I can immediately start drawing a shape, as
>> the Bezier tool is on by default.
>>
>>
>>
>> Ron Ganbar
>> email: ron...@gmail.com
>> tel: +44 (0)7968 007 309 [UK]
>>  +972 (0)54 255 9765 [Israel]
>> url: http://ronganbar.wordpress.com/
>>
>> On Tue, Mar 31, 2015 at 9:14 PM, Simon Björk 
>> wrote:
>>
>>> For some reason I always reach for the RotoPaint node instead of the
>>> regular Roto node. I'm not sure why I got into this habit, but it might be
>>> (if I'm not mistaken) that the RotoPaint node was introduced before the
>>> Roto node back in 6.0.
>>>
>>> Anyway, does anyone know if there's a difference in
>>> performance/stability when doing just regular roto? We've all had or
>>> problems with the RotoPaint node over the last couple of versions, but I
>>> have never actually compared the two nodes to see if one is "better" than
>>> the other.
>>>
>>>
>>>
>>>
>>>
>>> ---
>>> Simon Björk
>>> Compositor/TD
>>>
>>> +46 (0)70-2859503
>>> www.bjorkvisuals.com
>>>
>>> ___
>>> 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
>
___
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] RotoPaint vs Roto

[Randy Little]

clean UI.   No accidental painting.  bigger memory footprint maybe?

Randy S. Little
http://www.rslittle.com/
http://www.imdb.com/name/nm2325729/



On Tue, Mar 31, 2015 at 2:21 PM, Ron Ganbar  wrote:

> No idea about performance, but I do love the fact that when I use the O
> hotkey instead of the P hotkey, I can immediately start drawing a shape, as
> the Bezier tool is on by default.
>
>
>
> Ron Ganbar
> email: ron...@gmail.com
> tel: +44 (0)7968 007 309 [UK]
>  +972 (0)54 255 9765 [Israel]
> url: http://ronganbar.wordpress.com/
>
> On Tue, Mar 31, 2015 at 9:14 PM, Simon Björk 
> wrote:
>
>> For some reason I always reach for the RotoPaint node instead of the
>> regular Roto node. I'm not sure why I got into this habit, but it might be
>> (if I'm not mistaken) that the RotoPaint node was introduced before the
>> Roto node back in 6.0.
>>
>> Anyway, does anyone know if there's a difference in performance/stability
>> when doing just regular roto? We've all had or problems with the RotoPaint
>> node over the last couple of versions, but I have never actually compared
>> the two nodes to see if one is "better" than the other.
>>
>>
>>
>>
>>
>> ---
>> Simon Björk
>> Compositor/TD
>>
>> +46 (0)70-2859503
>> www.bjorkvisuals.com
>>
>> ___
>> 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] RotoPaint vs Roto

[Ron Ganbar]

No idea about performance, but I do love the fact that when I use the O
hotkey instead of the P hotkey, I can immediately start drawing a shape, as
the Bezier tool is on by default.



Ron Ganbar
email: ron...@gmail.com
tel: +44 (0)7968 007 309 [UK]
 +972 (0)54 255 9765 [Israel]
url: http://ronganbar.wordpress.com/

On Tue, Mar 31, 2015 at 9:14 PM, Simon Björk  wrote:

> For some reason I always reach for the RotoPaint node instead of the
> regular Roto node. I'm not sure why I got into this habit, but it might be
> (if I'm not mistaken) that the RotoPaint node was introduced before the
> Roto node back in 6.0.
>
> Anyway, does anyone know if there's a difference in performance/stability
> when doing just regular roto? We've all had or problems with the RotoPaint
> node over the last couple of versions, but I have never actually compared
> the two nodes to see if one is "better" than the other.
>
>
>
>
>
> ---
> Simon Björk
> Compositor/TD
>
> +46 (0)70-2859503
> www.bjorkvisuals.com
>
> ___
> 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] RotoPaint vs Roto

[Simon Björk]

For some reason I always reach for the RotoPaint node instead of the
regular Roto node. I'm not sure why I got into this habit, but it might be
(if I'm not mistaken) that the RotoPaint node was introduced before the
Roto node back in 6.0.

Anyway, does anyone know if there's a difference in performance/stability
when doing just regular roto? We've all had or problems with the RotoPaint
node over the last couple of versions, but I have never actually compared
the two nodes to see if one is "better" than the other.





---
Simon Björk
Compositor/TD

+46 (0)70-2859503
www.bjorkvisuals.com
___
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