Brian, I'm running the DSP24 with the envy24 chipset without any problems. I was somewhat concerned at first due to reports of this kind but I found a lot of answers (potential answers) on the ST Audio pages. Specifically : http://www.staudio.de/kb/english/conflicts/index.html Their FAQ and Knowledge base are also pretty good sources of info. Jan On Mon, 2002-12-30 at 14:02, Brian Redfern wrote:

Brian, I originally had an ATI Rage card and had to take it out because it conflicted with my MOBO. The damn thing wouldn't even boot. I switched to an NVIDIA card and that straightened it out. I listened to some of your music. What kind of gear/software are you using to do that? I've never done anything with synthesizers so I'm completely clueless about that stuff. Jan http://www.mp3.com/bluesbakers On Mon, 2002-12-30 at 17:59, Brian Redfern wrote:

Anthony, It could be a huge number of things, but like you I doubt it's just interrupts. As you say, no card is going to generate more interrupts than it needs to. Some cards could require a few more interrupts to get the job done, but I doubt they'll generate that many more interrupts. More likely is the quality of the DMA controller in the sound chip, and how well it gets the data across the bus. If a card has to deliver 1024 bytes, and can do that in one burst of 256 cycles, while another card delivers the same 1024 bytes in 8 bursts of 128 bytes, the first card will be much more efficient and better behaved in the system, and probably use less PCI time doing it. This is also HEAVILY driven by what the chipset will allow a PCI device to so, hence my RME and your RME cards, while identical, might give different performance results because our PC chipsets give it different access to system resources like memory. To answer Brian's original question, I don't think Jack yet supports 96K, but the RME cards do, and they work pretty nicely. Unfortunately they are not inexpensive... One thing I hope Brian understand is that not every xrun is caused by the sound card. Many (IMO most!) xruns are potentially caused by the disk subsystem. Study that machine carefully Brian! With best regards, Mark -----Original Message----- From: linux-audio-user-admin(a)music.columbia.edu [mailto:linux-audio-user-admin@music.columbia.edu]On Behalf Of Anthony Sent: Monday, December 30, 2002 2:15 PM To: linux-audio-user(a)music.columbia.edu Subject: Re: [linux-audio-user] 24bit 96khz cards that work well * Brian Redfern <bredfern(a)calarts.edu> [Dec 30 02 14:03]: Also, out of interest, what does IRQ hungry mean? Isn't the frequency of interrupts determined by HW parameters you choose? How can there be any 'extra' interrupts. You mentioned in an earlier thread that your SB card didnt seem so interrupt hungry, but are you sure the device is opened with the same params? I'm no expert. Can anyone explain this? --ant

Mark, JACK supports 96KHz.

Anthony, It could be a huge number of things, but like you I doubt it's just interrupts. As you say, no card is going to generate more interrupts than it needs to. Some cards could require a few more interrupts to get the job done, but I doubt they'll generate that many more interrupts. More likely is the quality of the DMA controller in the sound chip, and how well it gets the data across the bus. If a card has to deliver 1024 bytes, and can do that in one burst of 256 cycles, while another card delivers the same 1024 bytes in 8 bursts of 128 bytes, the first card will be much more efficient and better behaved in the system, and probably use less PCI time doing it. This is also HEAVILY driven by what the chipset will allow a PCI device to so, hence my RME and your RME cards, while identical, might give different performance results because our PC chipsets give it different access to system resources like memory. To answer Brian's original question, I don't think Jack yet supports 96K, but the RME cards do, and they work pretty nicely. Unfortunately they are not inexpensive... One thing I hope Brian understand is that not every xrun is caused by the sound card. Many (IMO most!) xruns are potentially caused by the disk subsystem. Study that machine carefully Brian! With best regards, Mark -----Original Message----- From: linux-audio-user-admin(a)music.columbia.edu [mailto:linux-audio-user-admin@music.columbia.edu]On Behalf Of Anthony Sent: Monday, December 30, 2002 2:15 PM To: linux-audio-user(a)music.columbia.edu Subject: Re: [linux-audio-user] 24bit 96khz cards that work well * Brian Redfern <bredfern(a)calarts.edu> [Dec 30 02 14:03]: Also, out of interest, what does IRQ hungry mean? Isn't the frequency of interrupts determined by HW parameters you choose? How can there be any 'extra' interrupts. You mentioned in an earlier thread that your SB card didnt seem so interrupt hungry, but are you sure the device is opened with the same params? I'm no expert. Can anyone explain this? --ant

No, I think perhaps "irq hungry" is a meaningless statement, rather there's a nasty fight for resources between my AGP Rage card and the Audiophile, I'm testing this simply by running Jack, and watching the reports of xruns, the sblive is popping an xruns every twenty minutes, and then the xrun is tiny like .009 miliseconds, while the Audiophile was popping a 54 milisecond xrun every two seconds. The whole "irg hungry" thing is perhaps a misnomer.

What I notice is that I have hiccups during recording and playback, at first I thought my machine was just too slow for lowlatency, but I was wrong. In my case I may do better with usb-audio, since my usb defaults to irq 9, which is apparently the ideal irq for usb audio.

Unfortunately I don't know how to excatly quantify the problem, but what it would appear to me is there are just conflicts between some video and some audio chipsets. Now if I swap out my AGP video card for my old junky card and the xruns under jack stop altogether, then I know that the AGP Rage is a doo-doo card for video. Interesting that a more high end card solved your problem.

specific issue, it also crops up under windows.