Windows 11 can't direct play

[jsm777 1]

Hello,

Fresh install of 4.7.9.0 setup on Debian 11.

Seems to be working correctly but for some reason I am unable to get direct play working on my Windows 11 PC.

Direct play works on my Android Phone and also on my Roku.

I tried using Edge, Chrome and Firefox they all transcode. I tried Emby download from the website and Emby app from Microsoft Store, they also transcode. Every bandwidth setting is on AUTO server side and user side (in the player).

Attached is a picture of the same media playing on Android, Roku, Chrome, Emby Theater and Emby app from windows Store at the same time. Only Android and Roku seem to be able to direct play.

Can anyone tell me what I am missing?

Thank you

 

Edited November 22, 2022 by Happy2Play
edited image

[Abobader 3464]

Hello jsm777,

** This is an auto reply **

Please wait for someone from staff support or our members to reply to you.

It's recommended to provide more info, as it explain in this thread:

Thank you.

Emby Team

[Luke 42078]

Hi, on a remote connection the auto setting can sometimes be on the conservative side. If it's too conservative for you then I would try setting it to a specific value that makes sense for you. Thanks.

[Happy2Play 9780]

"Auto" the majority of the time is the issue as it will be conservative on a Remote connection.

But ffmpeg logs per client and server log are needed but from the image suggest per client playback quality setting.

 

 

[jsm777 1]

Hi,

All clients are on the same network, but the server is on the internet. So Auto works for Roku and Android but not for Windows?

I have tried on the web player on edge, with auto it was 1080p - 6 Mbps, I changed it to 1080p - 15 Mbps then 1080p - 60 Mbps and all 3 settings cause transcoding.

I have attached some logs hopefully these can help.ffmpeg-transcode-8c8b1a0c-9998-47fc-8f6b-423ab0d567e4_1.txtembyserver.txt

Thank you

Edited November 22, 2022 by jsm777

[Luke 42078]

14 minutes ago, jsm777 said:

Hi,

All clients are on the same network, but the server is on the internet. So Auto works for Roku and Android but not for Windows?

I have tried on the web player on edge, with auto it was 1080p - 6 Mbps, I changed it to 1080p - 15 Mbps then 1080p - 60 Mbps and all 3 settings cause transcoding.

I have attached some logs hopefully these can help.ffmpeg-transcode-8c8b1a0c-9998-47fc-8f6b-423ab0d567e4_1.txtembyserver.txt

Thank you

This example is different. Did you explore the stats feature in the video player to learn why it was transcoding? This one tried to direct play, but the browser video player had an error with it, and so the web app automatically switched to transcoding in order to ensure successful playback.

[jsm777 1]

Not sure what you mean by this example is different?

The screenshot of my first post is exactly the same thing I am trying in my reply:

Windows transcodes on - Firefox, Edge, Chrome, Emby theatre and Emby app. Same network as the windows pc - Android and Roku don't transcode.

The server is on the Internet, my PC is wired by the way, not even on wifi.

The log I had attached showed me opening the web player on Edge, changing speeds from Auto to 15 Mbps and 60 Mbps and the server kept transcoding in all 3 cases.

This is what I see in stats in edge with 60 Mbps setting on the web player:

it's the same thing as my first screenshot as far as I can see, I don't understand why it transcodes on Windows but not Android and Roku.

 

Edited November 22, 2022 by jsm777

[Luke 42078]

2 minutes ago, jsm777 said:

Not sure what you mean by this example is different?

The screenshot of my first post is exactly the same thing I am trying in my reply:

Windows transcodes on - Firefox, Edge, Chrome, Emby theatre and Emby app. Same network as the windows pc - Android and Roku don't transcode.

The server is on the Internet, my PC is wired by the way, not even on wifi.

The log I had attached showed me opening the web player on Edge, changing speeds from Auto to 15 Mbps and 60 Mbps and the server kept transcoding in all 3 cases.

This is what I see in stats in edge with 60 Mbps setting on the web player:

it's the same thing as my first screenshot as far as I can see, I don't understand why it transcodes on Windows but not Android and Roku.

 

In other words it transcoded for a different reason other than the quality setting, and so is this one here.

Notice how it says - "converting to compatible container".

Web browsers have limited format support compared to Roku, Android/ios/windows apps etc.

[jsm777 1]

Ok I understand, this a browser limitation.

I tried with emby for windows instead and instead of Auto set it to 1080p - 60 Mbps and I guess that does work:

Thank you very much for your help.

Have a nice day

[Happy2Play 9780]

From the ffmpeg log Chrome

&TranscodeReasons=ContainerNotSupported,DirectPlayError

But browsers will not be as tolerant as devices.  Along with LiveTV variables.

[Luke 42078]

Nowadays MS Edge gives you the best chance of direct play in the browser given that it has both hevc and ac3 audio support. But it doesn't support mpegts so the above example would still transcode.

[Bottles51 74]

Windows 11 needs a hvac add on to play h265 it will cost you I think 2 bucks.

Edited November 22, 2022 by Bottles51

[Happy2Play 9780]

12 minutes ago, Bottles51 said:

Windows 11 needs a hvac add on to play h265 it will cost you I think 2 bucks. Is your videos h265 that you are playing? Try and play the file directly and it will tell you if you need the add-on.

You can still get it for free.  But still won't help with mpegts.

 

Edited November 22, 2022 by Happy2Play

[Luke 42078]

Hi there, did you explore the stats feature in the video player to learn why it was transcoding?