- Posts: 1
- Joined: Tue Mar 21, 2023 1:41 pm
- Real Name: Nils Schildhauer
Hello everyone,
I am fairly new to Resolve and just encountered a puzzling behavior - hoping anyone might be able to shed some light on whether this is intended behavior/user error or a bug...
I am working on video from a concert and have one timeline ("Cut") where I performed a basic multicam edit of three angles. I then created a separate timeline ("Compilation") to put together a short compilation/highlight reel with a few nested clips of the "Cut" timeline.
My expectation was that if I make an edit in the "Cut" timeline (i.e. changing an angle or retiming a cut), this change would be reflected in nested clips on the "Compilation" timeline. However, that seems to not be the case. I have tried restarting Resolve as well as doing an export, because I suspected there was some caching issue, but to no avail.
A solution/workaround I have already found is to decompose in place and perform the fine-tuning on the "Compilation" timeline, which is totally fine in this case, but still not what I imagine my ideal workflow to be like.
Do any of you know anything about this sort of behavior?
I can tell from a quick search that nested timelines are far from unproblematic (mostly in terms of audio issues), but I haven't found anything on this particular problem.
I am using Resolve 18.1.4 on a Mac Mini M1 running MacOS Ventura 13.2.1
I am fairly new to Resolve and just encountered a puzzling behavior - hoping anyone might be able to shed some light on whether this is intended behavior/user error or a bug...
I am working on video from a concert and have one timeline ("Cut") where I performed a basic multicam edit of three angles. I then created a separate timeline ("Compilation") to put together a short compilation/highlight reel with a few nested clips of the "Cut" timeline.
My expectation was that if I make an edit in the "Cut" timeline (i.e. changing an angle or retiming a cut), this change would be reflected in nested clips on the "Compilation" timeline. However, that seems to not be the case. I have tried restarting Resolve as well as doing an export, because I suspected there was some caching issue, but to no avail.
A solution/workaround I have already found is to decompose in place and perform the fine-tuning on the "Compilation" timeline, which is totally fine in this case, but still not what I imagine my ideal workflow to be like.
Do any of you know anything about this sort of behavior?
I can tell from a quick search that nested timelines are far from unproblematic (mostly in terms of audio issues), but I haven't found anything on this particular problem.
I am using Resolve 18.1.4 on a Mac Mini M1 running MacOS Ventura 13.2.1