NOTE: I already submitted this as a bug, but if 3PointEdit or anybody else could take a look at this and give their thoughts (and, God willing, a solution!) that’d be good.
This issue is somewhat hard to articulate, so please bear with me.
I have HD videos with audio tracks >
I set the audio volume to 0.000 because, USUALLY, I will not need the audio (though in some cuts I will) >
I then applied a Transform Strip to the video (to prevent them from distorting to the render dimensions) >
I created a Meta-Strip from these (combining the HD Video, audio, and Transform) >
So, I was slicing-and-dicing the new Meta-strip, cutting as needed. After a while, I got to the part where I needed sound for a cut. So, I:
Tabbed into the Meta-strip so that I could access its component parts >
Selected the audio strip >
Set the audio to 1.000 >
Tabbed out of the Meta-strip’s Edit Mode
I placed my new cut where I wanted…and then this apparent bug was revealed: for some reason, the audio now plays for the ENTIRE strip. The specific cut where I needed the sound is only 5 seconds. The whole Meta-Strip is 2 minutes. Well, for some bizarre reason, when I go and set the volume to 1.000, now the volume plays over the entire length of the original Meta-strip, even though I now just have a five-second slice of it! I’ve tried everything I can think of to keep the audio limited to the 5-second cut its meant to be at, but this bug always plays the original strip’s full audio.
Along this line, I would like to make the related request (though I know this is not the place for requests): For VSE Meta-Strips which contain audio tracks, please allow the Properties (“N”) window to control the volume. You can control the Opacity of its component visuals, so it only stands to reason that you should be able to do the same with the audio. This would save much effort in always having to Tab into the Meta-Strip’s Edit Mode.
I cannot attach a .Blend since Blender doesn’t allow you to link video files into .Blends (plus this is a huge, messy file, as well.)
Thanks to everybody at Blender, as always, despite this frustrating issue.