Front Panel Mic not working with Sound Blaster Z

[Tisdan]

Hello everyone,

today I got my new Soundcard, a Soundblaster Zx and I must say that I really love the quality.
However, I have a problem and I don't know how to fix it.

My PC is a custom build. Case is a Bitfenix Ghost, Mainboard Gigabyte 970A-UD3.

I installed the Soundcard in my PC and disabled the onboard sound.
Driver were installed and updated after that. Sound is working.
My case has a connector labeled with "HD-Audio" wich i plugged in into my soundcard.
Sound is working in Headphones but the mic is not listed in my recording devices.

This is a list of stuff that I have done already:
-> Updated Drivers
-> Re-enabled Onboardsound (Disabled it after that)
-> Ordered a new Soundcard, same Problem

So if you are able to help me, please

 

[fireberd]

Exactly what model SoundBlaster Z sound card do you have? Is it the Audigy 2 ZX?

Does it work if you plug the microphone into the rear Mic jack on the sound card?

 

[Tisdan]

Model is Creative Sound Blaster Zx (SB 1500)
Mic in Rear works

 

[fireberd]

Did the mic work with the internal audio? and now does not work with the SoundBlaster? If that is the case, check the front panel connector to verify it is correctly installed on the SoundBlaster.

If it has never worked before, then either the cable or the front panel assembly in the case is suspect.

 

[Tisdan]

Front Panel connector worked before with my Via Onboard card.
Now, with my Soundblaster Z, only the headphone jack works.

I will try to disable my Soundblaster, connect my front panel to my onboard card and see if there's a defect somewhere.

 

[joebots]

I am having the exact same problem with a Sound Blaster Z which I installed yesterday. I know the front mic input jack worked with both my on-board VIA sound, and a Creative Audigy Fx which I had. The front speaker jack works just fine.

Joe

 

[fireberd]

Hmm. Sounds like a problem with the SB Z card, either some internal setup configuration issue or the front panel connector since two have the exact same problem.

Since two are having the same problem, contacting Creative support would be my suggestion.

 

[Tisdan]

Well, I had the Soundblaster Z and now, the Sounblaster Zx. Both had the same Problem.

 

[fireberd]

The front panel mic jack works with the internal motherboard sound and the mic works in the rear panel of the SoundBlaster. That eliminates the case wiring and front panel jack and puts it back to the SoundBlaster, either a driver/setup issue internal to the sound card or how the front panel connector on the SoundBlaster is wired. Either issue, Creative needs to be contacted since two (reported) have the same problem.

 

[NoN]

Hi there,

I've got the Sound Blaster Z (Red leds - SB1500) and i've got my microphone to work both front and rear plugs.

Just one tip maybe...when you plug from back to front panel and versa , Sound Blaster engine doesn't switch the mic automatically. You have to switch it manually from rear mic to front mic in the "crystal voice" panel.

That's how i got it to work.

PS: Better disable HD audio panel in bios settings, but seems obvious if you do plug the case HD Audio cable onto the Pci-e card..

 

[joebots]

Just one tip maybe...when you plug from back to front panel and versa , Sound Blaster engine doesn't switch the mic automatically. You have to switch it manually from rear mic to front mic in the "crystal voice" panel.

I tried this but I could never get front mic to appear in the crystal voice panel no matter what I did, or in the Windows 7 recording properties. I looked for hidden or disabled recording devices as well. Nada.

PS: Better disable HD audio panel in bios settings, but seems obvious if you do plug the case HD Audio cable onto the Pci-e card..

I did this even before I installed the card.

There were other peculiar things going on, too. Sometimes coming out of sleep mode Windows 7 would recognize the card as a Recon3D PCIe. I'd have to reboot when this happened to get sound back. I also got a few Blue Screens, which never happened before. It could be just be compatibility problems with my motherboard, the OS, or some kind of driver issue. I gave up trying to get it working and returned it for a refund. It's a shame because it put out really nice sound.

Thanks for your reply.

 

[NoN]

Just one tip maybe...when you plug from back to front panel and versa , Sound Blaster engine doesn't switch the mic automatically. You have to switch it manually from rear mic to front mic in the "crystal voice" panel.

I tried this but I could never get front mic to appear in the crystal voice panel no matter what I did, or in the Windows 7 recording properties. I looked for hidden or disabled recording devices as well. Nada.

PS: Better disable HD audio panel in bios settings, but seems obvious if you do plug the case HD Audio cable onto the Pci-e card..

I did this even before I installed the card.

There were other peculiar things going on, too. Sometimes coming out of sleep mode Windows 7 would recognize the card as a Recon3D PCIe. I'd have to reboot when this happened to get sound back. I also got a few Blue Screens, which never happened before. It could be just be compatibility problems with my motherboard, the OS, or some kind of driver issue. I gave up trying to get it working and returned it for a refund. It's a shame because it put out really nice sound.

Thanks for your reply.

Its a shame you couldn't make it on your Motherboard and system based OS.

The Sound Blaster Z just working like a charm on mine with latest drivers. No cracks & poppy noises coming out my sound system 5.1 (only one pop coming from a light commutator in the house, badly isolated that i can hear out the speakers).

Otherwise great sound for watching movies, musics, and fear myself on some games.

 

[robort1138]

I had two computers both running Sound Blaster2 ZS (SB0350), one was the platinum. Both setups worked fine with XP but forced out of XP (thanks Microsoft) went with Win7. Neither sound card was functional using either installation disc and drivers that came with them. Great sound cards but a generation before Win7 so the drivers just don't work.
Googling, one discovers the Creative Labs site offers updated driver downloads. Problem is, Creative Labs at this point sidesteps escaping all responsibility, because these are third party drivers. To download them you must navigate through the trial licensing agreement (Ireland) which mentions possible unspecified charges for using this software may (or may not) follow in the (unspecified) future. Furthermore, the agreement warns that avoiding adhering to the agreement guidelines could result with incurring "serious damage to your computer system." I wanted my sound systems working so I tried going along with it. Upon installing the software my speakers now worked great, but I noticed some of my folders were not functioning normally. I decided to uninstall and delete some folders the result of which was "NOT ALLOWED." I now get the occasional BSOD, especially recovering from sleep mode. These third party driver downloads corrupted my clean install. I haven't resolved this yet, although I have begun researching the BSOD issue.
Initially, it seemed I might do well to perform another clean install and get rid of the Sound Blaster products.
I read a PROFESSIONAL comparison review and subsequently purchased a ASUS Xonar Essence ST sound card with an ASUS H6 7.1 extension card to go with it. Then I discovered via USER reviews that they were having all kinds of problems with the drivers ASUS provides for Windows 7.
So many problems trying to use a broad range of peripherals (graphics, sound, etc.) with Windows 7.
As operating systems are released relatively frequently, apparently no one wants to invest time and money writing software for older products (they of course instead prefer to sell you new stuff) and the OS will be here today and gone tomorrow.
I will, little doubt, eventually do a new clean install but first I want to see where researching the BSOD leads. I would suggest (to be safe) use only current products that list on packaging they're compatible for your configuration. Don't totally rely on "after the fact" contrived driver updates that may not function.