Cache's green line refresh problem

[Francois-Grassard]

Hi friends,

The green line is not well refreshed in certain case.

Step to reproduce :

• Start Natron
• Add a read node and source a sequence
• Connect it the viewer
• Press Play to load all frames in RAM (wait for the end of the sequence)
• Place the mouse cursor on the image and press Space to maiximze it

----> Composite is recalculated from scratch because of the new size of the image (we can be sure of that because Natron play the sequence slowly) ... but the green line is still there. :o)

Natron 0.94 / Win8 / 64 Bits / Zip Version

Thanks !!!

[MrKepzie]

Actually this is because the whole sequence that you read at a lower scale factor is still in the cache, the the green line won't go away.
If we clear it while in playback at a different scale factor, then if you would get back to the original scale factor the timeline wouldn't be coloured green but in fact all the images would still be cached (because of the first playback). As said, this line is more to be viewed as a hint than a perfect hint on what's in the cache.
Otherwise we would have to do more heuristics to update this cache line (every time you zoom in/out…) and it would slow down the software as a whole… for very little purpose.

On Jun 28, 2014, at 2:36 PM, Francois-Grassard notifications@github.com wrote:

Hi friends,

The green line is not well refreshed in certain case.

Step to reproduce :

Start Natron
Add a read node and source a sequence
Connect it the viewer
Press Play to load all frames in RAM (wait for the end of the sequence)
Place the mouse cursor on the image and press Space to maiximze it
----> Composite is recalculated from scratch because of the new size of the image (we can be sure of that because Natron play the sequence slowly) ... but the green line is still there. :o)

Natron 0.94 / Win8 / 64 Bits / Zip Version

Thanks !!!

—
Reply to this email directly or view it on GitHub.

[Francois-Grassard]

I understand now. :o)
Thank you to have clarified this point.

[blackearth2014]

What if you have multiple computers that you want to use as a render farm, could this feature that Francois request be possible as an active background render? The render or cache engine continuously distributes the process amongst multiple render nodes. I think I saw a demonstration of this in Digital Fusion with its compositor. They provide additional software that can be installed on other computers and used to render realtime.

Not really a need for now though.

[MrKepzie]

I don't understand what feature request you're talking about ? You want a cache shared by all render nodes ?

[blackearth2014]

I am sorry wrong use of words or terms. I referring to Francois issue with the cache. Your last paragraph and I quote

"Otherwise we would have to do more heuristics to update this cache line (every time you zoom in/out…) and it would slow down the software as a whole"

So I was wondering since Natron can be used on a render farm, can the cache be distributed to other render nodes on a network?

[MrKepzie]

No, the cache is local to a computer's RAM, it is not shared. Plus there's no point sharing this cache as on a render farm typically each node is rendering a different frame range, such as
Node 1: 0 - 99
Node 2 : 100- 199
etc..

So they don't have anything to share really

[Francois-Grassard]

And AFAIK, sending the cache trough the network could be far slower than recalculate it on each local machines. At least with most common networking solutions (simple switch with Gigabits connections :)

[blackearth2014]

Got it.