Inconsistency in the behavior of 'Jump to next/previous keyframe' operator #100493
Labels
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
6 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#100493
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
System Information
Operating system: Linux-5.4.0-124-generic-x86_64-with-glibc2.31 64 Bits
Graphics card: NVIDIA GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 510.47.03
Blender Version
Broken: version: 3.3.0 Beta, branch: Unknown, commit date: Unknown Unknown, hash:
rBUnknown
Worked: as far as I know, none.
Short description of error
When calling the 'Jump to next/previous keyframe' operator, there are inconsistency of behavior depending whether the active object is a Grease Pencil one or not.
For standard keyframes, it jumps to next keyframe if the object is active, regardless of if the object or any of its channels are selected.
For grease pencil layers keyframes, it jumps to next keyframe only if the layer channel is selected.
Exact steps for others to reproduce the error
Reproduce the bug :
issue_jump_to_next_keyframe.mp4
Added subscriber: @amelief
Added subscribers: @mendio, @pepe-school-land
@pepe-school-land @mendio
I would like some user feedback on this. AFAIK, this behavior was always here, but it was not really visible because the grease pencil layer keyframes were not displayed with the 'regular' keyframes in the main dopesheet.
What do you think the behavior should be ?
In my opinion the jump should at least disregard selection in grease pencil layer channels if it disregards selection of other types of channels. But that change may be confusing for grease pencil users.
Added subscriber: @PierreSchiller
When a 2d animator sets main keyframes (aka reference keys), this function to "jump to next keyframe" is a quick solution to "flip pages back and forth" (just a figure of speech). The Jump to previous/next keyframe" should target all layers not just the current GP layer.
There can even be an operator that targets this from a custom (ie. hardware buttons in any stylus tablet) shortcut:
Insert Blank keyframe (all layers) /// bpy.ops.gpencil.blank_frame_add(all_layers=True)
Added subscriber: @lichtwerk
Changed status from 'Needs Triage' to: 'Needs Developer To Reproduce'
Looks like this is something the #grease_pencil and #animation_rigging modules have to discuss/agree upon.
Yes, I agree.
Also, as I mentionned in the chat, the code makes it look like the intended behavior was to only include animation channels that are selected in the jump :
screen_ops.c:3071 (keyframe_jump_exec)
When I call 'Jump to next/prev keyframe', flag
SCE_KEYS_NO_SELONLY
is not set. (meaning the if condition above is true).However, this is not what's happening (at least for non-grease pencil keyframes)
Added subscriber: @AndyCuccaro
I believe that it would actualy make sense if jumping to next keyframe would jump to the next "global" keyframe if there's nothing selected at all, just like within Grease Pencil, if there's no layer selected it then jumps to the next keyframe from that whole GP object.
Added subscriber: @hamza-el-barmaki
as a user of Grease Pencil, i share the same opinion with some addition in summary column
1- clicking in empty place in summary column will diselect all layers so jumping happen for all layer as they are all selected
2- we can use selection box and circle to select a bunch of layers quickly and scrolling automaticaly while selecting layers when using selection box.
3- invert selection (already existe).
......
Hi everybody!
The Grease Pencil team we have met to discuss this issue. The current behavior is based on a lot of feedback from productions that are using GP, where it is important to only be able to jump between keyframes on a specific layer.
In an ideal world it would be great if these two behaviors existed by default in Blender. An operator to jump between global frames of the object and another operator to jump only between frames of a selected channel, so it would be consistent.
Apart of this when we have been investigating this matter, we have discovered a small problem related to this when you are in the doopesheet (in Grease pencil submodule)
https://developer.blender.org/T100538
Daniel
Okay. I understand, if the behavior is proofed, then it makes sense not to disturb it.
As Andy Cuccaro said, maybe we could add the 'Jump to next keyframe' to be global in the gpencil layers if no layer is selected ?
That would be a way for users to do this global jump, without having to add another operator.
I guess future development of the grease pencil will allow more hybrid 3d/2d projects, so I'm thinking that we should keep in mind this kind of consistency issues.