Page MenuHome

Keyframes of Compositing Nodes get deleted when muting that node
Closed, ResolvedPublic

Description

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

Event Timeline

Thomas Beck (plasmasolutions) lowered the priority of this task from Needs Triage by Developer to Confirmed, Medium.Jan 15 2014, 11:46 AM

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

@Lukas Toenne (lukastoenne) I will look into this after my pc is running again (tomorrow)
@Christian Elsässer (chris74656) thanks for reporting!

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. ;-)

@Bastien Montagne (mont29) or @Lukas Toenne (lukastoenne): 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!

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 ...