NEW: ProFx (3538) Update Incl. MX6 and AC97

Lex Nahumury

Update: ProFx v3.09
Note: There are 3 versions available;
- 3534 to 3537 compatible
- 3538 to 3541 compatible
- 3545 compatible
Make sure you get the right one here;
ProFx Version 3.x

- SRC
- ADC
- KXLT
- ASIO
- MX6
- MX8
- PEAK4/6/8
- NOISEGATES (stereo & mono versions)

Installation;
Remove/delete any previous profx_xxx.kxl file
Unzip and register the new .KXL file.
Restart kxmixer.

/Lex.

popej

Does it have to be red?

I instaled then found it unlegible and unmatching to my desktop. Why kx drivers look cannot simply comply to general system settings?

Probably you did a good work, but I cannot force myself to give it a try.

Nando Dominguez

Long waited day, LeMury
I do like it!!!
Nando

>>edit

I'm going to be recording for the whole weekend with it. Will report.

John Lodge

Lemury,

looking good and works with SB0400 (using digital outs for the speakers).

I am running at 1200x1600 and for that a much more convenient text setup is X125% it is the standard Windows DPI=120 setting. And I don't suppose this is unique. You do not seem to be correcting for that. The effect is that the letters are too large in some places.

SRC: is fine
AC97: the nn.n dB's are too large, the Gang Rec Source is unreadable (too small).
Kxlt: the SB0400 [d400] part of the title runs into the launch plugin button.
MX6: the varoius dB numbers on the slider but not the numbers down the VU meters. However thenumbers at the top of the Vu meters are clipped in their boxes. The channel ids 1-6 are clipped in their boxes.

In general the color scheme is not the best, you might want to look at a Lecourier legibility table.

I may be missing something but how is it intended to launch these applets.

For example in the DSP the objects can be renamed and the new name shows in the DSP and in the launchfx plugin in the controls but does not show in the control title, nor does it show in the kX manager effects where the defined effects can be launched.

The result is there is as far as I can see no way to lauch them with their defined names and stay within that naming context in use.

If there was a dummy stubb FX called FXLauncher for example it would show as such in kX manager and can then be used to bootstrap the components (or maybe a tray object that does the same). But the Window title remains unchanged by the rename.

In closing, this is very good work.


...John

Tiger M

Nice, a little bit too red, but ok...

You know waht would be fantastic? If the combo boxes were right on the dsp blocks, so ins and outs could be selected without opening additional dialogs. Just a thought that would make a big difference...

Lex Nahumury

When I asked my wife; "Honey, what color should I use for my plugins?",
she answered; "Well, I do like the Red, but I think you should use Grey".
"Why?" I asked. She answered;
"Nobody really Loves Grey, but nobody really Hates it either".
(Smart woman my wife)

Confirmed. I'll see if I can/will fix that.

'K' shows a list of *uploaded* DSP effects which GUI (tweak window)
can then be opened provided it has one of course.
(Not to seldom I find myself with just 1 open fx gui and quickly need
the dsp window or tweak one of the other effects)
Maybe 'Launch' isn't the right label here.

The fx title does not take over 'renaming', simply because I don't want it to.
(too large user text input)

Yes. Good idea. It seems something went wrong with the color.
(apart from taste that is)
Yes. I suspect my TFT screen isn't the best one to objectivly judge colors
because it looks 'great' here. (apart from personal taste)
Hmmm, If all else fails, I think I roll back to good 'ol' silver grey.

Yeah. Have to be small boxes/labels though.
Anyway, I'm still working of making mixer strips like EMU's stuff,
but that approach will never have the same flexibility as our current DSP window.


Thanks for the feedback everyone!

/LeMury

Russ

I really like that "K" Launch fX PlugIn button. It is a nice shortcut for tweaking other loaded plugins without having to go through the DSP window. I wish all the plugins had a similair ability.

Nice work!

John Lodge

In retrospect (and this has probably been discussed). The sliders on the kX mixer top page: Wave/PCM, Midi Synth may be superfluous..

With FXBus0/1 and FXBus2/3 in SRC joined to MX6 they are duplicated by the input mixer sliders. Yes, the function is probably buried in kMixer code but that was not the case with some of the other kMixer sliders (well of course they were related to objects surfaced in the DSP).


...John

Lex Nahumury

Yep. That's correct.
One can control those sliders through kx api, but one can't 'remove' them.

/LeMury

townkat

nice work,
too red for me too

John Lodge

Perhaps its documented somewhere but I just noticed that the mixer Channel names can be overwritten with more meaningful names and are remembered. Very nice!!!

