Operating system: Windows-10-10.0.18362-SP0 64 Bits
Graphics card: Radeon RX 580 Series ATI Technologies Inc. 4.5.13596 Core Profile Context 20.10.35.02 27.20.1034.6
Broken: version: 2.93.0 Alpha, branch: master, commit date: 2021-04-02 21:26, hash: rB321eef6a0c0f
Short description of error
If you have Auto Keying enabled with "Only Active Keying Set", Blender creates keyframes for properties that aren't in the keying set, and creates keyframes for properties in the set when changing properties that aren't.
Exact steps for others to reproduce the error
- Load the default startup scene.
- Add two shape keys for the default cube (Basis and Key 1) and create keyframes for Key 1's "Value" and "Range Min" properties.
- In the Timeline editor, open the channel region (little ">" on the left) and expand the "Summary" and "Key" groups.
- Enable Auto Keying and move the playhead to another frame.
- In succession: move the cube, change the shape key's Value property, and change the shape key's Range Min property. Each time, Blender only creates the relevant keyframes. So far so good.
- Rightclick the Value property and choose "Add to Keying Set", then enable "Only Active Keying Set" in the Timeline editor. From now on, we only expect automatic keyframe creation for the Value property.
- Move the playhead to another frame.
- Change the Range Min property. Blender again creates a keyframe for it, even though it's not in the active keying set.
- Move the cube. Surprisingly, Blender creates a keyframe for the Value property, even though we didn't change it.
- As a bonus, move to another frame, move the default light, then select the cube again. Blender created a Value keyframe for the cube even though we didn't touch it.