* Mark Knecht &lt;mknecht(a)controlnet.com&gt; [Dec 20 02 09:39]: I was under the impression there are a few more, maybe not running ardour however. I don't know if I can afford to be a trailblazer, heh The IRQ's are all different. I'll put /proc/pci at the bottom These are both ATA100 drives, but I'm not sure if thats supported on the kernel. Its really not a drive problem, since audio plays back fine. In fact I can compile ardour without causing a jack xrun at 256*2 buffersize. This is something different. Back to google... Thanks. lspci -v 00:00.0 Host bridge: Advanced Micro Devices [AMD] AMD-760 MP [IGD4-2P] System Controller (rev 11) Flags: bus master, 66Mhz, medium devsel, latency 32 Memory at fc000000 (32-bit, prefetchable) [size=32M] Memory at fb800000 (32-bit, prefetchable) [size=4K] I/O ports at e800 [disabled] [size=4] Capabilities: [a0] AGP version 2.0 00:01.0 PCI bridge: Advanced Micro Devices [AMD] AMD-760 MP [IGD4-2P] AGP Bridge (prog-if 00 [Normal decode]) Flags: bus master, 66Mhz, medium devsel, latency 0 Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 Memory behind bridge: efe00000-efefffff Prefetchable memory behind bridge: fb700000-fb7fffff 00:07.0 ISA bridge: Advanced Micro Devices [AMD] AMD-768 [Opus] ISA (rev 05) Subsystem: Asustek Computer, Inc. A7M-D Mainboard Flags: bus master, 66Mhz, medium devsel, latency 0 00:07.1 IDE interface: Advanced Micro Devices [AMD] AMD-768 [Opus] IDE (rev 04) (prog-if 8a [Master SecP PriP]) Subsystem: Advanced Micro Devices [AMD] AMD-768 [Opus] IDE Flags: bus master, medium devsel, latency 32 I/O ports at d800 [size=16] 00:07.3 Bridge: Advanced Micro Devices [AMD] AMD-768 [Opus] ACPI (rev 03) Subsystem: Asustek Computer, Inc. A7M-D Mainboard Flags: medium devsel 00:08.0 USB Controller: NEC Corporation USB (rev 41) (prog-if 10 [OHCI]) Subsystem: Unknown device 807d:0035 Flags: bus master, medium devsel, latency 32, IRQ 12 Memory at ef000000 (32-bit, non-prefetchable) [size=4K] Capabilities: [40] Power Management version 2 00:08.1 USB Controller: NEC Corporation USB (rev 41) (prog-if 10 [OHCI]) Subsystem: Unknown device 807d:0035 Flags: bus master, medium devsel, latency 32, IRQ 3 Memory at ee800000 (32-bit, non-prefetchable) [size=4K] Capabilities: [40] Power Management version 2 00:08.2 USB Controller: NEC Corporation USB 2.0 (rev 02) (prog-if 20 [EHCI]) Subsystem: Unknown device 807d:1043 Flags: bus master, medium devsel, latency 32, IRQ 10 Memory at ee000000 (32-bit, non-prefetchable) [size=256] Capabilities: [40] Power Management version 2 00:10.0 PCI bridge: Advanced Micro Devices [AMD] AMD-768 [Opus] PCI (rev 05) (prog-if 00 [Normal decode]) Flags: bus master, 66Mhz, medium devsel, latency 32 Bus: primary=00, secondary=02, subordinate=02, sec-latency=32 I/O behind bridge: 0000b000-0000cfff Memory behind bridge: ec000000-edffffff Prefetchable memory behind bridge: eff00000-fb6fffff 02:04.0 Multimedia audio controller: C-Media Electronics Inc CM8738 (rev 10) Subsystem: Asustek Computer, Inc. CMI8738 6-channel audio controller Flags: bus master, stepping, medium devsel, latency 32, IRQ 3 I/O ports at c800 [size=256] Capabilities: [c0] Power Management version 2 02:05.0 Multimedia audio controller: IC Ensemble Inc ICE1712 [Envy24] (rev 02) Subsystem: IC Ensemble Inc: Unknown device d633 Flags: bus master, medium devsel, latency 32, IRQ 10 I/O ports at c400 [size=32] I/O ports at c000 [size=16] I/O ports at b800 [size=16] I/O ports at b400 [size=64] Capabilities: [80] Power Management version 1 02:06.0 Ethernet controller: 3Com Corporation 3c905C-TX/TX-M [Tornado] (rev 78) Subsystem: 3Com Corporation 3C905C-TX Fast Etherlink for PC Management NIC Flags: bus master, medium devsel, latency 32, IRQ 3 I/O ports at b000 [size=128] Memory at ed000000 (32-bit, non-prefetchable) [size=128] Expansion ROM at <unassigned> [disabled] [size=128K] Capabilities: [dc] Power Management version 2 02:08.0 VGA compatible controller: nVidia Corporation NV11 [GeForce2 MX] (rev b2) (prog-if 00 [VGA]) Subsystem: VISIONTEK: Unknown device 0023 Flags: bus master, 66Mhz, medium devsel, latency 248, IRQ 11 Memory at ec000000 (32-bit, non-prefetchable) [size=16M] Memory at f0000000 (32-bit, prefetchable) [size=128M] Expansion ROM at efff0000 [disabled] [size=64K] Capabilities: [60] Power Management version 2

