[Nuke-users] Filmic Dissolve

[Darren Coombes]

I saw a few years back (in a book) a way to make a more filmic dissolve in Nuke.
It had something to do with inverting and dissolving or something along those 
lines.

Does anyone have a good setup to achieve a nicer dissolve rather than just 
using a standard dissolve node?

I'm dissolving between a night shot and a day shot.

Thanks.
Daz.



Check out some of my work...
www.vimeo.com/darrencoombes/reel2015

Mob:  +61 418 631 079
Instagram: @7secondstoblack
Instagram: @durwood0781
Skype:  darren.coombes81
Twitter:  @durwood81___
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] CPU cores vs clock speed

[Frank Harrison]

On Wednesday, 9 November 2016, Sven Schönmann 
wrote:

> Hi all,
>
> lots of good input here.
>
> One thing that confuses me: I was assuming that rendering in Nuke (not in
> background mode) would only affect one CPU - especially when rendering a
> quicktime movie file. But when I render a file, all my CPUs give full
> throttle. At least that is what my CPU-Meters tell me.
>



>
> Does Nuke render multi-threaded by default?
>
Yes.



> Cheers
>
> Sven
>
>
> On Wed, Nov 9, 2016 at 8:44 AM, J Bills  > wrote:
>
>> I know it depends on lots of things - but would it be safe to say from
>> purely a processor standpoint - the benefits of more cores comes at render
>> time, but in an interactive gui session, a faster clocked 4/6/8 core
>> machine would be preferable?  Since single threaded horsepower counts for
>> quite a bit, and there's only so much that multithreading helps.
>>
>> I've seen freelancers and one-person shows working from home that seem
>> happy with a single 20-36 core machine to take care of their rendering
>> needs all in one. But I would think that would be overkill at a shop with a
>> solid renderfarm - and you'd just need to focus on interactive session
>> power and somewhat disregard rendering.
>>
>>
>>
>>
>> On Tue, Nov 8, 2016 at 11:07 AM, Daniel Hartlehnert > > wrote:
>>
>>> Hi Michael,
>>>
>>> I have no direct answer for your question, there are just some things i
>>> think are worth considering:
>>> Much RAM is not only helpful in general, but more cores also need more
>>> memory to do their calculations! Otherwise the system will start swapping
>>> and the speed boost is gone.
>>> Also, the more cores you have, the faster the bus system has to be in
>>> order to keep the cores busy. Data might not be transfered from/to cores
>>> fast enough, so they start
>>> to sit idle waiting for the rest of the system to catch up.
>>>
>>> So all in all i would agree with everybody else: higher clock speed over
>>> more cores.
>>>
>>> Daniel
>>>
>>>
>>> Am 08.11.2016 um 16:28 schrieb michael vorberg <
>>> pingkin...@googlemail.com
>>> >:
>>>
>>> Thanks for the feedback
>>>
>>> Am 08.11.2016 16:01 schrieb "Frank Harrison" >> >:
>>>
 Right now, for NUKE/NUKEX specifically, a hIgher clock speed would be
 better. In a future release you will likely see more benefit from a higher
 number of cores.

 hth

 On 8 November 2016 at 14:38, michael vorberg > wrote:

> I was referring mostly to using nuke
> I know adding as much RAM as possible is helpful, GPU does not matter
> so much but CPU I'm not sure.
>
> Am 08.11.2016 14:48 schrieb "Rakesh Malik"  >:
>
>> That depends a lot on the workload, especially these days when the
>> processors' clock speeds are so dynamic, in that a 2.5GHz processor can
>> overlock itself to over 3GHz. Desktop processors that are designed around
>> more robust cooling solutions than mobile processors have even wider
>> "turbo" ranges.
>>
>> Generally, adding more cores gives you more computing power overall,
>> so it's more a question of how well the software you're using can take
>> advantage of parallelism during rendering. Most software runs in a single
>> thread, so adding cores has no direct benefit, but most of the higher end
>> solutions in color grading and VFX are heavily threaded and get pretty 
>> good
>> utilization out of additional cores.
>>
>> The GPU is another major variable to consider; some software leans
>> heavily on the GPU and doesn't use the main processor for computing, and
>> some that do a surprisingly good job of consuming both.
>>
>>
>> -
>>
>>
>> [image: --]
>>
>> Rakesh Malik
>> [image: https://]about.me/WhiteCranePhoto
>>
>> 
>> Director of Photography
>> http://www.WhiteCranePhotography.com
>> 
>>
>>
>>
>> On Tue, Nov 8, 2016 at 3:54 AM, michael vorberg <
>> pingkin...@googlemail.com
>> > wrote:
>>
>>> Hi,
>>> When buying a new workstation would I benefit more from a CPU with
>>> higher clock speed and less cores or do more cores with lower speed 
>>> give me
>>> overall more render speed?
>>>
>>> Or is this all a 

Re: [Nuke-users] Swapping nodes up/down in DAG

[Daniel Hartlehnert]

Cool. Doesn't work though when there is no node connected to the node above the 
one you are moving (if that makes sense)

Where could i find the python code for that? :)


