(Mute) Slopes

[Todd R]

It never ceases to amaze me what I don't know about SAWStudio

For example:
"Output Mute SwitchThe data next passes through the Mute routine. This switch mutes all data from this point on. All
signals before this switch are still active and untouched.

This switch has a slope value associated with it that controls how fast the muting action occurs.
Smaller slope values create a more instant response, and larger values create a slower response,
which can be used in place of a quick fade to ramp a signal up or down smoothly.
This switch may be automated."

OK, so I tried it...wow, works great!
Anyone else using this?

[jmh]

Don't think I've ever adjusted that slope either.

[Dave Labrecque]

I'll usually do it with a SoftEdge on the final region entry. But I can see that that might not work for every scenario.

I don't remember the last time I did that with a mute entry. But I do it with single volume-change entries often.

[UpTilDawn]

I'll usually do it with a SoftEdge on the final region entry. But I can see that that might not work for every scenario.

I don't remember the last time I did that with a mute entry. But I do it with single volume-change entries often.

I also like using a softedge on a final region.
Every now and then I end up having to use an alternative, because I needed to cut that final region up for some editing reason and then the resulting final region is too short to create a shallow enough softedge slope, since it can only slope to the left as far as the left boundary of the region.

[Dave Labrecque]

I also like using a softedge on a final region.
Every now and then I end up having to use an alternative, because I needed to cut that final region up for some editing reason and then the resulting final region is too short to create a shallow enough softedge slope, since it can only slope to the left as far as the left boundary of the region.

Yes. That would be one limitation of the SoftEdge approach. But if I'm not mistaken SoftEdges have the advantage of bring in sync with the underlying audio, where automation isn't, unfortunately. Although it's usually close enough to be a non-issue. If not, you can always move it around until it sounds right. OR you can figure out the actual latency for the session and move the automation entry(ies) by that number of samples to compensate.