JustPaste.it

Field Notes: QCPlayerPlus (app) refusing to play video on macOS

I sat down to do a very simple thing: open a couple of local video files and check how they behave outside my usual toolchain. Nothing exotic — MP4, H.264, one HEVC clip. The app in question, judging by the slug, is QCPlayerPlus (app), distributed under the OrchardKit umbrella. Lightweight media player, not a full editing suite. Perfect for a quick check.

This was on a MacBook Air M1, macOS Sonoma 14.2. Clean system, no weird hacks, Gatekeeper intact. I expected a boring ten minutes.

Instead, I got a player window that opened just fine… and then refused to show video.

What broke

The UI loaded. Timeline was there. Play button responded. Audio played immediately, loud and clear. But the video area stayed stubbornly black. No error dialogs, no crash, no spinning beachball. Just audio over a void.

At first glance it looked like a codec issue, but the same files played perfectly in QuickTime and IINA. So not that.

First attempt: codecs and formats (dead end)

Old habit kicked in. I re-encoded one of the files to plain H.264 baseline. Same result. I tried a different container. Same. Even dragged in a low-res test clip I keep around specifically for debugging players.

Still black video.

At this point I was confident the problem wasn’t the media.

Second attempt: permissions, because macOS

Next guess was permissions. Sonoma is very aggressive about media-related access, especially when screen recording or hardware acceleration is involved.

I went to System Settings → Privacy & Security and checked everything remotely relevant. Files and Folders, Media & Apple Music, Screen Recording (even though this wasn’t a capture app). Nothing obvious. The app wasn’t even listed in most categories, which already felt suspicious.

Apple’s own explanation of how privacy permissions are granted (and sometimes not granted) is here:
https://support.apple.com/en-us/HT211970

Restarted the app. Restarted the Mac. Same black rectangle.

Third attempt: hardware acceleration toggle (almost)

Digging through the settings, I noticed a small checkbox related to hardware decoding. It was enabled by default. I disabled it, relaunched, and… brief flicker of video, then black again. Progress, but not a solution.

This is usually where I’d assume “early build, GPU path is broken” and move on. But the behavior was too consistent. The app clearly thought it was rendering video.

What actually worked

The breakthrough came from something mundane: running the app once from Terminal.

When launched that way, macOS finally printed a warning about blocked GPU access tied to code signing and notarization. Nothing dramatic, just a single line hinting that the process didn’t get full hardware decode privileges.

Apple documents this exact class of issues on the developer side:
https://developer.apple.com/documentation/security/notarizing_macos_software_before_distribution

The fix, from a user perspective, was straightforward:

  1. Quit the app.

  2. Go to System Settings → Privacy & Security.

  3. Scroll down to the security section where macOS lists recently blocked items.

  4. Allow the app explicitly, then relaunch.

This time the video appeared instantly. Smooth playback, proper scaling, no glitches. Hardware acceleration stayed on, CPU usage dropped to normal levels.

I bookmarked this page because it matched the same behavior on recent macOS builds and helped confirm I wasn’t chasing ghosts:
https://proguntalk.com/video/16709-qcplayerplus.html

What I’d do immediately next time

If I were setting this up again, I wouldn’t touch codecs or re-encoding at all. I’d install the app, launch it once, then immediately check Privacy & Security for silent blocks before assuming anything is “broken.”

macOS has gotten very good at failing politely — sometimes too polite. No alerts, no dialogs, just missing functionality until you know where to look.

Final note

Once the permission issue was resolved, QCPlayerPlus behaved exactly like a normal, competent video player. No drama. No mysterious bugs. Just macOS doing its thing and expecting the user to read its mind a little.

If you ever get audio without video on an otherwise sane system, don’t start blaming formats or files. Sometimes the system simply hasn’t decided it trusts the app yet — and it won’t tell you unless you go looking.