Yeah, pretty much what I thought. Just another reason I can't wait to afford an upgrade to the system. Justin On Sep 24, 2010, at 10:05 AM, Bryan Smart wrote: > I was just playing with one of those last week on Windows 7 64-bit, and I > couldn't get it to work right, either. Then, I tried the original US144 (not > MK II), on a customer's Win 7 64-bit system, and it worked, though it > glitched if latency was low at all. In this case, the updated product seems > to operate worse. Not that the US144 was trouble free on XP. > > I've only been hearing about their low-end stuff lately. I haven't played > with a US2000, for example. The low-end stuff definitely has problems. > Certainly there is better for the same money. > > Bryan > > -----Original Message----- > From: ddots-l-bounce@xxxxxxxxxxxxx [mailto:ddots-l-bounce@xxxxxxxxxxxxx] On > Behalf Of Justin Kauflin > Sent: Thursday, September 23, 2010 4:58 AM > To: ddots-l@xxxxxxxxxxxxx > Subject: [ddots-l] Audio Interface Issue with 64 bit Sonar > > Hey, > I know you all must love questions about audio interfaces and why there > creating unwanted noise and what not. Please forgive me for this post, but > I'm stumped right now. > I'm using a Tascam US122MKII interface with Windows 7 64 bit. I've been > using it with no problems with the 32 bit version of Sonar 8.5.3 with the > latest CakeTalking scripts. I've been using it with the ASIO drivers and > everything's been sounding great. > When I installed the 64 bit version of Sonar, I've been getting those > pops and clicks that occur when the buffer settings are too low. I tried > switching it to a higher buffer with the ASIO drivers, and I've switched to > WDM drivers and have upped the buffer there as well and haven't been able to > rid myself of those terrible clicks. > I've also checked the drivers that I downloaded from Tascam and they are > supposedly 64 bit drivers. > Does anybody have any ideas why this might be? I'd really love to check > out how well Sonar runs in 64 bit, but so far can't really appreciate it as > its unusable right now. > > Thanks a lot for any advice. > > JustinPLEASE READ THIS FOOTER AT LEAST ONCE! > To leave the list, click on the immediately following link: > ddots-l-request@xxxxxxxxxxxxx?subject=subscribe > If this link doesn't work then send a message to: > ddots-l-request@xxxxxxxxxxxxx > and in the Subject line type > unsubscribe > For other list commands such as vacation mode, click on the immediately > following link: > ddots-l-request@xxxxxxxxxxxxx?subject?q or send a message, to > ddots-l-request@xxxxxxxxxxxxx and in the Subject line type faq > > PLEASE READ THIS FOOTER AT LEAST ONCE! > To leave the list, click on the immediately following link: > ddots-l-request@xxxxxxxxxxxxx?subject=unsubscribe > If this link doesn't work then send a message to: > ddots-l-request@xxxxxxxxxxxxx > and in the Subject line type > unsubscribe > For other list commands such as vacation mode, > click on the immediately following link: > ddots-l-request@xxxxxxxxxxxxx?subjectúq or > send a message, to > ddots-l-request@xxxxxxxxxxxxx > and in the Subject line type > faq > > PLEASE READ THIS FOOTER AT LEAST ONCE! To leave the list, click on the immediately following link: ddots-l-request@xxxxxxxxxxxxx?subject=unsubscribe If this link doesn't work then send a message to: ddots-l-request@xxxxxxxxxxxxx and in the Subject line type unsubscribe For other list commands such as vacation mode, click on the immediately following link: ddots-l-request@xxxxxxxxxxxxx?subjectúq or send a message, to ddots-l-request@xxxxxxxxxxxxx and in the Subject line type faq