Eugene Gavrilov

hi there

one more release -- 'development/alpha', as usual

http://kx.maincore.nl/beta/kxdrv3536b-update.exe
and
http://kx.maincore.nl/beta/kxdrv3536b-sdk.exe

changelog:
Improved kernel-level 3-D audio synchronization<br>
Improved SMP / HyperThreading support (EXPERIMENTAL)<br>
Fixed bug with kX Mixer notifications / RemoteIR support<br>
Effect names and languages are now sorted alphabetically in the kX Tray menu<br>
Added support for CL-compatible sampling rate interpolation<br>
Added option to reset hardware voices (kxctrl -rv)<br>
Improved SoundFont support (looped and non-looped samples)<br>
kX API: added card-specific input/output labeling<br>
kX API: added support for text-align properties<br>

todo before 3536c/rc:
improve soundfont subsystem
further improvement of HT/SMP code

/Eugene

nicklad

The right hand side of the peak meter still bleeds accross into the left hand side by 1 pixel. (When in Vertical orientation.)

See referenced image:

http://www.jbod.net/peak.gif

nicklad

Eugene - Just noticed >> It is virtually impossible to select and copy the text under "Input/Output Status" because it is ALWAYS being continuously refreshed and focus is immediately lost. It also flickers ocassionally,

Why not change it so that the text is only refeshed when it actually changes?

Daniel Drummond

nicklad, hit printscreen key on your keyboard. Open an image editor (or even word) and paste it there so you can read it just fine. Anyway, why selecting and copying that text would be important to you? Eugene, new release is working fine here as always. Thanks.

__________________
www.palcomp3.com.br/ed

nicklad

I agree a screenshot is a workaround if you wish to save a copy - however, I though the general idea was to improve kX as much as possible.

I still believe this is a bug.

Lex Nahumury

Yes, but you may understand that there are far more important issues to solve first
then the ones you've managed to come up with.

/LeMury

nicklad

Agreed - But you also have to take into account the amount oif programming effort/time that is required.

Neither of these would consume a large amount of time and/or effort.

Also - I am not pressing for a timescale - merely reporting them.

Eugene can choose to fix them or not to fix them - and at a time to suit him.

So your point really isn't valid.

Lex Nahumury

>>Neither of these would consume a large amount of time and/or effort.

Well, Then I assume we can expect you will fix the peak meter any day now. OK?
It's in the SDK, look for Peak.h, Peak.cpp and da_peak.cpp.
(ah..silly me, of course you already knew that, sorry)
Let us know when you are finished. It would save us some work.


>>So your point really isn't valid.

Seems to me that you don't understand *my point* to begin with.


/LeMury

eyagos

Don't know what were the expectations, but my computer stilll experience ocasional reboots with HT enabled.

Eugene Gavrilov

hey, guys I doubt this thread is a good place for discussing decision making theory
it was supposed mainly for bug reports
- I will add the peak meter & IO Status issues in my internal 'todo' list [I will have a closer look as soon as I find enought (free?) time ]

>> Don't know what were the expectations

unfortunately, since I don't have a HT-enabled machine, I cannot debug this stuff directly
so, I cannot promise any real progress

/E

HunterZ

Eugene: I just upgraded from 3536a to 3536b, and now when I try to change any of the settings on the Tweak menus for DSP effects/plugins, the whole mixer crashes. For example, if I try to move sliders or (un)check boxes in Treble, Bal, or Surrounder, *bam* it crashes. Looks like this release made it out the door a little too quickly

LeMury & nicklad: We're all on the same side here - please don't get hostile towards each other. It doesn't help anyone.

__________________
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

Lex Nahumury

>>hey, guys I doubt this thread is a good place for discussing decision making theory

???????????????

Never mind. I'm out of here.

/LeMury

NightBreed

This release is working fine for me. The only plugin crash I had was with the Bal plugin. No other plugin crashes yet. Even LeMury's plugins work fine. I had to re-register the main kx plugins over the uniform ones from Max because of changes to the surrounder.

And maybe it's just me, but I've noticed better panning with midi playback using soundfonts.


Peace out

HunterZ

NightBreed & Eugene: I tried reregistering the main plugins and that fixed my problems as well. Must have been a problem with some of the UFX or other pre-3536b plugins I was using.

__________________
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

Robert McClelland

Hey Should I wait to these get beta? heheh

__________________
"XTREME AUDIO IS CRAP!" "There no support for it. It's crapist card on face of the earth it should be throw into the sun"
http://www.speedtest.net/result/1949536385.png

HunterZ

Robert: So far I would say you only need to wait if you want to use UFX plugins. On the other hand, I don't use ASIO, SPDIF, AC3, or any of that fancy stuff so I can't tell you if there are any issues there.

__________________
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

SBeaver

I still have problems with the output level changing itself in the mixer and the sound becoming distorted because of it (sounds as if I had set the output level higher than 0 when in fact it is not acording to mixer)
I thought the problem was fixed in 3535 but it wasn't.

