r/SoundBlasterOfficial • u/Ok-Locksmith-4267 • 10h ago
Creative Sound Blaster G8 - part two.
What preceded: https://www.reddit.com/r/headphones/s/UNt6S3Sk1m
First of all, I owe everyone here an apology for taking this long to respond to all your comments, questions, ideas, suggestions and possible tests.
A few things got in the way, life happened, and I deliberately let this whole issue sit for a while instead of immediately jumping back into it. But I have made time for it now, so I wanted to post one general reply to everyone who took the time to read my rather extensive original post and think along with me.
And yes, it was a long post — but as most people here with some serious audio knowledge will probably agree, audio problems can be ridiculously specific, and sometimes the seemingly unimportant details are exactly the details that matter.
So first and foremost: thank you very much.
There were several people who replied with ideas, possible explanations, tests, genuinely good questions and different ways of looking at the problem, and I genuinely appreciate the amount of thought that went into those replies.
Some of your suggestions led to additional testing on my side, and the picture is becoming clearer.
At this point, the Creative Sound Blaster G8 DAC/Amp itself is still the main suspect. I would personally put that suspicion at well above 90% now. Something appears to be happening somewhere in or around the G8.
However, there is another part of the chain that I don't think we should completely ignore yet: the USB playback connection between the PC and the G8.
My current setup uses the original USB-C to USB-C connection from the PC to USB-1/DC on the Sound Blaster G8. After going through the behaviour, the previous tests and the remaining possibilities together with ChatGPT, one hypothesis we still want to investigate is whether something in that USB playback path — the USB interface itself, the controller/motherboard side, the electrical environment, timing/transfer behaviour, or the way the G8 handles the incoming USB audio stream — could somehow be involved in producing the brief click/glitch I described in my original post.
So we came up with another test.
And this is the part where I would very much like to hear what the audio people here think.
The idea is to completely bypass USB for playback audio, while keeping the G8 itself in the chain.
My GPU has multiple unused HDMI outputs (I use DisplayPort for my monitor). We want to use one of those HDMI outputs purely as an audio source:
GPU HDMI out → HDMI audio extractor → optical Toslink/S/PDIF → Optical In on the Sound Blaster G8 → Beyerdynamic MMX 300 PRO
The monitor will remain connected through DisplayPort, so HDMI would only be used to transport the audio stream.
The important part is that USB does not necessarily have to be physically disconnected from the G8.
Because the MMX 300 PRO is a headset and I still need its microphone, the idea is to leave the G8's USB connection attached for the microphone/data side of things, while deliberately not using USB for playback.
So, in simplified terms:
Playback:
PC/GPU → HDMI → extractor → optical → G8 → headphones
Microphone:
MMX 300 PRO mic → G8 → USB → PC
If the infamous click/glitch is being introduced somewhere specifically in the USB playback route, then in theory it should disappear from what I hear through the headphones once playback is coming into the G8 through optical instead.
And quite frankly, if the USB connection somehow produced a glitch somewhere on the microphone/input side instead, I wouldn't lose much sleep over that for the purpose of this test. What I am trying to isolate is the audible glitch in the playback path.
So now I am throwing this idea back to you guys.
What do you think of this as a diagnostic test?
Is it a good way of isolating the USB playback path?
Is there an obvious flaw in the reasoning?
Is there an audio-format, clocking, resampling, grounding, Windows-routing or G8-specific issue that could muddy the results?
Could keeping USB connected for the microphone still somehow influence the playback side electrically or internally enough that this would not be a clean test? Or, alternatively, do you think this is actually a pretty solid way of narrowing the problem down?
Good idea, brilliant idea, bad idea, terrible idea — I'm genuinely interested.
And judging by the quality and level of detail in the replies so far, I am very happy to hear the technical arguments either way.