REW CALIBRATION WITH TASCAM US-122MKII GUIDE (REV 0.

02)
CAUTION:
ALWAYS MAKE SURE PHONES/LINE OUT IS TURNED FULLY DOWN
(COUNTERCLOCKWISE) BEFORE CHANGING ANY CONNECTIONS OR SWITCH
SETTINGS. This is to project your ears and any equipment, including speakers and headphones
that may be connected.

ALWAYS SET PHANTOM TO OFF UNLESS YOU ARE USING A CONDENSOR

MICROPHONE THAT REQUIRES PHANTOM POWER AND ALWAYS SET
PHANTOM TO OFF WHILE CHANGING ANY CONNECTIONS. This is to avoid
damage to any equipment that is attached.

INSTALLATION NOTES:
Follow instructions for installation from manual, except I recommend downloading latest
Drivers and Firmware from TASCAM website first.
Once you have the latest drivers updated, and confirm the unit is connected and powered, you
probably want to update to the latest firmware also. Follow all precautions from TASCAM.
Comments about my installation experiences. Don't give up!
NOTE THAT I INSTALLED THE TASCAM US-122MKII ON THREE DIFFERENT
OPERATING SYSTEMS so far, WITH A VARIETY OF VERSIONS OF REW, AND A
VARIETY OF DRIVER VERSIONS. THERE WERE SETTINGS ON EACH THAT I
NEVER GOT TO WORK, BUT WAS ABLE TO GET AT LEAST ONE COMBINATION
OF SETTINGS TO WORK ON EACH INSTALLATION.
OSX 10.7.4 Lion on Mid 2010 Macbook Pro, REW 5.0
Use Java Sound Audio Engine Output and US-122 MKII Input.
44.1KHz works, 48KHz fails.
No ASIO option presented.
The OSX interface appears to be the most stable and noise free on the Macbook Pro.
Windows Vista 32bit on Bootcamp on Macbook Pro, REW 5.0 and Beta 5.09
Used ASIO at 48kHz and 88.2kHz ok, 44.1kHz and 96kHz failed.
Note, I need to check that I have latest Java JRE installed.
I had noise issues when moving the mouse. I think it may be poor generic USB
drivers as part of the Boot Camp installation.
WinXP Pro SP3 X86-Win32, in VMFusion Virtual Machine on Macbook Pro
Used Java at 44.1kHz works.
48Khz Java and all ASIO fails with latest Java JRE installed.
This worked better than boot camp for me though, less noise.
Windows Win7 SP1 X86-32 on Desktop PC. Still have to try.
Windows Win7 SP1 64bit on Core i7 HP Laptop. Still have to try.
PROCEDURE:
Hardware Settings:
Begin with TASCAM US-122MKII disconnected from computer.
Turn PHONES/LINE OUT down, by turning knob fully left (counter clockwise).
Set MON MIX to COMPUTER by turning knob fully to right (clockwise). This is critical
so that the the audio from the computer is fully applied to the LINE OUT, without any mix

from any of the input channels.

Set MONO switch to OFF by sliding it to the left position.
Turn both INPUT knobs down, by turning fully left (counter clockwise).
Set PHANTOM switch to OFF by sliding to the left position.
Set MIC/LINE/GUITAR switch to MIC/LINE by sliding to left position.

Hardware Connections: (Some Adapters or special cables are required, see REW Help)
Connect Loopback Cable, LINE OUT (RCA Jack, either channel) to LINE IN (1/4 TS
Jack, same channel). REW instructions recommend Right Channel for both for consistency.
Connect Headphones to the PHONES (1/4 TRS Jack) if you want to listen to computer
sounds.
Connect the USB cable, the USB LED should turn green.

REW Software Procedure: (SEE REW HELP FOR MORE DETAILED INSTRUCTIONS)
Select Input and Output devices to match US-122 MKII or similar. The available options
may be different depending on OS and Version of REW software and version of TASCAM
drivers.
Select Sample rate. Experiment. Some may work while others may not.
Select Input Channel, Use Right as default.
I was able to use the default settings for everything else.
Press the CALIBRATE button.
Press NEXT.
Press NEXT Again to output the 1kHz tone to adjust level.

TASCAM US-122MKII Setting Adjustment:

If everything was set according to instructions above, I now turn the PHONES/LINE OUT
knob to the right (clockwise) until the RIGHT bar matches the -12.0dB sweep level
displayed on the OUT bar. For me, I turned this fully to the right. CAUTION: This knob
turns up both the LINE OUT and PHONES at the same time and therefore the PHONES can
get quite loud. Be sensible so not to damage your hearing or headphones. EDIT: I ran
more tests on this and found that as long as the PHONES/LINE OUT was adjusted to more
than half-way right (clockwise) that the ADC Conversion yielded good dynamic range.
Now unless your bars already match, turn the INPUT R knob slowly to the right (clockwise)
until the bars match at -12.0dB.
If the bars still don't match, turn the INPUT R back down, go to REW screen, select the
CONTROL OUTPUT and CONTROL INPUT check boxes. Then adjust OUTPUT
VOLUME up wards and INPUT VOLUME upwards until the bars match. NOTE that
sometimes these bars are greyed out, and if so, you shouldn't have needed to adjust them
anyway.
If the bars still don't match, turn the INPUT R knob slowly to the right (clockwise) until the
bars match at -12.0dB.

REW Software Procedure Continued

Now with the bars matching at -12.0dB, press NEXT.
Wait a few seconds for the sound card to settle out, then press NEXT again.
The sweep will execute and the results plotted in the main REW window. It should look
like the graph below. Note that the top line is the SPL and the bottom line is the Phase. It's

the SPL that is important. It shows being down only 0.5dB at 10Hz, which means that it
will do a good job capturing the low frequencies and frequencies all the way up to 20kHz.

Now if you are satisfied, click on MAKE CAL and notes for file and then reenter file name
and save.

Now a tip. Technically, you can adjust PHONES/LINE OUT independently from INPUT R
and any number of combinations will provide matching bars at -12.0dB. However, I found that
I obtained the best low frequency range (dynamic range), by turning PHONE/LINE OUT all the
way up, so I only had to turn the INPUT R up modestly. If I did the reverse, I lost some of the
low end, which is not optimal. EDIT: I ran more tests on this and found that as long as the
PHONES/LINE OUT was adjusted to more than half-way right (clockwise) that the ADC
Conversion yielded good dynamic range.

DISCLAIMER: Always fully read and adhere to the directions for any equipment and software that
you are using. I am not an expert and am not responsible for any injury or damage under any
circumstances.