3538l bug reports - Page 3

Lex Nahumury · Sep 29, 2006, 08:17 PM

Quote:

lex, have you got a chance to compare 3538l performance with 3534f?

Only a few quick tests. It seems that the anomalies discussed here;
http://www.driverheaven.net/showpost...33&postcount=7
appear to have have gone!
(haven't had the time to test it on my HT machine though)

Quote:

I added several optimizations and re-organized the code, so, in general it should work fast enough (and, under certain circumstances, even faster than 3534f)

Yes. Although not my original point of discussion,
it seems the actual driver performance in terms of
"minimum achievable stable ASIO latency" has indeed improved even over 3534f.
Eitherway, ..the best release since 3534f as far as I can judge from the few tests.

Quote:

..also, what do you thinkg about proFX plugins bundled with the driver?

Not sure.
A half year ago I'd rather seen KXGUI beeing replaced with
some adaption of my much more leaner WIN32API GUI-Framework.
You were otherwise engaged then and absent for quite a while,
so I moved on too working on non-kX related projects.
Nobodies fault of course.

My point still is; just using plain MFC for GUI is great if you stick to default Windows look.
However, customizing MFC control/window classes is bad practise IMO.
That is subclassing subclassed subclasses resulting in bloat, CPU waste
and weird tricky code to get around MFC's default Window Look for which it was originaly designed for to begin with.
Bottom line IMO; If one is going to customize (skin) ones app's GUI anyhow,
why not use win32api right away?
(ok, you probably already had MFC based skin classes, so why write again,..right)
Vica versa, if one chooses to use MFC for GUI, why not stick to it's default Window look!
Well, just my ponderings. Pay no attention.

Anyway,..I most recently released an updated ProFx version for users to enjoy your 38L.

Quote:

memory usage:
confirmed. working on it...

while you are at it;

- DSP right-click popup menu pops at wrong offset if
"show content while drag" is off.

- populate_presets(HMENU mnu) for WIN32API does not work.
(no priority, thanks for adding it though)

- Feature suggestion;
The ability for plugin developers to add sub-menus
or at least add plugins to existing sub-menus in "Add Fx" Menu.
(no priority either)

Cheers,

/Lex.

**Eugene Gavrilov** · Oct 3, 2006, 06:20 PM

3534f & 3538l: ok, good
--
MFC/GUI question:
unfortunately, I doubt I manage to re-write kxmixer/kxdsp code to work with any non-mfc API: porting the code to any 3rd party gui library (there are a lot of them on the net) would involve a lot of bugs and a lot of time.. I'd be happy to use your win32 api-based gui front-end, but cannot port kx code to it due to lack of time (and I'm sure we won't find the volunteers to do this)..
as for mfc, it is not 'bad' or 'good' by itself: I've seen quite nice skinned applications based on MFC. kX GUI was one of my first experiments with gui/skins, so, it is not perfect. of course, I'd be happy to re-write everything, but who will benefit?..
by the way, I still guess any cross-platform GUI library is a better idea (e.g. Qt or Juice or whatever): this might help us to port kX DSP stuff to MacOS or Linux, if necessary.
--
my particular question was related to ProFX effects currently bundled with the driver: since they are no longer supported and function incorrectly, it might be a good idea to either update them to your most recent versions or to remove them. there are pros and cons: pros: a user gets the latest effects out of the box (especially those, who don't browse the forums etc.). cons: the effects are not updated fast enough; some users won't even understand what these effects are used for

--
I can theoretically release kX DSP source code as 'kx add-on' (as I planned previously) -- and release several kx applets, too -- this might help to port them to some different GUI libraries etc. but this will require some more time and I need to be sure this work won't get lost, that is, I need to know whether there are people willing to keep working on this code.

E.

Lex Nahumury · Oct 3, 2006, 11:08 PM

Well, kX is a 'One Man Only Project', so naturaly there will always be
the "Lack of time" barrier/excuse on any development proposal/suggestion.
I'm working on other projects through CVS and that works great
in terms of overall development progress.
(Yeah I know,.. lot of work for you to seperate stuff and setup CVS.)

But why are we even talking about this stuff on a user forum??
Nevermind, so be it.

Here's what we do;
Just delete Profx plugins from kX distribution.
Users can download the package seperatly if they want to,
same as with Max's UFX.

Cheers,

/Lex.

**Eugene Gavrilov** · Oct 6, 2006, 06:30 PM

I don't see any true objections against a brand-new replacement for kxmixer based on kX API and any GUI library. however, such project has never started due to lack of developers or intention. kxmixer does not use any undocumented functions, kxfxlib is opensource; so, anyone can just take kX SDK, kxfxlib and preferred GUI library and write his own kX DSP with any features (and omit/support any set of features currently present in the kxmixer, e.g. WinMM Mixer or ac-3 decoding).
--
yes, I will probably remove legacy profx code per your suggestion
--
concerning 'adding sub-menu' feature: pls drop me a message how exactly do you see it implemented (currently this data is stored in categories.ini file of the kxskin.kxs)
--
btw, thanks for 38l-compatible ProFX build!

E.

scegg · Oct 8, 2006, 09:04 PM

No support for recording in Vista RC2 (x86)...

cics · Oct 12, 2006, 05:52 AM

Skin bug in 24/96 router.

10K2 & p16v labels are swapped. I playback 24/96 using wave hq from foobar and only get sound when '10k2 -> spdif' is on. For 24/48 playback, i set 'p16v -> spdif' to on and others are off.

cics · Oct 12, 2006, 05:55 AM

Some kX Remote keys not working in foobar 0.9.3.

Volume, Step, Cancel, Power, up, Down all work across windows xp 2, kxmixer and foobar.

Can't get Play, Stop, Pause, Next & Prev to work.

cics · Oct 12, 2006, 06:45 AM

kX installation seems to use a common dll in windows or sourced from creative. There is a new version available. (http://us.creative.com/support/downloads).

I have the latest creative driver (for audigy 2 zs platinum) under windows xp sp 2 which was removed. On kX installation i get 'target file is newer than source. do you wish to replace?' Tried both files but playback is better with newer version.

Edit: file in question is 'sfman32.dll'

Russ · Oct 12, 2006, 01:01 PM

When saving settings that includes binary data (write_bin_abs), to a file, the data is written as the ASCII representation of the data (as it is a text file after all). I think it would be better if the read/write functions were modified such that, if it is binary data, and it is being written to a file (as opposed to the registry), that it read/writes the actual BYTE values (hex values as text) instead of the ASCII representation of those BYTES.

-Russ

**Eugene Gavrilov** · Oct 14, 2006, 05:12 AM

sfman32.dll: no, we use our own sfman32.dll. always overwrite CL file with KX one
--
write_bin_abs: yes, this function is not implemented properly. it is not recommended to use it

E.

Maddogg6 · Oct 22, 2006, 01:30 PM

It seems 24/96 record was broken somewhere between KX V3538H and 3538L

I tested (im pretty sure??) in kX V3538H (my firsy KX version and loaded the longest period) - a 24/96 project in sonar - and it recorded and played back fine (using WDM driver model)
But now - when I record - it plays back at double speed - like its actually recording @48Khz -

It is visually illustrated in sonar - buy AFTER recording - the wave display shrinks to half its size as well.

It IS possible - I have a setting wrong some where - but I dont think its in sonar - as I said I can playback an old project no problem - and I dont see how this would be possible with same settings.

Can anyone confirm this? - or slap me the direction of correction.

ivanlaszik · Oct 23, 2006, 03:41 AM

Here`s my only and kinda big problem:After a couple of hours of pc operation the soundcards (all 4 of them) disapear from Sound And Audio Devices and from other software that needs sound (i.e.:audio & video players),exept for winamp,the cards disappear from Preferences but winamp is still playing,and sound comes out from the speakers.The cards simply disappear without any error message,or anykind of happenings of Windows Operation.The strange thing is that in Device Manager everything is ok,the soundcard is there,functioning properly,the only thing that solve the problem is if i restart my pc.and after a couple of hours,it disappears again.SO NEED BIG HELP.....cheers!!!

PS.:using kx for almost 2 years now,with the same card sb022xb 10k1 (d000),NEVER had ANY problems with previous drivers.

BiCho · Oct 23, 2006, 02:00 PM

it keeps forgetting whenever you select the double-click option for the tray icon. you have to select the option each time you run kx

BiCho · Oct 23, 2006, 02:59 PM

some of the plugins don't carry the custom, user generated name, but the generic one...happens in some of them. even after restarting the app

ivanlaszik · Oct 23, 2006, 11:53 PM

BiCho: the icon from the tray DOESN`T disappear.everything running perfectly execpt for the disappearence of the cards in windows sounds and audio devices,and when i play multimedia files in all the players i have installed there is no sound.only winamp works everytime,and in winamp preferences the cards don`t disppear.and i have this problem with all the 3538 drivers,cause i tryed them all.