The TC Electronic Impact Twin is a mid-level firewire interface with 14 inputs and outputs. It has two preamps, onboard effects, S/PDIF, ADAT Lightpipe and MIDI I/O. It’s not as compact as some other interfaces but packs a ton of features and i/o yet still small enough to fit in a backpack.
The Impact Twin caught my eye in spring 2011. I was looking for a more compact replacement to my M-Audio Profire 2626 (see review here), or a way to expand the I/O of my system, or at least a portable option so I don’t have to tear apart my studio all the time I go out to record. I trust TC Electronic to make nice clean digital gear, for about $400 it had pretty much every feature and function I wanted. I ordered one through Revolution Audio (note: I work for this company and got dealer pricing) and when it arrived I started writing my review. I don’t really have a good excuse why it took nearly a year to write, other than that l got busy being awesome in other aspects. Jump down to the end if you’d like to see what I think of it after about 8 months of owning it.
Design and construction
The case isn’t metal but thick plastic with a rubbery texture. Rugged? Hell yeah. It’s definitely not very compact though. Think backpack size rather than pocket size. If you’re looking for ultra portability it’s not the right thing.
Dimensions = 9.5″ L x 9″ W x 2″ H; Weight = 1628g (3.6lb)
There’s an edge around the front of the interface that is curved to both protect the knobs in transport and recessed to allow knob tweaking. Pretty smart.
Speaking of knobs, they turn smoothly and feel very solid, infinitely more so than a lot of high-end outboard gear. Every piece of TC gear I’ve used is always perfect in this respect.
TC designed the interface to angle up slightly to improve visibility and hand movement. After a couple trips in my backpack I lost one of the glued-on rubber feet so now mine wobbles.
There were no issues with installation on either system. Everything went as expected. I’ll list the steps for those that come across this that don’t know the correct way.
- Find TC Near software online
- Run installer, remember to select impact twin driver in the options
- Connect and turn on the device. wait for windows to identify and assign the driver
- Open TC Near control panel
- Update firmware
There was a typo with the firmware update but that’s about all I can complain about there. I love when stuff just works.
Windows 7 64 bit
Apple MacBook Pro 5,5
Preamps and inputs
Inputs 1 and 2 are Neutrik combo jacks and there’s a censor to tell the control panel which is being used and are otherwise muted. Muting unused inputs automatically keeps the monitoring clean. If you are using the line inputs on the back you’ll have to push the Line In button on the front panel. The preamps have plenty of gain and are very clean and transparent. The back panel has 2 additional line inputs as well as all the standard digital options you’d expect.
Direct guitar recording
The Hi-Z inputs have a 1M Ohm impedance. Of all the options for recording direct guitar I have in my studio, right into the TC sounds best to me. That was a bit of a surprise to see the $400 interface beat my $500 super transparent P-Solo preamp. The transient response was great, capturing the bite of my Telecaster right, and the bottom end was tight, not thin or flubby like with many DI boxes.
The interface provides 4 analog outputs on TRS jacks, and 1 each of S/PDIF, MIDI and Lightpipe (can operate with 2 or 8 channels). The main outputs are linked to the output knob on the front.
Two headphone jacks
One thing I just can’t wrap my head around is the headphone monitoring options on this interface. The two headphone jacks receive the same signal that is assigned to output 1-2, it is also sent at the same level. One of the jacks works as anyone would expect, the other mutes the main outputs when plugged in. Why, I have no idea. A monitor mute button would have been simpler and more useful. Two jacks but no way to send a different mix to one is strange. One jack with its own volume control would have been awesome.
As with most audio interface that cram a hundred features into a box at a certain price point, there is always some corners cut and often it’s in the headphone monitoring flexibility. My M-Audio Profire 2626 has this problem as do all the Focusrite Saffire series. Its a shame as that will be one of the most often used features.
In my studio this mean that I have to use out 3-4 to my TC Level Pilot and monitors and use either jack for my headphones. Output 1-2 can’t be used in my setup. When I use the interface mobile with just my laptop and some mics, I’m unlikely to be using the main outputs at all so no problem.
If this was your only interface for a home studio, using an external headphone amp might be the best solution. MIDI ports aren’t essential, independent level of headphones and monitors is, it pains me to see they messed this up.
A feature I’m seeing in a lot of audio interfaces these days is onboard DSP effects. Some have them just for monitoring, some have the effects in the input path, the Impact Twin has both.
Input path effects
Inputs 1 and 2 have console style channel strips with 4 band EQ (SSL-esque in layout at least), Compressor and De-esser. When you use these effects they will be applied to your recording, which means if you overdo it with the compression the file is ruined just like with a hardware compressor. What makes it different from a hardware compressor is that it is far less flexible and cannot prevent clipping the converter. The de-esser is something I’m unlikely to use ever, it doesn’t have a frequency select option and every voice and mic combination will require a different setting.
I’m just pointing out some of the downsides, these are cool features to have on an interface, I’ll have to see if it becomes something I use. [it turns out it’s not a feature I used often]
The compressor amount can be controlled via the encoder on the interface. This is great. Even better is that the gain reduction is shown on the LEDs around that knob. The compressor has various style presets designed for different sources so you’ll have to experiment to see which works best for you. I wish you could change this from the front panel too but of course, there’s only so many features you can cram into that space.
Pushing the adjust knob in when in compressor mode will bypass all input fx.
From the control panel you can also activate a guitar tuner.
The reverb built into the Impact Twin is very nice sounding, and can only be used in the monitor path. I had a lot of fun playing guitar into it and pushing it to extremes. There are 14 reverb models with decay, pre-delay and color (EQ) controls. The front panel ‘adjust’ knob can control the reverb level fader and decay.
The thing that confused me a bit with the reverb is that the Main MIX control needs to be turned to the left (direct monitoring). I’ve never really understood the whole reverb while recording but not on playback concept. I think I’ll stick with a plugin.
This feature is disable at higher sample rates.
Before I got the Impact Twin I read through the manual and remember thinking the routing matrix looked very simple to use. It actually is, but I am a bit disappointed with the flexibility of it. It could be a little clearer what is going on. Outputs are left to right, Inputs are top to bottom. click where you want each signal to go. The problem is you can’t send multiple signals to one output. Because you only have 1 usable stereo output for fx or extra headphones this is pretty limiting. I will be adding this interface to my system rather than replacing it and using the digital i/o, you may not have this option. There is a possibility that features like this can be changed in firmware updates but I’ve never seen a company follow through, but perhaps if enough users demand it, something can be done. [no software/firmware updates were released in the time I’ve owned this]
One of the perks of buying a TC Electronic interface is the included plugins. The Impact Twin comes with 4 full-version plugins: Assimilator Native (a matching EQ); Integrator (simplifies hardware effect integration); M40 Reverb; and ResFilter Native (a synth filter).
M40 and ResFilter are useful plugins. Resfilter would be better with an LFO or auto-envelope option but that’s not really the point of this review. M40 is a decent, simple reverb though not really one I would likely use. Assimilator has a ton of latency and as far as I can tell, does not work in Reaper at all. The plugins don’t come with any documentation tutorials or help files and could not find much info online. Note that the interface authorizes the plugin, so if you aren’t using that interface, you can’t use those plugins. Overall I was unimpressed with the bundled plugins.
Where are the plugins?
Ok so I lied, there is one complaint with the installation. The PC installer didn’t ask where to put these so they ended up in the usual VST folder which might not be somewhere your DAW of choice will look. Take the TC Electronic folder out of Program Files/Steinberg/VST Plugins/ and move it to your preferred VST plugins folder.
Sync and ADAT
I didn’t feel this was covered clear enough in the manual so I’ll explain as best I can.
When connecting digital devices you must sync them and you need to determine which is the master and which is the slave. The clock signal is sent on the digital output jacks.
- When no external equipment is connected to the digital i/o, clock source should be set to internal.
- In the case of an external mic preamp with ADAT output (Presonus Digimax for example) connecting to an audio interface (such as the Impact Twin), the mic preamp would be the master and the interface would be the slave. In the TC Near options this would be enabled by selecting ADAT as the clock source.
- If you want a device to receive something from the ADAT out of the interface, you must have the Interface set to internal Sync and the other device set to ADAT sync.
- If you want to send and receive on the ADAT jacks then you’ll need two cables. The clock source technically can be either but may only work in one configuration without dropouts or glitches. Use this configuration for bi-directional ADAT devices such as a Profire 2626 or Firestudio in standalone mode. The Impact Twin can also run in standalone mode and I occasionally used it this way along with my Profire 2626.
If you change sample rates often, either of these options may cause some headache.
It’s silly, but I was impressed by the external power supply. It feels sturdy, the IEC side of the cable is nice and thick and grounded. The thing that impressed me most was that it was actually labeled as to what it belongs to. It’s way too common for devices to ship with generic ac adapters without even a brand name on them. It costs no money for a manufacturer to put a sticker on it before shipping but it’s never done. When you’ve already got a drawer full of unmarked ac adapters you start to get impressed by little extra effort here. What’s a shame is that this interface works flawlessly bus powered so you may never use this nice external power supply. Where the power supply connects to the Twin is a little wobbly but I’ve seen much worse.
Stability and quirks
On my Windows 7 system (see specs), the stability is great. I had one quirk where I changed the buffer size from 128 to 64 in Reaper and the device wasn’t reactivated for reaper. Restarting reaper corrected the problem.
With an optimized system and using a quality firewire card you should have no problem recording with very low latency. The driver also has some “safe modes” which will improve stability at the cost of latency. On both my systems I am able to run in normal mode with a buffer of 64 without issues.
On the MacBook Pro I was recording and editing at 24/96kHz on the internal drive with WIFI, Bluetooth, Firefox, Evernote, and Gobbler running. I was also running off the battery with the interface bus powered. I think that’s a pretty good test and the interface worked exactly as expected for hours.
With 3 or more firewire devices connected to your computer, you may run into some problems, like dropouts or missing devices, which is common.
As for quirks, there are a couple things I’ve noticed related to the onboard DSP and sample rates. At 88.2kHz and above the reverb is disabled. At 176.4kHz and 192kHz the mixer is disabled completely. Not sure if it retains the previous settings before sample rate change or if everything reverts to defaults. This effects my life minimally.
Overall this is a great audio interface. Stable, lots of features, great sound, good design. I recommend this for anyone that needs a portable interface with a variety of analog and digital i/o, and great sound quality. Alternatives would be the (now discontinued) M-box 2 Pro which would sound worse and have less I/O, new AVID Mbox (3) Pro, which is considerably more expensive. and still less I/O or Focusrite Saffire Pro 24, which has 8 fewer outputs.
After about 8 months, the Impact Twin did not become my main interface, thinking back, I hardly used it at all, though when I did, it worked just as it should.
The main thing that bugs me is the headphone monitoring thing, it just wasn’t thought out well enough and I would have rather them cut out the MIDI ports than a headphone volume control.
Im am completely new to this . i bought a new computer and an Impact twin to record (for my own posterity) vocals and acustic guitart. the pc: an asus motherboard, corei7 processor, running windows 7 64bit, sp1, with a fiewire 800 PYRO pvc-815 PCIe sound card. I recently baught a TC Electronics Imact Twin audio interface device. i’ve tried several ways to configure it to get the sound to output to my computer speakers to no avail. i cant even get output on any of the AID ports. Any suggestions?
All audio inputs and outputs go through the Impact Twin, so if you want to hear out of your computer speakers, you’ll have to connect them to the interface. One of the headphone jacks would work for that.
Hey Jon. thanks for taking the time to replay. i tried that too. no luck. i tried to find just the most recent driver for the Impact Twin on TC Electronic’s website but all i could find was the was the entire software suite and i already have the most up to date release. do you know of a reference soucre for driver conflicts? I’m wondering if my sound card driver might be interfering with the driver for the Impact Twin.
I think it’s important to speak to drivers and driver stability when reviewing interfaces, as it’s a well know fact that the drivers are what seperate the men from the boys and nothing…nothing is more frustrating that an interface with sh1t drivers..
I agree, fancy features are nice but useless if the drivers suck. Perhaps you missed the part of the article where I wrote about stability. In this case, there was really nothing to say about the drivers. The interface works on all 3 of my systems perfectly. I’ve found that people blame drivers often when its their firewire card.
Ah, i guess i did miss that part
“I’ve found that people blame drivers often when its their firewire card.”
True, if people want to use their RICOH and NEC F/W chipsets, let em try – although there are tricks to even get those to work which I’ve done via the device mngr in Windows 😉 Mac’s rarely have crap f/w chipsets and all that I’ve used use the industry standard Ti chipsets so not an issue with the f/w, but soley the drivers, hence my initial remark.
Hey Paul; do you know a good reference source that i can learn about these 2 devices (sound card and interface)? i have checked the manufacturers web sites and all i could find was sales lit. thanks.
What are you on, PC or Mac.
Also, your audio interface is actually your “sound card” 😉 A regular sound card or – integrated sound chip on your motherboard – would be redundant for the most part.
If you want some help, I’ll keep my xmas spirit alive and help you 😉 Just shoot me an email chander.singha AT gmail DOT com
Thanks for the review, I’ve found your comments and complaints to be pretty much inline with my own. I have a question for you in regards to your unit. I know that the on-board reverb is lost after 88 kHz but have you also noticed losing both compressors AND headphone monitoring through the unit when in 192 kHz mode? I can understand losing the compressors, no big deal but losing headphone monitoring at 192 kHz makes no sense to me. I’m forced to monitor through core audio and my DAW (Logic 9). I’m trying to figure out if my unit is broken but it took them a week to get back to me through their web portal and I’m losing confidence that I’ll actually get a meaningful answer since they took a week to tell me to “read the FAQ, install the latest firmware (which I had done previously) or send it in for repair.
Hi Justin. Looks like this comment is for me, Paul doesn’t work here.
I never work at 192kHz so I did not test it thoroughly. If I recall correctly, all DSP functions are disabled at 192, and it is 2 in, 2 out. I guess the ‘direct’ monitoring of the inputs wouldn’t work because that goes through the dsp first. I primarily work through software monitoring so this wouldn’t effect me.
It sounds like it is working as designed.
Sorry for the mix up Jon, I did mean to ask you and thank you for the response despite my mistake. I’m not sure how much I’ll be working in 192 myself but I just wanted to be sure the unit isn’t broken. I’m somewhat new to audio recording interfaces and not sure what to expect from them. The round trip latency is pretty low on my imac @ 64 bit OS/24bit sampling/192 kHz/ is about 4.2 ms so I’m not too concerned about it. Admittedly I almost hoped it was broken because the Phonic Firefly 808 is currently on sale for the same amount I paid for this unit, hehehe. Do you have any experience with the Phonic unit? It looks REALLY nice for the price. I’m wondering how sturdy it is.
I haven’t used that particular Phonic unit but I’ve mixed a project that was recorded on one of the phonic mixer interfaces and it sounded kinda crap.
I’d say TC Electronic is a better company for interfaces.
That’s good to know. I appreciate your input, I wish TCE’s customer service portal was as helpful. So far I’m not impressed with their Customer service and it will make me think twice about buying another one of their products in the future. As it stands the product disks didn’t install the reverb plugin and I haven’t been able to find it – it did install Assimilator, Integrator and ResFilter but no M40 reverb to be found (unless the onboard reverb module @ 48 kHz is supposed to be it). Unfortunately I don’t feel very confident I will hear back from them about that either. Oh well, good thing Logic comes with good reverb plugins, hehehe.
I’m happy with all my TC Electronic gear but have not needed to contact support.
I never install the software that comes on the cds/dvds included. I always go for the latest download.
I mentioned in the review that I had trouble finding the plugins at first on my PC, on mac there are a couple places where AU plugins are stored in either system or user library.
TBH, missing the reverb is no big loss. I highly recommend Valhalla Room or Audio Damage Adverb plugins.
Thanks a lot for the advice Jon, I appreciate the recommendations on the plugins too. I’m glad I found this place, lots of good articles and info to be had.
I wanted to come back to this post and relate that one week after the warranty expired so did my Impact Twin. I now have a $500 paper weight.
Oops, I meant $250 paper weight…
Hi, thank you for review!
There’s a simple way to use separate leveling to speakers and headphones:
1. Connect speakers to 3-4 line outputs.
2. In patchbay module set “from mixer” to “line 3-4” and “FW 1-2” to “line 1-2”
For headphones leveling use “output” knob, for speakers leveling use “adjust” knob with “mix” mode.
How to turn on the plugins and where those programs are?