Page 1 of 1

Output attenuated on Firewire 410 channels (SOLVED)

Posted: Wed Jan 26, 2011 1:39 am
by Austin R
Trying to trouble shoot a problem with our system. We are currently using SCS 10.7.3 on a Lenonovo PC running XP (SP3) into an M-Audio Firewire 410 via a SIIG firewire PCI card. This has worked fine in the past. Recently however, we can only get normal volume output on channels 1/2. Channels 3-8 appear to be attenuated when I look at the Firewire 410 mixer screen. There's some signal there but not much. Channels 3/4 are almost zero, channels 5-8 very low volume. The SCS output representation indicates it is outputting on all eight channels at the desired levels. I have driven the Firewire 410 from a laptop and it, and everything downstream, appears to work ok.

We have reinstalled SCS from the setup file of SCS 10.7.3 that I retained, also reinstalled the 410 driver and removed and reseated the PCI firewire card. The setup is in a community theatre so others have used the system although it is only used for audio work. In the hope we could find a setting problem left by a previous user we have poked and tweaked various settings in SCS, and as many audio settings in the Windows morass as we can find, but with no success. I did find that I could direct audio from Windows Media Player to any of our eight output channels.

If anyone has suggestions on what we might try to resolve this it would be appreciated.

Austin

SOLUTION

A younger mind has found a way to solve our problem. We used to set up our devices as Firewire 410 1/2, Firewire 410 3/4, etc and the speaker/output assignments as 1/2 stereo, 3/4 stereo, etc to match the device specification. This no longer appears to work for us.

What does work is to leave the device assignments the same and use 1/2 stereo as the speaker/output for each device. The system also works by choosing only Firewire 410 ASIO as the output device then specifying 1/2, 3/4, 5/6, 7/8 as speaker output assignments.

We still don't know why this change has occured but assume it may have something to do with upgraded M-Audio Firewire drivers.

Again, if anyone has an explanation we'd be interested to hear. It's great that we are back in business but it would be nice to know why!

Austin