View Full Version : M-audio Firewire 410 problem :(
conuk
07-03-2006, 12:44 PM
After installing this as per instructions Im getting corruption on sound playback.
For example playing an mp3 through winamp (latest) or media player... the tune can play from 30 seconds to 2 minutes or so - then it sounds as if the speakers have been submerged in water (best way to describe the sound) - usually closing the player and restarting (either of them) gets the correct sound back - but not every time... mostly though.
Have the latest M-audio drivers.
installed them first before connecting - have uninstalled and resintalled 3 times...
specs :
ASUS K8VSE mobo (410 connected via 6 pin firewire to onboard controller)
athlon 64 3400
gig ram
6800 GT OC
erm other parts.
Previous card was Soundblaster Audigy PCI - and worked fine.
I DID leave that card in at first and just disabled it - but later uninstalled the software then took out the card... since then I have installed the firewire a number of times.
Any clues ?
from device manager I cannot change the IRQ settings for the 1394 controller...
Very frustrating!
itsplayed
07-03-2006, 08:13 PM
Make sure your on-board sound is disabled in the BIOS and go into the control panel under sounds and audio devices to make sure Windows is seeing the 410. Look in the Device manager as well to make sure there are no issues...ie. question marks, X's etc.
conuk
07-04-2006, 09:41 AM
hey,
already disabled the onbaord sound in BIOS.
disabled the onboard 1394 as well and tried seperate card... uninstalled drivers etc... (not hot swapped ) reinstalled etc...
Phoned M-audio support.
My 1394 controller is using IRQ 16 - along with GFX card.... he says this might be the problem...
how can I change it ?
its greyed out......
have just played a mix for over 5 minutes before it got corrupt :(
and what will be better to use the Pyro platinum PCI firewire card ?
or the one built into the Asus K8v SE mobo ?
itsplayed
07-04-2006, 09:58 AM
If the on-board 1394 controller is sharing an IRQ with the graphics card then disable the 1394 controller and use the PYRO 1394/PCI card instead. This card is more than likely better for the 410 anyway as it probably sports the TI chipset. The PYRO card should also be assigned it's own IRQ, try to find the unshared PCI slot on the MOBO to install to.
conuk
07-04-2006, 10:21 AM
ok - tried the last PCI port - and its now got the IRQ 17
http://img.photobucket.com/albums/v280/conuk/irqlist.jpg
http://img.photobucket.com/albums/v280/conuk/irqlist.jpg
there doesnt seem to be anything conflicting now..... I have read somewhere that it should be on an IRQ of less than 16 - but how am I gonna achieve that ?
itsplayed
07-04-2006, 10:35 AM
I don't know why an IRQ assignment of less than 16 should matter. The important thing is that it has it's own IRQ.....continue with the install of the 410 and keep us posted.
conuk
07-04-2006, 11:02 AM
aint IRQs 0 to 15 and the rest are virtual ones or something ?
Anyways.... if I dont get it sorted soon I will have to sell it !
No good if I can only hear sound for couple of minutes ;)
If theres anything else I can try just holla :)
itsplayed
07-04-2006, 12:14 PM
No, in APIC mode your IRQ assignments are controled by Windows not the BIOS. If anybody uses the term "virtual IRQs" to explain these high interrupt numbers, you have my permission to thrash them soundly. They're just as real as any other IRQ. Without going heavily into the IRQ/PCI bus arrangement, If you're using Windows 2000 or XP then it doesn't really matter what the BIOS says.
So, back to the problem at hand....it still seems that your sharing IRQ 17 with the ethernet controller card. Is it possible to reinstall Windows or is that not an option for you? If it is an option, start by disabling some unused ports in the BIOS to free up IRQ's, such as serial, printer and COM ports. Doing this will increase the chances that all devices will recieve it's own IRQ. Your also ahead of the IRQ assignment game by having already disabled the 1394 port on your MOBO.
vBulletin v3.5.3, Copyright ©2000-2009, Jelsoft Enterprises Ltd.