- User Since
- Feb 11 2018, 12:27 AM (48 w, 5 d)
Thu, Jan 10
In the newly introduced bug, the curves are initially not functioning, but "spring into action" as soon as any kind of animation data is changed in the strip (even a cancelled move - hitting G on a keyframe and hitting ESC) .
After a bit more testing, it looks like this patch indeed solves this bug, but also introduces a new minor bug T60194.
Sorry about that, it looks like I introduced this bug in my local build by applying a patch I made to solve this bug : T60194
After applying my patch, I was unable to reproduce T55668. It looks like each strip its given a unique name properly, even with nested Meta-Strips.
Sun, Jan 6
Sat, Jan 5
After investigation, I believe I can submit a patch that solves this issue. Please let me know what you think and how much testing this requires
I've been using my patch since Feb. without any issues, therefore I believe adding support for clip, sene and meta proxies is an easy task, although I'm not familiar enough with the Blender coding conventions to submit a commit myself.
Feb 15 2018
But are we really calling this proxy function with sound strips ? Maybe we should show a warning if we reach this point ?
Feb 14 2018
No, they should have a unique proxy path. I am not an expert, but for scene and meta clips, using seq->name seems to do the job.