![]() ![]() Ironically because the laptop is so new it doesn't have firewire which is now being phased out and is becoming a legacy interface. What bugs me is that I bought a brand new laptop with more than enough RAM and processor power just so I record music without problems. I was glad to see that thing go away actually. I know some here have been successful in getting it setup and working, but I never had that luck. Out of these three interfaces the US1641 was the most miserable experience I've encountered with an interface. I ended up ditching it and moving to a firewire interface (M-Audio Profire 610) on a dedicated PC Card interface so it wasn't using any of the onboard firewire resources on my laptop. ![]() I can't really help with your issue, because frankly I experienced the same problems a few years ago when I had a 1641. Perhaps this is a hardware fault? Thing is it works on my 32bit machine. If there was a common conflict I would happily give up but I cant find anything to suggest this should not work on my system. I cant add another dedicated usb port as this laptop lacks express card or firewire, the lack of firewire being why I bought the US1641 ! I tried a fresh install of Vista 64 and it is just the same. Its as thought the driver just wont work on my system at all but Tascam are not aware of any conflicts with particular chip sets or anything. I just cant make it play ball whatsoever. I'm still having a nightmare with this device. I bought a SIIG FireWire ExpressCard and dedicated it to nothing by my audio interface and all problems went away. Ironically I had similar issues when I switched to a FireWire interface (M-Audio ProFire 610) when trying to use onboard FireWire ports. I had to get a dedicated USB ExpressCard to keep my USB audio interface from sharing resources. Are you connecting it to the any of the on board USB ports? I had problems with my old 1641 under Windows XP when connected to any of my laptops onboard USB ports. ![]()
0 Comments
Leave a Reply. |