goldy

RE: CONTINOUS BEEPING

I was using xx34.. with the new drivers, xx36, the beeping is gone, yay!

g.

kalimba

Others have said that is not the case. Let me know if the beeping is still gone in a few days after you've used it for a while.

Thanks.

Guillaume

I recently installed more memory, from 256MB to 512MB (PC133). Ever since I have not experienced the beeping anymore. (several weeks already).

__________________
Listen to Guillaume
I see seven towers, but I only see one way out...
AMD Athlon 1,2GHz, 512MB Ram PC133 (M.teq), Asus A7V133, 160GB WD + 20GB WD, Sapphire Radeon 9600XT, Creative SB Audigy 1394, Hoontech SB DBII Bracket, Pioneer 106D DVD-writer, Plextor 12/10/32A CD-RW, Iiyama ProLite E481S

rubber_glove

well a while ago (maybe two months) i posted a message saying that flashing my bios had taken care of the beeping problem... well, unfortunately this has proved not to be the case. i have experienced the bug a few times now, but the frequency of occurrence has dropped dramatically. before, the beeping would occurr many, many times a day, whereas now it happens quite rarely... maybe 2 or 3 times over the past few months...

i would prefer, of course that this bug went away forever, but i'm pretty satisfied with the state of things right now....


oh well..

Kyle70

Hi all!
Eugene, I get the constant beeping noise frecuently. Seems to happen only at 44.1 Khz and not at 48, and since 3535 or higher releases. Here are my experiences.
A friend and I have bought two identical computers, but with different SB Live models; the basic setup is:

AMD Athlon XP 2000+ (T'bred B)
MSI K7N2 Delta L (bios v5.6), nForce drivers v3.13 (nVidia IDE installed)
2x256 MB DDR 333 CL2.5, "High Perfomance" settings in BIOS
Geforce4 MX 440 64 MB DDR AGP 4x
40 GB ATA/133 Maxtor Diamond Plus 7200 RPM (primary master)
30 GB ATA/100 Quantum Fireball Plus 7200 RPM (primary slave)
52x Sony CD-RW (secondary master)
Pioneer DVD 115-F on PC1 / Asus 52x CD unit on PC2 (both secondary slaves)
SB Live CT4620 on PC1 / SB0100 on PC2 (both on PCI #3)
WinXP SP1

On PC1 with 3535/3536/3537 drivers, I was able to reproduce the issue with WMP9, Sound Forge (6 and 7), Cubase SX (1 and 2) in both DX & ASIO modes, but seems that only happen working with files at 44.1... I don't remember to have problems working on projects at 48 Khz.
On PC2, with 3534 drivers no problems at all with those audio programs, running in DX or MME mode (ASIO was not tested enough).
Another difference between the 2 computers was the use of the nForce integrated LAN port, in PC1 was always active because I use it with ADSL connection, while with PC2 was enabled but not used (cable disconnected). I'm talking about this because I read some nForce forums often, and SoundStorm users reported a "high pitch whine" with almost all LAN drivers released during 2003; people also reported that LAN drivers had a high CPU use.
Hope this helps.

Kyle

PS: ASIO @ 44.1 Khz now works fine since 3537rc1!!!!! Tested with Cubase, Wavelab 4, ACID 4 at 5-10-20 ms... Thanks Eugene!!!!!!!!!!!

Kyle70

Forgot to say something about PCI latencies; Powerstrip reports everything in the PCI bus with latencies of 32, and Geforce4 AGP with 248.


Kyle

PrEzEs

Well I'am able to reproduce this problem VERY often (20-30 times a day).
I see it mainly in playing SWF (shockwave flash) files, less often - in games or listening to music (winamp 5.0 DSound output).

What is helping to recover from it - use the explorer and generate some clicks when going up and down the folders ... after 10-20 clicks/beeps the normal sound is returned.
I saw too, when an object is still playing, which generated the beep/no sound issue, then the up/down folder thingy is not working. I must close the source which generated this bug in order to reset the sound with some up-down folder clicks in windows.

My config :

Windows XP SP2 build 2082 (in SP1a with all patches it happened too) Enghlish version, Kx Drivers : 3537 beta (with other versions this happened too... at least from 3535+).
Mainboard : Abit NF7-S (NForce 2 with 3.13 drivers without the IDE, and with Soundstorm disabled).
CPU: Athlon 1.7 @ 2.4
Mem : 2x256 CL 2.5
Sound : SB Audigy
Graphic: Radeon 9700 Pro
Network adapter - integrated Nvidia ethernet controller.
Power Supply : Deer 450 Watt

I'm new in here, but I have _some_ experience in bug-tracking/beta testing.
What shall I do first ? This thread has grown Laaaaaaaaaaarge... I have some spare time and I'm freely willing to track down this goddamned bug, because it's really piss***g me off.
PM me or write an e-mail.

__________________
-=PrEzEs Rig=-
|| Core2Duo E6400@3.0 GHz || ASUS P5W DH Deluxe || ATi X1950XTX || GeiL DDR2 800 Ultra CL4 2GB Kit ||
|| Cooler Master Real Power Pro 850W PSU || Thermaltake BigWater SE + Chieftec BIG Tower + Custom UV Cathodes ||
Audigy 2 Value @ KX-Drivers

Rox271

Yes the thread is getting large. And this is actually the second thread about this issue!
No clear explanation was ever found. Some talked about PCI latency, hyper threading etc...
Well, I did quit SBLive and now use my onboard Soundmax soundcard. It is simply brilliant and I get very low latency (same as SB + ASIO).

PrEzEs

Yeah, but it doesn't happen with the Creative drivers ...

only KX has this #$@! nosound-beeping issue. and I like the drivers A LOT!

__________________
-=PrEzEs Rig=-
|| Core2Duo E6400@3.0 GHz || ASUS P5W DH Deluxe || ATi X1950XTX || GeiL DDR2 800 Ultra CL4 2GB Kit ||
|| Cooler Master Real Power Pro 850W PSU || Thermaltake BigWater SE + Chieftec BIG Tower + Custom UV Cathodes ||
Audigy 2 Value @ KX-Drivers

Eugene Gavrilov

>> Yeah, but it doesn't happen with the Creative drivers

kX uses different voice allocation scheme
I will try to add a 'compatibility' option, that -might- fix the issue, however, it seems the real solution lies somewhere else -- in the deeps of PCI latency tweaking...

/E

PrEzEs

I remember the early latency fixes for Via chipsets with Audigy cards.
Maybe You could include such a thingie ? Just a thought.

Oh ... I removed my one ram - now running in single channel mode for the sake of the tests ... but no effect - the beeping is not gone. And the RAM settings were set to "by spd" (slow, compatibility settings).

I think that's not the RAM problem at all... ;(

__________________
-=PrEzEs Rig=-
|| Core2Duo E6400@3.0 GHz || ASUS P5W DH Deluxe || ATi X1950XTX || GeiL DDR2 800 Ultra CL4 2GB Kit ||
|| Cooler Master Real Power Pro 850W PSU || Thermaltake BigWater SE + Chieftec BIG Tower + Custom UV Cathodes ||
Audigy 2 Value @ KX-Drivers

Jorgo

I also get the beeping noise after random activity and then have to re-boot to get rid of it.
I am using the 3537 drivers and never had that problem before. My MB is an MSI KT3-Ultra (KT333) + Creative Audigy 2 OEM. My PCI latency is set at 128.
Keep up the good work, the drivers are nice otherwise.

pottypotty

Say, when I wait about 10 minutes, the sound is back.
For about 15 minutes, when I work with audio. Then it just starts beeping again.

Daniel Drummond

are you using 3537? Latest version?

__________________
www.palcomp3.com.br/ed

XDread

Just checking in... Too bad there is no real solution for this problem yet. It's about 2 yeasr now (i think) since I first started this thread. (Or the other one one that got closed for this one because of size.)

After all that time I hoped there would come a fix for the problem, but it is "nice" to see that I am not the only one. (It took about 6 months till I got my first responses, do I remember correctly.

*sniff* I am getting kindda sentimental regarding this very long-lived thread... *sob* lol Cry me a river, will ya! Haha!

Oh, well, since I bought a new motherboard and os, I haven't bothered to reinstall the sound card, running on a crappy on-board via-shit... hehe Cubase runs really bad - I need a good sound card!!!

Can anyone recommend M-audio? Or something else and not too expensive?

Edit:

Funny thing: I remember a lot of you who are writing here! lol Hi!

XDread

Are you absolutely sure about this?

I had the same problem on all my former motherboards, on win32. I did use the card on win16, which I can't remember any problems, but then I probably ran with the drivers from Creative.

Hmm... I am curious. I think I'll install the card on my computer again. On a completely new system - and on win XP instead of 2k, since I just bought an upgrade.

dj_stick

i sometimes have this happen, but there is another symptom
when i select in windows media player 9 kx wave 0/1 as playback device, no sound file will play, keep getting errors, but if i set to default directsound device (which is kx wave 0/1) i will get play back and occasionally beeps

but atm kx wave 0/1 works in wmp9 not sure what the trigger is either, it will occur after transition to the next track in the playlist.

__________________

XDread

Try to make a short summary for this bug, the best I can remember:

It's a transitional bug, ie: it does appear/disappear at start/stop of a sound, that is in turn at (re)allocation of a channel. (You pressing play/stop on your favourite audio/video player.)

It does never appear without such a (re)allocation, but you as a user does not necessarily need to do anything to produce the bug if a program plays sounds in such a way that (re)allocations of sounds happen during play. (Say: MS Messenger making a beep each time you receive a message.)

The bug may or may not happen on intervals of 16, 32 or 64. It may or may not disappear on such a bondary. This bondary may shift. (Possible bug?)

The bug DOES appear regardless of playing frequecy (sample rate).

The sound is pronounced as a continuous beep. This beep MAY be altered in volume by effects in games or you altering the volume. That is: In Diablo II LOD, if you move around, the characteristic of the (multiple) beeping sounds change. (in soud or volume? I don't remember!)
(On one certain version of KX and one certain occation I have heard faint distorted "thing" which could vague remind me of what should really be played.

If the beep-bug is pronounced, then so is it for ALL channels playing.

On older versions of the KX driver, the bug appears/disappears more often and more random.

I do seem to remember that I found the bug to appear/disappear during the STOP phase, not play. Reason I found this is that when I played one sound in one channel, then tried to reproduce the bug, it appeared when I STOPPED the playing sound. (Remember the bug is pronounced on all channels.)

It seems like the most people experiencing this bug is using the VIA chipset or in some cases (old (and new?)) IBM chipset.

The bug happens regardless of Direct X or ASIO.

There are speculations wether this is a latency related problem or not.

My initial guess was that this is a buffer related problem, but Eugene says it is definitly not so. I believe in Eugene. His guess is probably better than mine!

If you think you have a solution to this problem, use your computer for three more months. Then you will probably be safe if you haven't heard anything till then. The bug may appear often, and it may be gone for long periods of time.

Are there more things which I have forgotten?

sTARkdC

I have an nforce2 board with an SB Live! Value and I am experiencing the constant beep bug. I would like to note that this problem only started happening recently and I was using these drivers happily for about 3 months prior.

I use foobar2k to play my mp3s and this is how I first heard it. I have been able to recreate it a few times now most recently was about 30mins ago. It happens when I hit play constantly or use my mouse to seek through the track. It can happen within a few secs or mins but generally does not take any longer then that. A reboot sometimes fixes the problem but normally I uninstall the drivers and go back to the shitty Creative ones . Tonight I was able to fix it by opening the System Information utility in Windows and opening up the IRQ's option under Hardware Resources. Well at least I think it was that because it was the only other thing I was doing at the time.

I thought the root of my problem was something to do with IRQ's because I had recently started using some tweaking programs such as WinXP Manager (which I have uninstalled) and most recently Tune XP from Driverheaven. It has an option under the Hardware menu called "Speed up windows IRQ handling" which I had enabled and this is when I suspect my problems started. So I disabled the option and rebooted, played an mp3 and the beep came back and thats when I ran the System Information utility.

Now I am happily playing mp3s again and no matter how hard I try to reproduce the problem I cant do it.

Below is my System summary. Besides Tune XP there are no other programs I run that started giving me the beeping sound. My sound card does not share an IRQ with anything else. I have used driver versions 3534, 3536 (using now) and 3537

Hope this helps a bit.

SiSoftware Sandra

System
Host Name : STARK
User : Matrix
Domain : STARK

Processor
Model : AMD Athlon(tm) XP 2800+
Speed : 2.09GHz
Model Number : 2800 (estimated)
Performance Rating : PR3028 (estimated)
Type : Standard
L2 On-board Cache : 512kB ECC Synchronous Write-Back (16-way, 64 byte line size)

Mainboard
Bus(es) : ISA AGP PCI USB i2c/SMBus
MP Support : No
MP APIC : No
System BIOS : Phoenix Technologies, LTD 6.00 PG
Mainboard : nVidia-nForce2
Total Memory : 1023MB

Chipset 1
Model : Nvidia Corp nForce2 AGP Controller
Front Side Bus Speed : 2x 167MHz (334MHz data rate)

Video System
Monitor/Panel : MEA DV172
Adapter : RADEON 9800 PRO
Adapter : RADEON 9800 PRO - Secondary

Physical Storage Devices
Removable Drive : Floppy disk drive
Hard Disk : WDC WD1200JB-32EVA0
Hard Disk : WDC WD1200JB-32EVA0
Hard Disk : WDC WD1200JB-32EVA0
CD-ROM/DVD : LITE-ON DVDRW LDW-411S
CD-ROM/DVD : Generic DVD-ROM SCSI CdRom Device <---- Virtual drives
CD-ROM/DVD : Generic DVD-ROM SCSI CdRom Device
CD-ROM/DVD : Generic DVD-ROM SCSI CdRom Device
CD-ROM/DVD : Generic DVD-ROM SCSI CdRom Device

Logical Storage Devices
1.44MB 3.5" (A : N/A
Hard Disk (C: ) : 8.0GB (1.2GB, 15% Free) (NTFS)
Morpheus (D: ) : 103.8GB (41.4GB, 40% Free) (NTFS)
Neo (E : 111.8GB (5.9GB, 5% Free) (NTFS)
Trinity (F : 111.8GB (86MB, 0% Free) (NTFS)

Peripherals
Serial/Parallel Port(s) : 2 COM / 1 LPT
USB Controller/Hub : Standard OpenHCD USB Host Controller
USB Controller/Hub : Standard OpenHCD USB Host Controller
USB Controller/Hub : Standard Enhanced PCI to USB Host Controller
USB Controller/Hub : USB Root Hub
USB Controller/Hub : USB Root Hub
USB Controller/Hub : USB Root Hub
Keyboard : Standard 101/102-Key or Microsoft Natural PS/2 Keyboard
Mouse : HID-compliant MX500 Optical Mouse
Human Interface : Logitech USB MX500 Optical Mouse

MultiMedia Device(s)
Device : MPU-401 Compatible MIDI Device
Device : Standard Game Port
Device : kX 10k1 Audio - Model CT4670 Value
Device : kX 10k1 Audio - Game Port

Printers and Faxes
Model : Microsoft Office Document Image Writer

Operating System(s)
Windows System : Microsoft Windows XP/2002 Professional (Win32 x86) 5.01.2600 (Service Pack 1)

Network Services
Network Drivers Enabled : Yes

SiSoftware Sandra

Device Information
Device Type : Audio Multimedia Device
Device ID : bus 1, device 5, function 0
Windows Device Name : kX 10k1 Audio - Model CT4670 Value
OEM Device Name : Creative Labs EMU10K1 Audio Chipset (SB Live!)
OEM Hardware ID : FUN_0, VEN_1102, DEV_0002, REV_05
Device Name : Creative Labs CT4850 SBLive! Value
Product ID : VEN_1102, DEV_0020
Revision : A / 6 (5)

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 : 00009000
Irq. No. : 18
INT Pin : A#
Dynamic Management : Yes




.

Eugene Gavrilov

>> The bug may or may not happen on intervals of 16, 32 or 64. It may or may not disappear on such a
>> bondary. This bondary may shift. (Possible bug?)

no, this is expected since voice allocation can be quite random depending on channel usage
the actual interval can be traced visually by watching the Analyzer window

>> On older versions of the KX driver, the bug appears/disappears more often and more random.

since voice allocation algorithm was a little bit different
however, the issue is not related to the particular algorithm
that is, theoretically -any- algorithm should cause the issue, but with different frequency

>> It seems like the most people experiencing this bug is using the VIA chipset or in some cases (old (and new?))
>> IBM chipset.

IBM chipset?.. probably nForce/nForce2 chipset

>> There are speculations wether this is a latency related problem or not.

it is somewhat related to PCI traffic between the card & the host memory
so, it might be caused by invalid PCI bus timings, latency timers, 'bus noise' and so on

>> My initial guess was that this is a buffer related problem

the bug manifests itself as a 'buffer problem' -- that is, the card cannot access the PCI bus properly, that's why it uses internal audio cache -- and the host memory is not accessed. thus, you get a 16..32 samples 'loop' that sounds as a 'constant noise'

>> If you think you have a solution to this problem, use your computer for three more months. Then you will
>> probably be safe if you haven't heard anything till then. The bug may appear often, and it may be gone for
>> long periods of time.

I've experienced the bug only =once= and it was caused by some tricks with PCI latency, SiSoft Sandra and DMI/BIOS update procedure ... cannot remember the details

---

unfortunately, the bug cannot be solved at the moment

/Eugene

dj_stick

sounds like it is a PCI bus problem… those with RAID cards or RAID chips on the PCI bus, and other, high bandwidth devices, USB2, Firewire 1394, would experience this more often than most…
I doubt it is a bug with kX, and many pro-audio websites that i have read say that you should avoid using PCI sata/raid chips and motherboards with such features built in…

__________________

HunterZ

Eugene, he probably means Intel and not IBM or nVidia. Just a guess though.

__________________
Athlon XP 3200+, Gigabyte GA7N-400Pro2 Rev 2.0 (nVidia nForce2 chipset), 1 GB DDR400 (CAS 2.0, dual-channel), ATI Radeon 9800 Pro 256MB AGP 8x, WinXP Pro SP2, DX9.0c., Logitech Z-5500 5.1 speakers

Rox271

LOL XDread. Funny to see you back on this thread
I never could fix this issue but I'm now using the onboard sound card and gained a lot stability.

rubber_glove

Ha... since everyone is coming back to post on this thread, i thought i'd add in my input. after flashing my bios....many.... months ago, i experienced a significant drop in the frequency of occurrence of the bug. to the point where i cannot remember the last time it popped up, and i haven't even checked this thread for a few months.

Jorgo

I have also never experienced the beeping noise again but I have not changed the bios. The difference on my system is that I keep loading a little soundfont of 4k now. Before I didn't have a soundfont loaded.
Strange connection it is, but there you go.

sTARkdC

This bug has not reared its ugly head (touch wood) for more then 2 months now.

dj_stick

its happened several times to me - luckily the last time it happened i was speaking to eugene at the time… play and stopping about 32 (¿) times helps

__________________

EnigmaTorrent

Hmm.. well I have (had) this problem before.. I'm running an SBLive 5.1, on an nforce 2 board. Ahm.. it first started buzzing while I was away from my comp (MSN Messenger perhaps) and then more recently when I was on one of those humor websites which make you click on an "OK" box over and over.. these drivers are awesome, I want to use the ASIO portion to reduce my realtime midi latency, but.. I don't know if I'll be able to if this problem happens outta nowhere (i.e. at a live show :S). So far I have had no trouble while in FruityLoops while playing stuff, but it'd be nice to know if there is something I can do that has NO risk of going into "beep-mode"..

EDIT: Hmm.. I've also had the audio cut out, a program crash, and been able to fix the sound by continually restarting whatever screwed it up.. what a strange bug.. the drivers rock tho.

MoonJihad

I can reproduce the bug easily enough on my setup(read: I can make it happen within a couple of minutes).

The steps to reproduce it are simple :
1. Start something that does a lot of disk writes(defrag or copy a couple of large files)
2. Click like mad on the foobar2000 seek bar

I assume that it occurs because the PCI bus is locked due to the write and the driver gets out of sync with the card's actual status.

EnigmaTorrent

Yeah, all I gotta do is continually start songs in winamp, or seek a lot.. but doing the same thing fixes it.. and if it gets screwed up by some other app, starting songs in winamp repeatedly SOMETIMES fixes it.. thankfully fl studio only opens its channels once, or something, 'cause I've never had this prob with FL.