Thanks Maartian!

Paul P
 
Why doesn't physical input 2 show as "Right US-16x08 ASIO Analog IN 2" ?
Then first stereo as "Stereo US-16x08 ASIO Analog IN 1-2" ?
 
Ah, maybe this is what you wanted to avoid when you said "I'll skip the 'commentary'" ?
 
So it's a Tascam screwup ?

Right.
 
Nope. SONAR. Don't know that I'd call it a "screw up", but it sure is non-intuitive. There have been feature requests for Friendly Input Names. Once you understand how it works, and get your routing set up properly, it's a no-big-deal. Many more important things for the Bakers to get to first.
 
And welcome to SONAR!

Anderton
If I may add two more rah-rah TASCAM comments...the USB 3.0 connection is class-compliant, so it will work with just about any chip set you throw at it. Although USB 3.0 isn't quite as fast as Thunderbolt, I think you'll enjoy playing an instrument and hearing the note when you play it, not afterward.

Does class compliant mean that you don't use Tascam drivers, but generic Windows drivers instead? Is the same for other interfaces like RME?
 
This is important to me because I always feel so susceptible to the manufacturer stopping support for their product, leaving me with a nice piece of hardware that won't work on my computer.
 
Thanks
 
 

pharohoknaughty

Anderton
If I may add two more rah-rah TASCAM comments...the USB 3.0 connection is class-compliant, so it will work with just about any chip set you throw at it. Although USB 3.0 isn't quite as fast as Thunderbolt, I think you'll enjoy playing an instrument and hearing the note when you play it, not afterward.

Does class compliant mean that you don't use Tascam drivers, but generic Windows drivers instead? Is the same for other interfaces like RME?
 
This is important to me because I always feel so susceptible to the manufacturer stopping support for their product, leaving me with a nice piece of hardware that won't work on my computer.
 
Thanks

Class-compliant means it will work directly with OS-X (no driver required; and the AE Mobile USB driver for Android, for example). I don't know that it has any meaning on a PC. You still need to use the ASIO driver under Windows.

Here's a good explanation of what class compliance means on a PC. I haven't tested it myself, though, as I use the ASIO drivers. 

Hi,

regarding "As far as the signal TO the DAW goes, its DRY from the i/f."; is this correct?

i.e. if you EQ and/or COMP a signal entering the interface, isn't the processed signal sent to the DAW as well as the monitor output?

I would like it to be otherwise (get the dry signal to the DAW but be able to process the monitor mix freely), but I haven't figured out how to do so.

cheers
LPS91

I also have a 20x20, but I have not yet tried the "standalone mixer mode..." and people here seems to say that the mixer only works sending tracks to the master bus? It is not possible to patch AUX SENDS to physical outputs of the unit (for monitoring purposes during a show?).
 
I'm quite floored by this...

As far as I could tell yummay, you can do exactly what you describe; in the Settings Panel you select which physical outputs you want to use for the AUX 2, 3 & 4 sends. Only problem is that you cannot route the Reverb to AUX 2, 3 & 4, so no FX in monitors using the unit in standalone (mixer) mode.
 
cheers,
LPS91

All right... thanks LPS91...
 
It is a little shame that we can't use the FX for monitor mixes. Oh well, maybe in a future update we'll be able to? (I am also dreaming to see insertion points implemented as well... big dream, I know...)  ;-)

Yes, allowing you to select the Reverb as the input to the COAX-channel for example could solve this, without having to change the mixer much (the reverb return level would then be controlled by the COAX-fader instead of the Reverb Return Pot).

And my biggest gripe; not being able to send signal to DAW direct from the mic-pre, and using the EQ+COMP DSP for the monitoring only (not like now, when the processed audio is also sent to the DAW),
 
cheers,
LPS91