Eugene Gavrilov

pls post 3538l bug reports here

E.
===
please review 'known issues' before reporting any bugs
previous reports:
3538j bug reports
3538i bug reports
3538k bug reports

Russ

I am not sure what this means, but I am seeing several debug messages from kxmixer indicating warnings and bugs:

i.e.

ikX: mmsystem: bug: 0 [401] -- 12 685232 0 [cnt=10]
...
kxmixer: [warning] mixer api: control '12' not found [ttt=0]

There are many messages such as the above (some have different 'control' numbers, 'cnt' numbers, 'ttt' numbers).

-Russ

Eugene Gavrilov

yep, these messages are caused by lack of kX 0/kX 1 mixer controls
I will probably remove kxmixer code trying to save/load them
--
by the way: ALL: make sure to reset your kX settings, since otherwise 3538l will behave unpredictably!

Russ

Not necessarily a bug...

The "Double click" option for the kX systray icon, does not show any indication of its current setting (i.e. no check mark or anything).

<edit>
The language selection menu also does not have any indicator of the current setting.
(I think it is probably the same for the skin slection menu as well (but I currently only have the default skin so I cannot be sure).
</edit>

Russ

Thanks E., I have been hoping for the above for a while (particulairly with the Master Volume)...

Just a couple of things regarding this:

The usage instructions are not complete (I had to look at the kxctrl source code to figure out how it works).

The usage is (for anyone trying to use it):
ma <id> <pgm_name> <reg_name_left> <reg_name_right> <max_volume>
i.e. (to assign Master Volume to epilog)
ma 0 epilog MasterL MasterR 0x7fffffff

Unloading the assigned plugin, or reintializing the DSP does not map it back to epilog/default mapping.
Unmapping it (setting <pgm_name> to 'undefined') does not map it back to epilog/default mapping.

Once you change the mapping, you have to manually map it back to epilog to get the default functionality. I guess this is intentional, but can lead to confusion if you are not aware of it (so hopefully people will be aware of it now).

-Russ

nakamichi

Issues in 3538l:

- kxmixer.exe (the system tray process) has a very large memory footprint - about 34MB or more,a lot more than the previous versions.

- The audio device/options are grayed out (SB0240) in 'Sounds and Audio Devices' in the control panel.

- The included ProFX AC97 plugin has some serious issues: UDA is not working in the AC97 plugin,illegible pitch-black 'skin' and font corruption in the drop-down boxes for inputs after a selection.

ReWired

- it takes 100% CPU usage and few seconds when loading E-FX plugins interface (seems this happens to all skinned plugins)

- the setting for "Double Click" on tray icon is not remembered on restarting kX Mixer

Max M.

>- it takes 100% CPU usage and few seconds when

same for me, + 20..40Mb per each skinned plugin!

nkulas

My problem is distorted soundfont playback on SB0530 (audigy ZS NB). Laptop is Compaq EVO N800v. After playing several notes, midi playback becomes distorted....
This bug was present in 3538j release, so I was hoping for cure...
Any idea, Eugene?

Nenad

Max M.

minor stuff: (kX DSP:) plugin's context menu should not have "..." in "Presets..." item
edit: and its child items "Import/Export presets" should

nakamichi

More minor bugs:

- When the option 'Show window content while dragging' is unticked,the right-click context menu in the kX DSP appears with a large offset to the down-right.The menu should normally appear below the cursor.

- The red/green 'LEDs' in the 24/96 Router are still messed up.

Russ

That problem existed in 3538k as well.
http://www.hardwareheaven.com/showpost...88&postcount=5

Same here, I am guessing that this is related to the work being done on the kX skin architecture...

Russ

There is a minor issue with the ASIO Control Panel.
Setting defaults does not restore the latency settings list correctly, if using one of the 44 KHz settings.

i.e.
Change format to '16 bit / 44.1 kHz [16+0]'
Set defaults.
The latency times listed are for the 44.1 kHz setting.

The issue only appears to be with the Defaults button, as manually selecting the default format (or other formats) does update the latency times correctly.

nakamichi

I see,haven't tested 3538k,but with 3538j it was a lot worse (no context menu at all)

P.S. Why there's no 16bit/48kHz [2+0] ASIO mode? Hmmm...

Russ

I doubt such a setting is necessary. The [2+2] setting is basically the same thing as [2+0], if you do not use the ASIO inputs (out of the DSP). The reason for the [2+0] setting (and other [x+0] settings) with the 44.1 kHz format, is because you cannot record using ASIO at 44.1 kHz (as the DSP is fixed at 48 kHz). Those settings basically set which inputs/outputs are available for use, but that does not mean that they all have to be used (and because we cannot record (using ASIO) at 44.1 kHz, the number of recording inputs needs to be 0 for that format.).

Behaviour

in my system also.

Russ

The assignments made using the "ma" console command do not appear to be applied after a reboot or when loading a saved config (they are saved).

RDaneel

I would also like to comment on the insanely high "Working Set" memory requirements of this new release (which otherwise works wonderfully for me)...

Nothing else in my XP system even comes close to sucking up this kind of memory (including Windows Explorer and the huge VMware services) until we get to say, a modern Web browser that has been running for a while... Visual Studio 2003 with a good-sized project loaded is way smaller than the 3538L "kX Manager"!

So even though I assume this was not intentional, I trust this worthy-of-Microsoft bloat will be removed for the next release.

Before anyone rushes in to defend Eugene (not that he needs the help), I love kX and have used it as my only audio driver for years... but if I hadn't just upgraded to 2 GB of memory, I would be forced to abandon ship!

Tril

I noticed something that could be a small bug. When I right-click the kX icon and go to Settings->Double click, one of the choices is 'kX Mixer / E-Card'. I have a soundblaster live! so I don't have an E-Card and I don't have an E-Card pane in the mixer.

I can also select the '24/96 Router' even if my card does not support it.

These two choices should be removed from the list on cards that don't support them.


I also suggest to change the captions and reorder the choices under the double click menu to make them similar to those you see when you right-click the kX icon. They all have kX intheir name but not in the double click menu and there is one called 'Remote control' instead of 'kX remote'.

wmjordan

The huge 35MB-or-so memory consumption occurs on my machine too.
I have got to roll back to the previous 3538j version since I can't afford so much memory.

__________________
Me's box:

• Sempron 2200+, 1G DDR RAM,
• SBLive! CT3843 10k1,
• Windows 2003 Chinese Simplfied SP2, DirectX 9

Lex Nahumury

Yes, this is without doubt related to kX's skinning architecture
which is currently beeing revised.

Untill Eugene has fixed this, here's a workaround that works for me;
After every kxmixer restart (thus every reboot),

- open the DSP window,
- minimize it (not closing)
- maxime it

kxmixer.exe mem usage should have dropped.
Now you can open/close DSP window etc. and work normaly after this.

However, using any skinned plugin that relies on kX's skinning architecture,
- All EFX plugins
- Dynamic Proccesor etc.
will raise mem usage again with ~20to ~30mb per plugin,
and take up several seconds to load with 99% CPU utilization.

Note that Max.M's UFX and my ProFX3.x do not suffer from these abnomalies.

HTH,

/Lex

Russ

Thats pretty good Lex, it works with skinned plugins too.

i.e.
Open the tweak window for a skinned plugin.
Minimize the plugin window and the DSP window (if it is open), and the memory usage drops back down again.
Then you can restore the plugin window and use it normally (but you have to repeat the process anytime you re-open the plugin window).

wmjordan

Thanks for replying.

Actually this trick is quite misleading. Eugene will know that min & max does not help reduce the private bytes (that is, the memory which can not be shared with other processes) that KxMixer.exe consumes. You can see this amount of memory consumption by selecting the "Virtual Memory" in the "Columns" dialog of the Task Manager. You can see that Min&Max dramatically modifies the "Physical Memory" consumption, however, the "Virtual Memory" (the private bytes), won't change much.

I hope that Eugene can have this issue fixed soon so that we can enjoy his new works.

And...I guess that alternatively, Eugene can use this, MS OneNote 2003 does so too.

The resident tray icon sitting there is a very small and slim little executable, and its memory consumption should be ignorably less than 1M. When we click the tray icon, the icon executes the main module, which is somewhat memory-hugging. And well, we modify the settings, like the DSP or something, and then close the main module.
Thus, the main module ends its process. But the little tray icon is still sitting there, consuming the same small amout of memory as usual. So we can change the settings every time, yet the memory consumption will only jump to the ceiling, when the huge main module is running.

__________________
Me's box:

• Sempron 2200+, 1G DDR RAM,
• SBLive! CT3843 10k1,
• Windows 2003 Chinese Simplfied SP2, DirectX 9

Lex Nahumury

True, but it would have kept a few user's minds at ease untill it got fixed. (thanks for spoiling that)

RvC-Kenny

i can confirm this, about 33,6MB process in task manager

Russ

lol...
It may not help users that do not have enough memory to begin with, but it is still good to not have kxmixer eating 33MB of physical memory, even when you are not actively using it.

Max M.

wmjordan

>The resident tray icon sitting there is a very small and slim little executable, and its memory consumption should be ignorably less than 1M

unfortunately, this won't suite kX. in order to operate properly, most parts of the mixer should stay in memory - because of plug-in subsystem, kX automation etc. etc. - it's not just tray icon used to launch mixer but the whole mixer sticking behind.

but, well, that's not about this partucular bug.

wmjordan

However, the previous version does not hog so much RAM.
Perhaps, most of the increased RAM requirement was introduced due to the new Skin system. If so, this 'separated tray icon and main module pattern' can help reduce the idle time RAM consumption.

__________________
Me's box:

• Sempron 2200+, 1G DDR RAM,
• SBLive! CT3843 10k1,
• Windows 2003 Chinese Simplfied SP2, DirectX 9

Max M.

>However, the previous version does not hog so much RAM.

yes, sure. but this is a bug - nothing more.
so i hope it will be fixed to at least to return to its previous state (any version before) - that's it.
after fixing it, Eugene could think of any further optimizations - but well, unfortunately, kX is well known for its non-optimized way of being (as a back side of faster development and a multitude of the features).

sorry, if i was unclear - what i wanted to say is just that the pattern is another story.
(in other words: 'main module' sits in memory _not_ because of the tray icon)

Eugene Gavrilov

lex,
have you got a chance to compare 3538l performance with 3534f? although it is technically impossible to use 3534f code since it is absolutely ht/smp-incompatible, 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). also, what do you thinkg about proFX plugins bundled with the driver? they seem to be very outdated.

memory usage:
confirmed. working on it


E.