HunterZ

I noticed that the Bal plugin still crashes the mixer in the way I described, even though the official kX plugins work fine now that I re-registered them. I guess something must have changed between 3536a and 3536b that causes incompatability between kX and old plugins.

__________________
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

Eugene Gavrilov

>> I guess something must have changed between 3536a and 3536b that causes incompatability between kX and old
>> plugins.

yes, some plugins might fail to function correctly due to minor changes in the kX API
however, the changes are source-level back-compatible, so, re-compiling the plugins will do the trick

/E

Lex Nahumury

Nightbreed, HunterZ and to others who are fairly new to kX;

It goes without saying that DSP plugins which are *not* standard bundled
with the kX Driver Package, are not garanteed to work with newer driver releases.
These are not bugs but merely incompatabilities.

In the rather rare event this occurs (like with the Balance plugin), simply 'right click' on the plugin,
look for the Authors name, and request him/her to re-compile/update it.

Please post such reports/requests in forum's DSP section.
This will help kX development and ultimatly yourself.

/LeMury

HunterZ

LeMury: That's cool - I just wanted to check here first to make sure it was what I thought it was (a change in the API) and not a bug before reporting it elsewhere (wouldn't want the plugin authors to get confused and/or frustrated due to a bug instead of an incompatability).

Eugene: I've noticed something else strange with 3536b - every time I reboot, the DSP gets scrambled and I have to re-load my settings file to get sound (and proper DSP settings) back.

__________________
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

Eugene Gavrilov

>> I've noticed something else strange with 3536b - every time I reboot, the DSP gets scrambled

can anybody confirm that?
[btw, 3536b might require to re-register kxfxlib.kxl and re-set your DSP settings...]

/E

HunterZ

I'm pretty sure I've already re-registered the main library and recreated by DSP settings, but I'll try again just to be sure.

__________________
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

danespen

Could you use my machine to debug via VNC or something like that? I'm unemployed right now (for 3 months) so I could for sure use an houre or a couple a day to help you test your releases....? I have a P4 2.4ghz "northwood" and was experiencing reboots with 3535... using 3534f now...

By the way, nice work on the project

Dan Espen Reinfjord
Norway (please don't say no to .no....)

asgard

kx Drivers are fantastic!

The most frequent crash I am getting using 3536b is with Netcaptor forward/back buttons they trigger a small windows sound which gives a rare chance of blue screen. No other config has been changed apart from kx added to the system 2 days ago.

The offender sometimes is naveng.sys which is related to Norton virus defs so perhaps we are seeing some issue with Norton 2004 / KX (???)

This crash is certain to be kx related. Removing kx, or reverting to standard drivers removes this problem.

Below the config states I have LiveBay1 from KX detect but actually its just an Audigy SE card no bays or extras.

My config is:
P4 3.0C (sigh.. yes HT.. its probably this)
XP SP pre2 v1213
Card: SB0162 10k2 [9000] - Its own IRQ
DaughterBoard (if any): LiveBay1 <--- no i dont have ;-)
AC97 Codec (if any): SigmaTel STAC9721/23
PCI ID: device=0x41102 subsys=0x521102 chiprev=0x3
OS Version: 0x5.0x1 [build=0xa28] id=0x2

Any input anyone?

Eugene Gavrilov

>> so I could for sure use an houre or a couple a day to help you test your releases

ok. please watch any new development releases and test them

/E

p.s.
>> DaughterBoard (if any): LiveBay1 <--- no i dont have ;-)

that's a little bit strange
run 'kxctrl -dbr' and re-check kxmixer's 'about...'

asgard

Ok did the DB reset, still thinks theres some daughterboard. My unit is a relatively newish SB Audigy SE which is the one with no firewire. It has the option for RemoteIR allowed also which would be from a LiveBay

----Hardware / Software configuration---------------
Driver Name:kX Audio Driver (Debug)
Driver Date: Oct 30 2003 01:31:32
Driver Version: 5.10.00.3536 - debug
DB Name:LiveBay1
SB0162 10k2 [9000]
PCI Information:
Device: 41102 Subsys: 521102 ChipRev: 3
Card is '10k2'
Card has MPU device
Card model is '5.1'
Card HAS AC97 codec
Codec name: SigmaTel STAC9721/23
3D Extension: SigmaTel 3D Enhancement
Codec is 2.0 compliant
Capabilities[6940] :
DAC resolutions : -16-bit- -18-bit-
ADC resolutions : -16-bit- -18-bit-
Ext Capabilities [200]: -slot/DAC mappings-
Port: 9000 Irq: 0xa(10)
Playback buffer: 20a0
Record buffer: 4000
Number of AC3 buffers: 4
Tank memory: 256 kb
GSIF buffer: 256 samples
OS version: [2 5 1 Service Pack 2, v.1213; 2 5 1 Service Pack 2, v.1213; 156 148]
----------------------------------------------------