TASCAM US-800 and Windows 8 compatibility?

  • Thread starter Thread starter John Smiff
  • Start date Start date
J

John Smiff

Banned
(I posted this in the TASCAM forum, but I probably should have posted here in the first place. Sorry about that.)

I might be buying a new computer, and it seems that most new computers come with Windows 8. I have a TASCAM US-800 Audio Interface.

It seems the TASCAM has drivers only up to W7, but not W8. I think they discontinued the US-800 before W8 came out, maybe?

Anyway, I'm wondering if anyone is using the US-800 with W8.

Thank you.
 
Also, it seems that new computers come with USB 3.0. I know the US-800 works with USB 2.0, but have no idea if it will work with USB 3.0. Anyone know?
 
The last post here talks about windows 8 with us800. Looks good. :)

USB is backwards compatible with usb 2 gear.
You're the man, Steenamaroo.

That's really re-assuring. I don't have to limit my search to computers equipped with W7. I didn't know that about USB 3. I did read a few people saying they had issues with the TASCAM and USB 3, so hopefully what you're saying is true. Thanx.
 
I'm not sure what that guy meant "installed drivers for every USB port." How do you even do that?
 
I'm not sure what that guy meant "installed drivers for every USB port." How do you even do that?

I would suggest the following scenario?

When installing the primary drivers for most usb AIs it is almost always done with the device disconnected (goes for a lot of other usb kit as well. My Brother printer e.g.)

Then, when you plug in the AI to any given port the PC generally says "found new hardware" or some such----fiddly-diddle a bit then "your hardware is now ready to use". I would bet if you powered down and then plugged into a different port you would get the same little dance? Once you had gone round ALL the usb ports PC would probably be happy.

Ah now! I just remembered. When I had a Fast track pro, whenever I plugged it into any port on any PC it would try to install but often would not until I ran the drivers. I therefor kept the drivers (only about 3mb) on the Desktop and ran them first then plugged in FTTP. Only took about a minute.

My NI Ka6 on the other hand tells me nothing! Not on this old P4 xp nor either W7/64 machine. I plug it in, open a DAW, Samplitude, AA1.5, whatever and it is THERE! No messin'!

Dave.
 
If you've read about issues it'd do no harm to search and find comments by someone with the same circumstances as you.
Even if the manufacturers have a driver or whatever, I always look for someone who can call something tried and tested before I buy. :)
As a general rule, though, USB 3 is designed to be backward compatible. (In the same way that USB 2 was).

Drivers for every port : I guess the guy was talking about USB chipset drivers.
These should be automatically installed by windows. If not, the motherboard manufacturers website is the place to look.
This is a different thing to the interface drivers.
 
If you've read about issues it'd do no harm to search and find comments by someone with the same circumstances as you.
Even if the manufacturers have a driver or whatever, I always look for someone who can call something tried and tested before I buy. :)
As a general rule, though, USB 3 is designed to be backward compatible. (In the same way that USB 2 was).

Drivers for every port : I guess the guy was talking about USB chipset drivers.
These should be automatically installed by windows. If not, the motherboard manufacturers website is the place to look.
This is a different thing to the interface drivers.

Sometimes, and I have seen this with a few USB hardware devices, you plug in your USB, install the driver, good. Then, when you plug it into another USB port, it sees it as a new device and you have to install the driver again. I am sure there is a way to avoid this (like you said, install first). I have not researched it much as it doesn't really install a second version, it just installs over top of the original and then both ports know where the driver is.

I am pretty sure this be avoided, or maybe a flaw in some drivers, I just never thought enough of an issue to research (I'm getting lazy in my old age, or just care less about these small issues).
 
Back
Top