Page 1 of 1

New node numbering behaviour ruins default nodetree approach

PostPosted: Sat Nov 14, 2020 12:44 pm
by Anton Meleshkevich
Please give us an option to bring back fixed numbers of nodes.
In v17 it is impossible to use any standard node tree structure for all shots.
Let's say I have node 10 as a trim pass node in all the clips. And I have different quantity of nodes for power windows in different clips before this trim pass node. In previous versions of resolve I could just set selecting the same node and I always got trim pass node selected when I switch for one clip to another.
Also I have node 1 preserved for CDL, but I have some nodes before node 1.

But now it is impossible to use this approach.

I know, there are many colorists work like this including @waltervolpatto
(I tried to mention a user, but it didn't work)

Re: New node numbering behaviour ruins default nodetree appr

PostPosted: Sat Nov 14, 2020 1:27 pm
by Jean Paul Sneider
+1

I agree, the new approach is useful for navgating tree with "pre node" "next node" but less useful when switching between clips

Re: New node numbering behaviour ruins default nodetree appr

PostPosted: Sat Nov 14, 2020 1:36 pm
by Lee Niederkofler
+1
The new mode would cost me a lot of time in sessions

Re: New node numbering behaviour ruins default nodetree appr

PostPosted: Sat Nov 14, 2020 2:00 pm
by Lee Niederkofler
And if you don‘t want / can‘t change the behaviour, I‘d suggest adding the ability to jump to a specific node via keyboard shortcut.
I only need 3-4 nodes to be quickly accessible most of the time in my node tree, so I would love to be able to create shortcuts for them!
I know this is somewhat possible via the big panel, but also that would take to much button pressing for me. I want 1 button push to jump to node x. This would be quite the time saver for most colorists.

——-
A bit more detailed why the old behaviour was so much better:
As most people do, I use a prevuilt node tree for every project. In that node tree I place the first couple numbers of nodes on key positions. So I can quickly jump via the next/prvs node buttons on the mini panel to those nodes that I always use. And this is without the need to look at the UI, so I can be very efficient and fast.
F.e. Lets say my last node in the tree is controlling my shadows. (Its no 4, even though I have 20 nodes, before that node)So I only need to press the next node button 3 times to quickly get from first node to the last node. I don‘t need to look at the UI as I alway know its the 4th node.
With the new way, I would need to press 10/sometimes 11/12.. times the next button to jump f.e. to the last node. it would be different on many shots. I would need to constantly look at the UI while switching nodes. And this would cost a lot of time over the day, as I need to jump to those nodes on pretty mich every shot. Constantly jumping forward and backward..

Hope this helps BMD to see why it is a problem

Thanks

Re: New node numbering behaviour ruins default nodetree appr

PostPosted: Sat Nov 14, 2020 3:11 pm
by Master Nurmi
My suggestion would be to get labels behave like that
"Correction" jumps to "correction" to "correction" to "correction", and so on

Re: New node numbering behaviour ruins default nodetree appr

PostPosted: Sat Nov 14, 2020 4:06 pm
by Tom Early
A user preference should fix this, there's pros and cons to each approach

Re: New node numbering behaviour ruins default nodetree appr

PostPosted: Sat Nov 14, 2020 6:47 pm
by Anton Meleshkevich
Tom Early wrote:there's pros and cons to each approach

I can't see any reason to exist node numbers at all, if they aren't associated with nodes. They become just a decorative thing and loose all of their functionality.

Re: New node numbering behaviour ruins default nodetree appr

PostPosted: Sun Nov 15, 2020 5:15 am
by Jim Simon
Anton Meleshkevich wrote:I can't see any reason to exist node numbers at all

'Exist' is an intransitive verb, it doesn't take an object. You can't 'exist' something.

So...what?

Re: New node numbering behaviour ruins default nodetree appr

PostPosted: Sun Nov 15, 2020 7:05 am
by Anton Meleshkevich
Jim Simon wrote:So...what?

I apologize for my bad English. I mean, this new node numbering is something that has no reason to be there in its current state at all. Because now it is just ...numbers. All its functionality is gone. I don't know how this can be useful at all.

"I can't see any reason for this new node numbering system to exist at all"

Re: New node numbering behaviour ruins default nodetree appr

PostPosted: Sun Nov 15, 2020 6:14 pm
by Jim Simon
Ah, got it. Thanks.

It's my understanding that nodes added 'before' and being assigned a 'later' number was an issue that many folks wanted corrected.

It's been corrected.

Re: New node numbering behaviour ruins default nodetree appr

PostPosted: Tue Dec 01, 2020 5:01 pm
by Anton Meleshkevich
Just wanted to bump this thread as I think this is important.

Re: New node numbering behaviour ruins default nodetree appr

PostPosted: Tue Dec 01, 2020 5:12 pm
by Lee Niederkofler
+1

Re: New node numbering behaviour ruins default nodetree appr

PostPosted: Fri Dec 18, 2020 2:11 pm
by Anton Meleshkevich
Please add the possibility to disable node numbers auto sorting.