laserbeak

3537 Doesnt Work For Me The Only Thing That Works Is Ac97 And Asio.

Russ

@laserbeak,
I think you need to be more specific. What exactly doesn't work for you in 3537? Are you getting any error messages? ,etc.

Russ

@Lemury,
I just thought I would add my name to the list of people who are eagerly awaiting the 3858i verison.

laserbeak

i had assumed that he said that i could load the 3537 profx modules in my 3538i wich doesnt work.
i just want to be able to load them to save as much computer resuorces as possible.

laserbeak

oh so there is no version for the i then?

so it would be best for me to run h?

Russ

The one's that came with 3538i do work. There is just a bug with the skin on the AC97 plugin, and I think that they are slightly older versions than that of the last update.

laserbeak

they dont work for me but i see the skin problem for the ac97 that and the asio is the onlly thing that works
maybe i should uninstall the drivers all together?

i will uninstal evertything and try reinstalling.


after i uninstal should i reboot before i perform the reinstall?

Russ

Again, in what way are they not working?

In any case, reinstalling kX should fix it, just make sure that when you uninstall that you include the registry stuff, etc. Rebooting after removing kX would probably be a good idea.

Russ

BTW: Sometimes you have to reset AC97 (on the AC97 page of kX mixer) as at times it seems to get out of sync with some of the ProFx plugins with 3538i.

laserbeak

i get a message that says failed to instantialize plugin do you want to unregister it?

on all but the two profx plugs that i said work

and
now im trying to uninstal the registry stuff and its just frozen

Russ

Hmm, that is strange as most of them are located in the same .dll.
I would try re-registering the .dll's before doing a reinstall.

Double click on these 2 files in the Windows/System32 directory to re-register them.
kxfxpack.kxl
kxfxadc.kxl

<edit>
Never mind, I guess I was to late with this reply. Anyway the reinstall should do it.
Before starting the install, make sure that the kX registry kX was removed (since it froze up on you)
HKEY_CURRENT_USER\Software\kX

Russ

BTW: The kX install does not fix broken or modified registry keys during the installation. Additionally, all .dll based plugins need to be recompiled to work with 3538i. Because of this I would recommend (to anyone) doing a clean install of 3538i (rather than upgrading), or you may end up in a situation such as this (as well as having a whole list of plugins that do not work).

laserbeak

heh thanks russ youve been a big help. but it was my fault all along. i was so exicited cause i saw the headline"new profx plugins" and i installed them not realising that they were for the h. sometimes i'm such a dunce. and at everyone else's expense. thanks for your patience ands i apologise. my intentions were sincere.

Lex Nahumury

hmm..!

Lex Nahumury

3538i??? Or do you mean the (old) included profx plugins?

Anyway;
Yes, there is no 'sync' between the ProFx's ADC plugin and kxmixer settings.
That is, both can take control over ac97 device's settings.

I don't use any 3538, but with 3537 and earlier I never have to reset ac97
while using the ADC plugin. (Reboot/restore etc. all work fine)

Ofcourse, If someone or something alters AC97 settings behind 'ADC's back', sync is lost.

Russ

I mean the version that comes with 3538i. Sometimes when I load AC97 or src, and choose line_in, I get no sound from that source without first resetting AC97 (and I mean when I first load the plugin and select a source, so nothing should be changing ac97 settings behind it's back). I do not remember it happening so often with 3538h (with the latest ProFx), but it does happen fairly frequently to me in 3538i.

Lex Nahumury

>>but it does happen fairly frequently to me in 3538i.
Ah yes, that one is old and buggy.

monohouse

Thanks Duuuuuudeeeeeee, You Da Man !!!

is it really necessary for the gui to be that slow ?

Lex Nahumury

What do you mean exactly with slow?
Could you be a bit more specific?

Russ

I think he probably means in the time it takes for the plugin window to open. Skinned plugins are noticeably slower to open than non-skinned ones (depending on how complex the skin is).

Lex Nahumury

Sure, but I wouldn't label that as "that slow" don't you agree?
On my slowest PC (1ghz P3) all plugins open within msecs.

Russ

Well for me, it is almost a full second (1.3 GHz Athlon Thunderbird) for some plugins. Still nothing major, but I do remember thinking that it was a little slow the first few times I opened windows like that.

Russ

You know something, I have been thinking about (trying to remember) and it may not even be the tweak window he is talking about. There was something, I just cannot remember exactly what it was. (I am using 3538i, so I cannot test it, and I am not even sure that it would act the same in 3538i if I could). I do specifically remember something though (that was very noticeable on my old beast) when I was using 3538h, and now that I think about it, it may have been loading the plugin. All I remember is that there was some delay somewhere (and I seem to remember it locking the whole DSP Window, sort of like when loading a saved config) with one of the ProFx plugins. I thought there was another plugin that exhibited the same behavoir (Dynamics Processor, maybe), but I notice no such behavior with any plugins in 3538i, so I cannot be sure about it. Sorry, it has been a little while now, so I cannot remember exactly. Hopefully monohouse will elaborate on his comment so we will know for sure what he was talking about.

Maddogg6

Confirmed. with A2ZS also.
Yes, the version of profx with 3538i is all but unusable IMHO - I used them all the time in 3538H.. but now its prolog and FX buss for me in 3538I.

MX6 - if I tie a MONO signal to both L & R inputs of 1 channel. sometimes a L or R channel will get lost - you will hear it in only 1 channel and the internal meter refelects this as well.

Not sure if thats been addressed??

Lex Nahumury

This has been discussed many times since 3538i release; That code wasn't meant to be included!
You mean non-skinned 3538i version of mx6?

Lex Nahumury

It's still unclear to me if you guys talk about
skinned ProfX plugins or other skinned plugins, since 1sec on a 1.3ghz pc to open a plug's gui is to long IMO.

Maddogg6

@Lemury:

Yes - the unskinned MX6...

I also noticed it disconnect itself from epilog once also...

Russ

LeMury, just ignore my last couple of posts. I really cannot remember, and for all we know, monohouse may have had a bad connection and was talking about the time it took him to download it. He could have been talking about anything. His post just reminded me of something from a while ago (that I thought had something to do with ProFX, but I cannot be sure, and it is possible I only made that connection because he posted it to this thread.).

SUN

Hi LeMury i'm back again ;-)

Just bought an SB0280 (Audigy2 Platinum eX) with no AC97...

But when i start your superb MX6(GUI) datet 06/02/2005 04:43 or 04/18/05 it consumes up to 60% CPU-Power with all 6 Channels enabled and 4 Channel input incl. Record Out Signal...

If no signal is on the Inputs it uses 20%.

If i disable all 6 Inputs: the CPU use of kxmixer sinks to nearly 0% :-)

Are the Levelmeters so CPU hungry or is there another reason... ???

btw: If i close the MX6-GUI then kxmixer uses also uses nearly 0% (in Task-Manger)

Please Help!

Greetings,
SUN alias DJ-Sunnie

John Lodge

LeMury, Well what was true for i is true for j. Still includes the old ProFX.