• Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.

What sample rate and bit depth should i use ???

Joined
Jun 3, 2018
Messages
911 (0.42/day)
Location
Al Balqa', Jordan
Processor AMD Ryzen 5 2600 (Covered with Cooler Master MasterGel Pro)
Motherboard ASRock B450 Steel Legend, BIOS Version: 8.01 [Beta]
Cooling Cooler Master MasterLiquid ML120L V2 RGB, 5x Galax Vortex Wind-02 (3xFront Intake, 2x Top exhaust)
Memory Kingston FURY Beast RGB 3600 MT/s 32 GB (8 GB x4), (KF436C17BBA/8)
Video Card(s) Palit GeForce GTX 1660 Ti Dual OC
Storage Kingston NV2 1 TB
Display(s) MSI PRO M251 (HDMI), Running @104 Hz
Case Cooler Master MasterBox MB520
Audio Device(s) HP H360G USB
Power Supply Cooler Master MWE 550 80+ White
Mouse HP G200 Black
Keyboard Redragon MITRA K551-1 RGB
Software Windows 11 Home
Hello guys , so today i found something in speakers properties in the advanced tab called default format , but i really got confused about which one should i use , so help me guys about choosing a format , all what i care about is the BASS and the clear sound , u can find my sound system in the system specs.
 
Joined
Oct 2, 2004
Messages
13,791 (1.93/day)
As high as supported by the audio chip DSP unit. Some support 16bit 48kHz, some 24bit 96kHz, my AE-5 supports 32bit 96kHz. There is a catch though. My soundcard supports 32bit 384kHz, but only as passthrough, so the audio basically goes straight through the chip directly to speakers. If I want DSP to process them, I need to use 32bit 96kHz.

If your specs are correct, I'd say 16bit 48kHz is what you'll probably be able to use with your system (assuming you're using onboard audio).
 

FordGT90Concept

"I go fast!1!11!1!"
Joined
Oct 13, 2008
Messages
26,259 (4.63/day)
Location
IA, USA
System Name BY-2021
Processor AMD Ryzen 7 5800X (65w eco profile)
Motherboard MSI B550 Gaming Plus
Cooling Scythe Mugen (rev 5)
Memory 2 x Kingston HyperX DDR4-3200 32 GiB
Video Card(s) AMD Radeon RX 7900 XT
Storage Samsung 980 Pro, Seagate Exos X20 TB 7200 RPM
Display(s) Nixeus NX-EDG274K (3840x2160@144 DP) + Samsung SyncMaster 906BW (1440x900@60 HDMI-DVI)
Case Coolermaster HAF 932 w/ USB 3.0 5.25" bay + USB 3.2 (A+C) 3.5" bay
Audio Device(s) Realtek ALC1150, Micca OriGen+
Power Supply Enermax Platimax 850w
Mouse Nixeus REVEL-X
Keyboard Tesoro Excalibur
Software Windows 10 Home 64-bit
Benchmark Scores Faster than the tortoise; slower than the hare.

Aquinus

Resident Wat-man
Joined
Jan 28, 2012
Messages
13,147 (2.94/day)
Location
Concord, NH, USA
System Name Apollo
Processor Intel Core i9 9880H
Motherboard Some proprietary Apple thing.
Memory 64GB DDR4-2667
Video Card(s) AMD Radeon Pro 5600M, 8GB HBM2
Storage 1TB Apple NVMe, 4TB External
Display(s) Laptop @ 3072x1920 + 2x LG 5k Ultrafine TB3 displays
Case MacBook Pro (16", 2019)
Audio Device(s) AirPods Pro, Sennheiser HD 380s w/ FIIO Alpen 2, or Logitech 2.1 Speakers
Power Supply 96w Power Adapter
Mouse Logitech MX Master 3
Keyboard Logitech G915, GL Clicky
Software MacOS 12.1
It's unlikely you'll notice any benefit above 48Khz and some claim that re-sampling can cause really high frequency sounds you can't hear that can damage your hearing but, I think that's a load of crap however, the quality of re-sampling an audio stream should be considered because this is done before the audio gets to the audio device. Honestly, 48Khz at 24-bit sound be more than enough and is least likely to result in your audio getting re-sampled. You can try higher sampling rates but, with lesser hardware I've noticed certain frequencies getting washed out when using 96 or 192Khz. However with that said, I've had pretty good luck using 96Khz when the source audio is already sampled at 96Khz but, re-sampling tends to harm quality.
 
Joined
May 30, 2018
Messages
1,890 (0.88/day)
Location
Cusp Of Mania, FL
Processor Ryzen 9 3900X
Motherboard Asus ROG Strix X370-F
Cooling Dark Rock 4, 3x Corsair ML140 front intake, 1x rear exhaust
Memory 2x8GB TridentZ RGB [3600Mhz CL16]
Video Card(s) EVGA 3060ti FTW3 Ultra Gaming
Storage 970 EVO 500GB nvme, 860 EVO 250GB SATA, Seagate Barracuda 1TB + 4TB HDDs
Display(s) 27" MSI G27C4 FHD 165hz
Case NZXT H710
Audio Device(s) Modi Multibit, Vali 2, Shortest Way 51+ - LSR 305's, Focal Clear, HD6xx, HE5xx, LCD-2 Classic
Power Supply Corsair RM650x v2
Mouse iunno whatever cheap crap logitech *clutches Xbox 360 controller security blanket*
Keyboard HyperX Alloy Pro
Software Windows 10 Pro
Benchmark Scores ask your mother
Put me on the list of people who can't hear the difference between 44.1 and 96... ...I mean really. I'm not gonna get into the science behind it too much. I'm just not interested in understanding something I personally don't perceive. I've had mixed results forcing sample rates. Either same or worse, really. If there's an auto option, leave it be... ...best sample rate is the one the source is at. If not, 44 or 48. Up-sample artifacting is not nice. Some dacs and sources really hate to have that stuff messed with. I can tell you this, you're not going to get more bass than is already there at 44.1. Nor is there likely to be an increase in clarity. All you are really doing is increasing the range of ultra-high-frequency content beyond what you can hear. If you drop down to 22, you'll lose a lot of the high frequencies, as its trunicating the highs down into what you can hear. Once you hit 44.1, the entire reproducible frequency range is there.

Going higher is like having a monitor that outputs infrared or ultraviolet. Does that make sense?

Getting into a gray area, there is a theory that DACs benefit from oversampling. There is a measurable artifacting phenomenon that occurs at 44.1 that has to do with the calculations that the DAC has to do for its conversion. It's mathematically not bit-perfect by nature, meaning it's not 100% accurate. At a certain point in the process, a peice of info is lost and there's no way around it. Increasing sample rates artificially is basically supposed to drag out those artifacts that bring out measurable inaccuracies in the output completely up and out of the "hearable" range. So it's still inaccurate... ...but mostly only to dogs. And for maximum benefit the source has to be a higher sample rate to begin with. Only some dacs can do oversamling properly... ...the architecture has to be designed for it. Just because a DAC or sound card can work with high sample rates doesn't mean it can upsample properly. Most sound cards probably can't, and forcing them to will likely sound worse than the native sample rate of 44.1. Scaling it up past that can cause problems of its own.

Personally I'm not a big fan of theoretical audiophilia, or strict measurement adherence. There is a measurable difference in ultra-high sample rates, with the right methods and the right equipment. But if there's anything these past several years in the world of high end audio has taught me, it's that measurements and numbers aren't everything. I have heard stuff that measures near-perfect frequency response and nearly zero distortion that sounds like stepped-on shit, and then there's stuff that measures over 10% THD that actually sounds incredibly even, dynamic, clear, and nuanced. And sometimes the opposite is true. But there are multiple ways to look at and interpret data like this. At the end of the day, when something sounds wrong, measurements will often tell you why - for instance, ringing distortion in certain ranges with specific characteristics in the time domain will denote certain audible defects in a transducer's sound, such as "cupping" or sibilance. You can see that without even hearing it and just know.

So sometimes we can see "bad." But nobody has figured out how to measure good. A lot of measurable differences that you can see on a chart or graph, can't likely be heard, or maybe don't manifest in the ways you expect. Sometimes things that measure as less distorted or more technically accurate do not sound better. We are not even close to understanding the hows and whys of what we experience vs how the input is processed and what our speakers put out. It can be quite the rabbit hole.

Bout all I can say there. Play with it and see if you can hear the difference. If not, then there you have it. If so, there it is. Trust your ears. There are situations where I can see it mattering for playback, but past having the full audible frequency spectrum or perhaps a little more, the real-world implications are limited, outside of like, ridiculously expensive super-granular, hyper-resolving setups. We're talking several thousand bucks minimum for entry. And it may not even be worth it, not for the accuracy anyway... ...though maybe for other things. The amount of accuracy gained is so small when most dacs are already approaching 100%. 44.1 will be fine for most. The majority of your source material is mixed down to that anyway, though it may have been mastered at a higher sample rate.

Which brings me to the next point. One use case for these higher bitrates and sample rates that I CAN argue for is in the actual production phase. There are actual benefits to recording/processing tracks at 24 or 32 bit at 192 or whatever crazy high sample rate you can squeeze out.

When it comes to digital processing and mixing, headroom is critical, and upping the bitrate helps bring the noise floor down and improve dynamic range. In a sense, it gives you a finer canvas... ...a wider range of values, which is important in the digital world. It's like working with a 20-megapixel image vs a 4-megapixel image. Things will be smoother when scaled down to the final resolution for the 20mp. It makes a big difference when you have noisy, high gain sounds, or lots of layers with different dynamic signatures, especially when you're messing with dynamics a lot. I'm really oversimplifying and there's a lot more to it, but that's the gist. Mixes done at 24 or 32 bits sound better, even when mixed down to 44.1.

Super-high sample rates mostly come into play with plugins... ...circuit emulators, synths, eq's, IR's, reverbs. A lot of these things benefit from being allowed to work with frequencies far beyond what you hear. Many actually have an "oversampling" feature that jacks up the sample rate for the plugin. In these cases, what happens past the audible range actually influences the output on the audible spectrum. It completely alters their behavior. Many plugins just perform better at higher sample rates that makes sense when it comes to audible frequency range. Again, it comes down to how they calculate the output, and certain quirks of how they work causing nasty things to happen past a certain point of the total frequency range available to them. The closer the ceiling is to the audible range, the harsher they tend to sound. So upsampling works similar to antialiasing in this case... ...smoothing over nastiness to an imperceptible level.

Another reason for higher frequency bandwidth is when you're doing a lot of time/pitch altering. There's simply more information to extrapolate from... like stretching an 8k image on one axis before shrinking it down to 4k, versus stretching a 4k source image. Which will look better?

But again, final mixdown is gonna be 16-bit, 44.1. By the time the tracks are processed and bounced down to a single stereo track, the benefits of higher sampling/bitrates have been and gone. For better or worse, that's standard practice. The common consensus is that nothing important is really lost.

But hey, don't take my word for it. Seriously, just try different sample rates and see how it goes. There is so much to this stuff, I wouldn't trust anyone who claims to know the absolute truth to it all.
 
Last edited:

FordGT90Concept

"I go fast!1!11!1!"
Joined
Oct 13, 2008
Messages
26,259 (4.63/day)
Location
IA, USA
System Name BY-2021
Processor AMD Ryzen 7 5800X (65w eco profile)
Motherboard MSI B550 Gaming Plus
Cooling Scythe Mugen (rev 5)
Memory 2 x Kingston HyperX DDR4-3200 32 GiB
Video Card(s) AMD Radeon RX 7900 XT
Storage Samsung 980 Pro, Seagate Exos X20 TB 7200 RPM
Display(s) Nixeus NX-EDG274K (3840x2160@144 DP) + Samsung SyncMaster 906BW (1440x900@60 HDMI-DVI)
Case Coolermaster HAF 932 w/ USB 3.0 5.25" bay + USB 3.2 (A+C) 3.5" bay
Audio Device(s) Realtek ALC1150, Micca OriGen+
Power Supply Enermax Platimax 850w
Mouse Nixeus REVEL-X
Keyboard Tesoro Excalibur
Software Windows 10 Home 64-bit
Benchmark Scores Faster than the tortoise; slower than the hare.
Last edited:
Joined
May 30, 2018
Messages
1,890 (0.88/day)
Location
Cusp Of Mania, FL
Processor Ryzen 9 3900X
Motherboard Asus ROG Strix X370-F
Cooling Dark Rock 4, 3x Corsair ML140 front intake, 1x rear exhaust
Memory 2x8GB TridentZ RGB [3600Mhz CL16]
Video Card(s) EVGA 3060ti FTW3 Ultra Gaming
Storage 970 EVO 500GB nvme, 860 EVO 250GB SATA, Seagate Barracuda 1TB + 4TB HDDs
Display(s) 27" MSI G27C4 FHD 165hz
Case NZXT H710
Audio Device(s) Modi Multibit, Vali 2, Shortest Way 51+ - LSR 305's, Focal Clear, HD6xx, HE5xx, LCD-2 Classic
Power Supply Corsair RM650x v2
Mouse iunno whatever cheap crap logitech *clutches Xbox 360 controller security blanket*
Keyboard HyperX Alloy Pro
Software Windows 10 Pro
Benchmark Scores ask your mother
Wouldn't the difference there be due to the compression to 192 kbps though? If I took that flac and converted it to a 16-bit 44.1k wav file would you still hear such a dramatic difference?

Edit: Went ahead and tried it in reaper. Sometimes I think I hear a difference, but most of the time I can't. It's like it's there, but then I go back and it's gone. Opening up the 3 together in reaper and soloing between them, I can barely even pick out the AAC most of the time. Not via Modi 2 Uber/JBL LSR 305's, anyway.

I uploaded the .wav file, for anyone curious. This is your standard, uncompressed CD-quality 44.1khz 16-bit. https://www.dropbox.com/s/u19uqqwnu1xciew/untitled.wav?dl=0
 
Last edited:
Top