A few ideas to improve the NLA Editor #66115

Closed
opened 2019-06-25 12:11:32 +02:00 by Tom Wilson · 4 comments

I've been using Blender a lot recently to create short narrative animations.
Blender is amazing, don't get me wrong, but over the past few months I've built quite a list of gripes, particularly with the NLA Editor.
Here's some proposals for improvements that I think would make our lives easier.

  • Key frame insertion outside of tweaked strip's action extents - It seems very counter-intuitive to me to prevent a user from inserting key frames outside of the strip bounds of a tweaked strip, especially with Sync Length enabled. It may not seem like a massive problem at first, as one can easily set the action extents within the sidebar, but if you're testing a cyclic animation and you're trying to find the best length for your action you may need to set the action extent end frame time after time to allow new keyframes to be inserted. It's also quite easy to assume you're inserting keyframes with auto-keyframe insertion enabled, only to realise later that none of it is being recorded because it's outside the action extents. It's also quite easy to mistakenly set the strip extents, scaling the strip instead. I just don't understand why keyframe insertion isn't allowed outside the action extents while tweaking but you can duplicate keyframes in the action editor and place them anywhere outside the extents, this just seems like a mistake that's been overlooked.
  • Extend NLA Strips with a hotkey / dragging the edges with mouse - This needs no explanation really. There's the scale operator, but there isn't an extend operator / shortcut as far as I can see.
  • Context.nla_tracks - There is currently no easy way to find the NLA Tracks and Strips that are currently in view in the NLA Editor - which makes any Addon or Python manipulation involving NLA elements an incredibly difficult task. If I want to find the selected NLA Strips in the current context, I have to check every object with animation data in the blend file and apply all the NLA Editor filters manually in Python, and only then will I have a list of NLA Tracks that matches my context's NLA Editor.
  • Keyframe editing on zero influence NLA Strips (at the beginning / end of Blend In / Out) - OK, maybe this is my biggest gripe. I would really appreciate the ability to properly edit the beginning / end of an NLA Strip being blended in / out or with animated influence. I think influence should be ignored while a strip is in tweak mode so we can more accurately interpret the strip's action in the 3D viewport. The way I get around this currently is to create a temporary linked duplicate strip above the strip I want to edit, set the blend in/out to 0, tweak that, then delete it. Quite a faff though. (EDIT - Just realised I can unpin the action in the NLA Editor and this not only disables stretching / time remapping, but also influence)
  • Breakdown Selected NLA Strips into single action - This is not the same as baking NLA Tracks into frame-by-frame keyframes, but simply taking all the keyframes and doing the best job possible of creating a single action with them. I have written a script to do this for me and I use it a lot. It ignores blend in / out and any animation data on the strip itself (animated influence, strip time), but for 99% of cases this is not an issue.
  • Create a new Action with selected channels of an existing action - Very often I find I need to split an action into parts with specific channels, for separate NLA Strips. Again, I wrote myself a script to do this and it is very useful.
  • A toggle button in the header bar to Show only Tweaked NLA Strips - Often I'll find I'll accidentally leave some strips in tweak mode and if you have a very busy NLA Editor (as I do) it can be a pain to find the relevant strips sometimes. I would appreciate a way to filter out NLA Tracks without any strips in edit mode.
I've been using Blender a lot recently to create short narrative animations. Blender is amazing, don't get me wrong, but over the past few months I've built quite a list of gripes, particularly with the NLA Editor. Here's some proposals for improvements that I think would make our lives easier. - **Key frame insertion outside of tweaked strip's action extents** - It seems very counter-intuitive to me to prevent a user from inserting key frames outside of the strip bounds of a tweaked strip, especially with Sync Length enabled. It may not seem like a massive problem at first, as one can easily set the action extents within the sidebar, but if you're testing a cyclic animation and you're trying to find the best length for your action you may need to set the action extent end frame time after time to allow new keyframes to be inserted. It's also quite easy to assume you're inserting keyframes with auto-keyframe insertion enabled, only to realise later that none of it is being recorded because it's outside the action extents. It's also quite easy to mistakenly set the strip extents, scaling the strip instead. I just don't understand why keyframe insertion isn't allowed outside the action extents while tweaking but you can duplicate keyframes in the action editor and place them anywhere outside the extents, this just seems like a mistake that's been overlooked. - **Extend NLA Strips with a hotkey / dragging the edges with mouse** - This needs no explanation really. There's the scale operator, but there isn't an extend operator / shortcut as far as I can see. - **Context.nla_tracks** - There is currently no easy way to find the NLA Tracks and Strips that are currently in view in the NLA Editor - which makes any Addon or Python manipulation involving NLA elements an incredibly difficult task. If I want to find the selected NLA Strips *in the current context*, I have to check every object with animation data in the blend file and apply all the NLA Editor filters manually in Python, and only then will I have a list of NLA Tracks that matches my context's NLA Editor. - **Keyframe editing on zero influence NLA Strips (at the beginning / end of Blend In / Out)** - OK, maybe this is my biggest gripe. I would really appreciate the ability to properly edit the beginning / end of an NLA Strip being blended in / out or with animated influence. I think influence should be ignored while a strip is in tweak mode so we can more accurately interpret the strip's action in the 3D viewport. The way I get around this currently is to create a temporary linked duplicate strip above the strip I want to edit, set the blend in/out to 0, tweak that, then delete it. Quite a faff though. (EDIT - Just realised I can unpin the action in the NLA Editor and this not only disables stretching / time remapping, but also influence) - **Breakdown Selected NLA Strips into single action** - This is not the same as baking NLA Tracks into frame-by-frame keyframes, but simply taking all the keyframes and doing the best job possible of creating a single action with them. I have written a script to do this for me and I use it a lot. It ignores blend in / out and any animation data on the strip itself (animated influence, strip time), but for 99% of cases this is not an issue. - **Create a new Action with selected channels of an existing action** - Very often I find I need to split an action into parts with specific channels, for separate NLA Strips. Again, I wrote myself a script to do this and it is very useful. - **A toggle button in the header bar to Show only Tweaked NLA Strips** - Often I'll find I'll accidentally leave some strips in tweak mode and if you have a very busy NLA Editor (as I do) it can be a pain to find the relevant strips sometimes. I would appreciate a way to filter out NLA Tracks without any strips in edit mode.
Author

Added subscriber: @hedgehog90-3

Added subscriber: @hedgehog90-3

Added subscriber: @brecht

Added subscriber: @brecht

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
Brecht Van Lommel self-assigned this 2019-06-25 12:45:42 +02:00
Please see here: https://wiki.blender.org/wiki/Communication/Contact#User_Feedback_and_Requests
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
2 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#66115
No description provided.