Question Sound Blaster AE7 and Realtek both no longer recognize microphone input from a known good microphone

I'm at my wits end here: I have a Creative Soundblaster AE7 I've been using for quite some time now, with no problems. Me and my buddies got online for the first time in months today, and for whatever reason my microphone no longer picks up any audio. OS is Windows 11 x64.

What I've done:

  • Used two separate audio cables; one is a combined headset/mic and the other splits into Microphone (Pink) and Speaker (Green) TRS jacks
    • The latter was the setup I was using for years without issue
  • Confirmed both the Microphone and cabling work via plugging the pink TRS connector into a smartphone and calling
  • Tested with the onboard Realtek device via front panel
  • Updated both Soundblaster drivers and Control Panel to latest versions
  • Updated to Windows 11 2H22
  • Ensured the correct device is selected within Windows
  • Confirmed that "Microphone" is set in the Multipurpose select
Everything is plugged into the soundcard correctly as shown here:

parts1.jpg


Microphone input is at the far end of the card, headphone output is next to it. I'm not using the ACM.

I'm at my wits end at this point; I've never had a problem like this and have ruled out basically everything except Windows itself. And as I haven't tested the microphone in Windows in months I couldn't even tell you when this first happened.
 
What headset and mic are they? Not sure if it's software, could test a fresh Windows install on another drive if you have one spare.

If by chance headset or standalone mic has an on/off switch you forgot about? Not sure headsets have a on/off button for the mic but standalone PC mic i got did and didn't pay attention, that little button sent me on a goose chase.
 
Its a Sennheiser GSP 500, which had the microphone work previously without issue. It only mutes when the Microphone is pulled up, and as I noted above I confirmed it works via my smartphone, so the Microphone itself isn't defective and the mic cable is known good.

Also forgot to mention that the microphone has app permissions, so that shouldn't be blocking it either.
 
Something is screwy here.

As a last gasp, I tried going into the rear motherboard microphone input port. Windows sees it as a mic input and makes it the default. No dice.

...Until I go to the Sound Blaster control panel, and with the motherboard microphone input still as the system default, enabled the Sound Blaster Control Panels "Listen to this device", and I can hear the audio being played back fine.

Now it gets "MORE" interesting: You would now think I just use the motherboard mic input for everything right? NOPE. In Xbox Party Chat, with the motherboard mic input still as the default, I have to now select to use the Soundcards Mic Input port to get any audio to come through, even though nothing is physically connected to that input. Even then, the audio levels are very low.

I *think* the way everything is configured right now:
Sound Blaster Microphone Input: Default Communication Device
Realtek Microphone Input: Default Audio Input

Then selecting the Sound Blaster input somehow works?

The hell?

I'm going to keep screwing around a bit tonight, but this is looking more and more like Windows has totally screwed something up. At least now I have an easy way to swap which input im physically connected to (yay for extra extension cables!) for testing.

EDIT

I'm using the ACM now and what I *think* is happening is both the audio and voice are going over the same connection, like a single-plug connector would. I physically have my microphone input cord disconnected from everything and the microphone works over that single connection.

EDIT2

Sorry about all the edits: I've confirmed my above suspicion is correct: With *only* the Green plug inserted into the ACM module, which is connected to both the Headphone Output and Microphone Input port of the soundcard, I get Microphone input. When I insert the Microphone plug into the ACM, no Audio.

The only thing I can think of is the microphone input port on the Soundcard has outright failed, as that's the only component I can not confirm actually works. The ACM is probably smart enough to handle microphone input via one plug if that is how everything is plugged in.

*shrug*
 
Last edited:
Ok, final post of the night, would be interesting to hear if anyone has any thoughts:

Right now, this is the connection chain that works:

GSP 500's -> Audio cable that ends in a TRRS connector (one plug for both Headphones and Microphone) -> Sound Blaster ACM module -> Splits into Headphone Output and Microphone Input -> Soundcard

This *works* as you would expect for a single-plug TRRS connector: The ACP module splits the incoming audio signal and both go to the soundcard on their merry way. If I physically disconnect the Microphone Input connection between the ACP and the Soundcard, I get no microphone audio (as you'd expect; nothing is connected). This proves the microphone input port on the soundcard is provably functional.


These connection chains do *not* work:

GSP 500's -> Audio cable that ends in a split TRS connector (two plugs; one each for Headphones and Microphone) -> Sound Blaster ACM module -> Splits into Headphone Output and Microphone Input -> Soundcard

GSP 500's -> Audio cable that ends in a split TRS connector (two plugs; one each for Headphones and Microphone) -> Soundcard

The ACM module doesn't matter here; using the split TRS connector results in no Microphone audio, even if I go directly into the soundcard.


This would lead me to suspect that the Microphone Input portion of the TRS cable is dead, right? Except I tested that by connecting that same TRS Microphone Input end of the cable into my phone and confirmed it functionally works. So both ends of this TRS cable are provably working.


Which begs the question: What in gods name is going on here? The soundcard is provably good. The ACP is provably good. The cable is provably good. The microphone/headset is provably good. Yet TRRS into the ACP works, but a split TRS connection doesn't even though the microphone input end of that cable has been proven to work?

I'm utterly mystified. The only thing I can think of is there's a configuration problem within Creatives software (shocking; it *is* Creative we're talking about here) which is causing a split TRS to not work...but then why does it work coming out of the ACP?

*screams*

I'm going to bed. I'd love to hear what any of you have to say on this.
 
Looks good, and the ACP is now plugged in and working with the TRRS plug, so the connector itself (on the soundcard end) isn't the issue.

I'm usually good at diagnosing nonsense like this, but so far as I can tell literally *everything* works individually.

EDIT

Just for reference, the ACP module:

convenience_diag.jpg


Right now, the ACP is plugged into the soundcard via its built in (and non-replicable) cable which I assume is a split-ended TRS connector. For the moment, I have a single TRRS cable going between my Headset and the ACP.

The question is why the split-ended TRS cable that goes between my headset and the ACP doesn't want to work.

I'm leaning towards just getting a replacement split-ended cable for the headset; it's more likely then not the cable, even though all indications are its working.
 
Last one I promise for real this time:

This is the cable that is the issue:

418F1-3dVbL._SY445_SX342_QL70_FMwebp_.jpg

Nothing special; one end goes into the headset, then splits into Headphone/Microphone plugs. The Headphone plug appears to work in all cases. The microphone plug works when connected to a phone, but not when connected to the Soundcard or ACP.

Here's the epiphany I just had: When I connect the Headphone (green) plug into the ACP *by itself*, I get both Audio Output and Microphone Input. That...shouldn't be happening as the microphone input should be split off to the other connector. So I'm leaning heavily towards the cable being damaged and needing a replacement (one is now on order).

If anyone has any other ideas to try in the meantime, I'm all ears. Spent four hours diagnosing this. :/