Tascam Us-122, Review of new USB device Options

[rickenbacker]

A few people have been mentioning the Tascam US-122 lately, so I thought I'd post a review of the unit that I've just written for a music magazine. Might help someone thinking of buying one. Any further questions are very welcome.

Are you sitting comfortably? Then we'll begin...

The US-122 is the latest fruit of the Tascam/Frontier development partnership and is the logical successor to the US-428 and US-224 models. Where these sought to act as both interfaces and mini control surfaces for sequencers, the US-122 is a straightforward portable USB device.

Put simply, it is a two-input, two-output 24-bit AD/DA audio/MIDI interface, offering a respectable proliferation of ins and outs. There are two balanced XLR mic inputs; two 1/4” balanced line inputs (switchable to high-impedance unbalanced inputs for direct connection of any hi-Z source, such as a guitar, bass or synth); TRS inserts on each input channel for effects processors; impedance matching and a 16-channel Midi interface.

Output is via a pair of unbalanced line outputs on RCA connectors, although regrettably there is no digital option, either in or out. A separate headphone output with dedicated volume knob is provided, along with the master volume knob and a direct monitoring knob. The unit is entirely USB powered and provides phantom power to the two XLR sockets for use with condenser mics.

Construction is solid, the reassuringly chunky design and rubberised mid-section promising to withstand a few knocks. As the US-122 lends itself to portable use, this is an important issue. Its dimensions are also a boon, measuring just 149 x 60 x 196mm (W/H/D) and weighing just over 2lb (925g).

Installation of the tiny 5Mb driver was easy, the only caveat being that OS X owners must be running at least OS X 10.2.3. The driver also works in OS 9 and the device will support ASIO, Sound Manager, CoreAudio, CoreMIDI, OMS and Free MIDI. A version of Cubasis for Mac is bundled with the package, although this only works in OS 9.

The US-122 Manager contains settings for Audio Safety Buffer (1-5ms) and the USB Bandwidth Usage dialogue, an audio-disable function for when you just want to run MIDI and timing is crucial. A guitar tuner is also included. Sample rates of either 44.1 or 48Khz are possible, with a resolution of either 16 or 24-bits. These and other parameters (such as overall gain levels) can be set in Audio and Midi Setup in OS X.

In operation, using the US-122 is a no-brainer. Plug in your instrument or mic, move the mic/line or guitar switch accordingly, select phantom power if required and adjust the Left or Right channel levels as necessary, using the signal indicators as a guide. There is only one light to show the presence of an audio signal (when the level exceeds –37dBFS) and only one overload indicator (which lights at –2.5dBFS), so it’s something of a challenge to pinpoint the optimum recording level. Using your DAW’s channel-level indicators is advisable.

The latency of the US-122’s hardware input monitor is advertised at “always less than 1.5ms”, but you can avoid the latency issue completely while overdubbing live signals by using the Direct switch. There is also a Mono switch which folds the two direct monitor stereo channels to mono.

You can record and playback two audio channels simultaneously, although slightly disappointing is the fact that the manual advises against recording mic and line signals simultaneously as the signal level is summed and the two are likely to interfere with one another.

The sound quality achieved with the US-122 is of a professional quality and the unit delivers a nice loud signal on playback – some USB audio devices need cranking right up to get anything out of them. MIDI operation was also straightforward. Bear in mind that the US-122 is only a USB device, though, and that the limits of the USB’s data-carrying capacity generally prohibits playback of anything greater than 16 audio tracks.

One improvement we would suggest is that the dials could do with a coloured strip on top to better indicate their position. At present, there is only a groove cut into the plastic, but as all the knobs are silver on a silver machine, it’s hard to identify settings at a glance or in low light conditions.

Apart from that, if you need to capture analogue sources and are in the market for a small, portable recording and MIDI solution, this machine fits the bill. As a portable recording solution for capturing ideas on the hoof, for recording demos, gigs, rehearsals or any other type of location recording, the US-122 is a good bet.

[xingu]

You won't be able to run the OEM Cubasis (or any other audio app for that matter) under Classic. I suppose there's an off chance it might work, but probably not properly and it is not recommended. What capabilities do you need for your demo? Audio, MIDI, both? There's a few free/cheap apps mentioned in this thread (but Muzys isn't available for OSX yet). Also, one I forgot about - Audacity, which is a freeware multitrack audio editor.

[huwthom]

