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

Lex Nahumury

Ok, no problem.

Lex Nahumury

Added on request;

- Noise Gate Stereo
- Automation noise gates fixed ( @ReWired. plz check)

ProFx v3.08 compiled for 3534..!!
http://members.home.nl/nahutec/ProFx/profx3x_3534.htm

/Lex.

PS: THIS RELEASE WILL NOT WORK ON ANY 3538..!

ReWired

for now all seems pretty fine
thanx!

Russ

I did some quick testing with v3.08, and so far so good (no graphics problems or anything like that with WinME). The only issues are with the card specific stuff with kxlt.

Lex Nahumury

You mean;
the absence of newer card model support in 3534f?

Russ

Yes, and no.
Aside from the generic 3534f support stuff, the rear channel thing would have to be handled specifically for my card model in kxlt (probably in future kX versions as well, if Eugene removes the driver translation (because it kills the digital rear) and instead updates epilog's code.).

Lex Nahumury

I see.
Well, I guess I could write a seperate 'hardcoded' kxlt for your card type.
Perhaps with some user switch depending on wether or not the card type (codec) can be/is recognized by kX driver.
But IIRC you already did something similair right?

Russ

I am not positive, but I do not think that any models similair to mine, have a drive bay option, and if that is the case, then the drive bay headphone output is not necessary for these cards, so I was thinking that you could replace those with the analog rear output, and re-label the (current) analog rear output as digital rear (obviously detecting the card when the plugin loads, etc. to do it). Or something similair... In any case, it is entirely up to you how compatible you want kxlt to be, with different card models, etc. I think it should be fairly easy to do, once you know the specific property to check, to determine which cards need the special handling. I do have my own working plugins for my card, and eventually Eugene will probably update epilog's code, but most likely kxlt still will not work completely with these cards. Of course I understand if you do not want get into detecting different card models, etc, and maybe at some point Eugene will add some other mechanism for plugin developers, to avoid having to do such things (maybe some special variables that auto-translate to the correct outputs for the card model at plugin load time (based on what the driver detects), etc. (Of course if such a thing was implemented, I would still want the option of specifying the outputs directly, for testing purposes, as when the driver does to much on it's own, it can make testing more difficult)). In any case, it is probably not needed for 3534f, and it is probably a good idea to wait and see what Eugene does in future releases before making any changes.

ROBSCIX

@Lex, you have since abandoned the Black theme you had on you other plugs a while back? I was curious because they looked very cool and perfessional. Any thoughts on adding other plugins to the nice skinned PRFX line-up. Your work is very much appreciated.

Russ

I guess I will be the first to request ProFX v3.05 for 3538k

Doug W

I will second Russ's motion for ProFX for 3538k. We are a needy bunch.

laserbeak

version k?? wtf?? when did this happen?? :P

dj_stick

some time yesterday

__________________

laserbeak

cool had no idea...

faustus69

Another petition for ProFx for 3538k. We need you Lex

caballo

Lex, another petition for ProFx for 3538k, or better for 3539 in the future http://www.hardwareheaven.com/images/s...big%20grin.gif

Edit: appears a link, not an emoticon ????

wstanley

Hello

I've just installed 3538 on a 0090 Audigy card. Works fine. But I'm unclear how to install the new ProFX Plug-ins. I downloaded ProFX305.zip, unzipped it and moved the unzipped ProFX305.kxl to the folder containing my kx installation. (C;\Program Files|kX Audio Driver\3538. When I right click on ProFX305.kxl and select Register, I get an "Error: invalid plugin library" I then renamed the file kxfxlib.kxl to kxfxlib.kxl.bak Same error when I attempt to Register the Profx file.This is my first attempt at installing and registering plugins. What am I doing wrong?

Walt Stanley

Lex Nahumury

That version is for kX driver version 3538j.
(i guess you use the latest k version of the driver)

wstanley

Thanks--You're right. Guess I'll have to wair for the next relese.


Walt

ROBSCIX

We had discussed color and such before LEX, I am not sure if your doing a verion for the 3539 -or what ever version will be released as stable. have you decided on a color? also is it hard to put in a color dialog? Ijust wanted to say that I remember your black styled plugins and mab they looked great..well all your plug look great no matter the color but I really liked the black ones I thought they looked very slick and professional. I just though it would be nice if ALL the plugin in KX were skinned but I guess that's abig task and the important thing is how they sound and not how they look just my opinion though.

caballo

I am installed succesfully the 8 plugins in 3538k.

But, Where is it ?? How access to the new plugins ??

caballo

In DSP kX

Russ

I think you probably did not install them, as they are not currently compatible with 3538k. Installing a plugin requires registering the plugin (by double clicking on the file), and if you had tried to register these plugins in (3538k) you would get an error.

There is however, a version that is bundled with the kX 3538k, but it is an older version that has some bugs, and does not include many of the features of the newer ProFX versions.

ROBSCIX

I just installed 3538K and the version that is supplied of ProFX has the weird black/grpahics missing look to it. Now MAx released his UFX for 3538K..now if we could get the ProFX for 3538K ALL would be grand!!. IT seems like a never ending thing for me when I get one I lose the other But I love BOTH..I love ProFX for us with my External gear and Ilve Max Ufx for use with everything...Msaybe I can get UFX to intall on a earlier version..probably not....PLEASE LEX can you do ProFX for 3538K and make 3538K a well rounded release where people can have the best of both worlds. ..

faustus69

Any news about Lex?

nakamichi

I'd rather have updated ProFX for 3538L.It's a whole lot better than 3538K.
The included ProFX in 3538L are very old and unusable,especially the very buggy AC97 plugin (the predecessor to ADC) and the old,simple MX6.

And where's MX8? Shouldn't this also be included in the ProFX pack?

thomasabarnes

MX8 is included with the ProFX pack for 3534f. I guess it's safe to say that Lex included MX8 with 3534f because he uses that driver version. Lex did say something to the effect that MX8 is still in experimental stage. I'm sure he will include it in 3538 final.

Though i don't want to put words in the mouth of Eugene or Lex, I think it may also be safe to say that 3538l is an attempt by Eugene to obtain an ASIO driver performance equal to that of 3534f or better ASIO driver performance in the 3538 final version.

kX users may want to check out the 3538l ASIO Performance thread in the General discussion forum, and download and test the 3538l driver and post results as a beta tester? Unfortunately, I'm not in a position to test it out my self at this time. But it would be great to have the software and driver enhancements included in the newer kX driver versions with an ASIO performance better or equal to that of 3534f!

__________________

May a song always touch you in a positive way.
Sonar 8.5.3 PE, Windows 7 Pro 64Bit, MOTU UltraLite MK3, 150 GB HDD, 250 GB HDD, 1 TB HDD 7200 rpm,
My Music Production: Top 40, Contemporary Christian, Pop/Rock, Decent Rap, Inspirationals, and Children Songs

Lex Nahumury

ProFx updated.

Russ

Thanks Lex

It would be cool if at some point you could add support for the analog rear channels of my card, to kxlt.

It is done in epilog, in 3538k/L, by adding an extra instruction, and sending the same output to both 0x8/0x9 and 0xd/0xe (kX activates/mutes the appropriate output depending on the state of the DOO flag). If you look in the SDK, you will see the flag 'is_bad_sb22x' that can be used to detect cards like mine (it is used in the 'da_epilog.cpp' source code).

It would not matter to me if you were to do it like epilog does, or if you used seperate outputs for analog/digital rear, it would just be cool if they both worked.

-Russ

bzdang

Thanks Lex, your work is appreciated. Best wishes.