Sound card technical question

Norman Willis wrote on 10/31/2009, 11:51 PM
I need suggestions to get my sound card working.

I plug my studio monitors into a PreSonus Firepod (external Firewire sound card) via TRS cables, and then set Sony Vegas Options > Preferences > Audio Device > Audio Device Type to Firepod ASIO (from the drop-down menu).

In the last two projects, Vegas built sound peaks just fine on the new files, and then let me apply Noise Reduction 2.0 to the audio. I could also do my initial Pan/Crop, but then after I began cutting, Vegas no longer responded. I could press and un-press 'play', but the timeline would not move. On the second project it seemed like it started to move maybe a frame or two, because the green sound bars in the Master Bus moved a little, but nothing more than that.

I tried resetting Vegas via CTRL-Shift as I opened Vegas, to reset it to the factory defaults, and then it would work. However, when I went back to Audio Device Type and selected Firepod ASIO, it would lock up again. However, when I re-selected Microsoft Sound Mapper, I could edit again. So I guess Vegas does not like my PreSonus Firepod, or the Firewire card?

I contacted PreSonus, and they had me send them a copy of my System Information file. They noticed that I had a lot of devices on IRQ16, including the Video card, Intel X-38 chipset, PCI bridge, and IEEE 1394 (firewire) controller. They also noticed that my firewire card (standard Dell Precision 380) had an AGERE chip that causes known problems with the Firepod, so they recommended that I get a new card 1394 firewire with a Texas Instruments chipset. They recommended a SIIG firewire 3-port PCI card, so I bought that ($39.00 from CDW).

I installed the new SIIG card, but it was the same story. I could build peaks, apply Noise Reduction, and do my initial Pan-Crop, but then a few hours into cutting the same problem happened all over again.

I can use Microsoft Sound Mapper and it works, but yecch! It's just not the same. I plan to write Sony tech support and PreSonus next, but I was wondering what other people do to reliably power studio monitors.

I have an old Echo Mia internal sound card I can maybe use, but I would prefer to get the Firepod going, if possible, as the Firepod offers XLR inputs, and is much more flexible.

Does anyone have suggestions/ideas?

Thank you.

Comments

LoTN wrote on 11/1/2009, 1:07 AM
Hello Norman,

I don't know if it's related but I also face issues using ASIO with 9c under Seven, look here.

Since it's a new setup I have no clue about the root cause. I need to have some spare time to test with 9c and XP with the same hardware.
Dave Jones wrote on 11/1/2009, 2:07 AM
Norman,

If you haven't already done so, check that the Firepod has the latest firmware and drivers. I have had instances where funky audio interface problems such as you describe have been solved with the latest firmware/drivers.

Regards,

Dave
Ethan Winer wrote on 11/2/2009, 10:46 AM
One thought that may or may not be relevant. I've had that same behavior, where pressing Play is ignored, any time another program that plays sound is working. For example, if I switch from Vegas to Windows Media Player to play a media file, or view a YouTube video in Internet Explorer, when I go back to Vegas it ignores Play until I close the other program.

--Ethan
MPM wrote on 11/2/2009, 10:54 AM
Had it occur last night, shut Vegas down, restarted, everything was fine. [Vegas 9C 32 in 7 64]. I'll pay more attention if/when it happens again.
pwppch wrote on 11/3/2009, 9:50 AM
It sounds like you have the Firepod set up as your default Windows Audio Device. Using ASIO drivers for the audio and also assigning the same physcial device to be your default audio device can be very problematic. ASIO is not a shareable driver format, and once Windows grabs your device, it may prevent the ASIO drivers from communicating with it.

If you have onboard audio, I would suggest you use that for the default audio on Windows.

Peter
MPM wrote on 11/3/2009, 1:40 PM
Not complaining myself, in case it helps tracking this down...

Had it occur again late yesterday, using 9C 32 in 7 64, & rather than a quick restart I remembered this thread and switched the audio device in preferences to the MS Sound Mapper from Direct Sound, and everything returned to normal.