Movie Clip Editor's timeline allows scrubbing beyond the editor area #41857

Closed
opened 2014-09-17 15:56:56 +02:00 by Seth L. · 6 comments

System Information
OS X 10.8.5
ATI Radeon HD 4850 512 MB

Blender Version
Broken: 2.71 9337574 (2.72 test build)

Short description of error
In the Movie Clip Editor a clip can extend beyond the area of the editor. So if you click the purple timeline and drag all the way to the right the Time Cursor goes under the Properties Shelf and under whatever area is to the right of that (the Properties Window by default). This seems unintentional, because after releasing the mouse button the Time Cursor will be on a frame you can't see or access unless you go to the Timeline editor.

If you don't have a workspace area set up for the Timeline editor or if you are in full screen mode you've just lost track of your Time Cursor. But even if you can still navigate using the Timeline it's just weird that the Time Cursor can go out of range like that.

Wouldn't it make more sense if the full clip duration corresponded with the full pixel span of the purple timeline bar?
Sure, this width will change as the window/area size is adjusted, and change as the Properties Panel is hidden/shown but that happens anyway.
With long clips there may not be enough pixels to represent each frame, but maybe holding shift for scrubbing in finer increments would address that.
I don't want to turn this into a feature request, just point out that it's awkward for the Time Cursor to go underneath part of the interface.

Here is a random .mov you can load up to test this if you don't have one handy:
TestQuicktime.mov

Exact steps for others to reproduce the error

  1. Open the Movie Clip Editor
  2. Open a movie clip
  3. Click the purple timeline, drag to the right as far as you can, and watch the Time Cursor become obstructed from view
**System Information** OS X 10.8.5 ATI Radeon HD 4850 512 MB **Blender Version** Broken: 2.71 9337574 (2.72 test build) **Short description of error** In the Movie Clip Editor a clip can extend beyond the area of the editor. So if you click the purple timeline and drag all the way to the right the Time Cursor goes *under* the Properties Shelf and under whatever area is to the right of that (the Properties Window by default). This seems unintentional, because after releasing the mouse button the Time Cursor will be on a frame you can't see or access unless you go to the Timeline editor. If you don't have a workspace area set up for the Timeline editor or if you are in full screen mode you've just lost track of your Time Cursor. But even if you can still navigate using the Timeline it's just weird that the Time Cursor can go out of range like that. Wouldn't it make more sense if the full clip duration corresponded with the full pixel span of the purple timeline bar? Sure, this width will change as the window/area size is adjusted, and change as the Properties Panel is hidden/shown but that happens anyway. With long clips there may not be enough pixels to represent each frame, but maybe holding shift for scrubbing in finer increments would address that. I don't want to turn this into a feature request, just point out that it's awkward for the Time Cursor to go underneath part of the interface. Here is a random .mov you can load up to test this if you don't have one handy: [TestQuicktime.mov](https://archive.blender.org/developer/F110890/TestQuicktime.mov) **Exact steps for others to reproduce the error** 1. Open the Movie Clip Editor 2. Open a movie clip 3. Click the purple timeline, drag to the right as far as you can, and watch the Time Cursor become obstructed from view
Author

Changed status to: 'Open'

Changed status to: 'Open'
Author

Added subscriber: @quantumanomaly

Added subscriber: @quantumanomaly

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
Sergey Sharybin self-assigned this 2014-09-17 17:11:36 +02:00

Well, that's actually pretty close to what's happening in the timeline -- you can drag the current frame out of the visible range there as well (with the only difference of continuous grab). It's actually quite useful to see clip outside of the scene frame range.

Thanks for the report, but it's not a bug, just intended behavior to cover some usecases.

Well, that's actually pretty close to what's happening in the timeline -- you can drag the current frame out of the visible range there as well (with the only difference of continuous grab). It's actually quite useful to see clip outside of the scene frame range. Thanks for the report, but it's not a bug, just intended behavior to cover some usecases.

Added subscriber: @sebastian_k

Added subscriber: @sebastian_k

I agree it might be confusing. Then again, the timeline behaves similar, following the continuous grab behavior in Blender. On top of that I find it very handy to be able to check out what's beyond the frame range. For example if you're tracking huge 5k openEXR footage you gotta track in chunks, in which case it helps to work with shorter frame ranges and then glue the separate parts together. And there it is great to be able to scrub beyond the frame limit to check for continuity.
So no, this is not a bug, it's a feature!
:)

I agree it might be confusing. Then again, the timeline behaves similar, following the continuous grab behavior in Blender. On top of that I find it very handy to be able to check out what's beyond the frame range. For example if you're tracking huge 5k openEXR footage you gotta track in chunks, in which case it helps to work with shorter frame ranges and then glue the separate parts together. And there it is great to be able to scrub beyond the frame limit to check for continuity. So no, this is not a bug, it's a feature! :)
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
3 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#41857
No description provided.