Support / fallback handling for DRM-protected video playback (e.g., beIN CONNECT black screen)

[CanhK-2103]

Problem or use case

When mirroring an iPhone (iPhone 17 Pro on iOS 26.5) to Windows 11 over a wired USB connection, navigating the home screen and standard applications works smoothly. However, launching streaming apps such as beIN CONNECT immediately results in a completely black screen due to DRM / FairPlay surface capture restrictions. This prevents users from viewing or streaming authorized content through the mirror window.

Proposed behavior

When DRM-protected content is launched in apps like beIN CONNECT:

The stream should either properly display the video surface if supported by protocol-level adjustments, or

Provide a graceful fallback / indicator informing the user that DRM protection is active, rather than showing a silent, unhandled black screen.

Audio should continue to route cleanly over USB even when video frame capture is restricted.

Area

USB / device discovery

Alternatives considered

Reconnecting the USB cable and restarting the driver manager, which does not bypass the DRM surface blackout.

Using third-party wireless AirPlay receivers, which introduces noticeable latency compared to this tool's direct USB D3D11 pipeline.

Scope confirmation

• This request is for wired USB capture and does not require remote-control bypasses.

[RayrenSX]

Thank you very much for taking the time to report this issue and provide such a detailed description.

Regarding DRM-protected applications like beIN CONNECT, I would like to clarify the current technical limitation from iPhoneMirror’s side.

At the moment, iPhoneMirror does not receive any information indicating whether the currently displayed content is DRM-protected. The only data available to the mirror pipeline is the video frame stream and the audio stream provided by the device. There is no metadata or API exposed that allows iPhoneMirror to directly identify “this is FairPlay DRM content”.

The black screen behavior is caused by Apple’s FairPlay DRM system-level protection, which prevents protected video surfaces from being captured. Therefore, this is not a normal iPhoneMirror rendering bug, and a general mirroring application cannot legally bypass this restriction unless Apple provides a supported interface or protocol-level solution.

The only improvement I can realistically implement on iPhoneMirror’s side is to detect situations where the iPhone stops sending video frames (such as the complete black screen scenario you described), or when abnormal audio/video behavior occurs, and then show a helpful notification indicating that a possible FairPlay DRM restriction may be active instead of leaving the user with an unexplained black screen.

Thank you again for this valuable issue report. I will keep this issue open until either:

a better technical solution is found to handle this situation, or
it is conclusively confirmed that this limitation cannot be solved due to Apple’s DRM restrictions.

[RayrenSX]

Thank you again for the detailed report. I have now implemented the graceful fallback/indicator proposed in this issue.

What has changed

• iPhoneMirror first waits until the session has displayed normal video frames.

• If the decoded video then remains near-black for at least 8 seconds and 24 sampled frames, a compact warning is shown:

  Is the current video cast working correctly?
  The current video has remained black.
  This may be related to DRM / FairPlay or another content-protection mechanism.

• Audio is not required to trigger the warning. In practice, DRM-restricted playback may continue sending USB audio, or audio may also be unavailable. The warning therefore reports the observed audio state separately.

• When normal video frames return, the warning and preview overlay close automatically while the mirroring session remains connected.

• To reduce false positives, detection includes session warm-up, duration/frame-count thresholds, luma checks, and neutral-chroma checks.

This is still a heuristic because iOS does not expose FairPlay/DRM metadata to iPhoneMirror. A long black scene, an all-black page, the lock screen, or a decoder/video-output failure can look similar, so the UI deliberately says that content protection may be involved rather than claiming that DRM was definitively detected.

This change does not bypass FairPlay or make a protected video surface capturable when iOS refuses to provide it. It addresses the unexplained black-screen behavior with a clear, recoverable fallback.

The implementation and automated tests are complete locally. I will keep this issue open until the change is included in a release and can be verified with beIN CONNECT. After confirmation, this issue can be closed as completed for the graceful-fallback scope; actual playback of protected video remains dependent on Apple providing a supported capture path.