User can not hear sound when drilled into a meta strip in the VSE #44808
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
5 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#44808
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
Everything - it works the same on all machines
Blender Version
Broken: forever
Worked: (never - it's sort of a feature request)
Short description of error
User can not hear sound when drilled into a meta strip in the VSE.
Exact steps for others to reproduce the error
Changed status to: 'Open'
Added subscriber: @liquidape
Added subscriber: @mont29
Changed status from 'Open' to: 'Archived'
Thanks for the report, but there is no bug here, it works as expected. This sounds more like feature request - which are not allowed on the tracker. Please use forums or bf-funboard ML for that.
So, looked into it and making this work is quite simple even, but since it's enforced centrally looks like it's so by design, so I would like feedback to make sure this is intended to work as you want.
For me it makes sense as well to not mute sound - sound is not the same as picture, but there might be non - apparent use cases here. I think the most common one would be to have a metastrip of sounds and use it as an easy way to mute all other channels. Since blender does not differentiate between image and sound metastrip though, this quickly becomes a problem. A solo option per strip can solve this but it's not that usual. In any case, we need more people to make the decision.
Added subscriber: @Blendify
I don't think that it should behave in this way either
OK so it's three of us. Now we need to make sure that most users are OK with this too. Or I can play dictator of sequencer, commit the change and just follow any screams when the time comes.
I would do it, but not in bug fix period. There is not enough time to gather feedback and I'd rather have the current state in release (with just 3 known screams so far) rather than a new state with an unknown number of screams - may be less than 3 but I'm not risking it.
You can land it into gooseberry and see what people around the studio think. I dont see any reason on why this is like this
Changed status from 'Archived' to: 'Open'
Added subscriber: @iss
Changed status from 'Open' to: 'Archived'
I can imagine supporting this by:
With these words, I am closing this task