Nappylady

well, I increased my PCI latency to 64 for each card, and in 24 hours, no beeping.

Sometimes it was a beep, sometimes it was silence. (or perhaps a beep so quiet I couldn't hear it?)

Anyway. I think I smushed it. I think the PCI latency was the problem!

Thanks!

XDread

In that case you do have the same problem!

24 hours is no time with this bug... I haven't had the bug for several days now, I'm sure it will come back!

XDread

After vacation, I'll install a really old version of the driver that the bug is easily reproduced, then experience with latency settings!

Eugene Gavrilov

to XDread:
btw, update your BIOS

to everyone:
if you aren't too busy, try to install E-mu XP / Creative drivers and check the latency value

/E

Rox271

Good idea...
Done.
What I noticed:
1. Creative sets 64clks while kx used 152
2. My SB IRQ changed to 3 while I forced it to 10 in the BIOS
Below some details on the new Creative setup

For EMU-XP what do you mean? APS drivers? R they compatible with the Creative card

Device Information
Device Type : Audio Multimedia Device
Device ID : bus 2, device 9, function 0
Windows Device Name : Creative SB Live! Value (WDM)
OEM Device Name : Creative Labs EMU10K1 Audio Chipset (SB Live!)
OEM Hardware ID : FUN_0, VEN_1102, DEV_0002, REV_0A
Device Name : Creative Labs CT4780 SBLive! Value
Product ID : VEN_1102, DEV_8022
Revision : A / 11 (10)

Power Management Features
Version : 1.00
Supports Clock Slow-down : Yes
Supports D1 PM State : Yes
Supports D2 PM State : Yes
Supports PME# : No
Supports PME Clock : No

Device Capabilities
Latency Timer : 64 clk
I/O port resources : Yes
Memory resources : No
Bus Master Capable : Yes
Special Cycle Recognition : No
Memory Write & Invalidate : No
VGA Palette Snoop : No
Parity Error Response : No
Address/Data Stepping : No
System Error Line : Yes
Fast back-to-back Transactions : No
Detects Parity Errors : No
Supports System Error Line : No
Supports Parity Line : No
User Defined Format : No
66MHz Bus Support : No
New Capability List : Yes
Device Select Timing : Medium
Multi-Function Device : Yes
Header : 00
Interface : 00

Hardware Resources
I/O Range : 0000ECE0
Irq. No. : 3
INT Pin : A#
Dynamic Management : Yes

Eugene Gavrilov

so, Creative definitely re-configures the PCI latencies according to its 'undocumented' technical specifications
have you tried to tweak the PCI latency to a '64' value? did it solve the problem with kX?

btw, as far as I remember, there was a Linux guy interested in solving the same issue for Linux driver -- it is much easier to test if the issue can be fixed by modifying the Linux driver...

anyway, it is currently impossible to fix this PCI issue because kX Driver cannot tweak the PCI bus directly -- so, one needs a 3-rd party tools for that...

/Eugene

Rox271

I just don't undesrtand. I checked the BIOS that says IRQ10 and now Sandra reports IRQ10 too. Oh well...

I haven't found any program to tweak the PCI latency other than powerstrip. Any better recommandation from anybody?

Also I went on E-MU and downloaded their latest APS driver v1.6 which is supposed to be compatible with SBLive and WinXP. Installation is ok, I go in the control panel, system device manager and try to upgrade the audio driver. But I cannot see any EMU APS Manufacturer?? Any idea??
Is this the driver you meant Eugene when U said test EMU-XP?

Max M.

Well, Eugene mean that APS owners should test E-mu drivers and Live/Audigy owners should test Creative's...

__________________

RIV@NVX

Live/Audigy1 owners - this might help: http://www.hardwareheaven.com/showthre...&threadid=8874

__________________
-- Vedran

Rox271

LOL!
Though E-Mu claims compatibility with SBLive (that is written in very small chars in the doc )
Actually it looks like E-Mu is actually installing... Creative drivers!!
Anyway after that, there is no ASIO available and the E-mu mixer doesn't work etc....

So I went back on Creative and installed the latest official drivers (28Mb)
WHAT A F[...self moderated..]G MESS !!!!

Kx for ever guys!!!

After reinstalling kx v3533 I had a surprise.
The PCI latency is still 64clk. So it looks like my current PCI setting is a legacy from Creative.
This could also explain why I had this funny 152clk value, probably from my previous experimentation on powerstrip.
Well, I think I will stick on that and see what happens.

Max M.

Yes, the driver in E-mu APS 1.6 is identical to the one of the latest Live/Audigy1/Audigy2 drivers... Only on-top apps are different (EControl, Apssfmgr)... Well, there's nothing strange - same company, similiar cards, unified driver...

__________________

Rox271

Well...
No I have the Creative PCI setup and the driver beeps....

Eugene Gavrilov

>> I have the Creative PCI setup and the driver beeps

is that '64' or '32?
are you sure the PCI latency is not reset to any default value?
have you noticed any dependences between beeps & sandra?..

/Eugene

Nappylady

Bad news guys. I thought I'd smushed the bug. I was wrong.

It came back.

In the middle of a gig.

...

It was bad.

Eugene, we HAVE to get this smashed.

Rox271

I read 64. This is the default setting that was on when using creative drivers.
Apparently the latest setting is kept somewhere in the computer.
Nothing obvious.

I now have the most recent 3534 version installed.
Still beeping; yesterday I was trying to find a way to cancel the beep without the (about) 32 Start/Stops trick.
I noticed something strange. After a DSP reset, the Optical and cd digital CD inputs are automatically reactivated though I muted them before. Is this normal? I noticed that cos it produces a larsen effect (I use and external digital mixer with SPDIF connections and most of the time the Optical input which appears to be my SPDIF In is muted). Then I was wondering if the beep could be related to that?
I could kill the beep once by resetting the DSP and then muting the Optical input but I could only do that once.
After a while the beep came back and I had no other choice but rebooting the PC.

Raygmar

Hi all!

I am posting to let you know that I am having the bug too.
It occurs when I change quickly a song or inside it. Once even without doing that, I just boot my computer and I had no sound. Sometimes is a beep, sometimes no sound.
I started to have the bug with the latest drivers, or at least I realised that I have it with the latest drivers. But I can't say you which version was. Now I am using 3533.

If you want to know anything related to my hardware, or want any test just let me know.

Thanks to all the people that make possible this project, this drivers are really great (even with this strange bug )

C u!!

Judicus

Hey guys, I'm new here. Usually I just browse the boards and leach info from them, but this is too awesome a project to do just that...I have to try and help when I can.

When I first tried out these drivers, I had my PCI latency set to 8, and my sound would frequently skrew up (same symptoms). After reading this thread, I turned it back up to 32. The problem seemed to go away, but after about 13 hours uptime, it decided to do it again.

With the newest (3534) drivers, the bug does appear, but after about 30 minutes, it corrected itself (I was copying over a large chunk of stuff from one HD to another, so I had the time to wait).

XDread

EMU = Creative (Creative bought EMU some years ago)

XDread

That's the bug in a nutshell!

Boy, I am happy that I am not the only one having this bug anymore! Not that I am happy to have the bug at all or that anybody does have this bug, but now it is definitly something to look up on since so many people experience this problem.

I feel sorry for Eugene who has to solve this problem. I can imagine that is not a funny problem. When creating something the fun is when everything is working all right or when the bugs are easily solved.

I'll stick to my promise: Twice the donation if he manage to fix the bug! (I can't afford more!)

