A Windows XP help forum. PCbanter

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.

Go Back   Home » PCbanter forum » Windows 10 » Windows 10 Help Forum
Site Map Home Register Authors List Search Today's Posts Mark Forums Read Web Partners

Miracast?



 
 
Thread Tools Rate Thread Display Modes
  #1  
Old February 6th 19, 01:38 AM posted to alt.comp.os.windows-10
Peter Jason
external usenet poster
 
Posts: 2,310
Default Miracast?

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?
Ads
  #2  
Old February 6th 19, 02:38 AM posted to alt.comp.os.windows-10
Keith Nuttle
external usenet poster
 
Posts: 1,844
Default Miracast?

On 2/5/2019 7:38 PM, 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?

I don't know if this will help, but I believe I had the same problem and
suspect it is something the MS has done to my computer. The reason I
suspect MS is it was working on Saturday and I have not made any
adjustments to the TV.

I could not project to my smart TV. I reset the Wireless router but
that did nothing.

I went through and deleted the TV from devices. Restarted the TV and
Went to Add Devices and added back the TV. It took care of the problem.


--
2018: The year we learn to play the great game of Euchre
  #3  
Old February 6th 19, 04:43 AM posted to alt.comp.os.windows-10
Paul[_32_]
external usenet poster
 
Posts: 11,873
Default Miracast?

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
  #4  
Old February 6th 19, 07:55 AM posted to alt.comp.os.windows-10
Peter Jason
external usenet poster
 
Posts: 2,310
Default Miracast?

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


My very old (2011) computer seems to lack a
"Bluetooth Adapter"
https://www.google.com/search?as_st=... =&as_rights=
I'll buy one of these then try again.
  #5  
Old February 6th 19, 08:28 AM posted to alt.comp.os.windows-10
Paul[_32_]
external usenet poster
 
Posts: 11,873
Default Miracast?

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


My very old (2011) computer seems to lack a
"Bluetooth Adapter"
https://www.google.com/search?as_st=... =&as_rights=
I'll buy one of these then try again.


Does it need Bluetooth for pairing ?

I would have thought some sort of SSID was involved
for the WiDi ?

WiDi is a direct Wifi protocol between the source
device and the destination device, that doesn't use
the router. The purpose of the direct connection is
for efficiency for the high bandwidth application
of screencasting.

I would start here, to get some feeling for the pairing process,
if that's where you're stuck.

https://en.wikipedia.org/wiki/Wi-Fi_Direct

Wi-Fi Direct is single radio hop communication

Wi-Fi Direct negotiates the link with a Wi-Fi Protected Setup (WPS)
system that assigns each device a limited wireless access point.
The "pairing" of Wi-Fi Direct devices can be set up to require
the proximity of a near field communication (NFC), a Bluetooth signal (BT),
or a button press on one or all the devices (likely WPS?).

NFC requires a probing signal from a querying device, to
detect an adjacent NFC device.

"NFC employs electromagnetic induction between two loop antennas
... ISM band of 13.56 MHz"

So that would not interfere with the main broadcast.

If you have USB3, that can interfere with 2.4GHz Wifi activity.
It requires an active connection to a poorly shielded external
device (like a disk drive), to provide enough antenna to spew
signal into your Miracast attempt. That wouldn't necessarily
kill the setup though. Just make for miserable results.

Bluetooth operates in 2.4GHz and is frequency hopping spread spectrum.
It likely interferes a tiny bit with 2.4GHz transmission, and
not with 5GHz. I don't think any attempt has been made to
move Bluetooth into 5GHz to mess it up too :-)

Maybe a WPS button on a television, could be the start of Miracast.

https://en.wikipedia.org/wiki/Wi-Fi_Protected_Setup

Or the TV could have an NFC chip, and maybe an Android with
casting capability to probe the NFC and get identity info
about the TV and that it's Miracast ready.

Using Bluetooth pairing, like if the TV had a pairing
procedure, and you added a Bluetooth short dongle to
your desktop computer, that might work to establish the
setup of the connection. Once the connection is running,
further Bluetooth RF activity would not be needed.

*******

