VSE's UI disappears when forcing new vertical lines to overlap completely #90389

Closed
opened 2021-08-02 19:56:36 +02:00 by Gerard Taulats Braos · 7 comments

System Information
Operating system: Windows-10-10.0.19041-SP0 64 Bits
Graphics card: Intel(R) HD Graphics 4600 Intel 4.3.0 - Build 20.19.15.5171

Blender Version
Broken: version: 3.0.0 Alpha, branch: master, commit date: 2021-08-01 18:52, hash: 836aeebf70
Worked: 2.93

Short description of error
When forcing to draw more lines by changing the FPS and base, the point where all vertical lines overlap makes disappear these lines and the scrubbing bar (not the cursor).

Exact steps for others to reproduce the error

  • Open a Video Sequencer panel (Sequencer)
  • Set FPS to 1 and base to 10 (In Properties/Scene/Dimensions/Frame Rate/Custom
  • Zoom out
    image.png

Observations:

  • Of course the disappearing of the scrub bar may be fixed, behaving like 2.93.
  • On the other hand, the drawing of vertical lines keeps being "arbitrary" in the eyes of the times being displayed. For example, comparing 10 FPS and 5 FPS (base 1) max zoomed out, when using 10 there's 1 line inbetween the others that match with time displayed (I'll call them main lines). When using 5, it's 3. The problem scalates when using more extreme values, causing the lines to overlap.
  • Another way to trigger this issue is by changing the Resolution Scale in Preferences, where more lines will appear inbetween the main ones, the larger the UI is. Being this the case, with the UI at 2x the bug described in this report occurs with 1 FPS and base 5 instead of 10.
  • From the user point of view, I'd suggest to display up to 3 vertical lines inbetween main lines. At least for me, I loose track of the actual value of the inbetweeners by having 4 or more, aside it becomes crammed.
**System Information** Operating system: Windows-10-10.0.19041-SP0 64 Bits Graphics card: Intel(R) HD Graphics 4600 Intel 4.3.0 - Build 20.19.15.5171 **Blender Version** Broken: version: 3.0.0 Alpha, branch: master, commit date: 2021-08-01 18:52, hash: `836aeebf70` Worked: 2.93 **Short description of error** When forcing to draw more lines by changing the FPS and base, the point where all vertical lines overlap makes disappear these lines and the scrubbing bar (not the cursor). **Exact steps for others to reproduce the error** - Open a Video Sequencer panel (Sequencer) - Set FPS to 1 and base to 10 (In Properties/Scene/Dimensions/Frame Rate/Custom - Zoom out ![image.png](https://archive.blender.org/developer/F10260570/image.png) --- Observations: - Of course the disappearing of the scrub bar may be fixed, behaving like 2.93. - On the other hand, the drawing of vertical lines keeps being "arbitrary" in the eyes of the times being displayed. For example, comparing 10 FPS and 5 FPS (base 1) max zoomed out, when using 10 there's 1 line inbetween the others that match with time displayed (I'll call them main lines). When using 5, it's 3. The problem scalates when using more extreme values, causing the lines to overlap. - Another way to trigger this issue is by changing the Resolution Scale in Preferences, where more lines will appear inbetween the main ones, the larger the UI is. Being this the case, with the UI at 2x the bug described in this report occurs with 1 FPS and base 5 instead of 10. - From the user point of view, I'd suggest to display up to 3 vertical lines inbetween main lines. At least for me, I loose track of the actual value of the inbetweeners by having 4 or more, aside it becomes crammed.

Added subscriber: @Tabra

Added subscriber: @Tabra
Gerard Taulats Braos changed title from VSE's UI dissapears when forcing new vertical lines to overlap completely to VSE's UI disappears when forcing new vertical lines to overlap completely 2021-08-02 19:57:46 +02:00

Added subscriber: @iss

Added subscriber: @iss

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

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

I can reproduce the issue, but strangely it dissappears when showing frame numbers instead of time. This is the case in all editors not only VSE.

In VSE I have resorted in using hack, which multiplies line spacing by 3 so lines aren't too dense. But they still result in size steps of 1, 2, 4, 5, 10, 20, etc.

From the user point of view, I'd suggest to display up to 3 vertical lines inbetween main lines. At least for me, I loose track of the actual value of the inbetweeners by having 4 or more, aside it becomes crammed.

Can you explain this in more detail? Do you mean to add more lines?

I think main problem is fix when labels do overlap only every other is displayed but when you increase spacing by 3x, it is rather unpleasant to work with. So I may revert this change or at least make it even.

I can reproduce the issue, but strangely it dissappears when showing frame numbers instead of time. This is the case in all editors not only VSE. In VSE I have resorted in using hack, which multiplies line spacing by 3 so lines aren't too dense. But they still result in size steps of 1, 2, 4, 5, 10, 20, etc. > From the user point of view, I'd suggest to display up to 3 vertical lines inbetween main lines. At least for me, I loose track of the actual value of the inbetweeners by having 4 or more, aside it becomes crammed. Can you explain this in more detail? Do you mean to add more lines? I think main problem is fix when labels do overlap only every other is displayed but when you increase spacing by 3x, it is rather unpleasant to work with. So I may revert this change or at least make it even.

Can you explain this in more detail? Do you mean to add more lines?

Sure. What I mean is that the number of lines being drawn should be consistent regardless of any combination of FPS, base and/or UI scaling, since it's pointless to have more lines if you can't know what it represents and/or makes it crammed.

For example, using FPS=2 and Base=1:

  • Zooming out until 30:00 works as spected: drawing and removing new lines.
    image.png
  • From this point on, no more lines are being removed.
    image.png

What I meant by showing up to 3 inbetween lines is that it becomes crammed after that, but I guess the main issue is that the hour lines are not being removed.

> Can you explain this in more detail? Do you mean to add more lines? Sure. What I mean is that the number of lines being drawn should be consistent regardless of any combination of FPS, base and/or UI scaling, since it's pointless to have more lines if you can't know what it represents and/or makes it crammed. For example, using FPS=2 and Base=1: - Zooming out until 30:00 works as spected: drawing and removing new lines. ![image.png](https://archive.blender.org/developer/F10260902/image.png) - From this point on, no more lines are being removed. ![image.png](https://archive.blender.org/developer/F10260904/image.png) What I meant by showing up to 3 inbetween lines is that it becomes crammed after that, but I guess the main issue is that **the hour lines are not being removed**.
Richard Antalik added this to the Video Sequencer project 2023-02-09 21:18:24 +01:00
Philipp Oeser removed the
Interest
VFX & Video
label 2023-02-10 09:31:46 +01:00
Sergey Sharybin added
Module
User Interface
and removed
Module
VFX & Video
labels 2023-02-15 11:29:26 +01:00

This is a more generic problem than the VSE. It happens in the animation editors, both for horizontal axis when using Seconds, and vertical axis in the F-Curve editor.

This is a more generic problem than the VSE. It happens in the animation editors, both for horizontal axis when using Seconds, and vertical axis in the F-Curve editor.

I had patch for this issue, at least for horizontal ticks, will port to this site and poke review again.

I had patch for this issue, at least for horizontal ticks, will port to this site and poke review again.
Blender Bot added
Status
Resolved
and removed
Status
Confirmed
labels 2023-03-16 04:42:41 +01:00
Sergey Sharybin removed this from the Video Sequencer project 2023-11-22 11:56:47 +01: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
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#90389
No description provided.