* Jan Evil Twin Depner &lt;eviltwin69(a)cableone.net&gt; [Dec 20 02 09:58]: Thanks for the suggestion. Using either the "nvidia" or the free "nv" gives the same problem. I've played with the latency settings with no success. --ant

* anton &lt;addon(a)blueyonder.co.uk&gt; [Dec 20 02 14:47]: setpci -v -s 02:04 latency_timer=ff will see the timer to 256 for device 2:4 Did you recompile the nvidia driver after doing this? --ant

* Mark Knecht &lt;markknecht(a)attbi.com&gt; [Dec 20 02 20:19]: Well I don't seem to have that problem now ;) or on my previous platform. We've been throuh the laundry list of possible causes, but it seems more like voodoo trying to figure out whats doing what. My main concern is say JACK, which should *guarentee* some sort of consistency in feeding an audio device. If it can't meet that, then it should report something (usually an XRUN). But, with my recent expierence all applications seemed to be blisfully unaware that audio was slowing down and getting corrupted. For instance, how do I know now that everything is working correctly other than my ear? Dave Phillips mentioned something before about the metronome client I wrote for jack: he seemed to say that it was a bit shakey. I really couldnt understand this, it sounded fine to me, and if there was a math error, then most likely it would very very audible. When I played the metronome while debugging these problems I immediately knew what he meant. It was all over the place (from a drummers POV), yet JACK was happy as could be. Its one thing to get an xrun and say something is not right, its another to have corrupted audio and yet not be informed. My guess is it all boils down to buggy hardware and the difficulty of writing code for it. --ant

On Fri, Dec 20, 2002 at 07:19:13 -0800, Mark Knecht wrote: Yes, thats right, but using the jackstart program provied in Planet CCRMA you can run jackd as a normal user. Try creating a shell script, eg /usr/local/bin/run-alsaplayer: ---- cut ----- #! alsaplayer -o jack $* || alsaplayer $* ---- cut ----- then do: # chmod 755 /usr/local/bin/run-alsaplayer Then set that as the association, it will try to run under jack, then if that fails fall back to alsa. I haven't really used jackstart much, but when I did it dodn't seem to give me such solid performance, but that was a while ago, so maybe there was a bug. Running all our audio apps as root isn't really a good long term solution. - Steve

Spacey filenames should be handled ok if you change $* to "$@" as shown below. ---- cut ----- #! alsaplayer -o jack "$@" || alsaplayer "$@" ---- cut ----- This feature of the script depends on alsaplayer exiting with a nonzero "status" (aka "$?") if it is told to use jack and jackd isn't running. If this isn't happening, it could be considered a bug in alsaplayer (or perhaps in jack if jack isn't returning an appropriate failure indication to alsaplayer). -- "Can you remember the future? Forget it!"

The symptom of breaking up file name arguments that contain spaces is produced by the original shell script and is not produced by the modified one. Either you didn't really replace the shell script file (changing all $* to "$@") or something else is also breaking arguments at spaces. Anyway so long as falling back to something else when jackd isn't running isn't working, the script doesn't really bring you any benefit, does it? On Saturday 21 December 2002 10:36 pm, Mark Knecht wrote: -- "Can you remember the future? Forget it!"

On Sat, Dec 21, 2002 at 08:49:38 -0800, Mark Knecht wrote: As someone pointed out, this is wrong, it should be "$@", sorry, I didn;t test it before posting. Thats because your alsaplayer is broken w.r.t the ALSA drivers. Mine is too. - Steve