mrkeyoor.comAsk

burakgon/stop-stuttertested 29 Sept 2026commit 64d3008

stop-stutter review

Use Stop Stutter after an off-versus-on comparison shows that suppressing AWDL helps your streaming session.

  • Build 8 s
19 sto install
  • 35 packages
Automationevaluationupdated 01 Nov 2026
-27stars / 7d

Try Stop Stutter if disabling AWDL improves a repeatable streaming session on your Mac and you want that workaround automated. Stop Stutter holds AWDL off while selected apps run and restores it when the last selected app quits. Our run on September 29, 2026, at commit 64d3008 used a Debian sandbox; it did not test the native macOS app, privileged helper, or streaming performance.

Verdict

Use Stop Stutter after an off-versus-on comparison shows that suppressing AWDL helps your streaming session. Its selected-app automation can then save repeating the workaround, at the cost of AWDL-dependent sharing features during Boost. Our September 29, 2026 run at commit 64d3008 recorded successful sandbox command outcomes and skipped tests; it provides no native-app or performance validation. The maintainer reports no streaming-quality benchmark in the supplied validation record.

We ran it

Lab card: what happened when we ran stop-stutter
Lab card from our sandbox run
Screenshot of stop-stutter (github.com/burakgon/stop-stutter)
github.com/burakgon/stop-stutter
Install✓ · 19s35 packages · 37 MB
Build✓ · 8s
Testsn/ano test script
Known vulns0(pip-audit)
Repo52 files~2,521 lines of source · 2.7 MB · 1 CI workflows

Answers from our run

Does stop-stutter build from source?

Dependencies installed in 19 seconds (35 packages), and the build succeeded in 8 seconds. We cloned commit 64d3008 into a clean Debian container with 3 CPUs and no project-specific setup.

Does stop-stutter have tests you can run?

Not through a standard command: the project exposes no test script or target that our harness could run.

Does stop-stutter have known vulnerabilities in its dependencies?

pip-audit found none in the dependency tree at the time of our run.

Who should not use stop-stutter?

Windows or Linux users, or Macs running earlier than macOS 14.

What are the alternatives to stop-stutter?

AWDL Control, AWDL Toggle. Use Stop Stutter after an off-versus-on comparison shows that suppressing AWDL helps your streaming session.

Setup3/5The documented release installation needs administrator-approved helper setup. Source helper testing adds Xcode and signing requirements; our Linux run did not validate either installation path.
Docs5/5The supplied README explains modes, app-lifetime behavior, installation, signing, removal, and manual recovery. The validation document separates interface checks from unmeasured stream quality.
Community3/5A limited editorial assessment: the supplied repository documents reporting and contribution routes, but the extracts do not establish independent adoption or contributor breadth. The historical star count is not evidence of either.
Maturity3/5The signed, notarized v0.1.0 release has documented interface and helper checks. Streaming benchmarks, Intel runtime evidence, and several system recovery scenarios remain absent from that release's validation.

Who it’s for

Mac users who can compare the same streaming scene with Boost off and on before enabling automation.
Moonlight, GeForce NOW, Punktfunk, Parsec, and Steam Link users who want Boost tied to the native client's lifetime.
Users willing to approve a privileged helper and temporarily lose access to Apple features that depend on AWDL.

Who it’s NOT for

Windows or Linux users, or Macs running earlier than macOS 14.
Users seeking a general fix for router congestion, packet loss, decoding problems, or display timing.
Anyone who needs AirDrop, peer-to-peer AirPlay, or affected Continuity features during play.
Readers seeking demonstrated FPS or latency gains: neither our sandbox nor the maintainer's supplied validation establishes them.

Setup reality

The release route requires moving Stop Stutter.app into Applications, opening it, enabling the helper, and approving it in macOS settings. Administrator approval is required. The v0.1.0 release is Developer ID signed, notarized, and universal, with macOS 14 as its minimum. Liquid Glass controls require macOS 26.

Source builds require Xcode 26 or later. The default ad-hoc build previews the UI but cannot access the privileged helper. Live helper development requires your own Apple Development or Developer ID signature; macOS may also require notarization.

Our run recorded a Python-classified installation taking 19 seconds and a build step taking 8 seconds. Those command outcomes do not establish that the Swift application built. Tests were skipped because the harness found no supported script. The recorded dependency footprint belongs to this sandbox path, not a measurement of the installed Mac app.

Decide with an off-versus-on comparison

Stop Stutter holds AWDL off while selected apps run and restores it when the last selected app quits. That is useful when AWDL activity causes streaming hitches. It does not address independent causes such as congestion, packet loss, decoding, or display timing.

