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).
W10-19043.1645- Supermicro MB C9X299-PGF - RAM 128GBCPU i9-10980XE 16c 4.3GHz (Oc) Water cooled Decklink Studio 4K (12.3) Resolve 18.5.1 / fusion studio 18 GPU 3090ti drivers 512.59 studio
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.
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.
Last edited by jmaude on Thu Dec 31, 2020 3:37 pm, edited 1 time in total.
jmaude wrote: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.
W10-19043.1645- Supermicro MB C9X299-PGF - RAM 128GBCPU i9-10980XE 16c 4.3GHz (Oc) Water cooled Decklink Studio 4K (12.3) Resolve 18.5.1 / fusion studio 18 GPU 3090ti drivers 512.59 studio
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....
W10-19043.1645- Supermicro MB C9X299-PGF - RAM 128GBCPU i9-10980XE 16c 4.3GHz (Oc) Water cooled Decklink Studio 4K (12.3) Resolve 18.5.1 / fusion studio 18 GPU 3090ti drivers 512.59 studio
[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
i9 9900K 3.6Ghz, Gigabyte Z390 PRO AORUS, Gtx 3080, 64 GB RAM Crucial, M2 EVO Samsung 512, Intensity Pro 4K, Micro Panel
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.
i9 9900K 3.6Ghz, Gigabyte Z390 PRO AORUS, Gtx 3080, 64 GB RAM Crucial, M2 EVO Samsung 512, Intensity Pro 4K, Micro Panel
Stefano Marconcini wrote: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
Stefano Marconcini wrote: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...
W10-19043.1645- Supermicro MB C9X299-PGF - RAM 128GBCPU i9-10980XE 16c 4.3GHz (Oc) Water cooled Decklink Studio 4K (12.3) Resolve 18.5.1 / fusion studio 18 GPU 3090ti drivers 512.59 studio
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!!!!!
W10-19043.1645- Supermicro MB C9X299-PGF - RAM 128GBCPU i9-10980XE 16c 4.3GHz (Oc) Water cooled Decklink Studio 4K (12.3) Resolve 18.5.1 / fusion studio 18 GPU 3090ti drivers 512.59 studio
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.
i9 9900K 3.6Ghz, Gigabyte Z390 PRO AORUS, Gtx 3080, 64 GB RAM Crucial, M2 EVO Samsung 512, Intensity Pro 4K, Micro Panel
Stefano Marconcini wrote: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]
W10-19043.1645- Supermicro MB C9X299-PGF - RAM 128GBCPU i9-10980XE 16c 4.3GHz (Oc) Water cooled Decklink Studio 4K (12.3) Resolve 18.5.1 / fusion studio 18 GPU 3090ti drivers 512.59 studio
[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
Cyril Perrot-Botella C.S.I www.cyclopephotographie.com Ryzen threadripper 3970X 4.3GHz Liquid Cooler EVGA CLC 360 with 3 Noctua Gigabyte Designare TRX40 Corsair vengeance LPX-254GB-DDR4-3200MHz ASUS TUF Gaming RTX 3090 Ti 24GB DeckLink Mini Monitor 4K