ASIO, FL Studio, and signal stength problem.

Maddogg6

Or.... A downloaded DSP config from the kX Archive perhaps?

Tho, changing kX Router haphazardly makes a lot of sense too.
Thats not default for 3545a for sure... when did E. change all the routing?

xenomorph1138

Here http://i42.tinypic.com/9hnv51.jpg is the a full shot of the dsp you are reffering. The setup I used for the test. This one http://i43.tinypic.com/2gw7rmf.jpg is the default as it (3545b) was installed on Vista build 6001 for SB0350. I reinitialized the dsp to be sure. I don't mess with the router. I have'nt got the dsp figured out yet.



Does it?

Russ

Right, and with incompatible configs, who knows what bugs might pop up... and any changes in kX Router are going to effect which pins need to be tested on FxBus, etc.

I am not sure (without digging through old posts) in which version the routing first changed, but he is using wave 2/3, so it is using the new naming scheme (but the config looks like it is still using FxBus 2/3 for kX Synth's, which is not right (in default setup (with XP) anyway)).

OK, we really need someone else who is using Vista to chime in here and let us know if it is the same for them.

(I suppose it is possible that is the default DSP config with Vista (it seems odd that it would be), but if so, it just makes it that much more difficult/confusing for us to try and help Vista users (as it appears to be using a different routing scheme))

BTW: According to this thread: http://www.hardwareheaven.com/3-d-audi...dsp-vista.html
It seems that Wave 2/3 should use FxBus 2/3, as it does with XP, which would seem to indicate that something is screwy with your routing (but it is hard to say for sure)...

I suggest doing a "Reset Global Settings" (from kX Settings menu), and:

1) See if the default DSP config still looks the same as in your picture.
2) Re-test.

Note that resetting should bring settings back to the default install state, so you would have to re-register any 3rd party plugins that you may have installed, and redo your speaker setup, etc.

xenomorph1138

Ok. I reset global. I had the extra peak meters in the dsp at the time and I expected at the very least that the extra meters would not be there after reset but the dsp looked exactly the same. (default + the extra peak meters) So I reinitialized the dsp and it reset to default. Then I deleted "Prolog" and reset global again and it came back to default, minus "Prolog".
I tried this 2 more times. Each time deleting a different module (plugin), then resetting global, getting the same results. Default, minus the plugin that I had deleted. Apparently resetting global settings does nothing for the dsp in this case. Reinitializing the dsp seems to reset it. I also uninstalled and reinstalled 3545b and I get the same default dsp.

Anyway this http://i40.tinypic.com/9t0mqc.jpg is how the default dsp looks in my XP, with 3545b for SB0350. it does look more like yours. Mine still has the "p16v" module though. All the connections are paired also, unlike my Vista dsp.

So I'll post back later. After retest. I have to go over the last few post and see what else I can do.

Russ

Hmm, so it seems that Reset Global Settings is broken for you too (maybe another Vista issue)...

When you reinstalled, did you do a full uninstall first? Personally I would probably uninstall, and then verify that it really removed everything (the kX folder, and registry key (manually delete them if they were not removed)), and then reinstall to be sure that you are getting a clean installation.

In any case, do not drive yourself too crazy since we do not know if Eugene made the default config different with Vista for whatever reasons.

If any other Vista/kX (3545b) users are reading this, please post a screenshot of the default DSP config.

xenomorph1138

Ok. Here http://i41.tinypic.com/50nrwi.jpg and here http://i44.tinypic.com/f50vph.jpg are the results for the tone test with SF/kxasio/01. Ignore the rec meter. I wasn't recording. (Anyway, I don't seem to be able to record with kxasio. The rec/option is greyed out in SF when I select kxasio.) Notice the difference is again 12dB. Took me awhile to figure out how to use the mda plugin in SF. The only other program I might be able to do the test in is Acid Music Studio. I'll check it out tomorrow. This is actually kinda fun...when I'm not pullin my hair out or getting ready to throw my tower through the window. I hope this info helps E.

Note: I did the test with 41khz and 48khz with the same results. I just happened to upload the screenshots of the 41khz test.

Russ

Sorry, I am not really familiar with Sound Forge (I just downloaded the demo to see what you were looking at, etc). You could have just used it's own signal generator (Tools -> Synthesis -> Simple).

As for recording, again the sample rate has to be 48 kHz to record using kX ASIO. With SF closed, open the kX ASIO Control Panel and set sample rate to 48000, then open SF and configure the audio I/O (it doesn't seem to update right when done from within SF).

xenomorph1138

I guess we're not on the same page here. Please except my apology. I'm not a very good communicator. I was'nt trying to record with it. I did'nt mean for the rec meter to be in the pic. I had a feeling it would throw you off. I was just trying to confirm that it did'nt just have the problem (the missing 12 dB) in FL. So I did the test in SF. I know that I know very little if anything about this. So I'll leave it to the experts. Thanks again for all your help. It is very much appreciated. It would be nice if Creative had this kind of support.

Russ

No, I understood what you meant, I was referring to when you said:

The record option would be greyed out if the ASIO Control Panel was set to a 44.1 kHz format.

Maddogg6

For some clarity for the OP...
In kX ASIO control panel - the 'Format' options look something like this:
'10kX 16Bit/48Khz [16+16]'
or
'10kX 16Bit/44.1 Khz [16+0]'.

Noting the '+0' versus the '+16'...
That number is how many ASIO recording channels are available to the ASIO application.
kX ASIO with 44.1 khz is playback capable only - not record capable.
kX ASIO with 48Khz is record capable, 16 ASIO Channels possible, the numbers in the '[ ]' are reminders of how many 'playback + recording' channels are possible..

xenomorph1138

Thanks guys. Actually, I do have the kxasio control panel set to '10kX 16Bit/48Khz [16+16]' and recording bit and sample rate are set to 16/48 but it is still greyed out. Kxasio won't record in 41 or 48 in SF. I don't know for other programs. If you look here http://i40.tinypic.com/xndabc.jpg you can see that it is set at 16Bit/48Khz [16+16]' and that the record option is still greyed out. So, I don't know. I'm pretty sure I have it set right. Anyway, if you like me to do more test, please one or two at a time or I get confused. You helped me alot, so if I can help with Vista test for kx, I will try to do it for you.

Russ

Did you set it to 48 kHz before you opened Sound Forge, or did you do it from within Sound Forge. As I said previously, SF does not seem to update it's I/O options correctly when you change the kX ASIO format from within SF.

i.e.
If I have it set to 44.1 kHz and then open SF, the record option is greyed out as expected. If I then click on Advanced -> Configure, and change the format to 48 kHz, the recording option remains greyed out. However if I set it to 48 kHz (from kX Settings menu) before starting SF, I am then able to select which kX ASIO inputs I want to use for recording.

xenomorph1138

WOW!! You know, I swear that I learn something new everyday on this forum. That's a compliment. I hope you get paid for doin this forum gig. If you don't. You should be. Thanks again. So maybe I can Use the asio4all in FL since I get a good signal with it, and use the kxasio in SF to record. I'll post back tomorrow hopefully with good news.

Russ

Yes, that I what I was thinking, but do not get too excited yet.

Assuming that you changed the sample rate in the kX ASIO Control Panel (even if you did it from within SF), although the recording options would have remained greyed out (and assuming that you did not immediately change it back to 44.1 kHz) the next time you used SF, the recording options should have been enabled (i.e. the idea is just that the sample rate should be set in the ASIO Control Panel before launching SF). I only mention it because I thought that *maybe* you tried changing it to 48 kHz from within SF, and then when it did not make any difference, you set it back to 44.1 kHz, and thus never started SF with the sample rate already set to 48 kHz.

xenomorph1138

*That's correct. I did try to change it within SF. Even when I checked the kxasio CP from the kxmenu/settings it was already set to 16/48. So I dropped the menu down and selected it again (with SF closed). Then opened SF and looked in options/audio and sure enough there it is. Have'nt tried recording with it yet. Later today.

Don't want to get too off topic but is there a way to set kxasio driver to be used globally (don't know if that's the correct term) so that when ever I play and audio file in a media player like WMP or WinAmp, play a movie dvd or cd, cause I'm getting alot of the poping and clicking or maybe stuttering is more accurate. Yea, "stuttering" is more accurate. Even some system sounds get that stuttering at times. I'm not a big game player but this game I play occasionally has that same stuttering in the audio. I guess I'm asking if there is a way to set kx so whenever audio is played, from whatever source, kxasio is the driver that is used? Does that make any sense? I don't know. Or does it have to done from within each program? Or maybe I should start a new thread?

Anyway, you have been a really big help to me and I'll say it again, "Thanks".

xenomorph1138

A month ago I used SF to record examples of audio with latency setting off (crackling and popping), expanded the wave form and took screenshots of the location where the artifacts (if that's the correct term) were. Here are 2 examples http://i39.tinypic.com/2rxtc76.jpg, http://i41.tinypic.com/bfo11l.jpg.

This next pic http://i40.tinypic.com/23i807m.jpg is an example of what I was talking about in my previous post. Instead of spiking I get more like a dropout (stuttering) though they sound very similar. Here is another pic http://i43.tinypic.com/23hm25i.jpg. I'm sure you can tell the difference from the first 2 pics. Yes? Also I noticed the word "stuttering" was use to describe an undesireable audio effect while viewing a link in one of your posts below.

So anyway that is what I was talking about. And the only answer I seem to get is about latency adjustment. I think sometimes when people ask a question on the forum about crackling and popping, what they are actually experiencing a dropout effect and not latency being off.

I'ld like to get your input on that. That is, unless I should start another thread. Anyway I'll drop it for now.

xenomorph1138

Ok, this is it. Asio4all 2/3 in FL at 16/48 and SF with kxasio 16/48. Works perfect. The signal from FL is at FXBus_4/5 in dsp. That's where i'm getting a signal from, anyway. FXBus_2/3 go to xrouting Synth_L/R, 13/14. I did a test record and it works great! And yes I did the tone test it. See pic http://i42.tinypic.com/muennl.jpg. Same going in and same goin out. I am a happy camper!

Russ

No, applications have to support ASIO in order to use it. You would have to check each application to see if it supports it, and configure each application separately.

As for your test results, looks good, I am glad that you have a workaround.
...and it confirms that the level issue is only with kX ASIO into the DSP.

As for the noise issues (with kX Wave devices), you had another thread about that, and I really cannot think of anything else that I did not say in that thread (such things can be hard to diagnose in the first place, and you have an OS that I have never used, and a beta driver, and the 3 GB's of RAM thing, etc)...

xenomorph1138

Ok. That should do it then. I know I said this before. I really appreciate all your help and when I come up with any info I think might be of value reguarding Kx and Vista I will be sure to post it. I was going to mention that I replied to one of the links that you posted for me to view but I see you allready know that. Thanks again.

Russ

OK, you might want to post a Bug Report about ASIO input (to DSP) being -12 dB too low, and Reset Global Settings not working correctly, but personally I would probably wait for other Vista users to confirm the issues.

xenomorph1138

That works for me.