[ddots-l] Re: Choppy or no audio from the Tascam FW1884
- From: "Dancing Dots" <billlist1@xxxxxxxxxxx>
- To: <ddots-l@xxxxxxxxxxxxx>
- Date: Fri, 16 May 2008 09:48:35 -0400
Hi, Roberto,
One thing that has helped me and other customers in general is to check
Sounds and Audio Devices under the Control Panel to be sure that your
default playback and recording device is set to your low-end (probably
onboard) soundcard. Check "Use only Preferred Devices", tab to "Apply"
button and press space bar.
Are you using the TASCAM 1884?
Regards,
Bill
Bill McCann
Founder and President of Dancing Dots since 1992
www.DancingDots.com
Tel: [001] 610-783-6692
_____
From: ddots-l-bounce@xxxxxxxxxxxxx [mailto:ddots-l-bounce@xxxxxxxxxxxxx] On
Behalf Of Roberto Gonzalez
Sent: Wednesday, May 14, 2008 8:48 PM
To: ddots-l@xxxxxxxxxxxxx
Subject: [ddots-l] Choppy or no audio from the Tascam FW1884
Hi,
Wondering if anyone has experienced this problem and found a solution. More
than 50% of the time when starting Sonar 6 and attempting to play a project
one of the following occurs:
1. There is no audio and the meter also registers as such when F2 is
pressed.
2. If there is audio, it is extremely, and I mean extremely choppy and
barely identifiable.
In order to resolve this an unpredictable combination of unloading Sonar,
power cycling the Tascam, removing and reconnecting the firewire cable, and
power cycling the computer is required. Sometimes, several computer reboots
is necessary while other times simply restarting Sonar does the trick.
There doesn't seem to be any rhyme or reason as to why or when the problem
occurs nor a solid sequence of restarts to correct it other than the longer
the computer sits powered off then the more likely Sonar will not produce
playback audio. The problem is not restricted to certain projects as we
have had the problem occur with various projects including the Sonar sample
midi and audio bundle. Using WDM or ASIO drivers also doesn't make a
difference.
We're using a PCI firewire card with a TI chipset. I've upgraded to the
latest Windows drivers for the Tascam and updated to the latest Tascam
firmware.
My thinking is that we have a Windows XP hardware initialization issue of
sorts. Any idea whether changing PCI slots could make a difference. It's
currently in the bottom most slot furthest from the video card which I was
under the impression is a good position for the firewire card. Any clues to
resolve this annoying problem are greatly appreciated.
-Roberto
Other related posts:
