3538l bug reports

**Eugene Gavrilov** · Sep 17, 2006, 08:11 PM

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 · Sep 18, 2006, 12:21 AM

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** · Sep 18, 2006, 05:58 PM

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 · Sep 19, 2006, 11:50 AM

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 · Sep 19, 2006, 12:58 PM

Quote:

- enhanced support for assignable mixer controls. it should be possible to assign any dsp controls to master/wave/synth/rec levels. use kxctrl -ma (note: usage option has been changed!)

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 · Sep 20, 2006, 01:48 PM

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 · Sep 20, 2006, 11:40 PM

- 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. · Sep 21, 2006, 12:06 AM

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

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

nkulas · Sep 21, 2006, 02:56 AM

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. · Sep 21, 2006, 04:07 AM

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

nakamichi · Sep 21, 2006, 03:34 PM

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 · Sep 21, 2006, 05:35 PM

Quote:

Originally Posted by nakamichi

- 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.

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

Quote:

Originally Posted by ReWired

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

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

Russ · Sep 21, 2006, 05:53 PM

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 · Sep 21, 2006, 06:01 PM

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 · Sep 21, 2006, 06:38 PM

Quote:

Originally Posted by nakamichi

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

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.).