3538c 'known' issues and ideas

Eugene Gavrilov

here's a brief list of present 'todo/known issues' [semi-internal ]
feel free to comment it out. if particular line is marked with '?', then I'm unsure if the issue is still present or the feature is really needs to be implemented.

note: some of the ideas were just 'cut&pasted' from the forum. so, don't expect it to be written in 'plain english'

--------

* bugs / new hardware-related issues:
a2 value: check compatibility
a2 passthru: http://driverheaven.net/showthread.php?t=60667
[new code]
setup: check for valid kXL effects / kxu installation
Add support for Digital Output on Gateway OEM SBLive ?
* asio:
support for 24/96 playback [ASIO]
latency issue in 3538 compared to 3534 ??
new asio sync code [kernel event-based]
fake asio ins for 44.1
64 out channels [playback, asio] ??
* kX scripts support [or at least an environment for 3rd-party implementations]
Or a command line integrated in KxDSP like that one from AutoCAD
Or more than this, updating Kx Automation with this feature for any plugin that supports automation..
It would be nice to also add hotkeys for they keyboard? Volume, mute
--- up to 3rd party developers!

* surrounder+:
'headphone' preset -- not implemented still

* dsp-based synth [kx automation enhancements]
dsp-based synth
automation enchancement [midi events]
+ Kevin Horden effects [??]

* p16v router:
- finish
p16v & others: write(read) is unsafe [wdm/kernel]
'follow epilog' flag

* ac-3 stuff
passthru for 10k1 etc...
click on ac-3 pause/stop/resume (mute spdifs?..)

* sndvol32 / topology / -6dB bug under 9x

* dsound / eax
3-d spatialization -- re-implement [speaker test, surrounder, 3-d gaming]
KX_HW_P16V_FOLLOW_EPILOG [not implemented]
p16v router / levels / routs [4 flags; 8 volumes; follow_epilog flag; follow swap_f_r flag; routings [+kX API change]]
EAX?? [if ever! ]

* soundfont bugs:
attack [semi-fixed?]
looping bug [on 'stop sample']
panning for MIDI CC Pan (realtime)- fails [clicks]
sf 32Mb limitation [simultaneous playback]

* kX GUI bug: skinned sliders [see eYagos effects]

* hardware:
constant beep: solution: disable/enable device?..
i2s incorrect init (46/77/90 dB noise) [external units] http://driverheaven.net/showthread.php?t=53320

