NLA: New meta strip is created when the selection itself is one metastrip #99471

Closed
opened 2022-07-05 23:20:50 +02:00 by Alexander · 9 comments

System Information
Operating system: Ubuntu 20.04
Graphics card: Geforce MX230

Blender Version
Broken: 3.2.1 release candidate
Worked: (newest version of Blender that worked as expected)

Short description of error
We have the opportunity to create a meta strip from ONE meta strip, and, from the point of view of the Blender, it works quite well. A meta strip is created that contains the original meta strip, and this can be repeated indefinitely

Exact steps for others to reproduce the error

  • Open .blend file
  • Selet all available strips and create meta strip
  • select this meta strip and use the meta strip creation operator on it
  • repeat last step (will add new meta strip)
    untitled.blend
    2022-07-06 00-12-08.mp4
**System Information** Operating system: Ubuntu 20.04 Graphics card: Geforce MX230 **Blender Version** Broken: 3.2.1 release candidate Worked: (newest version of Blender that worked as expected) **Short description of error** We have the opportunity to create a meta strip from ONE meta strip, and, from the point of view of the Blender, it works quite well. A meta strip is created that contains the original meta strip, and this can be repeated indefinitely **Exact steps for others to reproduce the error** - Open .blend file - Selet all available strips and create meta strip - select this meta strip and use the meta strip creation operator on it - repeat last step (will add new meta strip) [untitled.blend](https://archive.blender.org/developer/F13261588/untitled.blend) [2022-07-06 00-12-08.mp4](https://archive.blender.org/developer/F13261586/2022-07-06_00-12-08.mp4)
Author

Added subscriber: @sanek2005

Added subscriber: @sanek2005
Member

Added subscriber: @PratikPB2123

Added subscriber: @PratikPB2123
Member

Changed status from 'Needs Triage' to: 'Needs User Info'

Changed status from 'Needs Triage' to: 'Needs User Info'
Member

Hi, thanks for the report. You mean don't add meta strip on top of it if selected is already a meta strip?
Will edit the report after your confirmation.

Hi, thanks for the report. You mean don't add meta strip on top of it if selected is already a meta strip? Will edit the report after your confirmation.
Author

it's easier to describe it with this picture
bug.png
let me remind you, this is all done with just ONE meta strip. In the process, no additional stripes appear, nothing is duplicated, we can just use the creation of a meta strip, having only one strip, which is clearly wrong

it's easier to describe it with this picture ![bug.png](https://archive.blender.org/developer/F13262355/bug.png) let me remind you, this is all done with just ONE meta strip. In the process, no additional stripes appear, nothing is duplicated, we can just use the creation of a meta strip, having only one strip, which is clearly wrong
Member

Added subscriber: @BClark

Added subscriber: @BClark
Member

Just a note, the idea and way MetaStrips work now are very limited and in the NLA roadmap that I am heading up for the Animation Module team, they need to be either improved on or replaced with more advanced organizational control/containers that can hold more than one strip across tracks and objects.

It looks like right now you are able to keep nesting them but there is no visual display of the nesting...no way to see the Meta "hierarchy"

Just a note, the idea and way MetaStrips work now are very limited and in the NLA roadmap that I am heading up for the Animation Module team, they need to be either improved on or replaced with more advanced organizational control/containers that can hold more than one strip across tracks and objects. It looks like right now you are able to keep nesting them but there is no visual display of the nesting...no way to see the Meta "hierarchy"
Pratik Borhade changed title from Strange behavior when adding a meta strip to New meta strip is created when the selection itself is one metastrip 2022-07-15 08:46:47 +02:00
Member

Changed status from 'Needs User Info' to: 'Confirmed'

Changed status from 'Needs User Info' to: 'Confirmed'
Philipp Oeser removed the
Interest
Animation & Rigging
label 2023-02-09 14:34:48 +01:00
Sybren A. Stüvel changed title from New meta strip is created when the selection itself is one metastrip to NLA: New meta strip is created when the selection itself is one metastrip 2023-05-19 15:06:55 +02:00

let me remind you, this is all done with just ONE meta strip. In the process, no additional stripes appear, nothing is duplicated, we can just use the creation of a meta strip, having only one strip, which is clearly wrong

This isn't actually the case. Try this:

  • Select the two Action strips
  • Press Ctrl+G to create a meta strip. It'll be called 'Meta' because this is the default name for meta strips
  • Press F2 to rename it to 'Meta 1' to give it a non-default name.
  • Press Ctrl+G to create a meta strip out of that. It'll be called 'Meta' again.
  • Press F2 to rename it to 'Meta 2' to give it a non-default, unique name.
  • Press Ctrl+Alt+G to un-meta the strip. You'll see that it now 'unpacks' into 'Meta 1'.
  • Press Ctrl+Alt+G to un-meta the strip. You'll see that it now 'unpacks' into the two Action strips.

If this isn't convincing, if you just press Ctrl+G and keep the names all 'Meta', you can run this code in the Python console:

>>> C.object.animation_data.nla_tracks['NlaTrack.001'].strips['Meta'].as_pointer()
140570209553608
>>> C.object.animation_data.nla_tracks['NlaTrack.001'].strips['Meta'].strips['Meta'].as_pointer()
140570209184168

This shows that, even though the inner and outer meta strip are both called 'Meta', they are in fact different strips in memory.

I'll close this report, as this is not a bug.

> let me remind you, this is all done with just ONE meta strip. In the process, no additional stripes appear, nothing is duplicated, we can just use the creation of a meta strip, having only one strip, which is clearly wrong This isn't actually the case. Try this: - Select the two Action strips - Press Ctrl+G to create a meta strip. It'll be called 'Meta' because this is the default name for meta strips - Press F2 to rename it to 'Meta 1' to give it a non-default name. - Press Ctrl+G to create a meta strip out of that. It'll be called 'Meta' again. - Press F2 to rename it to 'Meta 2' to give it a non-default, unique name. - Press Ctrl+Alt+G to un-meta the strip. You'll see that it now 'unpacks' into 'Meta 1'. - Press Ctrl+Alt+G to un-meta the strip. You'll see that it now 'unpacks' into the two Action strips. If this isn't convincing, if you just press Ctrl+G and keep the names all 'Meta', you can run this code in the Python console: ```python >>> C.object.animation_data.nla_tracks['NlaTrack.001'].strips['Meta'].as_pointer() 140570209553608 >>> C.object.animation_data.nla_tracks['NlaTrack.001'].strips['Meta'].strips['Meta'].as_pointer() 140570209184168 ``` This shows that, even though the inner and outer meta strip are both called 'Meta', they are in fact different strips in memory. I'll close this report, as this is not a bug.
Blender Bot added
Status
Archived
and removed
Status
Confirmed
labels 2023-05-19 15:14:04 +02:00
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
4 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#99471
No description provided.