I thought the purpose of OS Classic was to enable Mac users with newer machines to use older programmes. Why won't Cubasis work in Classic and is there anything that can be done to remedy the problem? I currently have a us 122 on order and don't want to be lumbered with a piece of kit that isn't going to work on my machine. Any advice will be greatly appreciated.

[jebbels]

I got a suggestion yesterday from a friend that seems to aliviate the OSX compatability problem. I was unable to open protools free in classic because my computer would ask for OMS settings and then it would crash.If you go to the start up disk option for your computer prefrences, you can set your computer to boot up in OS 9.2, at least thats what mine did, and my computers new so I'm assuming that's a standard thing. I was able to run protools just fine then, so I'm assuming Cubase will work the same. You can reset the start up disk if you want to go back to OSX. Does anyone know if there's any reason why this would be a bad way of doing things. It's a little time consuming, but if you want to use older sound programs, I don't see any other option.

[boze]

huwthom and jebbels-
booting into 9.2 (whether by holding the option key at startup or using the System Prefs method as J describes) is totally fine- not a 'bad way of doing things'. the two quick things i wanted to say is that booting into 9.2 is not the same as running Classic from within OSX (just in case this isn't obvious to somebody new who's reading this thread).

also, while you make a valid point that classic's purpose is to run older apps, the truth is that classic is not as robust as osx or a regular booting os9. it's best to think of it as OS9Lite or something- use it for a simple util or a fairly small program that isn't all that realtime processor dependant and it's okay, but don't expect to launch launch Cubasis in it and track audio or you'll be disappointed.

[xingu]

at least thats what mine did, and my computers new so I'm assuming that's a standard thing.

Actually, new Macs lost the ability to boot into OS9 as of January 2003. You must have bought a computer from some older inventory. Not that that's a bad thing! At least now you can run Cubasis if you get that 122. The only downside is really the limitations of that program, but depending on your needs, it might suit you just fine.

Huwthom - if your Mac doesn't boot into OS9, I think you'll have to consider one of the free/cheaper options mentioned in my previous reply, as I'm not aware of any bundled OSX-native DAW apps - at least not with interfaces this cheap.

[fisken]

Hi.
I just got my Tascam U-122.
I'm a PC user, but got the same problems with the "fuzzy" audio signal.
When I try to record from a Microphone, using the XLR input, I get a fuzzy signal that's
no good at all. I experience small pauses in the input signal. When i don't record, it sounds
well using the audio output or headphones.
Any suggestions to eliminate the fuzz ????
(Recording is done in Cubase sx)

[xingu]

Back when the Tascam forums were still up, I don't recall any PC users ever having a similar problem as with the OSX drivers. I would suggest playing around with the buffer settings - both within the 122 control panel and within Cubase.

[IMNiles]

The summed input issue is basically that - a mic and line in don't play nicely together inside the US-122, although it's not a total disaster. If you're a kind of one-man-band in your bedroom, or you want to build up a song one track at a time, or you want to record something live using two mics or a stereo feed or whatever, the 122 is fine. If you want to get some kind of Bob Dylan vocal mic, guitar and harmonica thing going on, it's not best suited for that.

I, too, thought it seemed from the manual that the summed input issue was only a problem when you tried to use line and mic/guitar on the same channel. Has anyone actually tried mic on one and guitar on the other, or a similar mixed combination, and did it work? This will be the primary application for me..

Thx!

[tas538cam]

Is there somebody also having problems with latency (with MIDI) using the tascam us-122 in cubase SX.
Basically the problem is the following: when I hit a note in the keyboard editor in cubase, the response when I have the tascam us-122 connected is quite long, and definitely longer than when I play on the soundcard of my laptop. I would expect the latency of my laptop's soundcard to be worse than the latency of the tascam us-122, and not the other way around. Is there somebody who can give me some suggestions for resolving this. Many thanks in advance

[Oakland Stroke]

I have been watching this thread for awhile. Although Tascams forums never reappeared after the OSX fizzle and drop-out problems were first reported, I have read here and there that Mac users are having better luck now with the US series.

Anybody out there who is using the drivers for Panther? I would love to hear more before I buy. Thanks.

Also, regarding the latency question concerning internal vs. external soundcards: The onboard card should have the least latency, especially if you are using core audio and MIDI. It's the roundtrip from your instrument to your interface, via your computer, that causes the latency.

Ce message a été modifié par Oakland Stroke - sam. 13 déc. 2003, 00:43.