* kX DSP:
info dsp plugin - unfinished
prologic ][ encoding/decoding [?]
rotary/b3 scanner [lemury effect]
agc effect http://www.hardwareheaven.com/showthre...threadid=13151 [eyagos]
dsp containers
Phase Shift [http://www.hardwareheaven.com/showthre...hreadid=35573]

* gsif2
- implement

* kx dsp fx plugin
asio interface [in/out] ?

* kx gui:
create_vslider/hslider: 'method' stuff
create_button: -""-

* minor changes:
'rename card' feature
map keyboard keys to tweak plugins
display the current filename anywhere on the window [dsp]
preset selection (as card name) -- LRU
change mouse cursors over ins/outs in the kX DSP
preserving filenames in the load/save dialog boxes would also be very handy
the inability to move between controls with the keyboard makes using kxmixer difficult
bug? viblfofreq: http://www.hardwareheaven.com/showthre...threadid=37453
bug: all the tweak windows show up in Always On Top mode, if the kX DSP is Always On Top
Also it would be nice that when one puts the mouse cursor over a pin, that pin would invert its colour, [hover]
For example in fxbus wave channels would be red, asio black
sliders on the ac97 page used the "deactivated" image when source is not Stereo Mix or Mono Mix [??]
auto set hw accel in setup [?]
bug: too short drums / metronome missing [!]
ctrl+alt+<letter> -> tweak window
multiple accounts - separate settings
speaker test: card selection
MIDI - LEARN - MODE [kx automation]
"automatic" labeling (peak on connect/disconnect)
bug? Reversed CC 74 (cut-off) response http://www.hardwareheaven.com/showthre...threadid=34076
[dsp effect] Allow minimize to tray (per window)
re-write kx_wcwait [wdm/kernel]
dsp effects: tweak plugin titles not reflect 'rename' option
shared constant gprs: re-check [semi-implemented]
mixer: solo mute etc.. (extended) + balance / pan + level; + smooth sliders [shift+mouse]+ balanced difference
mixer: make dB sliders more smooth (?)
bug: In Cubase; when selecting the midi channel 10 to select drum sets in a Soundfont; [??]
where they are located on Bank #128 of a professional Soundfont (from EMU); the
selection of drumsets are not displayed in the patch selection menu
bug: winme detection [under certain cfgs] [??]
bug:"Today I have found 15 files created by KX driver" [??]
save/restore kX Edit settings (like the font size).
bug: kx dsp resources [leak; minor; font] [once per start-up]
check: changing mixer backgrounds for diff. pages [diff. sizes
automation: interpolated + coarse/fine:
http://www.hardwareheaven.com/showthre...069#post186069
http://www.hardwareheaven.com/showthre...threadid=26348
bug: stand-by by timer : http://www.hardwareheaven.com/showthre...threadid=24543
make the checkbox labels in 'synth compatibility' somewhat larger
if you have a few peak meters going, it would be nice if you could stick them together
drum channel assignable
device-oriented systray menu
bug: it is also possible to start multiple instances of the driver compatibility and synth compatibility [??]
fix 'Update' function to restore 'output' connections, too
feature: free_unconnected_output_gpr()
bug: dane microcode is not 'unregistered' if file is deleted
p16v: mono playback (silence) [not confirmed]
force midi velocity [synth]
bug: kx_sfont_entry+3ED ? rare [??]
bug: kxdsp gpr regs incorrect
enhanced bypass (10k2)
bug: dxdiag: right only (3-D); fmod 3-d audio [??]
'v' bit (valid) for 10k1 [spdif]:
'v' bit (valid) for HCFG [10k2]
add 'mute spdif on bad audio' option ('v' bit; 10k2-only)
bug: simultaneous UART In + RemoteIR/Drive tweak (buffer lost)
vsti: save/restore dialog; card selection dialog
vsti: works with card '0' only!
ac-3 channel assignment / management [non-5.1 streams]
http://www.hardwareheaven.com/showthre...9&pagenumber=3

some additional ideas:
http://www.hardwareheaven.com/showthre...threadid=43743
http://www.hardwareheaven.com/showthre...threadid=25250
http://www.hardwareheaven.com/showthre...threadid=41276
http://www.hardwareheaven.com/showthre...threadid=39244
http://www.hardwareheaven.com/showthre...threadid=18969

--------
Eugene

mufasa

Wow, you guys are busy!

"i2s incorrect init (46/77/90 dB noise) [external units]":

Glad to see that's on the list, hope you get the info you need.

I've seen two problems with Cubase SE, not really sure they are KX problems but let me mention them in the interest of completeness...

1)
Sometimes when switching ASIO latency settings inside Cubase SE (KX ASIO control panel) it appears control is not returned to Cubase - Cubase just hangs (need to ctrl-alt-del shut it down). My workaround is to change ASIO outside of Cubase.

2)
One time Cubase SE completely froze (had to ctrl-alt-del) when recording audio using KX 3537 on an SB Live! Platinum. May have been my particular system, but mention it just in case it's been seen before.

dj_stick

for 2) random things happen
as for 1) many programs don't like driver changes to happen while they are accessing the driver. Logic manages to handle it be re-initializing the driver after changes

also for multi-card setups you may experience system hangs as the drivers install (issue with windows and multiple audio devices)

__________________

mufasa

When I say "inside" Cubase, I mean literally from a Cubase menu (not just when Cubase is running). I would think the program would be written to ensure it's not accessing the driver during critical code (it's aware the ASIO configuration is being changed), but who knows how they wrote it. Fortunately KX allows one to change ASIO outside of a program so it's not a problem.

Actually regarding 2) I don't think a random freeze is acceptable. I lost what I was working on and Cubase was unable to reload the project. Fortunately I backup projects often and was able to restore a previous version. While recording beats the hell out of the computer, I do think solid performance should be obtainable.

That said, I did say that this my have been my particular system and didn't mean to necessarily pin it on KX, really just trying to offer any information I can to be helpful. How seriously to take any given problem it is a judgement call that you guys make which I would think depends partly on how many post regarding a particular problem.

TravelRec.

Hi mufasa!

Just for clarification: do you mean Cubase SE or SX ?

I found out that certain VST(i)s aren´t very stable and if opened or only locked into the system, then cubase can freeze or crash randomly. If you can sort them out, then wipe them from the vst-folder and the problems are gone. I have a very stable SX installation with 3537 driver and sometimes, if I install new vst(i)s (for testing) then the program begins to run dirty, so no other solution than to kick off the new files or to look for an update of the vst(i) that fix the problem. It´s also a good solution to backup a stable running vst-folder from time to time to switch back, if there is a damage done.

__________________
Always take a look behind.

mufasa

TravelRec -

Thanks for the advice! Will do a cleanup. I have Cubase SE which although much cheaper than SL or SX should be a stable piece of software.

Sorry dj_stick and Eugene about the thread hijack, we should really all be posting about 3538c here, didn't mean to get into a Cubase discussion.

Samir

Plugin window position is now saved and restored automatically with the settings

When you set Peak window, after restart Peak is ALWAYS horizontal... Is it possible that it's position / mode is saved & restored auto?!?

__________________
MU3NKA 3A HAPO6!

JJones

Installed fine on my 'SB0060 5.1 [b800]', seems to work well!

I just noticed that the GUI panels are jumping to all desktops when I use the MS XP Powertoy 'Virtual Desktop Manager' MSVDM, which is a shame because it would be great to have the DSP window on its own desktop ...

Cheers!!

BiCho

actually the ASIO control panel issue has existed since 3538a. I already spoke about it here: http://www.hardwareheaven.com/showpost...6&postcount=84

up to version 3537, you could change the latency settings by opening the ASIO control panel from within the host. now it only works if you open the panel from the system tray.

__________________
Audiotecna - Innovación Musical
Native Instruments and Moog Music official distribution for Colombia

Eugene Gavrilov

can anyone confirm that?

DJ Pit

Seems to work as usual - changing ASIO latency within FLStudio works as it should. No problems here.

snake88

Eugene,its not an issue nor an idea.Just try to make the sound quality of the driver even better for the final release http://www.hardwareheaven.com/images/s...big%20grin.gif !

Game3DFreak

I just wanted to tell the other translators they should check the translation of the "rear left" tooltip in "speaker test".

From looking at the lang.ini file it seems they all say "subwoofer" instead of "rear left", but check it out yourself to make sure I didn't just mix up a few words

Search string: buttons.sw.test.tooltip=Rear Left

Greetings,
Game3DFreak

nakamichi

I have some requests for the next release:
1. Make the volume increase/decrease by 1dB,not 2dB as it is now,when using the multimedia keyboard volume Up/Down keys.
2. Make the OSD volume display more precise,with more rectangle blocks,so every dB of volume.change corresponds to 1 block.
3. Fix the bug where sliders in the mixer revert back 1dB,for example when setting volume from -1dB to 0dB and close the mixer controls,it reverts back to -1dB,the next time you start the mixer panel.

That's all that I can think of that is missing from the TODO list.Everything else major is there,especially the long awaited 24/96 ASIO support for Audigy2 series...great!

nakamichi

oh,there's more Installed this latest debug beta a few hours ago.

4. That kX ASIO Panel window is still buggy.It is still not showing on top of the FL Studio 5 application,and you can't right-click on the box in the taskbar and select "always on top".You must goto the desktop,set it and go back to FL Studio...very annoying.
And even weirder is that this bug happens in 70% of the time...not always

