Turned out the interface worked fine, but it required loading up the device firmware on each power-on, which in itself is a questionable, if not brain-dead concept. On a related note: M-Audio took over three months after the release of 10.5 to make available a compatible driver for their MIDIsport interfaces. It makes absolutely no sense to RUSH a buggy and incomplete driver to the market just to shut up a small number of people who are prone to jumping the gun and then complaining about it out of a sense of entitlement to public internet forums, rather than sitting tight and consider the folly of their ways. It was released a month earlier than ANY developer could reasonably have expected. Historically, that has meant sometime around the 25th. **** sure that their tools will continue to work or can be adequately replaced whenever they change any part of their setup.Īpple was going to ship their OS "in September". I have, in twenty years, never seen a major upgrade NOT break at least a small handful of products temporarily.Īnybody who relies on tools for their work is going to make US-122, US-224, US-428 – Appears to be functionalįireOne – Native driver, audio out functional
#Tascam 1641 driver for windows 64 bit drivers#
IF-FW/DMmkII – Appears to be functional, uninstaller did not work, new drivers in development Drivers in development, coming soon.įW-1082, FW-1884, FW-1804 – Expected to be functional M-164UF – No audio output, device not recognized. US-122L, US-144, US-1641 – No audio output, device not recognized. That said, here is the current status for TASCAM interfaces: We’ve installed them all and ran some audio through them, but we haven’t opened them all up in different hosts, sampling rates, etc. Right now, TASCAM hasn’t done the kind of extensive testing to determine whether an interface “works” in 10.6. I’ll be looking for similar situations from other vendors. I’m particularly concerned that USB audio appears to be a problem. Before you complain that they’re not ready, consider the amount of testing they have to do with different hardware, different hosts, and different sampling rates – and that’s just to find a problem, not to fix it.
#Tascam 1641 driver for windows 64 bit update#
Jeff Laity from Tascam writes with an update on Tascam’s hardware tools.
Tascam: Testing in progress driver updates coming
0 kommentar(er)
