Shared Nodes Possible Bug + Feature request

Hi,

just toying around with shared nodes in Resolve 15 studio full release on windows 10.

If I create a shared node and copy it to another clip and unlock the shared node, the software often crashes or it does unlock but still does not except changes.
Sometime it does work, so I do not see a consistent behavior.
If it does work, and I do a copy of the timeline, the shared nodes are no longer shared nodes. This is unfortunately a consistent behavior (a bug?).
This brings me also to a feature request. It would be cool, if a shared node would be persistent within different timelines. So when I do a change in Timeline 1 to a shared node, that change would be applied to the copy of the same shared node from Timeline 2.
The reason is, imagine grading a 30 second clip, when done the clients wants a 20 second cut down. Then he changes his mind about some grades from the 30 seconds version, would it not be cool if those changes would be applied automatically to the 20 second version (with the same clips and shared nodes.).

Thanks

Hello,

Here, I do not have any problems with the shared nodes by using them from one TL to another or from one clip to another in same TL.

No ISSUE to unlock them too or convert to corrector.

There is something wrong with your system.

Edit : typo error

I'm also finding Shared Nodes working just fine in Resolve Studio 15 on Windows 10 Pro (1803).

If it does work, and I do a copy of the timeline, the shared nodes are no longer shared nodes. This is unfortunately a consistent behavior (a bug?).

I'm seeing this too on MacOS, duplicating a timeline will convert any shared nodes to normal corrector nodes (albeit locked ones). Also, if I now take a clip in the duplicate timeline and add the shared node back into it, and then unlock it and try and make an adjustment, it crashes (and very consistently, tested when working on the same clip that had the shared node originally and also a different clip, and whether deleting the node that used to be a shared node or leaving it in).

Furthermore, swapping a shared node with another node will convert it to a regular (locked) corrector node. Even if you swap 2 shared nodes, they both become regular corrector nodes.

This brings me also to a feature request. It would be cool, if a shared node would be persistent within different timelines.

They already work that way

They already work that way

In that case, I move that from Feature Request to Bug report as this is not working for me :-/

If it does work, and I do a copy of the timeline, the shared nodes are no longer shared nodes. This is unfortunately a consistent behavior (a bug?).

I'm seeing this too on MacOS, duplicating a timeline will convert any shared nodes to normal corrector nodes (albeit locked ones). Also, if I now take a clip in the duplicate timeline and add the shared node back into it, and then unlock it and try and make an adjustment, it crashes (and very consistently, tested when working on the same clip that had the shared node originally and also a different clip, and whether deleting the node that used to be a shared node or leaving it in).

Furthermore, swapping a shared node with another node will convert it to a regular (locked) corrector node. Even if you swap 2 shared nodes, they both become regular corrector nodes.

This brings me also to a feature request. It would be cool, if a shared node would be persistent within different timelines.

They already work that way

Hi,

I did the manipulation:
I have a TL with a shared node
I duplicated => the shared node is no longer shared node but is locked. (Indeed he should have remained a shared node)
I unlocked it
I turned it into a corrector
I then changed LGG without crash.

I added the shared node (original)
I unlocked it
I turned it into a corrector
I then changed LGG without crash.

Mac issue for crash?