Now to some BIOS upgrade and stuff to help giving more info on what may cause the bug...

XDread

'

The bug does correct itself sometimes, but not allways. (By it self does as usual mean after some interaction by the user or a program reallocating resources.)

XDread

Woot? - What is this?

From the "http://www.emu.com" site:

"The new APS Version 1.6 Software allows users to run the E-MU Audio Production Studio under Windows 2000 and Windows XP operating systems."

Link:
http://www.emu.com/support/aps.asp

Rox271

Yeah Max told me...
Do you think they will purchase the kxProject after that?

XDread

I am now trying the EMU APS driver to see if there is any difference between that driver and Eugene-kX.

- the EMU kX mixer didn't work, but Eugenes kX mixer does and does work together with EMU's drivers too. Quite funny!

I have already noticed the following:
The EMU kX drivers (mixer) does only allocate the first (2 or 4) channels for playback using the same voices allways. (Except probably when starting other apps at the same time.)

The bug with a voice getting a higher volume than the other is still apparent. (Was also a bug with Eugene drivers earlier, don't know with the new versions.)

NO beep till now, but that is far too early to say anything about!

I'll update with a report from Sandra!

XDread

Report from Sandra:

<< Creative Labs E-mu APS >>
< Device Information >
Device Type: Audio Multimedia Device
Device ID: bus 1, device A, function 0
Windows Device Name: kX 10k1 Audio - Model APS
OEM Device Name: Creative Labs EMU10K1 Audio Chipset (SB
Live!)
OEM Hardware ID: FUN_0, VEN_1102, DEV_0002, REV_04
Device Name: Creative Labs E-mu APS
Product ID: VEN_1102, DEV_4001
Revision: A / 5 (4)

< Power Management Features >
Version: 1.00
Supports Clock Slow-down: Yes
Supports D1 PM State: No
Supports D2 PM State: No
Supports PME#: No
Supports PME Clock: No

< Device Capabilities >
Latency Timer: 32 clk
I/O port resources: Yes
Memory resources: No
Bus Master Capable: Yes
Special Cycle Recognition: No
Memory Write & Invalidate: No
VGA Palette Snoop: No
Parity Error Response: No
Address/Data Stepping: No
System Error Line: No
Fast back-to-back Transactions:No
Detects Parity Errors: No
Supports System Error Line: No
Supports Parity Line: No
User Defined Format: No
66MHz Bus Support: No
New Capability List: Yes
Device Select Timing: Medium
Multi-Function Device: Yes
Header: 00
Interface: 00

< Hardware Resources >
I/O Range: 0000D400
Irq. No.: 9
INT Pin: A#
Dynamic Management: Yes

XDread

No, not after what I found in the post before your previous one.

Eugene Gavrilov

unfortunately, we cannot be sure that Creative drivers don't experience the same issue simply because they use a different voice allocation scheme

well, I can change the allocation strategy for the kX driver (it will allocate the same voice pair each time -- the way it was in 351x releases)

I currently have no idea how to solve this issue
moreover, I haven't experienced it anymore...

/Eugene

XDread

Well... the 351x release was buggy too... (Same bug, different frequency.) Strange thing that is.

Last, the Creative driver won't install correctly.

It is back to the kX project then! No matter how annoying the bug is! (When it does appear.)

Rox271

Oh well...
Still have the best ASIO drivers ever seen on SBLive so I will stick on kx anyway, with or without the beep.
Eugene if any idea or anything to try sometime later, just le me know.

Nappylady

I had reported success earlier by changing my PCI latency to 32 on my Live! cards. This success has come to a screeching halt, and there are times now that not even cold-booting the computer will help things. Last night I did a gig with karaoke and some people wanted to preview music using my MP3 collection, but despite all my efforts, I couldn't get a single waveout to work for them.

I'm seriously considering switching to a Frontier Design Dakota. If only I had more money...

Rox271

Well, Eugene does his best but simply has no solution.
Anyway to play MP3, U don't really need a high performance audio card do you?