UnMeta Strip messing up strip order #97309

New Issue

Georg K · 2022-04-13T15:47:13+02:00

Georg K commented

2022-04-13 15:47:13 +02:00

System Information
Operating system: Linux-5.15.28-1-MANJARO-x86_64-with-glibc2.35 64 Bits
Graphics card: AMD VERDE (DRM 2.50.0, 5.15.28-1-MANJARO, LLVM 13.0.1) AMD 4.5 (Core Profile) Mesa 21.3.7

Blender Version
Broken: 2.79b, 3.1.0, version: 3.2.0 Alpha, branch: master, commit date: 2022-04-13 10:30, hash: babd027fae
Worked: -

Short description of error
In some cases, unpacking a meta strip with unmeta messes up the order of the included strips, breaking the compositing setup.
When creating a meta strip, the original absolute channel number of each strip seems to be saved in the meta strip, so, on unpacking, if there is another strip occupying the original channel, there is a "collision", no matter how much the meta strip has been moved away vertically from the occupying strip. The "collision" is solved by moving only the colliding strips from the meta strip to the top.

For example, if a source strip of the meta strip was in channel 1 and the meta strip is moved so that channel 1 is occupied by another clip, instead of unpacking the strips relative to the vertical position of the meta strip, the original absolute strip channel values are used and since two strips can't occupy the same space, just the colliding strip is moved.

Exact steps for others to reproduce the error

Start Blender with the Video Editing preset
Add a red color strip to channel 1 and a blue color strip to channel 2
select both and Ctrl-G turn them into a meta strip (meta strip is created on channel 2)
add a new color strip to channel 1
unmeta the meta strip in channel 2
now you have blue in the lower channel and red in the upper channel, the order has switched

**System Information** Operating system: Linux-5.15.28-1-MANJARO-x86_64-with-glibc2.35 64 Bits Graphics card: AMD VERDE (DRM 2.50.0, 5.15.28-1-MANJARO, LLVM 13.0.1) AMD 4.5 (Core Profile) Mesa 21.3.7 **Blender Version** Broken: 2.79b, 3.1.0, version: 3.2.0 Alpha, branch: master, commit date: 2022-04-13 10:30, hash: `babd027fae` Worked: - **Short description of error** In some cases, unpacking a meta strip with unmeta messes up the order of the included strips, breaking the compositing setup. When creating a meta strip, the original absolute channel number of each strip seems to be saved in the meta strip, so, on unpacking, if there is another strip occupying the original channel, there is a "collision", no matter how much the meta strip has been moved away vertically from the occupying strip. The "collision" is solved by moving only the colliding strips from the meta strip to the top. For example, if a source strip of the meta strip was in channel 1 and the meta strip is moved so that channel 1 is occupied by another clip, instead of unpacking the strips relative to the vertical position of the meta strip, the original absolute strip channel values are used and since two strips can't occupy the same space, just the colliding strip is moved. **Exact steps for others to reproduce the error** - Start Blender with the Video Editing preset - Add a red color strip to channel 1 and a blue color strip to channel 2 - select both and Ctrl-G turn them into a meta strip (meta strip is created on channel 2) - add a new color strip to channel 1 - unmeta the meta strip in channel 2 - now you have blue in the lower channel and red in the upper channel, the order has switched

Georg K commented

2022-04-13 15:47:13 +02:00

Added subscriber: @georgK

Philipp Oeser commented

2022-04-14 10:35:18 +02:00

Added subscriber: @lichtwerk

Philipp Oeser commented

2022-04-14 10:35:18 +02:00

Changed status from 'Needs Triage' to: 'Confirmed'

Philipp Oeser commented

2022-04-14 10:35:18 +02:00

Can confirm.

Richard Antalik commented

2022-04-14 18:48:00 +02:00

Added subscriber: @iss

Richard Antalik commented

2022-04-14 18:48:00 +02:00

This is technically expected behavior as un-meta just moves strips to level above regardless of causing conflicts. Then only conflicting strips are moved around in way, also regardless of hierarchy.

So can consider this as known issue. I think solution would be simple-ish in this case - try to resolve conflicts for all strips within meta, not individually. but in other cases resolving conflicts could be wiser too.

This is technically expected behavior as un-meta just moves strips to level above regardless of causing conflicts. Then only conflicting strips are moved around in way, also regardless of hierarchy. So can consider this as known issue. I think solution would be simple-ish in this case - try to resolve conflicts for all strips within meta, not individually. but in other cases resolving conflicts could be wiser too.

Philipp Oeser removed the

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

UnMeta Strip messing up strip order #97309