And when you ask questions like this, you can trim a lot
of effort off the answers by *specifying the TV make and model*.
The manual is full of helpful suggestions, and I download
the manual and have a look for keywords that might indicate
what flavor of tech the TV has got. That's better than me
enumerating the raft of possible suggestions, and then
I can focus on what's in this TV. For example, if
the TV didn't have Bluetooth for some reason (unlikely),
then buying a BT dongle would be a waste of time. You never
know what the latest fad is on TV sets.

For Wifi devices, they use "channel numbers". There are,
say, 13 or 14 channels, where about three of the channels
can be selected for their "non-overlapping" behavior. For
the WiDi devices to see one another, it would help if they
were on the same channel. I don't know what the practice is,
whether a certain channel is preferred by protocol design,
or it's up to the user to scoot them all onto the same channel.
If your regular router was on Channel 1 for example,
and there were movie downloads between the router and
computer number 2, then I'd want my Miracast on Channel 13
between computer number 1 and the TV, and that way you get
the best usage of the local RF spectrum.

I also have no idea, what networking options exist on your
desktop computer, when it uses WiDi and Miracast on its
only wireless interface. Can you be downloading movies
from the router via the Internet at the same time ?
Are two Wifi interface cards required, one for WiDi,
one for Wifi ? These are things you need to test once
the basic connection is established. I can't see it
being very practical to multiplex the two activities
through the same piece of hardware.

Paul
  #6  
Old February 6th 19, 11:45 AM posted to alt.comp.os.windows-10
Andy Burns[_6_]
external usenet poster
 
Posts: 1,318
Default Miracast?

Peter Jason wrote:

The device does'nt support Miracast, so you can't
project to it wirelessly.

In my experience, even when it works it's low resolution, laggy and
jittery so you won't want to use it :-(
  #7  
Old February 6th 19, 11:46 AM posted to alt.comp.os.windows-10
Andy Burns[_6_]
external usenet poster
 
Posts: 1,318
Default Miracast?

Peter Jason wrote:

My very old (2011) computer seems to lack a
"Bluetooth Adapter"


Miracast happens over wifi, not over bluetooth
  #8  
Old February 6th 19, 02:36 PM posted to alt.comp.os.windows-10
Keith Nuttle
external usenet poster
 
Posts: 1,844
Default Miracast?

On 2/6/2019 5:45 AM, Andy Burns wrote:
Peter Jason wrote:

The device does'nt support Miracast, so you can't
project to it wirelessly.

In my experience, even when it works it's low resolution, laggy and
jittery so you won't want to use it :-


The ability to project to a TV is a native function of my two year old
HP computer. It gives images as good as those on my computer only at
50" instead of 15'. If you have a need to project the pictures to your
tv, it is a great way for several people to view the pictures.

My wife is the chair of the hanging committee for a local art
association, and must review the work of many artist as part of that
job. I project those paintings to our 50" tv and get great images for
judging the quality of the paintings and photographs. There are multiple
people in these judging sessions. I also use it for family slide
presentations.

If you find you can not project from your computer, can you use a
thumbdrive with the pictures on your TV?


--
2018: The year we learn to play the great game of Euchre
  #9  
Old February 6th 19, 07:23 PM posted to alt.comp.os.windows-10
Paul[_32_]
external usenet poster
 
Posts: 11,873
Default Miracast?

Keith Nuttle wrote:
On 2/6/2019 5:45 AM, Andy Burns wrote:
Peter Jason wrote:

The device does'nt support Miracast, so you can't
project to it wirelessly.

In my experience, even when it works it's low resolution, laggy and
jittery so you won't want to use it :-


The ability to project to a TV is a native function of my two year old
HP computer. It gives images as good as those on my computer only at
50" instead of 15'. If you have a need to project the pictures to your
tv, it is a great way for several people to view the pictures.

My wife is the chair of the hanging committee for a local art
association, and must review the work of many artist as part of that
job. I project those paintings to our 50" tv and get great images for
judging the quality of the paintings and photographs. There are multiple
people in these judging sessions. I also use it for family slide
presentations.

If you find you can not project from your computer, can you use a
thumbdrive with the pictures on your TV?


