TASCAM FireWire Vista drivers realeased

Just an FYI that Vista drivers (32 & 64) for the 18xx series are now on the TASCAM website.

Follow-up: I installed the 1.60f driver over the 1.60 (European version, no letter) driver. All seems to be working fine in Windows XP sp2.

Note, I am also using the 1.22 beta SONAR Control Surface driver.

"Garbled" is pretty broad, but I'm assuming that means you are hearing the correct sound, just sounding horrible. Whenever I've experienced sound that was "garbled", the cause of it was

1) audio latency too low; change 64 to 128 etc. on the FW-1884 Control Panel

or

2) the wrong clock source on the Control Panel

or

3) somehow the sample rate got changed on the Control Panel

Note, I have no experience with Vista.

Hope this helps.

Use WDM drivers?

Anybody with Vista 64 that got this to work?

If I use WDM the only outputs I get are ADAT 5 6 and an SPDIF output.

If I use ASIO I have all the outputs but no matter what I do the audio sounds awful, as if the sample rates don't match. Adjusting latency doesn't help.

I'm really at wit's end with this. I finally get the drivers and I can't get them to work! If you wanna post your settings or any other ideas, go for it.

I was using Vista 64 with no success.
Went back to XP SP2 and all works fine now.

Note, I am also using the 1.22 beta SONAR Control Surface driver and the new 1.60 XP-Vista driver.


Guy

Feedback loop?

Still guessing...

ChronoT52, I have the same exact problem. I have tried a ton of different firewire cards with different chips and two different motherboards (ASUS P5B Deluxe and Asus P5K-E Wi-Fi). I tried it in 32-bit XP on the same system and using the same firewire port and the 1.60 driver and playback was perfect but in Vista 64 I'm getting that weird distortion/crackling.

It is not just a Sonar problem as playback from any source is affected. You can even try just playing Media Player through one of your analog outs and hear it.

I was able to solve my problem by turning off the "Memory Remap Feature" in the Chipset section of my ASUS P5K-E motherboard's BIOS. This effectively means I can not utilize more than 3.24gb of RAM under Vista 64, which is one of the main reasons I am using it. I'm not sure what the culprit is but I am leaning towards the FW-1884 driver... Low-latency playback is perfect now, though, and during my troubleshooting process I learned to tweak Vista pretty well and my DPC calls are averaging around 55μs. A new audio interface is on the way, and this time it is one with WaveRT drivers--the Echo Layla 3G.

Crackles? I'll get Vista next month at work... so take this for what it's founded on - a guess. Crackles has often meant that the interrupt number the sound card is using conflicts with that of another device on the system. Some fixes, iirc, are: 1) Try using the OS's device configuration tools to change the IRQ on which the card in operating, or 2) move the card to a different slot in the box, where it will likely[1] get assigned a different interrupt number.

[1] Not all slots are equal - try the card in every slot (and even move other cards) before curling up in the fetal position.

Way out on a limb...

Hey guys,

getting back on the issue.
First of all, thanks to Kzoink for your answer. I had given up for a while and hadn't seen your reply.
In the end, I have found the same solution as you, but since you've already posted it I don't need to do it.

For information, this problems seems to affect many different FW interfaces as i could read on several forums here and there.

I had contacted Tascam customer support, and as you can imagine, no answer.
On the other hand, I had contacted Frontier Design support, and the guys there were very supportive, trying to find solutions but without success.

I have forwarded them the finally identified source of the problem, suggesting the developers of FW Audio interfaces/drivers like them and others get in touch with Microsoft for a future possible hotfix.

Silverslate, you normally find the memory remapping option (or memory hole depending in Bios/Motherboard manufacturer) under the Chipset options of your Bios.

If you don't have more than 3.2 GB memory on your system then you won't lose anything.

In my case, I hope a better solution will be found in order to be able to use all the memory available on my system.

Cheers