[BUG] Black Screen Issue

[korovindenis]

I am experiencing an issue with the latest version of the application. When I run the client on Windows 10 version 22H2 and guests connect via the provided link, they can only see a black screen instead of the shared content.

Steps to Reproduce:

1. Download and install the latest version of Mira Screen Share.
2. Launch the client on a computer running Windows 10 22H2.
3. Generate a sharing link and share it with guests.
4. Guests click on the link to join the screen sharing session.

Expected Behavior:
Guests should be able to see the shared screen content.

Actual Behavior:
Guests are only seeing a black screen and no shared content is visible.

Environment:

• Mira Screen Share latest version (as of current date)
• Windows 10, version 22H2

Android:

[nlx-404]

Have this exact issue too

[iron-cc]

I'm also having this exact same issue.

[harrynull]

Does it work if the sharer and viewer are on the same device? If it works, then probably there is a firewall restriction etc.

Otherwise, it's likely an issue with the capturing or encoding on the sharer's side, but it is difficult to say what went wrong without debugging it. If you're interested, you can try to compile the sharer with logs on and see if anything suspicious comes up.

[iron-cc]

@harrynull It actually didn't work for me on the same device, and I also tried it in the same network "virtually" through a local virtual machine. Firewalls these days even on default Windows or Mac are really restrictive so I'm not entirely too sure what's going on but wouldn't be surprised if it is firewall related.

Is it possible it's because the TURN server isn't functioning? I also had another question related about that.

I saw it is currently using Twilio, does anything aside from the 2 required API keys need to be changed in order to swap Twilio for CloudFlare Calls? Or is the work more involved then that?

[harrynull]

@iron-cc It's possible. chrome://webrtc-internals should tell you more about the connection status.

I don't know much about CloudFlare Calls. From what I can tell you need some slight modifications on the signaller side to get it working: https://github.com/mira-screen-share/signaller/blob/main/src/state.rs#L155

[seung-gyu-kim]

I have exact issue too

[changchichung]

same here , , not able to see anything even on the same laptop.

[SergeantSerk]

I have tracked the issue down to the following line here, throwing the following error:

...
mira_sharer.exe (28692): Loaded 'C:\Windows\System32\AudioSes.dll'. 
mira_sharer.exe (28692): Loaded 'C:\Windows\System32\ResourcePolicyClient.dll'. 
[2025-03-15T14:46:37.761796000Z INFO mira_sharer::capture::audio] Audio config: SupportedStreamConfig { channels: 8, sample_rate: SampleRate(48000), buffer_size: Range { min: 0, max: 4294967295 }, sample_format: F32 }
[libopus @ 000001fed1338580] No bit rate set. Defaulting to 96000 bps.
[2025-03-15T14:46:37.761874600Z INFO mira_sharer::capture::audio] Begin recording audio
Exception thrown at 0x00007FFE3E02B699 (KernelBase.dll) in mira_sharer.exe: 0x8001010E: The application called an interface that was marshalled for a different thread.
Exception thrown at 0x00007FFE3E02B699 (KernelBase.dll) in mira_sharer.exe: WinRT originate error - 0x8001010E : 'The application called an interface that was marshalled for a different thread.'.
Exception thrown at 0x00007FFE3E02B699 in mira_sharer.exe: Microsoft C++ exception: winrt::hresult_wrong_thread at memory location 0x0000004D557F8580.
Exception thrown at 0x00007FFE3E02B699 in mira_sharer.exe: Microsoft C++ exception: [rethrow] at memory location 0x0000000000000000.
GraphicsCapture.dll!00007FFE0F386984: ReturnHr(1) tid(b19c) 8001010E The application called an interface that was marshalled for a different thread.
    Msg:[winrt::hresult_error: The application called an interface that was marshalled for a different thread.] 

thread 'tokio-runtime-worker' panicked at src\capture\wgc\wgc_capture.rs:40:37:
called `Result::unwrap()` on an `Err` value: Error { code: HRESULT(0x8001010E), message: "The application called an interface that was marshalled for a different thread." }
...

I'm not fluent in Rust nor do I have much knowledge in Windows Graphics Capture API but the issue definitely seems to be from the sharer's side.