Thanks Vic for pointing me in the right direction. Since others also had some questions about this, I cut and paste the relevant section from the Pro 40 manual here. Note, the line levels for monitoring the DAW specified here are probably different from those for the Pro 14 and 24, but the section below gives a pretty clear overview of the various routing options:
When in the Saffire Mix program and you hit Alt+Shift+R using Phil and Tim's HSC set as Vic describes, you will see the following options: >From the manual: Clear This turns off all output routing. This can be used to re-set the routing for when you need to completely restart a configuration, meaning you do not have to manually turn everything off first. DAW Tracking 'DAW Tracking' is used for the initial recording process. It will automatically output DAW 1 and 2 to be sent to all Line outputs and hence your main monitors (1+2) and to Headphone outputs 1 and 2. All input channels must be monitored from within the DAW application. Zero Latency Tracking Zero Latency Tracking is used for the recording process. It will automatically output Mix 1 and 2 to all your Line outputs simultaneously, and hence will route to the main monitors (1+2), and to the Headphone outputs 1 and 2. Line inputs and DAW outputs must be set up in Mix 1 so that you are able to monitor these sources with zero latency. You must also ensure that you are not monitoring the same signals from within your DAW at the same time, otherwise you will be monitoring the same signal twice (once direct from Saffire PRO 40 Control AND a second time (with latency) from your DAW.) Mixing 'Mixing' is used for the mixing process. When sending signals out to a mixer or to external processing hardware, hardware outputs are typically set exactly as they are set in the DAW software. DAW outputs route directly to the line output of the same number. (DAW outputs 1-10 to Monitor Outputs 1-2, Line outputs 3-10.) Loopback Use when recording from one software program to another. For example, to record audio from your internet browser into your DAW, or to record from one DAW to another. DAW 1 and 2 are routed back in a loop and are available for recording via inputs 19 and 20 in your DAW. To prevent any audio feedback, make sure that the DAW you are recording into is not set to monitor its inputs. Alternatively, set the outputs of the DAW into which you are recording to 3 and 4; this allows you to monitor the inputs without feeding the signal back into the record stream. I hope this is helpful. --Pete -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Victor Tsaran Sent: Sunday, April 24, 2011 1:12 AM To: JSonar -- JAWS Scripts for Sonar discussion list Subject: Re: [Jsonar] kRE: How to turn off direct monitoring of line inputs withSaffire Pro 24 It's not a toggle, it's a menu. I believe you access it by pressing alt+shift+r. On Apr 23, 2011, at 8:08 PM, Peter Torpey wrote: > Vic, > > Is this control the one in the HSC spot ring for DAW controls which is > labeled "DAW PFL"? I assume from what you're saying I can toggle this > control on/off to turn direct monitoring of line inputs on/off? Just want > to make sure I'm looking at the correct control. Never used this (but > sounds useful). > > Thanks. > > --)Pete > > > -----Original Message----- > From: [email protected] [mailto:[email protected]] On Behalf > Of Victor Tsaran > Sent: Saturday, April 23, 2011 6:14 PM > To: JSonar -- JAWS Scripts for Sonar discussion list > Subject: Re: [Jsonar] kRE: How to turn off direct monitoring of line inputs > withSaffire Pro 24 > > Pete, > You have to turn off the "0-latency monitoring" preset in Saffire control > panel and switch to "DAW Tracking". > On Apr 23, 2011, at 1:41 PM, Peter Torpey wrote: > >> Will do. I'm betting Phil knows how to do this! (But he doesn't sit in >> front of the computer all day!). ...And with these time differences > around >> the world you never know who might be sleeping. >> >> --Pete >> >> >> -----Original Message----- >> From: [email protected] [mailto:[email protected]] On > Behalf >> Of David Reynolds >> Sent: Saturday, April 23, 2011 4:36 PM >> To: JSonar -- JAWS Scripts for Sonar discussion list >> Subject: Re: [Jsonar] How to turn off direct monitoring of line inputs >> withSaffire Pro 24 >> >> Peter, >> >> I'm not a member of the midi mag list, so if you get an answer on this, > can >> you post it here too? >> >> Best, >> >> David. >> ----- Original Message ----- >> From: "Peter Torpey" <[email protected]> >> To: "'JSonar -- JAWS Scripts for Sonar discussion list'" >> <[email protected]>; <[email protected]> >> Sent: Saturday, April 23, 2011 9:31 PM >> Subject: [Jsonar] How to turn off direct monitoring of line inputs >> withSaffire Pro 24 >> >> >>> Calvin, >>> >>> Glad my suggestions worked. >>> >>> I am forwarding your next question (below) about muting the direct >>> monitoring of line inputs so that you can just hear the output from sonar > >>> to >>> the Jsonar and MidiMag list. I don't know of an easy way to do this >>> without >>> changing the routing assignments, but it sounds like there should be a > way >>> of doing this. Maybe we can all learn something! >>> >>> -----Original Message----- >>> Bro I got it to work!! I just created a master bus, and routed it out >>> to saffire pro mon 1, like you said, changed the routing preset in the >>> saffire mix control to loopback one and vuala!! Thanks so much!! I >>> also wanted to ask if their was a way to mute the direct monetoring of >>> line inputs so that i can only hear the output through sonar? Thanks >>> for the quick assistance! >>> >>> On 4/23/11, Calvin Botha <[email protected]> wrote: >>>> Wow! Thanks so much for the reply and for sending me this preset! >>>> unfortunately i have the pro 24 so this snapshot will unfortunately >>>> not load!! But thanks again Pete! >>>> >>>> On 4/23/11, Peter Torpey <[email protected]> wrote: >>>>> Calvin, >>>>> >>>>> >>>>> >>>>> Try using the pre-set attached and loading it to your Saffire through >>>>> the >>>>> mix control program. >>>>> >>>>> >>>>> >>>>> --Pete >>>>> >>>>> >>>>> >>>>> >>>> >>> >>> >>> _______________________________________________ >>> Find JSonar and Sonar FAQs, articles, guides and downloads at jsonar.org. >>> >>> Jsonar mailing list >>> [email protected] >>> http://jsonar.org/mailman/listinfo/jsonar_jsonar.org >> >> >> _______________________________________________ >> Find JSonar and Sonar FAQs, articles, guides and downloads at jsonar.org. >> >> Jsonar mailing list >> [email protected] >> http://jsonar.org/mailman/listinfo/jsonar_jsonar.org >> >> >> _______________________________________________ >> Find JSonar and Sonar FAQs, articles, guides and downloads at jsonar.org. >> >> Jsonar mailing list >> [email protected] >> http://jsonar.org/mailman/listinfo/jsonar_jsonar.org > > > _______________________________________________ > Find JSonar and Sonar FAQs, articles, guides and downloads at jsonar.org. > > Jsonar mailing list > [email protected] > http://jsonar.org/mailman/listinfo/jsonar_jsonar.org > > > _______________________________________________ > Find JSonar and Sonar FAQs, articles, guides and downloads at jsonar.org. > > Jsonar mailing list > [email protected] > http://jsonar.org/mailman/listinfo/jsonar_jsonar.org _______________________________________________ Find JSonar and Sonar FAQs, articles, guides and downloads at jsonar.org. Jsonar mailing list [email protected] http://jsonar.org/mailman/listinfo/jsonar_jsonar.org _______________________________________________ Find JSonar and Sonar FAQs, articles, guides and downloads at jsonar.org. Jsonar mailing list [email protected] http://jsonar.org/mailman/listinfo/jsonar_jsonar.org