Follow the repository's proposed comparison: use a repeatable scene over Wi-Fi, keep resolution, bitrate, and network setup unchanged, and compare Off with Always on. Watch recurring hitches and the client's latency-variation or dropped-frame statistics where available. Enable Auto only if the difference is useful and repeatable.

Boost leaves regular Wi-Fi enabled. AirDrop, peer-to-peer AirPlay, and some Continuity features may be unavailable while AWDL is held off. Auto follows application lifetime, including menus and background operation; it does not detect an active stream. Quit the last watched client to end its automatic session.

What our sandbox actually recorded

Our run on September 29, 2026, at commit 64d3008 used a Debian sandbox. The stored record identifies the Python 3.12 Bookworm image, with 3 CPUs and 8 GB of memory, and classifies the checkout as Python.

The attached harness summary records installation success in 19 seconds and build-step success in 8 seconds, both with exit code zero and neither timed out. It records 35 installed packages occupying 37 MB. The install log tail identifies a Python environment; the build log tail is empty. The record does not identify a native Swift build command or show a macOS workload.

Tests were skipped with the reason "no script". They did not fail, and there is no passing-test count from our run. The detector's failure to find a supported script does not mean the repository lacks tests: its README documents swift test.

Our sandbox did not exercise the macOS application, signing, helper approval, live AWDL control, or a streaming client. The harness records step status, exit code, elapsed time, timeout state, and available log tails. A successful command outcome alone cannot establish that those workloads ran. The testing-methodology page explains the publisher's reporting approach; its current text does not establish which methodology version governed this older run.

Pip-audit recorded zero advisories and a packages value of zero. Scanned-package coverage is unknown because no scannedPackages value is supplied. This is not evidence that the Mac app or its privileged helper passed a security review.

Separate maintainer validation from our run

The maintainer reports no streaming-quality benchmark in the supplied validation record. Its v0.1.0 section describes actual interface checks, Punktfunk launch and quit behavior, helper authentication, lease handling, and removal. Those are maintainer observations on an Apple Silicon development Mac, separate from our Debian results.

The supplied commit's validation document also contains a 0.1.1 section. It describes event-driven enforcement and update-recovery work, while leaving live revival correction and some update scenarios uncovered. These later checks must not be presented as v0.1.0 release validation or as work performed by our sandbox.

The v0.1.0 record says Moonlight was not installed on the development Mac. Intel hardware and macOS 14, 15, and 26 runtime testing remained open, along with several recovery scenarios. A universal binary establishes architecture inclusion, not successful operation on each supported Mac.

Helper recovery has limits

According to the README, the app renews a ten-second lease with a two-second heartbeat. Disconnects release the lease, and a recovery marker lets a restarted helper attempt restoration. The helper accepts a boolean Boost request rather than arbitrary commands, paths, or interface names, and both sides validate signing identity.

These controls narrow the operation; they do not guarantee restoration after every failure. A missing interface, OS error, or premature removal can prevent recovery. Use the documented Remove Helper flow before deleting the app, and avoid running competing AWDL controllers.

Choose one controller

AWDL Control follows the active game and restores AWDL when you quit the game or return to the desktop. Consider it instead if foreground-game behavior suits you better than Stop Stutter's selected-app lifetime rules. Its documented minimum is macOS 13.

AWDL Toggle keeps your chosen AWDL policy across app closure, logout, and restart. Consider it instead for deliberate manual control through macOS 26 Control Center. Its supplied README describes a local ad-hoc build and a persistent helper, with an uninstaller required for removal. These are replacement controllers, not utilities to layer over Stop Stutter.

How to read the ratings

The ratings are editorial assessments, not benchmark results. The scale runs from 1 for substantial barriers or little supporting evidence to 5 for a straightforward documented path or broad evidence for that dimension; 3 indicates useful support with material limits. Setup considers installation and signing requirements. Documentation considers whether instructions explain operation, limits, and recovery. Community considers visible participation evidence, not stars as a proxy for adoption. Maturity considers release and validation coverage rather than binary availability alone.

Alternatives

ProjectWhat it isPick it when
AWDL ControlA macOS menu-bar controller that can suppress AWDL while the active application is a game.Choose it instead when foreground-game detection and restoration on returning to the desktop fit your use better than selected-app lifetime rules. It requires macOS 13 or later.
AWDL ToggleA macOS 26 Control Center switch whose saved AWDL policy persists across logout and restart.Choose it instead for manual persistent control, accepting its local build, administrator installation, and dedicated uninstall procedure.

What people are saying

  1. [velocity-scout] burakgon/stop-stutter

Sources

  1. Stop Stutter README
  2. Stop Stutter v0.1.0 release
  3. Stop Stutter validation record
  4. Stop Stutter architecture and security notes
  5. Stop Stutter repository

More automation reviews