Audio of a scene strip can't be muted #38500

Closed
opened 2014-02-05 13:47:43 +01:00 by Paulo José Oliveira Amaro · 14 comments

System Information
Ubuntu 13.10 64-bit
Intel Ironlake Mobile x86/MMX/SSE

Blender Version
2.69.10 f70d966

Short description of error
If there's a Scene strip in VSE and it contain audio, it can't be muted or have its volume controled.

It's common to have the same audio track in different scenes to keep synchrony, but the master scene which combines all scenes has its own audio track. This way, the two audio track overlap and it's no possible to mute the audio from scene strip.

Exact steps for others to reproduce the error
An example file with audio included, to show how it can be problematic. There are 2 scenes, both with the same audio track. For test purposes, the master scene have its scene strip shifted, so you can listen the two audio playing together. The audio strip can be muted, but the volume of scene strip can not.

blender-audio-sequencer.zip

The same can be said about Meta strips, but at least it's ease to get inside it and mute its audio manually.

**System Information** Ubuntu 13.10 64-bit Intel Ironlake Mobile x86/MMX/SSE **Blender Version** 2.69.10 f70d966 **Short description of error** If there's a Scene strip in VSE and it contain audio, it can't be muted or have its volume controled. It's common to have the same audio track in different scenes to keep synchrony, but the master scene which combines all scenes has its own audio track. This way, the two audio track overlap and it's no possible to mute the audio from scene strip. **Exact steps for others to reproduce the error** An example file with audio included, to show how it can be problematic. There are 2 scenes, both with the same audio track. For test purposes, the master scene have its scene strip shifted, so you can listen the two audio playing together. The audio strip can be muted, but the volume of scene strip can not. [blender-audio-sequencer.zip](https://archive.blender.org/developer/F76096/blender-audio-sequencer.zip) The same can be said about Meta strips, but at least it's ease to get inside it and mute its audio manually.

Changed status to: 'Open'

Changed status to: 'Open'

Added subscriber: @PauloJoseOliveiraAmaro

Added subscriber: @PauloJoseOliveiraAmaro

Added subscriber: @Sergey

Added subscriber: @Sergey

You could hit H to hide the scene strip and it'll also mute the sound. However it'll indeed will also mute the video. But that's rather expected behavior. You could also open second video and have a separate sequencer editor there for the scene with sound.

What i can do is to add Audio Volume to Scene panel of a Scene strip. This way you'll be able to drag slider to 0 and disable audio for a given scene. You'll also be able to create a custom shortcut to toggle it. This ill go to git soon.

You could hit H to hide the scene strip and it'll also mute the sound. However it'll indeed will also mute the video. But that's rather expected behavior. You could also open second video and have a separate sequencer editor there for the scene with sound. What i can do is to add Audio Volume to Scene panel of a Scene strip. This way you'll be able to drag slider to 0 and disable audio for a given scene. You'll also be able to create a custom shortcut to toggle it. This ill go to git soon.

This issue was referenced by blender/blender-addons-contrib@2b9702f4bf

This issue was referenced by blender/blender-addons-contrib@2b9702f4bfb4b26a8bcef0288c8fe2d742699184

This issue was referenced by 2b9702f4bf

This issue was referenced by 2b9702f4bfb4b26a8bcef0288c8fe2d742699184

Changed status from 'Open' to: 'Resolved'

Changed status from 'Open' to: 'Resolved'

Closed by commit 2b9702f4bf.

Closed by commit 2b9702f4bf.

Perfect solution, Sergey. Thank you!

Perfect solution, Sergey. Thank you!

@Sergey, Could you add it to Meta strips too?

@Sergey, Could you add it to Meta strips too?

No, unfortunately no. For the scene strip you know for fact which volume to control. In fact the change simply exposed value setting from audio panel from the scene buttons.

For metas i could see how it could be useful for you, but that's not so trivial to do. You'll either need to somehow recursive the volume changes down to the strip hierarchy or somehow make system aware of volume override of the meta..

Also not clear the pipeline. For your case you need to mute audio, someone else might want to only mute video. Needs some kind of usability feedback discussion actually.

No, unfortunately no. For the scene strip you know for fact which volume to control. In fact the change simply exposed value setting from audio panel from the scene buttons. For metas i could see how it could be useful for you, but that's not so trivial to do. You'll either need to somehow recursive the volume changes down to the strip hierarchy or somehow make system aware of volume override of the meta.. Also not clear the pipeline. For your case you need to mute audio, someone else might want to only mute video. Needs some kind of usability feedback discussion actually.

I see, meta seems to be a little more complicated to control.

I'm not the sound guy, so I'm just speculating, but maybe to control the meta volume may be enough simply to apply the factor to the audio strips inside the meta. For instance:

  • If meta = { audioStrip1, audioStrip2, audioStrip3 } and volume(x) is the volume property of the strip x,
  • Then volume(meta) = volume(meta.audioStrip1) + volume(meta.audioStrip1) + volume(meta.audioStrip1)
  • To apply a 0.5 gain into the meta strip, you can do 0.5 * volume(meta.audioStrip1), 0.5 * volume(meta.audioStrip2), and 0.5 * volume(meta.audioStrip3)

Of course, I can be misunderstanding what you had explain to me. I'm understanding you exposed the value from audio panel from the Scene, and just using it, but not changing it directly. This way, you change actually a local volume property for the scene strip in that specific sequencer. Otherwise, would not to be possible to insert the same scene two times with different volumes in the same sequencer. If it is the case, it would not to be easy to change the meta's volume, since it has no volume property itself, like a scene. And it would give some side effects, like the one I said.

About the pipeline, I'm not ignoring the need of an usability feedback discussion, but to mute only video [of a meta strip] we already have the opacity property, so I can't see the issue about it. Some usability feedback to clear things up would be great here, of course.

I see, meta seems to be a little more complicated to control. I'm not the sound guy, so I'm just speculating, but maybe to control the meta volume may be enough simply to apply the factor to the audio strips inside the meta. For instance: * If meta = { audioStrip1, audioStrip2, audioStrip3 } and volume(x) is the volume property of the strip x, * Then volume(meta) = volume(meta.audioStrip1) + volume(meta.audioStrip1) + volume(meta.audioStrip1) * To apply a 0.5 gain into the meta strip, you can do 0.5 * volume(meta.audioStrip1), 0.5 * volume(meta.audioStrip2), and 0.5 * volume(meta.audioStrip3) Of course, I can be misunderstanding what you had explain to me. I'm understanding you exposed the value from audio panel from the Scene, and just using it, but not changing it directly. This way, you change actually a local volume property for the scene strip in that specific sequencer. Otherwise, would not to be possible to insert the same scene two times with different volumes in the same sequencer. If it is the case, it would not to be easy to change the meta's volume, since it has no volume property itself, like a scene. And it would give some side effects, like the one I said. About the pipeline, I'm not ignoring the need of an usability feedback discussion, but to mute only video [of a meta strip] we already have the opacity property, so I can't see the issue about it. Some usability feedback to clear things up would be great here, of course.

@PauloJoseOliveiraAmaro, sorry for delay.

That wouldn't be a sum i think more like multiplication or so.

Also, discussing such things is not so efficient in the bug tracker. There're not so many artists are reading comments for all the reports here. Better to start some discussion in ML or so.

@PauloJoseOliveiraAmaro, sorry for delay. That wouldn't be a sum i think more like multiplication or so. Also, discussing such things is not so efficient in the bug tracker. There're not so many artists are reading comments for all the reports here. Better to start some discussion in ML or so.

Thank you for the tip, @Sergey ! I'll join to the Mail List as soon as I can.

Thank you for the tip, @Sergey ! I'll join to the Mail List as soon as I can.
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#38500
No description provided.