You could get better results with an HDMI remote transmitter.
It consists of a point to point 60GHz Wifi, which delivers up
to 700MB/sec when the PC and TV are in the same room. That's
the best way to avoid compression artifacts, jag and jitter.

The following reference is just to demonstrate a pair. This
company was bought out by another company, and it's hard to tell
whether they're still retailing or not. Generally Gefen products
were high-end stuff (there was always a cheaper Chinese item).
It's even possible the chips to make these, have gone
out of production.

https://www.gefen.com/product/wirele...em-GTV-WHD-60G

And that doesn't interfere with your regular Wifi B/G/N/AC.
60GHz doesn't penetrate walls, or even like to go through
doorways. While the reach is claimed to be 33 feet, usually
the output speed has dropped at that distance, and some
fraction of that distance gives full rate.

But that should look better than Miracast.

They make more ambitious ones, but these probably compress
on the fly. The one above comes closest to transmitting
without compression.

https://www.amazon.com/SIIG-Wireless.../dp/B07J56LJ31

Paul

  #10  
Old February 6th 19, 11:34 PM posted to alt.comp.os.windows-10
Paul[_32_]
external usenet poster
 
Posts: 11,873
Default Miracast?

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


Thanks, I ran it and..............

********* dxdiag
---------------
Display Devices
---------------
Card name: NVIDIA GeForce GTX 1050
Manufacturer: NVIDIA

Driver Model: WDDM 2.3

Miracast: Not Supported


That's the same problem I have here, only my WDDM is
a different version, and still Miracast is listed as
Not Supported in that section of the dxdiag.txt report.

*******

Next, try here.

https://answers.microsoft.com/en-us/...52fd22#?page=2

netsh wlan show drivers

Wireless Display Supported: Yes
Graphics Driver: Yes
Wi-Fi Driver: Yes

I can't do that, because the Test PC has no Wifi.

Paul
  #11  
Old February 7th 19, 12:13 AM posted to alt.comp.os.windows-10
Paul[_32_]
external usenet poster
 
Posts: 11,873
Default Miracast?

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


Thanks, I ran it and..............

********* dxdiag
---------------
Display Devices
---------------
Card name: NVIDIA GeForce GTX 1050
Manufacturer: NVIDIA

Driver Model: WDDM 2.3

Miracast: Not Supported


Found another answer.

https://forums.tomsguide.com/threads...racast.140136/

"it is not only the wifi card that could be the issue, it could
also be the graphics card. Nvidia cut support for miracast over
a year ago, so any new drivers will not make it work. I rolled
mine back to 350.12

(http://www.nvidia.com/download/drive...px/83819/en-us)

and after that, miracast worked flawlessly"

Now, all you need is a painless way to migrate to a different driver.
You could clone over your OS to another drive, then do the
experimental driver test there. Or, do a backup of the current
device, and try the experiment. Then, doing a restore if for
some reason you can't get things back the way they were.

While it is possible to change drivers (I've done it, and it's
not a big deal), I also go into Task Scheduler and disable
some of the NVidia stuff afterwards. Stuff that doesn't belong
there. I have to go back to Task Scheduler and make note of the
current settings, so I know what to do after a different
driver is installed (which will undo my changes).

Paul
  #12  
Old February 9th 19, 04:00 AM posted to alt.comp.os.windows-10
Peter Jason
external usenet poster
 
Posts: 2,310
Default Miracast?

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,

  #13  
Old February 9th 19, 06:40 AM posted to alt.comp.os.windows-10
Paul[_32_]
external usenet poster
 
Posts: 11,873
Default Miracast?

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
  #14  
Old February 10th 19, 09:39 PM posted to alt.comp.os.windows-10
Peter Jason
external usenet poster
 
Posts: 2,310
Default Miracast?

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.
  #15  
Old February 10th 19, 09:46 PM posted to alt.comp.os.windows-10
Paul[_32_]
external usenet poster
 
Posts: 11,873
Default 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.


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
 




Thread Tools
Display Modes Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off






All times are GMT +1. The time now is 02:34 PM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 PCbanter.
The comments are property of their posters.