Sorry for the delayed reply. Since the forum migration, I apparently stopped receiving notifications for some Automation Blocks questions, so I’m only catching up on them now.
This is an interesting idea. For simple nested sequences, it may be possible with Automation Blocks and some custom code, but I would not describe it as a ready-made “Decompose Clip” replacement like in Resolve.
The basic logic would be:
-
Find the selected nested clip in the active sequence.
-
Detect which sequence this nested clip refers to.
-
Read the trim range of the nested clip.
-
Look inside the nested sequence and find the clips that overlap that trim range.
-
Recreate those clips in the parent sequence at the correct time positions, possibly on newly created video tracks.
-
Optionally remove or disable the original nested clip.
So for a simple nest that contains normal clips, no complex timing changes, and a predictable track layout, this could probably be scripted.
The tricky part is making it reliable for all real-world cases. Things like transitions, effects, speed changes, time remapping, adjustment layers, linked audio, nested nests, track targeting, and overlaps can make this much more complex. Also, the existing community script for nesting goes in the opposite direction; un-nesting is not just the reverse operation, because the script has to translate the visible trimmed range of the nested clip back into the timeline of the nested sequence.
So my answer would be: yes, this is a possible custom Automation Blocks scripting project for a controlled/simple use case, but probably not something I would recommend as a general-purpose one-click “decompose everything” tool without more testing.
If you can share a very small example project or describe the exact structure of the nested sequences, I can better judge how realistic it is for that specific case.