-
Notifications
You must be signed in to change notification settings - Fork 105
Black screen in desktop-source-test #178
Comments
@githaff Hi, did you find a solution to this problem? |
@majkrzak hi. I haven't. It was just an investigation of what is possible, for non-critical stuff. So had to abandon it. |
What I see is that both devices I've checked are detecting WDA dongle as a 1080p60, when trying to choose this resolution 303 repose is returned, at the other hand when choosing other from available black screen is seen and device is still detected as 1080p60. @microsoft any comments? |
Same results here. |
I have towo candidates, first barley possible is lack of audio codec setup,
second wrong gstreamar output format.
pon., 29 paź 2018, 23:47 użytkownik Marcos Alfredo Núñez <
[email protected]> napisał:
… Same results here.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#178 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AC7EUrtUB-40wMXk8M7h7J5t968FWVxpks5up3d6gaJpZM4PBd03>
.
|
@majkrzak any breakthroughs? I'm still giving this a try from time to time, but I can't seem to get this to work. I've modified the debian_source_test code a bit, limiting the resolution options, yet I keep hitting the same black screen. |
Has anybody found a solution? I get this with a Sony TV as a sink. |
I've dumped transmission of windows 10 connecting to Microsoft Wireless
Display. There is no anything special there except audio negotiation. I
would say that gstreamer may not encode stream correctly.
|
This is possible. I tried changing the |
I had an idea to emit stream itself with vlc after proper negotiation. |
I am trying to connect to the Microsoft Wireless Display Adapter. It connects ok. But after that, all I see is a black screen. Both when I use WFD_DESKTOP pipeline and WFD_TEST_VIDEO. Using --gst-debug-level=4 I can see that frames are sent. What can I do wrong? What can I do to investigate the source of the problem?
Log: wds-black-screen-log.txt
The text was updated successfully, but these errors were encountered: