MXL 990 Setup Questions

  • Thread starter Thread starter Ortizme
  • Start date Start date
Unless there's some kind of software breakthrough, I would try to get hold of a mic to test out - Preferably a dynamic.
Either that or find someone with a mixer/interface who'll test you mxl for you.

Also, bring up the windows meter (from your first pic).
Now turn phantom power off and let it drain for at least a minute.

Now, whilst watching the meter, turn phantom on. Did you see a spike on the meter?
If so, that would rule out a software/driver issue and probably indicate a faulty mic.
 
arcaxis said:
Volume control panel have any sliders down or inputs muted. Possibly that interface may not use a mic input. Then again I'm not sure it would go there or not.This is WinXP.
Click to expand...

This is the most its giving me as far as sliders go.
sound10.webp

@steenamaroo
I tried that and got no spike

@Mr. Clean
The USB mic is selected in audacity
 
At this stage I'd be thinking the unit isn't putting out phantom power.
Do you have access to another mic through a friend or anything?

Perhaps you know someone, with a multimeter, who could check for voltage at the interface input?
 
Steenamaroo said:
At this stage I'd be thinking the unit isn't putting out phantom power.
Do you have access to another mic through a friend or anything?

Perhaps you know someone, with a multimeter, who could check for voltage at the interface input?
Click to expand...

Yes I think I have a mic with an XLR connection in my garage from an old video camera. I'll look for it and get back to you.

Mr Clean said:
Silly question but have you tried another USB port?
Click to expand...

Yes I've tried two so far. Should I check the rest in the back?
 
Ok well it turns out I had an Audio Technica MB 4k condenser mic lying around with my canon camcorder. Tested it with the nady and got only staticy noise on audacity

Also tried the other USB ports to no avail
 
Steenamaroo said:
Unless there's some kind of software breakthrough, I would try to get hold of a mic to test out - Preferably a dynamic.
Either that or find someone with a mixer/interface who'll test you mxl for you.

Also, bring up the windows meter (from your first pic).
Now turn phantom power off and let it drain for at least a minute.

Now, whilst watching the meter, turn phantom on. Did you see a spike on the meter?
If so, that would rule out a software/driver issue and probably indicate a faulty mic.
Click to expand...

I tried it again but this time disconnected the mic and waited longer and when I turned the phantom power back on I did see a spike lasting ~2 seconds
 
Ortiz,
I have the SMPS-USB and used it with Audacity, in Win XP Pro. One question: have you enabled the mic in the Sound Properties/ Recording setting for your sound card in W7?
Connect the USB Nady and mic. No phantom power yet.
In W7, Right click on the Speakers icon in your Notification Area and select Recording Devices.
Next, in the dialogue box that opens, right click and select the option Show Disabled Devices.
Select the recording device/s and Enable it.
Open Audacity to see if it sees the recording device, then phantom power it up. Check for pops in a track or recorded signal. Also try WaveOut, instead of the MME.
Crosses fingers.
Dale
 
Last edited:
And here I am trying to figure out windows 8 :facepalm:

~BE~
CALM
 
Ortizme said:
I tried it again but this time disconnected the mic and waited longer and when I turned the phantom power back on I did see a spike lasting ~2 seconds
Click to expand...

Ok, don't change anything else in your software. You wouldn't see that spike on the meter unless the interface was working.
I suspect your mic is faulty.
 
arcaxis said:
itself.
3. Adjust headphone level using volume control on the USH-2S microphone[/I]
Click to expand...

Is this crucial? I saw several references online saying "suitable for *** series microphones".

Could this unit rely on a Nady mic with built in volume control or something daft?
 
None of these mic options seem to work and I have been going under the assumption that the Microphone (4-USB Microphone) is the one representing my MXL

sound11.webp

also I am using an old USB B to USB A cable that I found on my printer to hook the nady up to my computer. Could that be a problem? It has the right connections and everything but maybe its outdated and doesn't have the right drivers.

This is the kind of connector that goes into the Nady
usb6.webp
The one into the computer is standard USB
 
If he sees a phantom spike in his windows meter, surely the driver setup and device choice is ok, no?
Not necessarily within his daw, sure, but he doesn't get proper audio input right at the windows mixer/meter.

Not arguing..Just guessing.
 
A couple months ago I purchased this Behringer: XENYX 302USB to use as my pre amp and audio interface, but it didn't supply the 48v of phantom power my mic needed so I returned it. It required drivers that I'm pretty sure I uninstalled. Could having hooked the MXL up to a pre amp with the wrong power output have damaged the microphone?
 
I know it's practically up to being "generic" advice but I'd try downloading ASIO4ALL to avoid using the Nady drivers and see if that will recognise the mic and pass it onto Audacity.
 
Bobbsy said:
I know it's practically up to being "generic" advice but I'd try downloading ASIO4ALL to avoid using the Nady drivers and see if that will recognise the mic and pass it onto Audacity.
Click to expand...

+1 to that. More than worth a try.
 
The first thing I would have done is try the mic on some other device I knew worked with other condenser mics.

The second thing I would have done is try a different condenser that I knew worked on other devices on the Nady, which you eventually got around to doing.

Third thing I would have done is try different cables. I'm assuming you're using an XLR-XLR cable. Phantom typically won't be present at the 1/4" line or instrument input if there is one.

If the MXL and your other condenser work on other devices but neither works on the Nady then it's the Nady.
 
Unfortunately I don't have other devices at my disposal to test with and even worse, my monitor has crapped out and I can't use my PC at the moment. So for a while I will have to put my trouble shooting on hold. Thanks for all of the help already guys I really appreciate it.
 
You must log in or register to reply here.
Back
Top