Showing posts with label settings. Show all posts
Showing posts with label settings. Show all posts

Parameters that can be configured within an Wi-Fi 5 (IEEE 802.11ac) Wireless Network

Configurable Physical (PHY) Layer Parameters in an IEEE 802.11ac (Wi-Fi 5) Wireless Network

This focuses exclusively on the PHY layer parameters that network administrators can directly configure, influence, or cap. It explores the engineering trade-offs associated with each parameter, ensuring a comprehensive understanding of how PHY layer tuning dictates network capacity, coverage, and reliability.

1. Core Configurable PHY Layer Parameters

The PHY layer of 802.11ac is responsible for the transmission and reception of raw bit streams over the 5 GHz wireless medium. The following parameters represent the primary levers available to network architects.

1.1. Channel Width

Channel width dictates the amount of contiguous spectrum allocated to a single transmission. 802.11ac introduced wider channels as a primary mechanism for achieving "Gigabit" throughput.
  • Configuration Options: 20 MHz, 40 MHz, 80 MHz, and 160 MHz (the latter introduced in Wave 2).
  • Engineering Trade-off: Doubling the channel width theoretically doubles the data rate but also doubles the noise floor (reducing the Signal-to-Noise Ratio by 3 dB) and exponentially increases the probability of Co-Channel Interference (CCI).
  • Best Practice: While 80 MHz is the default for low-density residential deployments, enterprise and high-density environments should be configured for 40 MHz (or even 20 MHz) to maximize frequency reuse and network stability.

1.2. Operating Channel and UNII Band Selection

Administrators can manually lock an Access Point (AP) to specific 5 GHz channels to avoid interference, manage cell overlap, or comply with regulatory mandates. The 5 GHz spectrum is divided into Unlicensed National Information Infrastructure (UNII) bands:
  • UNII-1 (Channels 36, 40, 44, 48): Non-DFS (Dynamic Frequency Selection). Highly preferred for stability, though transmit power may be legally capped in certain regulatory domains.
  • UNII-2 / UNII-2 Extended (Channels 52–144): DFS-mandated. APs must actively monitor for military and weather radar. If detected, the AP must vacate the channel within seconds, causing network disruption.
  • UNII-3 (Channels 149, 153, 157, 161, 165): Generally non-DFS and often permits higher maximum transmit power, making it ideal for extending coverage in specific directions, provided local regulations allow it.

1.3. Transmit (Tx) Power Control (TPC)

Tx power determines the strength of the RF signal emitted by the AP’s antennas, typically measured in dBm or as a percentage of the hardware’s maximum capability.
  • Configuration Options: Usually adjustable in 1 dBm or 3 dBm increments (e.g., 12 dBm to 22 dBm).
  • Engineering Trade-off: Higher Tx power increases the coverage area (cell size) but also increases CCI with neighboring APs. Furthermore, Wi-Fi is a two-way communication system; a client may hear a high-power AP, but the AP may not hear the low-power client (the "hidden node" or asymmetrical link problem).
  • Best Practice: In high-density deployments, Tx power should be deliberately lowered (e.g., to 12–15 dBm) to shrink cell sizes, encourage client roaming to closer APs, and enable aggressive frequency reuse.

1.4. Guard Interval (GI)

The Guard Interval is a deliberate pause inserted between Orthogonal Frequency-Division Multiplexing (OFDM) symbols to prevent Inter-Symbol Interference (ISI) caused by multipath propagation (signal reflections).
  • Configuration Options: Long Guard Interval (800 ns, the 802.11ac default) or Short Guard Interval (400 ns).
  • Engineering Trade-off: Enabling the Short Guard Interval yields a theoretical ~10% increase in throughput by packing more symbols into a given timeframe. However, it requires a high Signal-to-Noise Ratio (SNR) and a clean RF environment. In environments with significant multipath distortion (e.g., warehouses with metal racking), a Short GI will cause symbol overlap, leading to packet corruption and retransmissions that negate the throughput gain.

2. Advanced and Enterprise-Specific PHY Configurations

Beyond the foundational settings, enterprise-grade wireless controllers and advanced standalone APs expose deeper PHY layer controls to fine-tune network behavior.

2.1. Spatial Stream Limitation

While the maximum number of spatial streams is dictated by physical hardware (e.g., a 4x4:4 AP has four transmit and four receive chains), administrators can sometimes artificially limit this via software.
  • Use Case: Restricting a 4x4 AP to operate as a 2x2 AP can be used to conserve power, reduce RF noise in ultra-dense environments, or force load balancing across multiple APs.

2.2. Modulation and Coding Scheme (MCS) Capping

The MCS index (0 through 9 in 802.11ac) determines the combination of modulation (up to 256-QAM) and Forward Error Correction (FEC) coding rate. While normally negotiated dynamically, some advanced systems allow administrators to set a Maximum MCS Index.
  • Use Case: Capping the MCS (e.g., to MCS 7 instead of MCS 9) forces the AP to use a more robust, lower-order modulation (e.g., 64-QAM instead of 256-QAM). This sacrifices peak speed for extreme reliability, which is highly beneficial for mission-critical IoT devices or in environments with consistently marginal SNR.

2.3. Explicit Beamforming Controls

802.11ac standardized Explicit Beamforming, where the AP shapes its RF signal toward a specific client based on channel state information (CSI) feedback.
  • Configuration Options: Enable/Disable.
  • Use Case: While almost always left enabled, it may be disabled in highly controlled lab environments or when troubleshooting specific client compatibility issues, as the beamforming handshake adds minor protocol overhead.

2.4. DFS Sensitivity and Channel Availability

Administrators can often configure how aggressively the AP monitors for DFS events.
  • Configuration Options: High, Medium, or Low sensitivity (vendor-dependent).
  • Engineering Trade-off: High sensitivity ensures strict regulatory compliance but increases the risk of "false positives" (e.g., mistaking a satellite signal for radar), triggering unnecessary channel migrations. Low sensitivity maintains network stability but risks regulatory fines if actual radar is present.

3. Quantitative Impact Matrix of PHY Configurations

The following table summarizes the primary configurable PHY parameters, their available options, and their direct impact on network performance.
PHY Parameter
Configuration Options
Primary Impact on Network Performance
Recommended Baseline (Enterprise/High-Density)
Channel Width
20, 40, 80, 160 MHz
Throughput vs. Co-Channel Interference (CCI)
40 MHz (balances speed and spectrum efficiency)
Operating Channel
UNII-1, UNII-2, UNII-2e, UNII-3
Stability vs. Regulatory Compliance (DFS)
UNII-1 and UNII-3 (non-DFS) where possible
Transmit Power
12 dBm to 22+ dBm
Cell size, client roaming behavior, CCI
12–15 dBm (shrink cells for high-density reuse)
Guard Interval
Long (800 ns), Short (400 ns)
Throughput (+10%) vs. Multipath Robustness
Long (800 ns) for reliability; Short only in pristine RF
MCS Index Limit
MCS 0 through 9 (Dynamic or Capped)
Link reliability vs. Peak data rate
Dynamic (default); Cap at MCS 7 for critical IoT
Spatial Streams
Hardware max, or software-limited
Aggregate capacity vs. RF footprint
Hardware max (limit only for specific load-balancing)

4. Conclusion

The Physical (PHY) layer of an IEEE 802.11ac network is not merely a passive conduit for data; it is a highly tunable engine governed by the laws of RF physics. Configuring these parameters requires a deliberate departure from "out-of-the-box" defaults. By strategically narrowing channel widths, managing transmit power to control cell boundaries, and carefully selecting non-DFS channels, network engineers can transform a fragile, interference-prone Wi-Fi 5 deployment into a robust, high-capacity infrastructure. For technical content creators and network architects, documenting these PHY layer trade-offs is essential for designing networks that prioritize real-world reliability over theoretical maximum throughput.

Media Player Classic Home Cinema - Optimal settings for better playback

Media Player Classic Home Cinema(MPC-HC) is a free audio and video player for Windows.

  • MPC-HC version: 2.4.2
  • Windows 10 and 11

Basic MPC-HC app settings

Set the Process priority above normal

    • To set the MPC-HC app to run with CPU process priority level Above Normal.
      • Select Player tab.
      • Enable the Process priority above normal.

    Limit window proportions on resize

    Set MPC-HC  windows to resize in proportion to the aspect ration of the video file being played.

    • Select User Interface tab.
    • Enable Limit window proportions on resize . 

    Associate Video files to open with MPC-HC

    Associate video files formats to run by default with MPC-HC app, when opened from Windows Explorer. Associating the MPC-HC app with video file extension in Windows OS is necessary if the user want MPC-HC app to be recognized as the default Video Player in Windows OS.

    • Select Player > Formats tab.
    • Click on Run as administrator in the group box labeled Association.

    • Click Associate with video formats only icon , to select File extensions of video file formats that will be associated with MPC-HC app.
    • Click on Apply button.


    Disable Auto zoom

    When a video file is played, Auto zoom feature resizes the MPC-HC window to a specified percentage of the resolution of the video file. 

    If the user wants MPC-HC window to remain at same size when video files are being played then he has option to disable the Auto-zoom feature.

    To Disable Auto zoom feature, do the following:

    • Select Playback tab.
    • Disable Auto-zoom in the group box labelled Zoom and Alignment.

    Set the Video and Audio Renderer

    Use MPC Video renderer as the Video Renderer engine.

    • Select Playback > Output tab.
    • Select MPC Video Renderer as the DirectShow Video.

    Use MPC Audio renderer as the Audio Renderer engine.

    • Select Playback > Output tab.
    • Select MPC Audio Renderer as the Audio Renderer.

    Internal Filter settings


    LAV Splitter settings: Preferred languages for audio tracks and subtitles

    Set the preferred language in which the subtitle will be selected from the list of subtitles available for display on the MPC HC app. The subtitle selection will be done by the LAV Splitter.

    To set the preferred language:

    • Select Internal Filters tab.
    • Select Splitter button to open LAV Splitter settings.
    • Set the Subtitles preferred languages in ISO 639-2 codes( ex. eng, spa, ger, fre).

    Similarly, the preferred language can be set in which the Audio track will be selected from the list of available audio tracks, for the playbakc on the MPC HC app.

    To set the preferred language:

    • Set the Audio preferred languages in ISO 639-2 codes( ex. eng, spa, ger, fre).

    LAV Video Decoder settings: Hardware Decoder

    If the GPU supports Directx 11 or higher, the D3D11 can be used as the Hardware Deocder.

    To set the Hardware Decoder:

    • Select Internal Filters tab.
    • Select Video Decoder button in the group box labeled Internal LAV Filters settings.
    • Set the D3D11 as the Hardware Decoder to use.

    Keep the MPC HC app window on top While playing Video

    Setting to keep the MPC-HC app window above others, while playing a video file. This will make sure that the video frame of is always in view when playing a video file in MPC-HC app.

    • Select View > On Top > While playing Video.

    Snap to desktop edges

    Its a handy feature for organizing your open application windows on your computer screen to the edge or corner of the desktop screen. It allows you to quickly arrange them side-by-side or in other configurations.

    To use Snap feature:

    • Select User interface tab.
    • Enable Snap to desktop edges.

    Control via Windows UI(SMTC)

    The System Media Transport Controls enable media application developers integrate with the built-in system UI to display media metadata such as artist, album title, or chapter title. The system transport control also allows a user to control the playback of a media app using the built-in system UI, such as pausing playback and skipping forward and backward in a playlist.

    To enable support of SMTC:

    • Select User interface tab.
    • Enable Control via Windows UI(SMTC).

    Set the default Audio track and subtitle language in MPC-HC app

    Set the preferred language in which the subtitle will be selected from the list of subtitles available for display on the MPC HC app.

    To set the preferred language:

    • Select Playback tab.
    • Set the Subtitles preferred language in ISO 639-2 codes( ex. eng, spa, ger, fre).

    Similarly, the preferred language can be set in which the Audio track will be selected from the list of available audio tracks, for the playback on the MPC HC app.

    To set the preferred language:

    • Select Playback tab.
    • Set the Audio preferred language in ISO 639-2 codes( ex. eng, spa, ger, fre).

    Normalize the Audio

    Normalizing the audio is useful in enhancing the certain audio with low level in the audio track. It is useful in playback of media files with very ow audio level.


    To normalize the audio signal, do the following:
    • Select Internal Filters > Audio Switcher.
    • Enable Normalize.


    Configure Font Style settings

    User may configure the Subtitle font settings hat suit their needs:

    1. Font Style
    2. Font spacing
    3. Font Border shadow
    4. Subtitle Screen alignment and margins.