> Am 09.11.2016 um 10:20 schrieb michael vorberg :
> 
> Ctrl+arrow up /down
> 
> 
> Am 09.11.2016 10:18 schrieb "Daniel Hartlehnert"  >:
> Hi,
> 
> i swear i saw this in action somewhere, but i can't remember if it was custom 
> or Nuke built-in:
> 
> How can i move nodes up and down the node tree?
> "Moving up" in this case means it swaps place with the node above it.
> 
> Daniel___
> 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] Swapping nodes up/down in DAG

[michael vorberg]

Ctrl+arrow up /down

Am 09.11.2016 10:18 schrieb "Daniel Hartlehnert" :

> Hi,
>
> i swear i saw this in action somewhere, but i can't remember if it was
> custom or Nuke built-in:
>
> How can i move nodes up and down the node tree?
> "Moving up" in this case means it swaps place with the node above it.
>
> Daniel___
> 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] Swapping nodes up/down in DAG

[Daniel Hartlehnert]

Hi,

i swear i saw this in action somewhere, but i can't remember if it was custom 
or Nuke built-in:

How can i move nodes up and down the node tree?
"Moving up" in this case means it swaps place with the node above it.

Daniel___
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] CPU cores vs clock speed

[Sven Schönmann]

Hi all,

lots of good input here.

One thing that confuses me: I was assuming that rendering in Nuke (not in
background mode) would only affect one CPU - especially when rendering a
quicktime movie file. But when I render a file, all my CPUs give full
throttle. At least that is what my CPU-Meters tell me.

Does Nuke render multi-threaded by default?

Cheers

Sven


On Wed, Nov 9, 2016 at 8:44 AM, J Bills  wrote:

> I know it depends on lots of things - but would it be safe to say from
> purely a processor standpoint - the benefits of more cores comes at render
> time, but in an interactive gui session, a faster clocked 4/6/8 core
> machine would be preferable?  Since single threaded horsepower counts for
> quite a bit, and there's only so much that multithreading helps.
>
> I've seen freelancers and one-person shows working from home that seem
> happy with a single 20-36 core machine to take care of their rendering
> needs all in one. But I would think that would be overkill at a shop with a
> solid renderfarm - and you'd just need to focus on interactive session
> power and somewhat disregard rendering.
>
>
>
>
> On Tue, Nov 8, 2016 at 11:07 AM, Daniel Hartlehnert  wrote:
>
>> Hi Michael,
>>
>> I have no direct answer for your question, there are just some things i
>> think are worth considering:
>> Much RAM is not only helpful in general, but more cores also need more
>> memory to do their calculations! Otherwise the system will start swapping
>> and the speed boost is gone.
>> Also, the more cores you have, the faster the bus system has to be in
>> order to keep the cores busy. Data might not be transfered from/to cores
>> fast enough, so they start
>> to sit idle waiting for the rest of the system to catch up.
>>
>> So all in all i would agree with everybody else: higher clock speed over
>> more cores.
>>
>> Daniel
>>
>>
>> Am 08.11.2016 um 16:28 schrieb michael vorberg > >:
>>
>> Thanks for the feedback
>>
>> Am 08.11.2016 16:01 schrieb "Frank Harrison" :
>>
>>> Right now, for NUKE/NUKEX specifically, a hIgher clock speed would be
>>> better. In a future release you will likely see more benefit from a higher
>>> number of cores.
>>>
>>> hth
>>>
>>> On 8 November 2016 at 14:38, michael vorberg 
>>> wrote:
>>>
 I was referring mostly to using nuke
 I know adding as much RAM as possible is helpful, GPU does not matter
 so much but CPU I'm not sure.

 Am 08.11.2016 14:48 schrieb "Rakesh Malik" :

> That depends a lot on the workload, especially these days when the
> processors' clock speeds are so dynamic, in that a 2.5GHz processor can
> overlock itself to over 3GHz. Desktop processors that are designed around
> more robust cooling solutions than mobile processors have even wider
> "turbo" ranges.
>
> Generally, adding more cores gives you more computing power overall,
> so it's more a question of how well the software you're using can take
> advantage of parallelism during rendering. Most software runs in a single
> thread, so adding cores has no direct benefit, but most of the higher end
> solutions in color grading and VFX are heavily threaded and get pretty 
> good
> utilization out of additional cores.
>
> The GPU is another major variable to consider; some software leans
> heavily on the GPU and doesn't use the main processor for computing, and
> some that do a surprisingly good job of consuming both.
>
>
> -
>
>
> [image: --]
>
> Rakesh Malik
> [image: https://]about.me/WhiteCranePhoto
>
> 
> Director of Photography
> http://www.WhiteCranePhotography.com
> 
>
>
>
> On Tue, Nov 8, 2016 at 3:54 AM, michael vorberg <
> pingkin...@googlemail.com> wrote:
>
>> Hi,
>> When buying a new workstation would I benefit more from a CPU with
>> higher clock speed and less cores or do more cores with lower speed give 
>> me
>> overall more render speed?
>>
>> Or is this all a "depends on" question?
>>
>> Greetings,
>> Michael
>>
>> ___
>> Nuke-users mailing list
>> Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
>> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
>>
>
>
> ___
> Nuke-users mailing list
> Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
>

 ___
 Nuke-users