Using SAC for overdubs and punch-ins

[Angie]

I decided to start a new thread as a followup to a previous thread so I could change the subject title.

Using SAC as the front end to SAWStudio is a no brainer when it comes to latency. Same settings in SAC noticeably reduce the latency for most singers and finger pickers. But I was having a hard time doing punch-ins.
It had been suggested that the best way to monitor during punch-ins was to assign the SS output to a channel in SAC while keeping the live channel open. When the punch in happens, the recorded track is muted. Makes perfect sense.

We use a Furman headphone system here in the studio. Curse or blessing? I haven't decided. Anyway, the system brings up some monitoring requests that have to be applied quickly. Switching back and forth between SAC and SAW just wasn't doing it for me. So, I came up with a way to send these requests with SAC that is a little more efficient for me.

I split the console. The first 24 channels(our max. right now) are set as the live inputs. The input assigns for 25 on are all assigned to SS input tracks.
FOH mixer becomes the control room feed and other monitor mixers are used for the headphone system. The Solo mode allows me to scroll through the mixers so that I can hear what is being fed where.
During basic tracking, the SAClink option in SAW is set to SRC. For overdubs, it is set to PST-FDR so that any automation and effects you've applied can be monitored.

One thing that needs to be mentioned again is that you must have the Auto Audio Monitor Switching turned off.
Bob, it would be nice if monitoring were switched off when the SAClink is active, unless someone can think of a reason otherwise.

These monitor changes made for a very happy and productive day-long session yesterday.

[Ian Alexander]

Glad to hear it. We like to keep Angie happy and productive. Without her, this forum would be a very different place.

Whatever happened to the woman with the tractor for an avatar?

[Angie]

Glad to hear it. We like to keep Angie happy and productive. Without her, this forum would be a very different place.

When my work is invisible to the musician, everyone is happy.

Whatever happened to the woman with the tractor for an avatar?

Hey, that's right! The IH, looked like an F cub, but it is hard to tell with such a small photo.

[Dave Labrecque]

Hey, that's right! The IH, looked like an F cub, but it is hard to tell with such a small photo.

I like a woman who knows her tractors!

[tomasino]

Hey Angie, thanks for this!

Switching back and forth between SAC and SAW just wasn't doing it for me. So, I came up with a way to send these requests with SAC that is a little more efficient for me.

I was resisting implementing SAC as the default setup in the recording rig because of all the switching involved. But this config has minimized it plenty.
Now I can't see going back, especially 'cuz midi latency has been reduced to zero no matter the size of the project/mix.

You still have to do some switching, right?

I split the console. The first 24 channels(our max. right now) are set as the live inputs. The input assigns for 25 on are all assigned to SS input tracks.
FOH mixer becomes the control room feed and other monitor mixers are used for the headphone system.

I followed your recommendation here.. it's awesome.. practically seamless.

One thing that needs to be mentioned again is that you must have the Auto Audio Monitor Switching turned off.
Bob, it would be nice if monitoring were switched off when the SAClink is active, unless someone can think of a reason otherwise.

Has this been implemented?
Found I still had Audio Monitoring On for a bit.. switched it Off but didn't notice any diff..


If you got any latency and/or PC performance issues, this is the answer.

Thanks again!

[Angie]

Glad it's working out for you!

You still have to do some switching, right?

Oh sure. But not nearly as much.

Found I still had Audio Monitoring On for a bit.. switched it Off but didn't notice any diff..

It hasn't changed. Maybe it varies depending on what interface you're using. I don't know. I have it off in the preference file.