If you have muted an event that’s in front and that event is overlapping another, non-muted event, then you can expect the non-muted event to automatically jump ahead of the muted one in render/bounce operations.
Insert audio into a project
Insert different audio overlapping the original audio
Mute the event that is on top ie. ‘in front’
Render or Bounce in place
Result: the non-muted audio takes its place and the muted event was ignored.
This means you cannot trust the bounce/render operations so long as there is a muted event on top overlapping a non-muted event on any portion of the audio you wish to bounce/render.
Tell me if this is a good or a bad thing? I think it’s catastrophic.
So this means, if you’re editing a comp, and you wish to mute certain sections of the audible event, you can kiss it goodbye if it happens to sit on top of unmuted sections.
No, I wish for the bounce result to honor the muted sections that I deliberately brought to the front. This should result in completely silent audio for those sections of the bounced audio.
Can you please verify whether or not if you are using the “mute” tool or the “comp” tool in the comping lanes ?
I believe that when using the comp tool that it will display the selected lanes audio event in the main audio track, which could possibly be the solution to your issue.
Okay, I can replicate this behaviour under specific circumstances.
You drag an audio event (does not matter if you mute it beforehand or afterwards) over an exisiting audio event.
Scenario 1 - Render Cycle
-set your cycle and select your track
-click somewhere in the project to unselect all events and Render
=> Result as expected and normal behaviour of the original track
Scenario 2 - Render Range Selection
-select these two parts with a Selection tool and Render
=> Result: the newly created file does not take into account the muted event
Unexpected behaviour on the original track: the muted part is practically non-existent; even un-mute/mute or pressing the key command U to confirm that the muted event is in the forground does not change the outcome.
The only way to get things backs to normal is to drag the muted event off of the regular event and drag it back in again
The state of the pre-bounced events is only altered in connection with a Selection tool. If you set it up without it everything behaves as expected. Both the newly created bounce and the after-behaviour of the events involved.
Maybe there is even more to it, I have not yet checked other variations. Just wanted to drop a short “yes, it’s not just on your system”.
The lengths of the files are irrelevant. It is about the mute-state of an event that is being ignored in this specific use case when it shouldn’t be ignored. Moreover, it changes the expected behaviour of the original files after rendering. That is an issue as well.
I understand why you are struggling:
Event 1 not muted = A
Event 2 muted = B
Now, if you have a track with A underneath and B completely or partially on top (Key command U) than you hear this:
AAAAABBBAAA
Render with scenario 1 and the result is exactly what you expect.
Render the same track with the Range Selection Tool and you get this:
AAAAAAAAAAA
Not only is B ignored it is also non-funtional on the original track no matter if you confirm its mute state and its being in the foreground.
P.S.: What you expect to hear is silence playing B as it is muted, of course. In other words, silencing A at the same time.
I kind of understand what you’re saying, but I need more clarification from zooterman as to exactly what the conditions are, what tools he is using ? what bounce / render methods he is using ? are the audio events fully overlapped or partially overlapped ? does this only happen in comping lanes ? etc etc
Here I have used the comp tool to select parts from 3 different takes. For clarity, I have colored the selected parts green. Note that the part colored red is both selected and muted.
Playing back this comp produces silence at the third part from the left, just as expected. Let’s Render In Place.
(In the RIP dialog I choose “Keep Source Events Unchanged”.)
What’s happened here is that the muted part on Lane 2 was ignored and the render instead chose the part on Lane 3. This is unexpected.
What is even more confusing is when I play back the original track, Audio 01, the 3rd part on Lane 3 is now audible even though it is not visually selected. The muted part on Lane 2 is. Clicking on the muted part with the comp tool twice solved this.
