a cheap pci and a cheap usb? the card that solved the problem was $26
Right you are but a firewire card is not the same as an audio interface is it? You go on ahead and use that card. Let us know if you get either of your audio cards to work with it. That will be a miracle indeed! And, once you have it all running post a song so we can all marvel at your genius.
I was trying to be nice about things but you obviously (as Jack would say) "can't handle the truth".
_________________ Ian Faith: "Certainly, in the topsy-turvy world of heavy rock, having a good solid piece of wood in your hand is often useful."
Space Recording Org Pro Audio Group
Joined: Jun 26, 2007
Posts: 840
Location: Exit 4, Alabama
it wasn't a contest my brother The wonder is that, when these forums move right, it is a great exchange of ideas from people giving up time, energy and experience to help out. So, right back
at ya!
Space Recording Org Pro Audio Group
Joined: Jun 26, 2007
Posts: 840
Location: Exit 4, Alabama
Space I'm not sure what exactly your point is about this, the thread is about noisy sound cards, what's your point?
Question? Do you run both of these cards at the same time on the same computer? I would recommend one or the other. And because usb is what it is, the pci would be my choice, if I had to choose one.
quadrivium Recording Org Pro Audio Group
Joined: Jul 06, 2006
Posts: 30
Location: Rhode Island and Providence Plantations
Space I'm not sure what exactly your point is about this, the thread is about noisy sound cards, what's your point?
Question? Do you run both of these cards at the same time on the same computer? I would recommend one or the other. And because usb is what it is, the pci would be my choice, if I had to choose one.
Sorry if I wasn't clear, I was in here looking for an alternative low cost interface that would not be as noisy as what I had tried in the past. My question was answered by the original poster. thanks for your help
hueseph Recording Org Pro Audio Group
Joined: Oct 31, 2005
Posts: 1329
Location: Vancouver, BC, Canada
Hello, I have this same issue as described above but with a projectmix io. This was not an issue till I upgraded the computer. Till now the sound has been fine in a recording.
After doing some digging I have noticed one main factor that I believe may be causing the issue: IRQ. On the old system the IEEE 1394 or firewire was on IRQ channel 19 and was the only device using that IRQ channel. However on the new system the FW is on IRQ 16. This channel is also used by the following system devices - IDE, PCIE & USB.
As I’m sure you all know, a main devices for your system really needs its own IRQ to work the best it can without interruptions.
It would be interesting to see if anyone else has the same IRQ issues with onboard FW.
Last edited by piano_wizz on Sat May 10, 2008 5:04 pm; edited 1 time in total
Space Recording Org Pro Audio Group
Joined: Jun 26, 2007
Posts: 840
Location: Exit 4, Alabama
Hello, I have this same issue as described above but with a projectmix io. This was not an issue till I upgraded the computer. Till now the sound has been fine in a recording.
After doing some digging I have noticed one main factor that I believe may be causing the issue: IRQ. On the old system the IEEE 1394 or firewire was on IRQ channel 19 and was the only device using that IRQ channel. However on the new system the FW is on IRQ 16. This channel is also used by the following system devices - IDE, PCIE & USB.
As I’m sure you all know, a main devices for your system really needs its own IRQ to work the best it can without interruptions.
It would be interesting to see if anyone else has the same IRQ issues with onboard FW.
Are you running Windows XP? IRQ conflicts were more common with Win98 and earlier when there were only 16 available (there are 24 in XP)... popping and clicking can result from this regardless of whether it is a firewire or usb device... have you looked in Control Panel/System/Hardware/Device Manager/View by type/IRQ to see that your system is using all 24?
quadrivium : All irq's are not in use on the system
You may be able to get XP to assign your FW card a unique IRQ by moving it to a different slot (then reboot and look at the device list by type/IRQ again). You may also want to boot into the BIOS (usually F2 Key while system is powered up), some BIOS's have the option to list out the PCI slots and see what the default IRQ is. If this doesn't do the trick then you can disable the devices that are using the shared IRQ that you don't need (floppy drive?). Last resort (and not generally recommended) is to set the Computer Driver to 'Standard PC' and assign the IRQ numbers manually, this is not great if you plan on adding new devices later...
Thanks for the advice, I have been doing taht sort of thing all day. I got a new firewire pci card today but its faulty, on 2 pcs the speakers make a heart beat sound from the second the system is powerd up and windows shows the device is faulty on 2 seperate computers. Looks like i will be taking it back and getting a replacement tomorrow.
About the changing PCI slot. this was originaly an Onboard IEEE 1394 and i could not change the irq, i have found a slot for pci that is not in use by any other device and will try plugging in a differnt card when i get a replacement.
NOTE: there is no option to change the irqs from the bios as strange as it may seem. its all auto config and there is no sign of IRQ config anyware on the setup screen.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum