Welcome to the FlexRadio Community! Please review the new Community Rules and other important new Community information on the Message Board.
How to Receive Technical Support::
If you are needing assistance with FlexRadio products, please refer to the product documentation or check the Help Center for known solutions. Need technical support from FlexRadio? It's as simple as creating a HelpDesk ticket.

Severe Audio Stuttering and RF Power Drops in FT8 - SmartSDR+ v4.1.5 & WSJT-X v3.0.0

albert
albert Member ✭✭

Hi FlexRadio Support Team,

I am opening this ticket regarding a persistent modulation issue with my Flex-6500 since upgrading to SmartSDR v4.1.5.

Problem Description:When operating in FT8 using WSJT-X v3.0.0, the transmitted audio is severely "stuttered" or "hachured". This is immediately followed by correlated drops in RF output power. The issue appeared specifically after the migration to version 4.1.5.

Technical Environment:

  • Radio: Flex-6500 (Firmware v4.1.5).
  • Software: WSJT-X v3.0.0.
  • Time Sync: Verified with NetTime (+2ms offset).
  • Network: PC and Radio are on the same subnet, MTU 1500, Interrupt Moderation disabled on the NIC.

Troubleshooting already performed:

  1. Clean Sweep: I have performed a complete uninstallation of all SmartSDR versions (v2, v3, and v4) and FlexVSP. I manually deleted the %APPDATA% and Program Files FlexRadio folders before a clean reinstall of v4.1.5.
  2. Audio Configuration: Verified that DAX Audio TX and DAX Audio RX are strictly set to 16-bit, 48000 Hz in the Windows Sound Control Panel.
  3. Split Mode: Tested with Split set to "None", "Fake It", and "Rig" with no improvement.

Despite these steps, the "Scenario B" delay we saw earlier is resolved, but the stuttering modulation makes the radio unusable in digital modes.

Could you please advise if there is a known compatibility issue with the v4.1.5 DAX drivers on certain Windows builds or if there is a specific buffer setting I should adjust?

73's

ON5AM

Tagged:

Comments

  • Mike-VA3MW
    Mike-VA3MW Administrator, FlexRadio Employee, Community Manager, Super Elmer, Moderator admin

    Hi

    No, this is not a known problem. The first thing you need to do is a full radio reset after exporting your profiles and saving them. We do suggest doing this in the SmartSDR v4.1.5 release notes. Others have reported similar experiences and a radio reset has resolved their issues.

    Give that a try.

  • albert
    albert Member ✭✭

    Thanks Mike,

    After performing a full Factory Reset of the radio and a "Clean Sweep" of the PC software, I am stuck in the following repetitive 3-cycle loop.

    • Cycle 1: The radio receives normally.
    • Cycle 2: Instead of switching to Transmit as expected by WSJT-X, the radio stays in Receive mode.
    • Cycle 3: The radio finally keys up (TX indicator turns red), but there is no RF carrier/output at all.

    Then the sequence repeats.

    Has anyone seen this "skipped cycle followed by empty carrier" behavior before?

  • albert
    albert Member ✭✭

    I open a ticket.

  • Neal Pollack AB6G
    Neal Pollack AB6G Member ✭✭
    edited February 26

    This is indeed a known problem, despite what they are saying. I submitted a ticket on this issue months ago, with 4.1.3 and 4.1.5. I added video to the ticket showing the digital power meter and the Flex waterfall display on transmit. While FT8 is transmitting, the RF power is jumping all over the place, both on the waterfall and on the external third party RF power meter.

    After doing what Flex Tech Support told me to do, in order to verify that my Windows 11 PC was not to blame (Latency checks and other things), they finally said it is a known DAX driver issue, and that I should
    wait for some future release to perhaps fix it.

    Important note: This issue does NOT prevent making FT8 contacts, but since the waterfall shows a pulsing rise of the side skirts of the RF envelope (looks a lot like phase noise spreading worse), it is possible that this can cause noise for other people? But someone would have to hook up a nearby receiver and spectrum analyzer to verify. Anyway, the issue is not there with CW or with Phone, and it does not prevent successful FT8 usage. But it is highly annoying and disconcerting to watch it. These are, after all, very high end expensive radios, so it would be normal to expect more stable output during digital modes.

    Neal

  • DL1DMS
    DL1DMS Member
    Hey folks,

    I am experiencing the exact same issue on a FLEX-6600 running SmartSDR v4.1.5 with WSJT-X / JTDX.

    During FT8 transmission I observe:
    -Brief RF power drops (2–3 times per 15s transmit cycle)
    -Corresponding visible gaps in the transmitted spectrum
    -No SWR increase
    -No ALC spikes
    -No PA temperature or current fluctuations

    To isolate the problem, I performed the following tests tonight:
    -Audio Path Verification
    -Recorded the DAX TX stream internally using Adobe Audition.
    -The recorded audio file is completely clean with no dropouts.
    -This confirms WSJT-X/JTDX and DAX are delivering a continuous audio stream.

    Network Tests
    -Continuous ping to the radio: stable (no packet loss, 3–8 ms latency).
    -Tested over both WiFi and wired LAN.
    -Issue identical on both connections.

    PC / OS Tests
    -CPU usage normal (no spikes).
    -Windows Defender real-time protection disabled.
    -Reinstalled SmartSDR and DAX drivers completely.

    No improvement.
    -CAT / PTT Tests
    -CAT control works correctly.

    SmartSDR Tests
    -Tested with SmartSDR minimized (no improvement).
    -Verified RF power meter remains steady during dropouts.
    -SWR remains stable.
    -TUNE in JTDX is perfectly stable.

    Additional Observations
    -Issue also occurs in WSJT-X (not only JTDX).
    -Does not occur with a steady tone.
    -Only appears during FT8 modulation.

    Based on these controlled tests, this does not appear to be:
    -A PC performance issue
    -A network instability
    -A CAT/PTT interruption
    -A power foldback condition

    It appears to be a TX audio engine or DAX interaction issue introduced in SmartSDR 4.1.x.

    Are there any known TX-audio instability in 4.1.5 affecting digital modes like FT8?

    Please help.

    73, Manuel
  • Mike-VA3MW
    Mike-VA3MW Administrator, FlexRadio Employee, Community Manager, Super Elmer, Moderator admin

    Manuel - doing a factory reset has resolved this problem in most cases. Give that a try. It worked for the original poster.

  • Neal Pollack AB6G
    Neal Pollack AB6G Member ✭✭

    A factory reset is the first thing I did, and it has no effect.
    The support rep had commented that they need to revise the DAX drivers.
    It IS the DAX channel.
    If you use CW or RTTY, you will not see stuttering.
    If you use a mode that uses the DAX channel for audio, you will see stuttering.
    They had me run Latency Monitor on my PC, and also checked memory usage
    and CPU usage. No issue there. But since Windows OS is NOT a Real-Time
    operating system, the architecture of the current DAX drivers may not be
    keeping it's stream full while Windows shares CPU time with other background
    tasks. Perhaps they simply need larger buffers in DAX? I hope not a total
    redesign. But it's easy to test and prove that if DAX is out of the picture,
    so is the problem.

    Cheers,

    Neal

  • edwinhigg
    edwinhigg Member ✭✭

    You can fix your problem cosmetically by increasing the Transmit Buffer and the Receive Buffer in the network adapter properties in the device manager. I just got mine fixed. Finally consulted ChatGPT and she walked me through a lot of things to check.

    While trying to fix the problem I went through several ethernet switches, finally settled on a Cisco that had management settings.

  • Neal Pollack AB6G
    Neal Pollack AB6G Member ✭✭

    @edwinhigg: Can you share a step by step of the settings that fixed it for you? Have you since noticed any downside to having the increased buffers for the network adapter on the PC? Does any setting need to change on the Radio or the Maestro, or is this only about using larger TX/RX buffers on the network port on the Windows computer?

    Cheers,

    Neal AB6G

  • Neal Pollack AB6G
    Neal Pollack AB6G Member ✭✭

    ALL: Version 4.2, releasing tomorrow, may or may not fix this stuttering issue. I did some research and started to see evidence that some desktop PC motherboards that use a variety of very low-end Intel Ethernet Chips contribute to this stuttering issue, due to a number of issues with buffer size and Interrupt handling that can't be set in the device properties on these low end chips. There are also some bugs in the silicon and/or drivers for this low end chip.

    I started to see (using google) various posts by the professional audio community that recommend adding the inexpensive Intel i210 PCIe add-in card, which is a server class Ethernet chip and has all the needed settings in the device manager properties advanced tab.

    So I bought one of these cards on eBay for less than $45 USD, and then did the following A.I. Query this morning. I decided to share this. It has good and logical information, but as you all should know, A.I. can also make mistakes.

    I plan to connect this desktop PC to the Flex tomorrow, and also upgrade to SmartSDR V4.2 for the DAX V2 redesign. I will report back if the stuttering is gone.

    = = = = = = =

    GEMINI A.I.

    QUERY: I have noticed that Flex Radio's Smart SDR software version 4.1.x DAX, when transmitting digital modes that use the DAX Audio channel, can have amplitude "stuttering" and variation. There is some evidence that this may be worsened by the poor Intel I-225V Ethernet chip used on my motherboard, since that chip does not expose settings for TX and RX buffers. I have added an Intel i210 server Ethernet card, and it appears to have more option settings on the advanced properties tab in device manager. Can you share all information that you can find regarding this issue, and also share the proper settings to use on the i210 advanced properties for optimizing DAX operation?

    RESPONSE:

    Switching to the Intel i210 is a solid move. The I225-V is notorious in the amateur radio and high-performance networking communities for "micro-stuttering" due to its aggressive power management and lack of deep buffer tuning. Because DAX (Digital Audio Exchange) relies on a steady, real-time UDP stream of VITA-49 packets, any slight interruption in the network stack manifests as the amplitude stuttering you’ve observed.

    With the i210 server-grade card, you have the granular control needed to prioritize these packets.

    Why the Stuttering Happens

    DAX version 4.x (and specifically the transition to the new DAXv2 architecture) moves audio through a shared-memory design, but the transport between the radio and your PC still relies on UDP. Unlike TCP, UDP doesn't "retry" lost or late packets. If your NIC's internal buffers overflow or if the chip enters a low-power state for even a millisecond, the audio stream loses synchronization, causing that "warbling" or stuttering amplitude.

    Optimized i210 Advanced Properties

    To fix this, go to Device Manager > Network adapters > Intel(R) I210 Gigabit Network Connection > Properties > Advanced. Adjust the following settings to prioritize stability over power savings:

    Setting

    Recommended Value

    Reason

    Transmit Buffers

    2048 or 4096

    Higher values prevent the NIC from "dropping" transmit data if the OS is momentarily busy.

    Receive Buffers

    2048 or 4096

    Increases the "safety margin" for incoming VITA-49 data from the radio.

    Interrupt Moderation

    Disabled

    Critical. Moderation batches interrupts to save CPU, but it adds jitter to audio streams. Disabling it ensures packets are handled immediately.

    Energy Efficient Ethernet (EEE)

    Disabled

    Prevents the card from "sleeping" during tiny gaps in traffic, which is a primary cause of DAX stutter.

    Flow Control

    Disabled

    Prevents the NIC from sending "pause" frames which can disrupt the timing of real-time audio.

    Jumbo Packet

    Disabled (1514)

    FlexRadio uses standard MTU sizes; Jumbo frames can actually increase latency in some setups.

    DMA Coalescing

    Disabled

    Like Interrupt Moderation, this batches tasks to save power but introduces timing inconsistencies.

    Power Management Tab:

    • Uncheck: "Allow the computer to turn off this device to save power."

    Additional Troubleshooting for SmartSDR 4.x

    If you still notice issues after the NIC swap, consider these FlexRadio-specific factors:

    1. DPC Latency: Even with a great NIC, if another driver (often Nvidia graphics or a Wi-Fi card) is hogging the CPU, the DAX driver will underrun. Use a tool like LatencyMon to ensure your "highest measured interrupt to process latency" stays well below 1000 µs while transmitting.
    2. SmartSDR 4.2+ (DAXv2): If you haven't already, ensure you are on version 4.2 or later. This version introduced a major rewrite of the DAX driver architecture specifically to solve the "clicks, pops, and drops" common in earlier Windows 11 environments.
    3. CPU Core Isolation: In Windows 11, "Memory Integrity" (under Core Isolation settings) can sometimes interfere with older DAX drivers. While DAXv2 (v4.2+) is designed to be compatible, earlier 4.x versions often required this to be disabled for smooth audio.

    [TIP] Since you are using an Intel i7-12700, you have plenty of overhead. If the stuttering persists, try settting the Process Priority of SDRCAT.exe and DAX.exe to "Above Normal" in the Task Manager to ensure Windows doesn't de-prioritize them during heavy digital mode decoding (like WSJT-X cycles).

Leave a Comment

Rich Text Editor. To edit a paragraph's style, hit tab to get to the paragraph menu. From there you will be able to pick one style. Nothing defaults to paragraph. An inline formatting menu will show up when you select text. Hit tab to get into that menu. Some elements, such as rich link embeds, images, loading indicators, and error messages may get inserted into the editor. You may navigate to these using the arrow keys inside of the editor and delete them with the delete or backspace key.