If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
|
Thread Tools | Rate Thread | Display Modes |
#16
|
|||
|
|||
Miracast?
On Sun, 10 Feb 2019 15:46:21 -0500, Paul
wrote: Peter Jason wrote: On Sat, 09 Feb 2019 00:40:43 -0500, Paul wrote: Peter Jason wrote: On Tue, 05 Feb 2019 22:43:08 -0500, Paul wrote: Peter Jason wrote: I'm trying to get devices paired to my main computer, but I get the following...... "The device does'nt support Miracast, so you can't project to it wirelessly. Version: 10.0.17763.1 (Beta Release)" Does the computer need another driver? https://www.tenforums.com/tutorials/...ows-10-pc.html Miracast requirements: * Graphics driver must support Windows Display Driver Model (WDDM) 1.3 with Miracast support * Wi-Fi driver must support Network Driver Interface Specification (NDIS) 6.30 and Wi-Fi Direct === shoots direct from src PC to dest TV [WiDi] * Windows 8.1 or Windows 10 OPTION ONE Check Miracast Support on Windows 10 PC To check if Windows 10 PC supports Miracast using Connect app 1. Open the Connect app. OPTION TWO Check Miracast Support on Windows 10 PC To check if Windows 10 PC supports Miracast using DXDIAG 1) Start : Run : dxdiag 2) Save as dxdiag.txt 3) Notepad dxdiag.txt, "Miracast: Available with HDCP" The HDCP means the image is encrypted in transit to the TV, to prevent "pirating". https://www.tenforums.com/tutorials/...dows-10-a.html Paul I fixed it by buying a Bluetooth "Dongle" and plugging in to a USB socket, The TV should have been sending a signal that Windows can see, via Wifi. The Bluetooth should not have been absolutely essential. Once the TV is set to Miracast as a "source", its Wifi interface should switch modes in response (and beacon for a Miracast source). What driver are you using for the GTX 1050 ? The driver I'm using (at least 417) has conflicting support like yours showed. I have a Bluetooth dongle I can plug in, to make Windows happy, so I suppose I could rerun DXDiag and get another DXDiag.txt. OK, I plugged in my Bluetooth and the status is still the same. ------------------ System Information ------------------ Miracast: Available, with HDCP --------------- Display Devices --------------- Miracast: Not Supported Windows is (apparently) supposed to support Miracast Source or Miracast Sink, but I don't necessarily have enough materials to test. It might mean I don't need a TV set to test it. I'd need a Wifi card for the desktop to test. In release 1607, it got Miracast Sink capability. https://www.laptopmag.com/articles/t...irelss-display The GTX 1050 has one NVenc block onboard, which means that if the software wanted to, it has an H.264 encoding device that can run at 330 FPS or so. Which should be sufficient to give Miracast encoding with less CPU than you would normally expect. You can fire up Task Manager in Windows 10, and if your WDDM driver is recent enough, there should be an "activity pane" for the GPU, and in there you can check and see if NVEnc is being used for Miracast transmission. So if it's running, what's the quality like ? Run any movies across it ? That would be the acid test. Paul Thanks Paul, the dongle works OK for my needs (no TV at this stage) but it's rater slow. I should have bought the expensive one ($40) instead of the cheap $14 one. Anyway my TV is over 12 years old and has no provision for miracast which I thought was necessary for Bluetooth. I've filed all this for when I upgrade my TV soon. If you have two well-equipped desktops with Wifi cards in them, you can always try Miracast Sink on one of them, then go over to the other PC and try Miracast Source. It's a long shot, but who knows, it might work at some level. I'm only mentioning that, because an article claimed both modes were available. I don't see a practical reason to use it, other than to "prove out" the hardware paths as being viable. I don't have a second PC "gnarly" enough to use. I only have one "supported" video card in the house now, purchased at the end of 2018. Previously, no video card was still in support. And the GTX1050 is as low as you want to go. The GT1030 is too low end for me to recommend to any prospective upgrader. With the GTX1050, even if not gaming, you get NVenc, and it could be used to compress H.264 for Miracast usage. The GT1030 is a "crap trap", an unnecessary offering on the market. Paul Mt GTX1050 is working OK. Lucky the computer shop was out of stock of the GTX1030s when I had to replace my old video card. |
Ads |
#17
|
|||
|
|||
Miracast?
Peter Jason wrote:
Mt GTX1050 is working OK. Lucky the computer shop was out of stock of the GTX1030s when I had to replace my old video card. Ouch! Dodged a bullet :-) Paul |
#18
|
|||
|
|||
Miracast?
Peter Jason wrote:
On Sat, 09 Feb 2019 00:40:43 -0500, Paul wrote: Peter Jason wrote: On Tue, 05 Feb 2019 22:43:08 -0500, Paul wrote: Peter Jason wrote: I'm trying to get devices paired to my main computer, but I get the following...... "The device does'nt support Miracast, so you can't project to it wirelessly. Version: 10.0.17763.1 (Beta Release)" Does the computer need another driver? https://www.tenforums.com/tutorials/...ows-10-pc.html Miracast requirements: * Graphics driver must support Windows Display Driver Model (WDDM) 1.3 with Miracast support * Wi-Fi driver must support Network Driver Interface Specification (NDIS) 6.30 and Wi-Fi Direct === shoots direct from src PC to dest TV [WiDi] * Windows 8.1 or Windows 10 OPTION ONE Check Miracast Support on Windows 10 PC To check if Windows 10 PC supports Miracast using Connect app 1. Open the Connect app. OPTION TWO Check Miracast Support on Windows 10 PC To check if Windows 10 PC supports Miracast using DXDIAG 1) Start : Run : dxdiag 2) Save as dxdiag.txt 3) Notepad dxdiag.txt, "Miracast: Available with HDCP" The HDCP means the image is encrypted in transit to the TV, to prevent "pirating". https://www.tenforums.com/tutorials/...dows-10-a.html Paul I fixed it by buying a Bluetooth "Dongle" and plugging in to a USB socket, The TV should have been sending a signal that Windows can see, via Wifi. The Bluetooth should not have been absolutely essential. Once the TV is set to Miracast as a "source", its Wifi interface should switch modes in response (and beacon for a Miracast source). What driver are you using for the GTX 1050 ? The driver I'm using (at least 417) has conflicting support like yours showed. I have a Bluetooth dongle I can plug in, to make Windows happy, so I suppose I could rerun DXDiag and get another DXDiag.txt. OK, I plugged in my Bluetooth and the status is still the same. ------------------ System Information ------------------ Miracast: Available, with HDCP --------------- Display Devices --------------- Miracast: Not Supported Windows is (apparently) supposed to support Miracast Source or Miracast Sink, but I don't necessarily have enough materials to test. It might mean I don't need a TV set to test it. I'd need a Wifi card for the desktop to test. In release 1607, it got Miracast Sink capability. https://www.laptopmag.com/articles/t...irelss-display The GTX 1050 has one NVenc block onboard, which means that if the software wanted to, it has an H.264 encoding device that can run at 330 FPS or so. Which should be sufficient to give Miracast encoding with less CPU than you would normally expect. You can fire up Task Manager in Windows 10, and if your WDDM driver is recent enough, there should be an "activity pane" for the GPU, and in there you can check and see if NVEnc is being used for Miracast transmission. So if it's running, what's the quality like ? Run any movies across it ? That would be the acid test. Paul Thanks Paul, the dongle works OK for my needs (no TV at this stage) but it's rater slow. I should have bought the expensive one ($40) instead of the cheap $14 one. Anyway my TV is over 12 years old and has no provision for miracast which I thought was necessary for Bluetooth. I've filed all this for when I upgrade my TV soon. There is a Miracast Receiver you can buy and attach to a TV set. But it's too expensive. It might be 1920x1080. (I think there's a ChromeCast from Google that is 4K by comparison.) Microsoft Wireless Display Adapter https://www.microsoft.com/accessorie...kit-highlights It should really be down in the "RPi Zero" price range. Paul |
#19
|
|||
|
|||
Miracast?
Paul wrote:
If you have two well-equipped desktops with Wifi cards in them, you can always try Miracast Sink on one of them, then go over to the other PC and try Miracast Source. It's a long shot, but who knows, it might work at some level. While I have succeeded in "projecting" an Android tablet and a Win10 laptop to a Samsung TV, I've failed to project from the tablet to the laptop. Actually it was my previous laptop that worked to the TV, this one goes through the motions but the TV-end eventually craps out. |
|
Thread Tools | |
Display Modes | Rate This Thread |
|
|