No sound or continuous beep w or w/o original sound on top on EMU APS

XDread

Great! I'll keep checking this forum to see where to download the kx.sys debug version.

TheDingo

Here's a shot of my error:
http://www.thinlineltd.com/beep.jpg

tek

As I read all these replies it seems as if it's your specific card that has the problem, so it's a hardware problem. I suggest you return it and exchange it as quickly as possible

__________________
[COLOR=White][/COLOR]

Rox271

I don't think this has anything to see with Hardware.
I used to be on Win98SE with kxdrivers and never had any such issue.
Since I moved on XP, I cannot use these brilliant drivers anymore except when I need to produce random beeps which unfortunately doesn't happen very often
Thanks to Eugene and XDread for their efforts cos this really sucks! Hope a fix will be found very soon. I miss kx drivers.

Eugene Gavrilov

>> I used to be on Win98SE with kxdrivers and never had any such issue

a very intersting fact
so, the problem is definitely in Windows XP memory management, because it is Windows that is responsible for the correct memory mapping...

anyway, a debug version of kx.sys to be included in 3533 development release

/Eugene

Rox271

I think so, Eugene, this problem is quite probably related to WinXP. But I have another clue. When I moved from 98 to XP, I (of course …) had to add another 256Mb RAM in my PC and now have 384Mb. I think I read somewhere in this post that kx drivers may be confused with a large amount of RAM.
XDread already tried a lot of things but I’m ready to do some tests if that can help; anything particular you would recommend to try?

TheDingo

This problem has only occured recently for me, though I have been using the KX drivers under XP with the Audigy for over a year. No new hardware or any change, I believe it either has to do with some change made in a newer driver release or some conflict with a Windows update.
As far as what causes it, there is no specific time. I believe that it occurs sooner depending how many times you open and close a program that uses sound. Sometimes I can go for a day of little use and it will be fine, sometimes I'm on for an hour with a bunch of audio programs opening and closing and it happens. Most often is if I leave the computer on overnight to download something, it will be ringing by morning.
Opening and closing Winamp 3 16 times does fix it, but I found that opening and closing Winamp 2.x 16+ times does not.

XDread

Yeah, it could be, but then I need an explanation why:
1. The bug is different with different kX driver versions
2. The bug was non-existant with W98 - Original drivers. (That was before I discovered kX, even before it existed...)

...

BTW: Is it really possible to return a discontinued product?

XDread

"Related to WinXP" - and w2k. (Possibly (and probably) same memory manager.)

Regarding the memory issue:
I have never tried anything less than 512MB RAM in any cfg with my soundcard, it is really hassle to do a test. (Rather easy, really, but I don't want to do it unless it is stated as important to test, there are a lot of cables and screws and the box is rather awkward positioned.) If it during a test should show that RAM is an issue, then I have to live with the bug or throw out the soundcard, because I am not going to run with anything less than 512MB RAM. I will do the test to sort out the problem, though.

I have only experienced this bug on w2k with kX drivers (doh... no other does exist...), so it migt very vell be what you are suspecting.

XDread

I really find this rather random. Sometimes I get the bug early, other times after the comp has been on for a long time, or even not at all.

When the bug appears, it has happened that it is fixed after a certain number of clicks, after a LOT of clicks, or even I haven't managed to resolve the problem.

Sometimes I really try to provoke the bug, but cant manage to do so, other times it happens rather often.

On early builds of kX drivers, the bug is easy to produce and easy to get rid of...

For you who have this problem, try the 3514 (or even 3518) build... As usual it is good to have some feedback...

Rox271

Well well well... Just installed v5.10.0.3532 on top of the old 3530 and... no problem May be it is too soon to open a bottle of champagne but so far it sounds ok.

Eugene, I did notice that the french translation of Analyzer is still "Spectrum analyzer" which is quite confusing since this is obviously not a spectrum (took me some time to figure out what the analyzer is )

Also the analyzer has quite a strange behaviour (may be I just don't understand??) and I suspect that could be connected to the previous beep issue. Actually every time I start/stop playing a sound with the media player, I can see two red strips (two voices allocated I assume?) in the analyzer. But the strange thing is this pair of strips is shifting from left to right every time I stop/start playing and then the whole thing is looping to left. This could have something to see with the beep disappearing after 16 winamp start/stop that XDread mentionned in some previous posts (I don't actually have winamp but I could cancel the beep the same way, using Media Player)??

When playing, I don’t only see two red strips; I can see 2 small red squares on top, next to the two large red strips. What the heck is this? Recording channels?

Well I guess this analyser may deserve some more documentation.

Anyway, I keep playing with v3532 and let U know if the evil beep is back

Eugene Gavrilov

3533 development release with some debugging information is finally out

check it here: http://www.hardwareheaven.com/showthre...threadid=15401

note: don't forget to 'screenshot' the spy.exe's output, too

/Eugene

p.s.
"earlier versions" simply did allocate the voices in different manner
however, the bug isn't related to the voice allocation, but to memory management

SkinJob

Yeah, I got excited after I installed the new build as well, but the bug did eventually manifest itself. It is much more difficult to make it happen however. With 3532rc1 I could produce the bug within a minute pretty much 100% of the time. Now I can click away indefinitely in WinAmp without incident most of the time. Eventually, it will happen, but much less frequent. I don't know if that's good news or just makes it even harder to track down.

Can anyone else out there consistently produce the bug with 3532?

Rox271

Yeah, looks like I was slightly too enthousiastic. I do have the problem and now that I installed the latest 3533 beta version, it is even worst Doh!
First I had no sound at all and then after repeatedly starting and stopping the Media Player, I had some beeps and eventually the normal sound.
I did try to install Monitor but this also seriously corrupted my PC and I removed it. Eugene, R U sure the NT dbgmsg.sys file is applicable for XP?

Eugene Gavrilov

the monitor should run correctly under XP
(I have it currently running with no problems)

copy the .sys to \windows\system32\drivers
and the .dll to \windows\system32

/Eugene

Rox271

Ok Eugene. Thanks for the info. Now I've got monitor running and reporting some information on buffer allocations as well as the latest version. So far I havent had the beep problem for the last couple of hours. Well, I know by experience that debugged programs are often more stable than released ones. Anyway, as soon as I have an issue, I send you a snapshot.

XDread

... It's just what makes the bug totally random ...

Rox271

Day 2. Still no problem.
Looks like Monitor is THE fix of the fixes. LOL. XDread, use Monitor, it is good!!!
Seriously, this beta debug version is probably not as fast as the release one. Would it be a timing issue?

Eugene Gavrilov

actually, 3533 included a very small and 'unserious' change that might, however, have affected this bug...

btw, there should be no performance impact because all the releases are 'development', including 'latest stable'
and adding 4-5 additional messages to the monitor window shouldn't affect the performance

a question: if you unload the monitor?..

/Eugene

Rox271

Hmmmm. This time I have a clue. I just started my PC and... no sound.
Had a look in Monitor and now have a huge list of messages and some of them are errors.
First I have to tell U that I only use the SPDIF out , not the analog output (it goes to a Roland VS-880).
Looks like the driver is facing problems with the SPDIF.
-1098.522911 Win32 ___Initializing shared data.___

-1099.972638 Default kx wdm debug: begin ------- cut here -------------------------------
-748.540451 Win32 + videoCreateDriverList
-1099.972602 Default waveout open[825d21f0;8220a000]: open(freq=48000; n_channels=2[2]; bps=16; type: ;
-748.540414 Win32 + videoFreeDriverList
-1099.972572 Default kx wdm debug: physical address: 0.2605000; system addr: 82205000
-748.540382 Win32 - videoFreeDriverList
-1099.972502 Default kx wdm debug: allocated pagetable space: 1
-748.540138 Win32 videoCreateDriverList: DeviceList contains 0 Video Device(s).
-1099.972480 Default kx wdm debug: re-mapped logical: 82205000 physical: 2605000 index: 1
-748.540084 Win32 - videoCreateDriverList
-1099.972453 Default kx wdm debug: re-mapped logical: 82206000 physical: 2606000 index: 2
-67.028892 Win32 kxmixer: spdif lost
-1099.972428 Default kx wdm debug: re-mapped logical: 82207000 physical: 2607000 index: 3
-59.755433 Win32 kxmixer: spdif (generic)
-1099.972402 Default kx wdm debug: re-mapped logical: 82208000 physical: 2608000 index: 4
-59.752040 Win32 kxmixer: spdif (generic)
-1099.972376 Default kx wdm debug: re-mapped logical: 82209000 physical: 2609000 index: 5
-59.512016 Win32 kxmixer: spdif (generic)
-1099.972167 Default kx wdm debug: end -------- cut here -------------------------------
-59.508099 Win32 kxmixer: spdif (generic)
-59.158177 Win32 kxmixer: spdif (generic)
-1095.719676 Default <kXLib> Changing TRAM size to 512kb
-58.964012 Win32 kxmixer: spdif (generic)
-58.960030 Win32 kxmixer: spdif (generic)
-1095.515047 Default <kXLib> !! internal error: empty input_gpr list. strange [8]
-58.831945 Win32 kxmixer: spdif (generic)
-58.828051 Win32 kxmixer: spdif (generic)
-1095.514991 Default <kXLib> !! internal error: empty input_gpr list. strange [8]
-58.763993 Win32 kxmixer: spdif (generic)
-58.760061 Win32 kxmixer: spdif (generic)
-1095.493847 Default <kXLib> !! set_tram_flag: tram instruction not found! [9; Surrounder]
-58.564000 Win32 kxmixer: spdif (generic)
-58.560073 Win32 kxmixer: spdif (generic)
-1095.493778 Default <kXLib> !! set_tram_flag: tram instruction not found! [9; Surrounder]
-58.399939 Win32 kxmixer: spdif (generic)
-58.396001 Win32 kxmixer: spdif (generic)
-1095.493709 Default <kXLib> !! set_tram_flag: tram instruction not found! [9; Surrounder]
-57.567951 Win32 kxmixer: spdif (generic)
-57.564024 Win32 kxmixer: spdif (generic)
-1095.493611 Default <kXLib> !! set_tram_flag: tram instruction not found! [9; Surrounder]
-57.083960 Win32 kxmixer: spdif (generic)
-1094.719988 Default [CMiniportCtrl::NewStream]
-57.080037 Win32 kxmixer: spdif (generic)
-743.430467 Default kx wdm debug: begin ------- cut here -------------------------------
-56.967953 Win32 kxmixer: spdif (generic)
-743.430430 Default waveout open[825d21f0;822ce000]: open(freq=48000; n_channels=2[2]; bps=16; type: ;
-56.964003 Win32 kxmixer: spdif (generic)
-743.430400 Default kx wdm debug: physical address: 0.263e000; system addr: 8223e000
-56.451351 Win32 kxmixer: spdif (generic)
-743.430331 Default kx wdm debug: allocated pagetable space: 1
-56.447963 Win32 kxmixer: spdif (generic)
-743.430297 Default kx wdm debug: re-mapped logical: 8223e000 physical: 263e000 index: 1
-56.335898 Win32 kxmixer: spdif (generic)
-743.430270 Default kx wdm debug: re-mapped logical: 8223f000 physical: 263f000 index: 2
-56.332016 Win32 kxmixer: spdif (generic)
-743.430245 Default kx wdm debug: re-mapped logical: 82240000 physical: 2640000 index: 3
-56.135934 Win32 kxmixer: spdif (generic)
-743.430219 Default kx wdm debug: re-mapped logical: 82241000 physical: 2641000 index: 4
-56.132019 Win32 kxmixer: spdif (generic)
-743.430193 Default kx wdm debug: re-mapped logical: 82242000 physical: 2642000 index: 5
-56.011934 Win32 kxmixer: spdif (generic)
-743.429991 Default kx wdm debug: end -------- cut here -------------------------------

Then the following sequence is repeating many times:
-56.008004 Win32 kxmixer: spdif (generic)
-706.403050 Default filter

Then I have that :
-109.741072 Default kx wdm debug: begin ------- cut here -------------------------------
-109.741034 Default waveout open[825d21f0;82203000]: open(freq=48000; n_channels=2[2]; bps=16; type: ;
-109.741004 Default kx wdm debug: physical address: 0.25e0000; system addr: 821e0000
-109.740934 Default kx wdm debug: allocated pagetable space: 1
-109.740913 Default kx wdm debug: re-mapped logical: 821e0000 physical: 25e0000 index: 1
-109.740875 Default kx wdm debug: re-mapped logical: 821e1000 physical: 25e1000 index: 2
-109.740849 Default kx wdm debug: re-mapped logical: 821e2000 physical: 25e2000 index: 3
-109.740823 Default kx wdm debug: re-mapped logical: 821e3000 physical: 25e3000 index: 4
-109.740797 Default kx wdm debug: re-mapped logical: 821e4000 physical: 25e4000 index: 5
-109.740366 Default kx wdm debug: end -------- cut here -------------------------------

And then the follwing line is repeating many times:
-67.030143 Default <kXLib> kX: SPDIF irq [ece0]

So far I couldn't get any sound. I think I'll have to reboot.
Don't know if this is of any use to you?

Rox271

Oh. I did reset the DSP and now everything is back to normal with no need 4 reboot.
1386.701018 Default Microcode reset request
1386.738598 Default <kXLib> Microcode compiled: May 7 2003 08:28:21; [Rear/Front swapped]; with '10 Band EQ'
1387.552158 Win32 -- start creating the page - 0 ms
1387.560400 Win32 -- background created - 10 ms
1387.562693 Win32 -- buttons parsed - 0 ms
1387.563122 Win32 -- soundfont data processed - 0 ms
1387.619889 Win32 -- page buttons created - 60 ms
1387.707925 Win32 -- additional buttons added - 90 ms
1387.712825 Win32 -- sliders created - 0 ms
1387.717723 Win32 -- static images created - 10 ms
1387.718155 Win32 -- subwindows shown - 0 ms
1387.718204 Win32 -- static images shown - 0 ms
1387.718243 Win32 -- sliders shown - 0 ms

Also note that though I didn't have any sound, the VS-880 was actually synchronised which basically means the SPDIF connection was active and ok.
So who's guilty at the end of the day???

Note : BTW, how am I supposed to remove the Monitor install? Can I delete the SYS file or is there something clever I'm supposed to do to prevent it from loading? This will be the next step, hmmm may be not right now but later for sure

Rox271

Another detail. Since the latest version, there's quite an annoying SPDIF Popup that regurlarly comes on top of screen, whatever the application is. That not very nice when playing a game full screen .

BTW, I keep talking about SPDIF for the 3 last posts, anybody else facing this sound issue is using a digital connection?

Eugene Gavrilov

>> !! set_tram_flag: tram instruction not found

it is safe to ignore this message (Surrounder uses on-the-fly code generation)

>> !! internal error: empty input_gpr list. strange

this seems to be a bug related to 'bypass' option - some effects seem to switch to 'bypass' mode randomly after reboot/hybernate
unfortunately I was never able to reproduce this bug in order to solve it ...

>> kX: SPDIF irq [ece0]

such message is shown when the status of spdif connection changes
frequent spdif status changes are usually caused by lack of synchronization, power failures etc...
if you don't wish to see the 'spdif' icon simply open 'OSD Notifications...' dialog and clear 'SPDIF' checkbox
if you wish to get more details, run 'kxctrl -istate' - it will display some more information (the spdif status)

>> uninstalling monitor
it doesn't require any special 'uninstallation'
simply delete the files - that's it

/Eugene

Rox271

Thanks for the info Eugene. I haven’t had to reboot the PC for the last 24h so we’ll see.
Everything is quite stable so far. Does the IRQ message mean I may have a bad connection? On the VS-880 I don’t have any particular message. Well actually I did the SPDIF connection myself using unshielded cables but as far as I know, the SPDIF is using a current loop and is not very sensitive to radio waves or whatsoever.
I think I will keep Monitor until the next official release of kx drivers, we never know.
It is a relief to have this driver back and stable, thanks for your hard work and support!

Eugene Gavrilov

so, XDread, how's 3533 for you? (haven't heard any reports)

---

spdif message: well, actually it means that the status of spdif input has changed
(that is, either the frequency or system bits (such as 'Valid Audio' and 'Sample Rate Locked') have been asserted)

usually it means that the hardware went out of sync due to some problem (such as power failure -- e.g. a refrigirator turned on)

>> stable/unstable release

well, I think we should check if the issue was timings-related - I'll remove any additional debug output in the next release to check if that was the case...

/Eugene

XDread

Sorry, I haven't had the time yet, but I have tested now.

This time I didn't have to click a lot of times to produce the bug... Unfortunately...

I will post details after installing monitor.exe. (If i have removed it.)

XDread

This produced the bug (First click with a bug):
(The paint messages++ came when I opened analyzer, so I closed the analyzer.)

48.158410 Default kx wdm debug: begin ------- cut here -------------------------------
48.158438 Default waveout open[f84e78c8;f795c000]: open(freq=48000; n_channels=2[2]; bps=16; type: ;
48.153160 Win32 kxmixer: WndProc: hwnd=0xA0232, msg = WM_TIMER (0x04D2, 0x00000000)
48.158456 Default kx wdm debug: physical address: 0.3a000; system addr: ff85c000
48.158506 Default kx wdm debug: allocated pagetable space: 1
48.158521 Default kx wdm debug: re-mapped logical: ff85c000 physical: 3a000 index: 1
48.153254 Win32 kxmixer: WndProc: hwnd=0xA0232, msg = WM_PAINT (0x0000, 0x00000000)
48.158537 Default kx wdm debug: re-mapped logical: ff85d000 physical: 3b000 index: 2
48.158553 Default kx wdm debug: re-mapped logical: ff85e000 physical: 3c000 index: 3
48.158569 Default kx wdm debug: re-mapped logical: ff85f000 physical: 3d000 index: 4
48.153359 Win32 kxmixer: WndProc: hwnd=0xA0232, msg = WM_ERASEBKGND (0x1B010C86, 0x00000000)
48.158584 Default kx wdm debug: re-mapped logical: ff860000 physical: 3e000 index: 5
48.158759 Default kx wdm debug: end -------- cut here -------------------------------
48.164187 Default kx wdm debug: begin ------- cut here -------------------------------
48.164217 Default waveout open[f84e78c8;f798c000]: open(freq=44100; n_channels=2[2]; bps=16; type: ;
48.164235 Default kx wdm debug: physical address: 0.72000; system addr: ff857000
48.164287 Default kx wdm debug: allocated pagetable space: 6
48.164302 Default kx wdm debug: re-mapped logical: ff857000 physical: 72000 index: 6
48.164318 Default kx wdm debug: re-mapped logical: ff858000 physical: 73000 index: 7
48.164334 Default kx wdm debug: re-mapped logical: ff859000 physical: 74000 index: 8
48.164350 Default kx wdm debug: re-mapped logical: ff85a000 physical: 75000 index: 9
48.164365 Default kx wdm debug: re-mapped logical: ff85b000 physical: 76000 index: a
48.164533 Default kx wdm debug: end -------- cut here -------------------------------

After a couple of clicks, bug gone:

208.855991 Default kx wdm debug: begin ------- cut here -------------------------------
208.856020 Default waveout open[f84e78c8;f793b000]: open(freq=48000; n_channels=2[2]; bps=16; type: ;
208.856069 Default kx wdm debug: physical address: 0.3a000; system addr: ff85c000
208.856121 Default kx wdm debug: allocated pagetable space: 1
208.856135 Default kx wdm debug: re-mapped logical: ff85c000 physical: 3a000 index: 1
208.856151 Default kx wdm debug: re-mapped logical: ff85d000 physical: 3b000 index: 2
208.856167 Default kx wdm debug: re-mapped logical: ff85e000 physical: 3c000 index: 3
208.856183 Default kx wdm debug: re-mapped logical: ff85f000 physical: 3d000 index: 4
208.856198 Default kx wdm debug: re-mapped logical: ff860000 physical: 3e000 index: 5
208.856367 Default kx wdm debug: end -------- cut here -------------------------------
208.859176 Default kx wdm debug: begin ------- cut here -------------------------------
208.859206 Default waveout open[f84e78c8;f795c000]: open(freq=44100; n_channels=2[2]; bps=16; type: ;
208.859224 Default kx wdm debug: physical address: 0.72000; system addr: ff847000
208.859276 Default kx wdm debug: allocated pagetable space: 6
208.859291 Default kx wdm debug: re-mapped logical: ff847000 physical: 72000 index: 6
208.859307 Default kx wdm debug: re-mapped logical: ff848000 physical: 73000 index: 7
208.859322 Default kx wdm debug: re-mapped logical: ff849000 physical: 74000 index: 8
208.859338 Default kx wdm debug: re-mapped logical: ff84a000 physical: 75000 index: 9
208.859354 Default kx wdm debug: re-mapped logical: ff84b000 physical: 76000 index: a
208.859522 Default kx wdm debug: end -------- cut here -------------------------------

THE WHOLE FILE:
http://www.galaasen.com/beepmsg.txt

ANOTHER GO:
http://www.galaasen.com/beepmsg2.txt

I don't know if you have got the information you wanted, if not, please tell!

XDread

I once again tried to reset the DSP, but no help.

Today it is rather easy to reproduce the bug. (Tomorrow, it might not...)

Last:

INIT SCREENSHOT:
http://www.galaasen.com/__init.bmp

FIRST WITH BEEP:
http://www.galaasen.com/__first_with_beep.bmp

8 CLICKS AFTER:
http://www.galaasen.com/__8_clicks_after_still_beep.bmp

FIRST SOLVED:
http://www.galaasen.com/__first_solved.bmp

Eugene Gavrilov

resetting the DSP should not affect the problem
well, according to the logs, the buffers are mapped absolutely identically for bad/good playback
I'll download winamp3 to test this issue

anyway, the problem might be related to your hardware [PCI bus]
there were linux people experiencing similar problems [running linux drivers, of course]

----- for all people experiencing the bug: -------

what is your chipset? nVidia/Via?
[pls give a full description. CPU/Memory (FSB)/Mainboard]


/Eugene

XDread

Chipset: NVIDIA nForce 2 based.
MOBO: MSI K7N2G
CPU: AMD Athlon XP 1800+
RAM: 500MB
HD: 200GB

But:
This is my OLD computer:
http://h20000.www2.hp.com/bc/docs/su...4/lpv07174.pdf

I had the same bug on that one too. (Another chipset.)

The ONLY similarity is that I run the same OS now that I did then and same amount of RAM. (Not the same chips.) I have made a fresh installation, of course.