Wi-Fi Limitations and Sample rates...16/44.1


Help me clear something up. I am getting conflicting opinions on whether or not Wi-Fi necessarily limites sample rates to 16/44.1. I have read on Agon and at other sites, that most Wi-Fi routers have a limit of 16/44.1

This is a concern if you had anticipated playing 24/48 (or higher) flack files on your WiFi based server.

I have also read that in no way does Wi-Fi have such limitations. Is there some validity to this matter...in that some "routers" are limited...Wi-Fi in general? If so, how does one determine if their Wi-Fi router has limitations?

Thank you.
2chnlben
2chnlben,

It is possible that software on your PC source could reduce the sample rate even though the router is not an issue.

For example, I have read (unconfirmed) that some older (pre Vista) versions of Windows may reduce sample rates implicitly in some cases. I believe this is possible though I do not recall specifics.

To avoid these kinds of problems, stick with newer computer platforms that are well suited for multimedia type apps, like Windows Vista or newer similar server versions of the OS (yes Vista gets a bum rap in corporate corners but it is essential to problem free playback off of PCs, I believe) or Apple.
Mapman,

Windows win95, win98 and WinXP do not down sample network packets on a wireless network.

Windows XP kmixer does re-sample audio to 44.1 or 48k.

Your confusing digital to analog conversion in a soundboard with streaming packets of data over a network.
Prpixel,

I do know the difference between the two but not the details of which MS software does what when, so that is helpful.

I only recall reading that it was an issue with the older versions of Windows in general but not XP.

Since it is very difficult often to determine what OS bundled software is actually doing what when something does not sound right, I recommend Vista in general as a more robust and less problematic platform for digital audio over older versions of Windows, that's all.
Think about it. If older versions of Windows were re-sampling data packets traveling over a network, then all data would be adulterated or corrupted whether it be a picture, music, excel spreadsheet etc. Because Windows, or any operating system, does not have the ability to distinguish the contents of a data packet, how would it be able to single out audio packets and re-sample them? The only thing that windows looks at in a data packet is the header information to determine where a packet came from, where it's going and the checksum to determine if it was corrupted during it's journey.

Now, you can get third party software that will do deep packet inspection, but even the best versions have very low levels of accuracy. The RIAA, and ISP's, have been doing trials with deep packet inspection software with poor results. In order to get high accuracy rates, they really need to capture the whole file being transferred, determine the type of file and if it's legitimate or illegal, and then either allow or stop the transfer.
PR,

I recall the issue was with certain core programs/components bundled into Windows that dealt specifically with sound, not windows IO functionality in general. It had to do with maintaining throughput with older, slower computers not necessarily designed for high performance A/V.

Don't recall the details nor can I confirm that the problem truly exists, but it makes sense to me that newer OS versions have more refined software components for A/V since that is now a core application area that people buy the computers for.