As well I note in regard to Audigy 2 (Well value in my case) that side-right and side-left are not there. Not that 7.1 is all that desirable but the two extra high quality DAC channels can provide a couple of extra analog outs. Just needs a couple of 4-pole to triple RCA's to split off the extra channels to get at the signal.

BiCho

bad news... i use both a SB0240 and a SB0060. worked fine with 0240, niiice plugs.

kXlt went nuts in 0060. the d00 light is always on, and as soon as i click on it, kX crashes without any message.

if i change the output destination with the menu, kX crashes.

next time I restarted, the output changed to the value i set before it crashed. but the output showed up again in the previous position, that means twice

besides, 0060 is not giving any sound since i installed pro fx 2....

thanks for the plugs, please change their color! http://www.driverheaven.net/images/s...big%20grin.gif

Lex Nahumury

That's not good.
Did my old k1lt/k2lt work fine on on your 0060?

/LeMury

EDIT:
Bicho,
Could you verify/check if the kxlt DOO crash only happens if you use [ac97] plug + [kxlt].
That is; does kxlt DOO also crashes without using ac97 plug the same time?

BODYPRINT

Very Nice plugs LeMury. Thanks so much for your contributions.

A little bug. If you slide a slider with the mouse, then decide to use cursor keys straight after to adjust them, the display corrupts a little. Moving the mouse over the corrupted areas restores the correct images again though.

Lex Nahumury

Strange. I can't reproduce this.
Does this happen on both mx6 and ac97?

/LeMury

BODYPRINT

Yeah.
Would you like a screen shot with it happeneing?

John Lodge

I looked and can see it too.

But it is intermittent or to be more precise:

It happens after the control is lkaunched; but not after it is minimised and then restored.

On MX6 the effected areas are:

The three thumbs/buttons at the top of each channel slider and the two for the outputs as well as the K & D buttons at the top.
Each area is a square white patch all the same size. Where the patch does not fully cover the button the remains of the button and its color can be seen. The patch is aligned to the LHS of the button and centred vertically to the button.

After mousing over they do not come back (at least for me).
Dragging a window over does not help.

Looks like it is quite specific to these buttons and related to going from mouse to keyboard

If one goes first into a channel name and then goes over to mouse a slider is still occurs. But again only immediatelu after a launch not after minimisation.

...John

John Lodge

Hmm driverheaven crashed.

Thought it might have been a disply byte alignment issue; changed from 32bit to 16lit no change to the effect.

PITmaster

There are still many 3537 users. Any chance?

PITmaster

John Lodge

Yes it happens with AC97 too same characteristics.
the K D buttons at the to then down the bottom:
4 locations in source and 6 in mixer

The source are: gang re source, enable and both spin controls for Mic Cd et al, but not the display of what is selected.
The Mixer are the enables and mic boost.
As with the mixer the white square is on top and opaque and does not cover the width of the control leaving the color still visible.

Lex Nahumury

Yes Please.

John,
Followed your steps but still can't reproduce it here. Hmm...

/LeMury

BiCho

It does crash the same way even if ac97 is not loaded. And it worked perfectly with previous versions

Forget what I said about the color, looks niice running along with Traktor's red skin http://www.driverheaven.net/images/s...big%20grin.gif

any chance you could choose mono/stereo channels on mx6?

John Lodge

OK so what are the dll's you are using that relate.

msvcrtd.dll 6.00.8797.0
msvcr71.dll 7.10.3052.4
kxapi 5.10.00.3538 debug
kxgui same
user32.dll 5.1.2600...the SP2
kernel32.dll same

Note msvcrtd is the debug import for msvdr71d.dll (or claimed to be in msdn) but it is mscvdr71.dll that is loaded not the former so says Taskinfo (Igor Arsenin).

Looking in in system32 I don't see an msvdr71d.dll.

hope this helps.

John Lodge

nope the existence of msvcr71d.dll does nothing. But I did come across some folks with issues between that and msvcr71d.dll. But maybe unrelated.

John Lodge

One more small factoid: the bottom left reset button of the panel clears the inner window occurences but leaves the top K & D buttons still exhibiting the problem.

Nando Dominguez

Here is a picture:

http://www.iespana.es/NandoDominguez/MX6%20bug.JPG

It happens here (the same as the rest) when you move a slider with the mouse first and then with the cursor arrows. Then you move the mouse pointer over the spot and it disappears, and it doesn't come out again until you close or minimize the window.
Nando

>>edit. It happens in AC97 too but in the text fields below the sliders: GANG, E, ENABLE UDA, etc. Here is a picture:

http://www.iespana.es/NandoDominguez/AC97%20bug.JPG

Russ