Keyframes of Compositing Nodes get deleted when muting that node #38221

New Issue

Christian Elsässer · 2014-01-14T22:27:52+01:00

2014-01-14 22:27:52 +01:00

System Information
Windows 8.1
NVIDIA GeForce GTX 660M - 2GB
i7-3740 QM @ 2.7GHz
16gb RAM

Blender Version
Broken: 2.69.0 r60995

Short description of error
When any value of a Compositing Node is keyframed everything works as expected. If that node now gets muted all keyframes of that node are cleared. when unmuting that node again keyframes are still gone. when pressing CTRL Z, the keyframes are back there (node is muted again) ... unmuting then won't clear the keyframes.

This Bug just affects compositing nodes and keyframes... shader nodes and texture nodes work fine, as well as drivers on compositing nodes don't get deleted.

Exact steps for others to reproduce the error
open node editor
switch to compositing nodes
tick "use nodes"
add any node (i confirmed this bug with mix, alpha over, invert, HSV, RGB Curver, so i guess all compositing nodes are affected)
while hovering over a numeric value press "i" to add a keyframe ==> turns yellow
mute that node by pressing "m" ==> turns grey

optional:
unmute that node by pressing "m" again ==> stays grey
CTRL Z ==> note is muted again, keyframes are back in position (fields are yellow)
unmute that node by pressing "m" again ==> keyframes stay there ==> field stays yellow

**System Information** Windows 8.1 NVIDIA GeForce GTX 660M - 2GB i7-3740 QM @ 2.7GHz 16gb RAM **Blender Version** Broken: 2.69.0 r60995 **Short description of error** When any value of a Compositing Node is keyframed everything works as expected. If that node now gets muted all keyframes of that node are cleared. when unmuting that node again keyframes are still gone. when pressing CTRL Z, the keyframes are back there (node is muted again) ... unmuting then won't clear the keyframes. This Bug just affects compositing nodes and keyframes... shader nodes and texture nodes work fine, as well as drivers on compositing nodes don't get deleted. **Exact steps for others to reproduce the error** open node editor switch to compositing nodes tick "use nodes" add any node (i confirmed this bug with mix, alpha over, invert, HSV, RGB Curver, so i guess all compositing nodes are affected) while hovering over a numeric value press "i" to add a keyframe ==> turns yellow mute that node by pressing "m" ==> turns grey optional: unmute that node by pressing "m" again ==> stays grey CTRL Z ==> note is muted again, keyframes are back in position (fields are yellow) unmute that node by pressing "m" again ==> keyframes stay there ==> field stays yellow

Christian Elsässer commented

2014-01-14 22:27:52 +01:00

Changed status to: 'Open'

Christian Elsässer commented

2014-01-14 22:27:52 +01:00

Added subscriber: @ChristianElsasser

blender-admin commented

2014-01-14 22:27:52 +01:00

#38286 was marked as duplicate of this issue

Thomas Beck commented

2014-01-15 11:48:49 +01:00

Added subscribers: @LukasTonne, @plasmasolutions

Thomas Beck commented

2014-01-15 11:48:49 +01:00

I can confirm that, seems like the keyframe data is deleted then...

@LukasTonne I will look into this after my pc is running again (tomorrow)
@ChristianElsasser thanks for reporting!

I can confirm that, seems like the keyframe data is deleted then... @LukasTonne I will look into this after my pc is running again (tomorrow) @ChristianElsasser thanks for reporting!

Thomas Beck self-assigned this 2014-01-15 11:49:15 +01:00

Bastien Montagne commented

2014-01-19 15:10:02 +01:00

Added subscriber: @quantumanomaly

Bastien Montagne commented

2014-01-19 15:10:02 +01:00

◀ Merged tasks: #38286.

Bastien Montagne commented

2014-01-19 15:10:31 +01:00

Added subscriber: @mont29

Seth L. commented

2014-01-20 07:23:16 +01:00

Thanks mont29 for identifying my report as a duplicate. Sorry I didn't catch it. I did search with similar keywords before submitting, I swear. At least better to get reported twice than never at all though. ;-)

Thomas Beck commented

2014-01-20 08:24:11 +01:00

@mont29 or @LukasTonne: Could one of you look into this and take ownership of this bug? As my PC is still broken I can't fix this issue.. writing from my mobile phone now..Thanks!

Thomas Beck was unassigned by Lukas Tönne

2014-01-20 12:21:57 +01:00

Lukas Tönne self-assigned this 2014-01-20 12:21:57 +01:00

Lukas Tönne commented

2014-01-20 12:21:57 +01:00

This is related to the anim fcurves cleanup, which is supposed to remove fcurves for deleted nodes:
https://developer.blender.org/diffusion/B/browse/master/source/blender/blenkernel/intern/node.c;1b3fdc43095d8d0a7dff9adf5c93dbad81a85576$1620

Possibly this happens when localized node trees from the compo preview job get deleted, although these should not be touching the original tree's animdata ...

This is related to the anim fcurves cleanup, which is supposed to remove fcurves for deleted nodes: https://developer.blender.org/diffusion/B/browse/master/source/blender/blenkernel/intern/node.c;1b3fdc43095d8d0a7dff9adf5c93dbad81a85576$1620 Possibly this happens when localized node trees from the compo preview job get deleted, although these should not be touching the original tree's animdata ...

blender-admin commented

2014-01-20 12:52:30 +01:00

This issue was referenced by blender/blender-addons-contrib@f70921d90c

This issue was referenced by blender/blender-addons-contrib@f70921d90ccbaf6d54f5bcc90a9ef665d9001361

blender-admin commented

2014-01-20 12:52:30 +01:00

This issue was referenced by f70921d90c

This issue was referenced by f70921d90ccbaf6d54f5bcc90a9ef665d9001361

Lukas Tönne commented

2014-01-20 12:57:07 +01:00

Changed status from 'Open' to: 'Resolved'

Lukas Tönne closed this issue