VSE remaining UI inconsistencies #65845
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
4 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#65845
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?
Here are some issues I found during working on manual:
Added subscriber: @iss
Added subscriber: @tintwotin
The contents of SEQUENCER_MT_change seems to have been moved into the Input menu in this commit: D2665
If the hidden elements(many different strip types and their options) all should be visible, but greyed out, it would be overkill. As it is now with a submenu changing contents depending on the current active strip will mean less clutter IMO, however image and sound strips does not have a sub-menu, because there are too few entries.
The major challenge in the VSE menus is to avoid they become that high that scrolling is needed to see the full contents. Currently the Strip menu is at maximum height(without scrolling) on a 1920x1080 screen:
Added subscriber: @WilliamReynish
I was a bit confused by this..
In a collective submenu for specific tasks for specific types there would be ~10 items, even if most would be grayed you can build "muscle memory".
@WilliamReynish is there convention for this? Or should I treat this as a bug?
Added subscriber: @Enetheru
Sorry if this is the wrong place to write this, but in the markers menu->jump to next marker, previous marker should instead be in the view->navigation menu instead with the other jump to commands?
Added subscriber: @brecht
There is some UI convention regarding this, though not exactly this case. In case of a boolean controlling the availability of something, it should be greyed out. For an enum it should switch between showing the buttons for each value, not grey out.
In this case I think hiding is ok.
Ideally the operator user interface names would indeed match. The operator names in the API should only be changed when really needed, since it breaks API compatibility.
We have a similar operator in the 3D viewport, though perhaps the naming could be better. There is a difference between a final render and a preview render using the viewport settings.
Sounds like a bug.
@iss - If you have a moment while going through the VSE functions when updating the manual, could you check the values in the "Timecode" Panel, if they make sense to you? For me, several of them do not. Here are my notes:
How I would expect the values to show:
The Strip and Hold values are the inside the strip values. These values are often referred to as player/source values:
The Playerhead value is labeled a bit misleading, because it is not the playhead position, but actually showing the duration between the playhead and the strip start. Maybe it should be called something like Time Measure or Duration to Start.
This used to toggle this on/off. The option is also in the timeline View menu, so maybe the operator hasn't been removed, but renamed?:
Where does this happen? In the Time panel?
If it is I'm posting this stuff here too which explains how I think the values in the Time panel should work:
Reading the manual text on the Time panel, I would like to add some words on how I think the values of the Time panel should have been for most usability:
Can you elaborate a bit more. Where do you see premultiply alpha? What needs to be done?
We can restore this functionality, but right now it's unused.
These changes can be done, but personally I would be happier if they were done in context of #59540 (VSE timeline manipulation API)
With great deal of luck I can start work on that task in next release, but it wont be priority.
With search https://docs.blender.org/api/master/search.html?q=alpha_mode&check_keywords=yes&area=default you can see where it is used.
What needs to be done is D5157: Move alpha_mode to color panel
Changed status from 'Open' to: 'Resolved'