[SOLVED] automatic node renumber fail upon upgrade

opening a project done on V16 on V17 RENUMBER ALL THE NODE STRUCTURE basically breaking all the node structure that we patiently buld.

following https://forum.blackmagicdesign.com/viewtopic.php?f=36&t=126211, this behaviour is highly not welcome as for automatic renumbering of nodes when a node is added in the middle of the stack.

fow the one of us the work with fixed node structure, this entirely break the workflow.

I have node numbers that mean something in the stack, do not change them arbitrarily please.

second issue: if you disconnect a early branch of a parallel node and you reconnect it, your node number get scrambled and never go back to what it was.

definitely prefer to revert back to V16 node numbering (take away the automatic part/give a preference to disable it).

I’m not on 17 but I wouldn’t want this to happen.
+1

Or at least, add Iran an option to turn on and off in preferences


Sent from my iPhone using Tapatalk

Agreed - i very much would like a preference for this. It's very easy to accidentally break a fixed node structure with they auto-number.

+1

It confuses workflow a lot.

+1 in adding this as a preference we can disable and enable at will and preferably at a project settings level and not at the software settings level.


Sent from my iPhone using Tapatalk

+1

There needs to be an option somewhere to keep the old node numbering system

Agreed, this not ideal at all, please set an option.

I can't see why this functionality would be useful in this state?

Keeping the existing v16 style and a "re-order node number ID's based on flow" would be a good be a good compromise?

+1

I would like to have the option.

I use a fixed node tree with narrative projects, and I'm dreading the upgrade to 17 because of this.

But then on commercials, I add nodes as needed, and automatic renumbering would be nice.

+1
Please give us the option to revert back. For people who use fixed node structures, this is a necessity.
Thank you

+1

Also:

1. Either allow node and tree position lock, and/or
2. Node and tree position reset through layout preset and/or
3. Release the API to select a node by number or name.

Thanks!

I think providing the option of customising the node number would work well for both user groups.

For non fixed node users, they can use the node system the way it currently is.

For fixed node users, they can number their nodes with 'gaps' in between them to allow new nodes without affecting nodes downstream.

EG:
Set first node as 05, second node as 10 etc. If you add a node before 05, it will become 04 and does not affect any nodes after it.
If you add a new node after 05 it becomes 06, and does not affect the node 10 or any nodes after it.
However if you insert 4 more nodes after 06 (07, 08, 09 & 10), it will effectively increment all nodes after by 1.

I think providing the option of customising the node number would work well for both user groups.

For non fixed node users, they can use the node system the way it currently is.

For fixed node users, they can number their nodes with 'gaps' in between them to allow new nodes without affecting nodes downstream.

EG:
Set first node as 05, second node as 10 etc. If you add a node before 05, it will become 04 and does not affect any nodes after it.
If you add a new node after 05 it becomes 06, and does not affect the node 10 or any nodes after it.
However if you insert 4 more nodes after 06 (07, 08, 09 & 10), it will effectively increment all nodes after by 1.

too convoluted.

the previous system was [FIFO] and the number sticks, the current is "dynamic alphanumeric renumbering based on flow".

just give us a tick in the settings and leave as it was.

How about the following check box?

Preferences>User>Color>Use a fixed node tree

Off by default, available for those who would use it.

How about the following check box?

Preferences>User>Color>Use a fixed node tree

Off by default, available for those who would use it.

It should be following the established paradigm: the default is the last version, don't change it unless we want to.

So you don't destroy the project upon upgrade the database....

+1 agreed @waltervalpatto


Dario Bigi, CSI
HP z840 - Dual 14 Core 2.6GHz - 64GB RAM - RTX 2x2080Ti - Internal SSD 8TB Raid. Windows 10 Pro 1903 - Resolve & Fusion Studio - FSI CM250 - Panasonic FZ1000 - Mini Panel

+1

Please go back to how it was.

It should be following the established paradigm: the default is the last version.

The setting would be new, so there wouldn't be a "last version" for that setting.

But that's a very small point, I think. The setting itself would satisfy, yes?

It should be following the established paradigm: the default is the last version.

The setting would be new, so there wouldn't be a "last version" for that setting.

But that's a very small point, I think. The setting itself would satisfy, yes?

Yes setting is fine, it is less problematic which is the default as long as you don't change the numbers during an upgrade of a project.

Oooh, that's a good point.

Also, let’s say that you have few nodes in parallel and you want to add a [serial before] node in one of the branch: that node number will be completely out of place and the renumbering will be weird as well, so now is not what i wanted and not ordered as well....

I can't access Reference, would you please help me to resolve it?
Thank you;
Landy500

[this post is moved by administrator because I started a new topic. Sorry for this)

Hello,
In the new version the node ordering is automatic.

This behaviour cause problem when using fixed node structure when I add nodes during grading in some clips. Is there an option to disable this type of ordering and use the old method available up to version 16?

Ex.
Suppose I use an invented structure:

[1]CST--> [2]CONTRAST--> [3]PIVOT--> [4]LOOK
and all clips has the same node tree.
When I go into node [4]LOOK and change parameters I can use RIPPLE NODE CHANGES TO SELECTED CLIP (OR GROUP) and apply a new parameters into all clip simultaneously at the same node without any problem.

but,
if during my grading, I have to add a node between (for ex) node [3] and [4] (for some reason) a new node tree become like this:
[1]CST--> [2]CONTRAST--> [3]PIVOT--> [4]NEW--> [5]PIVOT

In the last scenario if need to use RIPPLE NODE CHANGES TO SELECTED CLIP (OR GROUP) into a nodes [4] do not refer to the initial decision that was LOOK. Only clips with original node structure can be used into a clips where I added new nodes, there is a disaster.

Thank you.
Stefano

+1 agree @WalterVolpatto

+1 if there is an option to use the old method will be perfect.

There is a workaround for that: dont use the shortcuts to add a new node. if you add a node using right click into the node editor, resolve gives it an unused number, instead of changing the numbering in the whole node tree.

There is a workaround for that: dont use the shortcuts to add a new node. if you add a node using right click into the node editor, resolve gives it an unused number, instead of changing the numbering in the whole node tree.

Thx, but that is way to time consuming in a client session..
Please just give us the old way as an option

I agree, but waiting to come back this work around can be useful.

There is a workaround for that: dont use the shortcuts to add a new node. if you add a node using right click into the node editor, resolve gives it an unused number, instead of changing the numbering in the whole node tree.

no it does not work:

1) it renumber upon upgrade
2) make two parallel branch with few nodes each, go to the first node of the second branch, add a [corrector before] and the numbers are scrambled
3) in the same parallel branch disconnect the bottom branch and reconnect it. fun times...

looks like beta 17 has in teh [user] [color] [option] the ability to choose between the original database order of creation (the v16 method) and the automatic renumbering (v17 method).

THANKS!!!!!

I agree with you Walter,
I’m sorry, I didn’t try to refresh a clip or change clip and come back.
For this reasons I thought working but the problem is still there.
If you stay in the node tree seems to be right but is not so.
I hope BMD solving this issue.

I agree with you Walter,
I’m sorry, I didn’t try to refresh a clip or change clip and come back.
For this reasons I thought working but the problem is still there.
If you stay in the node tree seems to be right but is not so.
I hope BMD solving this issue.

it is solved in V17 beta7 with a setting in the [user][color][preserve node numbers when adding nodes]

Thank you Walter! BMD listened to you and your super node tree is preserved.

[quote="José Santos"]+1 in adding this as a preference we can disable and enable at will and preferably at a project settings level and not at the software settings level.

+5