F5F Stay Refreshed Hardware Desktop Problem with sound quality on motherboard audio connections

Problem with sound quality on motherboard audio connections

Problem with sound quality on motherboard audio connections

C
CriticalFrost
Member
61
04-28-2020, 02:09 PM
#1
The ASUS ROG STRIX B550-F claims 32-bit/192kHz audio, yet Windows reports a maximum of 24-bit/192kHz. This works for me, but I’ve noticed inconsistencies when using the Wiim Ultra—its output shows 16-bit/192kHz even though Windows is set to 24-bit/192kHz. I’m connected via optical out, and updating the BIOS didn’t help.
C
CriticalFrost
04-28-2020, 02:09 PM #1

The ASUS ROG STRIX B550-F claims 32-bit/192kHz audio, yet Windows reports a maximum of 24-bit/192kHz. This works for me, but I’ve noticed inconsistencies when using the Wiim Ultra—its output shows 16-bit/192kHz even though Windows is set to 24-bit/192kHz. I’m connected via optical out, and updating the BIOS didn’t help.

O
Olewww123
Senior Member
255
05-05-2020, 10:04 PM
#2
That "*" indicates missing or pending information. Please confirm if all drivers are available.
O
Olewww123
05-05-2020, 10:04 PM #2

That "*" indicates missing or pending information. Please confirm if all drivers are available.

A
Aydenman81
Member
139
05-06-2020, 02:03 AM
#3
If your audio inputs aren't at 96kHz or 192kHz initially, then adjusting output settings won't help much. Your games will still use 44.1 kHz or 48kHz, YouTube follows suit... It's conceivable that the Windows mixer notices all inputs are 16-bit and combines them, adding a null byte to fill the 16-bit space, turning it into a 24-bit signal where the third byte becomes padding. Perhaps your Wiim Ultra identifies this padding and provides the actual usable data—just 16 bits.
A
Aydenman81
05-06-2020, 02:03 AM #3

If your audio inputs aren't at 96kHz or 192kHz initially, then adjusting output settings won't help much. Your games will still use 44.1 kHz or 48kHz, YouTube follows suit... It's conceivable that the Windows mixer notices all inputs are 16-bit and combines them, adding a null byte to fill the 16-bit space, turning it into a 24-bit signal where the third byte becomes padding. Perhaps your Wiim Ultra identifies this padding and provides the actual usable data—just 16 bits.

M
Minerox13
Junior Member
12
05-06-2020, 03:28 AM
#4
The specification page and manual cite the S1220A codac for 7.1 channel audio. Considering this, it seems the optical connection isn't directly connected to this information.
M
Minerox13
05-06-2020, 03:28 AM #4

The specification page and manual cite the S1220A codac for 7.1 channel audio. Considering this, it seems the optical connection isn't directly connected to this information.

Y
YoungJJ7
Junior Member
39
05-07-2020, 06:20 PM
#5
I'm working with a 24/192 audio file and Windows configured identically.
Y
YoungJJ7
05-07-2020, 06:20 PM #5

I'm working with a 24/192 audio file and Windows configured identically.

V
vikkiii
Member
182
05-22-2020, 09:07 AM
#6
It seems the system isn’t recognizing a 32-bit architecture, likely because that option isn’t available. The 16-bit version appears to be the only one being shown. You might want to check the source for any guidance on what’s actually supported.
V
vikkiii
05-22-2020, 09:07 AM #6

It seems the system isn’t recognizing a 32-bit architecture, likely because that option isn’t available. The 16-bit version appears to be the only one being shown. You might want to check the source for any guidance on what’s actually supported.

S
SaySaeqo
Member
139
05-22-2020, 10:55 AM
#7
I don’t possess any 32 files, and it’s unlikely I’d notice the distinction between 24 and 32 on my system. What matters most is that I’m unable to hear the difference at all.
S
SaySaeqo
05-22-2020, 10:55 AM #7

I don’t possess any 32 files, and it’s unlikely I’d notice the distinction between 24 and 32 on my system. What matters most is that I’m unable to hear the difference at all.