• Coffee House
  • How I'm feeling about Tascam at the moment (p.2)
2015/08/14 12:03:35
bapu
I only care that legacy FW support is still in Win 10 (I've seen others say it is) so that my FW-1884 is still a control surface. I'll know sometime this weekend.
2015/08/14 12:39:37
charlyg
My US4x4 is working flawlessly in Win 10.
2015/08/14 12:43:49
TheMaartian
charlyg
My US4x4 is working flawlessly in Win 10.

Really? That's heartening. The driver for the US-16x08 installs, but Win10 issues a 0x31 device error code. The Tascam mixer can't see the ASIO driver, nor can anything else.
2015/08/14 13:12:37
craigb
TheMaartian
charlyg
My US4x4 is working flawlessly in Win 10.

Really? That's heartening. The driver for the US-16x08 installs, but Win10 issues a 0x31 device error code. The Tascam mixer can't see the ASIO driver, nor can anything else.




Is there a Device Manager area in Win 10 still?  And, if there is, is your device there with a yellow exclamation point?
2015/08/14 15:50:29
TheMaartian
craigb
TheMaartian
charlyg
My US4x4 is working flawlessly in Win 10.

Really? That's heartening. The driver for the US-16x08 installs, but Win10 issues a 0x31 device error code. The Tascam mixer can't see the ASIO driver, nor can anything else.



Is there a Device Manager area in Win 10 still?  And, if there is, is your device there with a yellow exclamation point?


Device Manager is still there. When you drill down to the Tascam driver, it's DM that says the device isn't working properly, with the given error code. The error is such that Windows does NOT see the US-16x08 as a device, so, no, no yellow exclamation point. Nothing to put it on.
 
I have uninstalled that latest driver yet again, so I can't go back into DM and grab some screen shots.
2015/08/14 19:39:49
TheMaartian
Here's Microsoft's description of the error code I'm getting:
 
Code 31: This device is not working properly because Windows cannot load the drivers required for this device. Update the device driver.
 
Doh.
Why would the US-4x4 driver load, but not the US-16x08? Dunno.
2015/08/15 13:44:51
TheMaartian
OK. So I tried what I promised myself I wouldn't do. I reinstalled the driver for my AudioBox 44VSL. It seemed to install OK. It showed up as a Playback device. Not one of my standalone VIs recognized the driver. SONAR seemed to see it, but as soon as I opened a project and played it, SONAR's audio engine crashed.
 
So much for PreSonus calling their 18+ month old driver Win10 ready. Shame on me for believing that. Uninstalling is WAY more of a pain than installing. Back to cleaning hidden devices and the registry.
 
Come ON, Tascam.
2015/08/15 13:48:07
Moshkito
bapu
Hi (Pedro),
 
Do you mean no one at IK knows computers in the biblical sense?



I don't mean nothing! You already know that! IK (themselves personally -- not you folks here) have lied to me twice and not helped. this is not about Bapu or any CH member, all of whom have been great! But I still can not and have not been able to use the IK Philharmonic Merde Orchestra with two different vocals (midi channels?) or whatever!
2015/08/18 16:54:58
BobF
There's a reason that I decided to keep things running smooth on 8.1 for now.  Sonar is working great.  The US-16x08 is working great.
 
No need to F with a Windows installation that worx.
 
I'll BUY Win10 when I retire this machine. Maybe next year.  Windows 10.3 should be cranking along with full driver support by then.
2015/08/18 17:58:48
craigb
BobF
I'll BUY Win10 when I retire this machine. Maybe next year.  Windows 10.3 should be cranking along with full driver support by then.




They'll probably be on Windows 12 by then...
12
© 2026 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account