5. The ASIO performance is now even bit better BUT sound seems a lot worse than in the "a" release. Am I imagining,or the sound is now somewhat flat,with less warmth and there's a strange effect of the sound being somewhere behind you? Hmmm...
Using SB0240 Audigy 2 Retail and Stereo 2.0 setup.

Eugene Gavrilov

>> or the sound is now somewhat flat,with less warmth and there's a strange
>> effect of the sound being somewhere behind you

anyone to confirm? that's too strange, isn't it?

E/

nakamichi

Also,I would like to see the peak level meter color to be much lighter (green) at the beginning.The dark green beyond the -90dB level is so dark,you can't distinguish whether is it active or not.
For example,Sound Forge's meters are really good.You can see the meter changes at the lowest levels because they use much brighter colors.
Especially for people like me who use 25% of the monitor contrast (saves your eyes when looking 20 hours a day at a CRT monitor

Oh,aside from better ASIO performance,I also get less noise as well with these drivers...-103dB...not bad at all.Nice work,Eugene.

Toadly_Ossum

Id like to see some of the MX6 improvements from this thread added:
http://www.hardwareheaven.com/effects-dsp/55988-mx6-wish-list.html

Also if a help/discription of all the dsp components could be access via right clicking on the dsp objects themselves.

salivating for the final,
Toad

HunterZ

Oops, I would have posted this here if I had seen this thread before the other one I posted in: I always thought that it would be cool to be able to group a set of plugins into a "black box" or "compound plugin" that looks like one plugin but really contains a group of them inside of it. It would make it easier to organize complex DSP setups into something more readable and maintainable, plus it would make it possible to send someone a compound DSP effect that they can plug into what they already have.

Now I'd better go grab 3538c and see how it works. I hope I can load my settings back into it, as I see I'll have to uninstall first. My DSP has 40 plugins and it'd take hours to recreate it from scratch!

Toadly_Ossum

My DSP settings would not load, I had to rebuild it

Toad

BiCho

most modular software does this. In Bidule http://www.plogue.com they are called groups, and in Reaktor they are called macros. I guess AudioMulch and Max/MSP have similar functions.

This function is a must if you really want to get out the most out of the DSP, and it would really be nice for us the hardcore users , since we could share our setups in an easier way.

Besides that, the background on the DSP shouldn't move the entire window when you click on it, it would be nicer if it had a blue bar on top to do that, just like every other software piece in windows...

Great work kX team!!!

__________________
Audiotecna - Innovación Musical
Native Instruments and Moog Music official distribution for Colombia

Toadly_Ossum

Im using midi automation to control reverb level in the new EF-X Reverb Station. EF-X midi automation seems to only work if the plug in it self is "open" or minimized. As soon as i close the plugin the automation quits working.

For example:

1. Open Reverb Station and use midi CC to set reverb level to 100.
2. Close Reverb Station and use midi CC to set reverb level to 0 and nothing changes, I still hear the reverb at 100!
3. As soon as I open Reverb Station plug, the reverb level jumps to 0 (or where ever my midi controller slider happens to be at that time.

Toad

----Hardware / Software configuration---------------
Driver Name:kX Audio Driver (Debug)
Driver Date: Dec 1 2004 13:43:03
Driver Version: 5.10.00.3538 - debug
DB Name:LiveBay2
SB0090 10k2 [b800]
PCI Information:
Device: 41102 Subsys: 511102 ChipRev: 3
Card is '10k2'
Card has MPU device
Card model is '5.1'
Card HAS AC97 codec
Codec name: TriTech TR A5/CT1297 TAT
3D Extension: No 3D Stereo Enhancement
Codec is 1.0 compliant
Capabilities[0] :
DAC resolutions : -16-bit-
ADC resolutions : -16-bit-
Ext Capabilities [0]:
Port: b800 Irq: 0x14(20)
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 1; 2 5 1 Service Pack 1; 156 148]
----------------------------------------------------

bardnone

I can't differentiate it with Audigy1 & sennheiser HD590

HunterZ

Just wanted to follow up with my previous post and mention that I was able to load my DSP setup from the previous version I was using (the original 3538 beta release). I cleared the DSP first and then loaded the settings file I had saved from the previous version that had just the DSP settings and nothing else.

So far the only difference I've noticed is that I'm pretty sure I've heard a couple of pop/crackle sounds, although I can't replicate them and they happen very infrequently (just a couple of times since I installed the new version yesterday). I haven't done a lot of tests yet, but I'm not expecting any big changes from what I've read (I mostly play games and watch video, with the occasional bit of Cakewalk MIDI composing).

nakamichi

It sounds good now,aside from the occasional pop/crackle when playing MP3s.Doesn't happen often.
It turned out I set the speaker settings somehow to Hph,not 2.0 Stereo by mistake.
Now sounds much better.

ROBSCIX

It's kinda been mentioned I think but DSP Containers would Be AWESOME...ok For example plugs can be added to a container all patched together within..and they can be LOCKED..then this module can be Saved/loaded..I/O is definable..I want to make sure I explain correctly. SO instead of loading 5 plugins and patching them to achieve a desired effect..you only need to do it once and save and lock it... then it would show up as one rectangular module in DSP..when clicked it would expand to show tweakables inside...So these Super plugins can be made..traded..I am sure this idea would evolve if implemented... Sort of the whole is greater than the sum of the parts What do you guys think could boost the DSP up a few notches.. I think this idea has been considered by many people...especially peopl who constantly change the DSP.....I hope to see it realized...

HunterZ

Just wanted to add to ROBSCIX's comment to say that, in addition to being able to see the tweakables, you'd need to be able to see a "mini-DSP" view of how the plugins internal to the contaner are connected in terms of inputs and outputs. In fact, you'd probably want to let the user access the individual plugin tweak menus from the mini-DSP view instead of seeing them all on one menu in case there is more than one of the same plugin being used.

Just a thought

ROBSCIX

YES..YES...I wasn't sure if I was explaining it correctly or not..seems you understand it though. I think this idea, would be a major innovation to KX DSP...I read in a few places people were thinking of this same idea... I keep thinking of say..a person wanted a distortion module for a guitar..then in the container it could be>
Gain
input timbre
distortion
graphic EQ
or P5
Gain

BUT when the DSP is opened it is one rectangular module the "container" with in's and out's..as hunter said then when you right click you could have a sub menu with each plugs tweakables..or maybe when you double click the module it expands to a larger rectangle showing the internal routings of this super module....

So Guys can make these super DSP processors out of basic ones...they could be traded and posted to the forum...

Tiger M

Guys, this idea came to me a few days after I started using kX. But as I thought everything over I figured out that such a complication in the dsp window is actually not needed. I mean, how complex can your dsp setup get?

__________________
Miss you, Steve...

ROBSCIX

Of course this idea would come up..it's a natural evolution to the DSP window paradigm. Actually you could view it either way..you could say that it complicates things or you can say that it simplifies things. It would also give people the ability to design their own plugins even if they can't program...some people always use the same processors for certain tasks..so instead of having 4 modules they can have 1 and name it say "Microphone Processor"..or "Guitar Super Distorion" I another thread I was speaking with another guy who designed a frequency analyzer using instances of peak and 2 or 4th order croosovers...clutters the DSP..but is useful...now if these modules could be "COntained within one module and name "Frequency analyzer" then it simplifies things...for example in a right click menu..it would be possible to change the centers of the frequency bands..just an example...and modules could be posted and traded....if it was implemented all that would need to be posted is scripts that contained internal routings, I/O definitions...and perhaps presets native to that module. Of course this is just my opinion. I don't really think it's about complicating things it's about making things easier to use for people who are used to the DSP windows..it's about functionailty....of course people Don't have to use the container concept..