Chrome using Emby on loopback 127.0.0.1 gives Playback Error No compatible streams are currently available.

[Jake.Yde 0]

I'm trying to play a local file that I created "Unforgiven (1992).m4v" on Emby using a the Windows server ran as a service Version 4.4.0.40 using the loopback IP 127.0.0.1:8096 on Google Chrome Version 80.0.3987.149 (Official Build) (64-bit). However the file errors out giving "Playback Error No compatible streams are currently available. Please try again later or contact your system administrator for details."

Steps to recreate error:
I open Chrome.

Go to webpage

On home screen of Emby server I scroll to right on the list of recently added media files

Click on play icon for movie

Trailer plays

Loading Icon displays

Error message pops up

Restart server: issue unchanged

Try Localhost instead of loopback IP: Issue unchanged
Try different file: same issue

Try another file: Plays fine
Try original file in VLC 3.0.8: Plays fine
Try original file in Microsoft Edge 44.18362.449.0: Plays fine
Scratch head, search forums, decide to create new post per https://emby.media/community/index.php?/topic/739-how-to-report-a-problem/

I have no idea what's going on. It usually seems to be a chrome issue. Maybe you guys can help me figure out what's going on. If any more details are needed, just let me know.

embyserver.txt

ffmpeg-transcode-84644f90-766f-47aa-b6a3-0ef5c47a634b_1.txt

ffmpeg-transcode-3d526a7a-9a85-47ee-a0c0-534fb5151329_1.txt

ffmpeg-remux-23a7163c-8e42-4e43-bc23-08ceaf0352b4_1.txt

[Luke 42083]

Hi,yes there's an issue with transcoding m4v's in the 4.4 release. we'll be pushing out a 4.4.1 update to resolve this. Thanks.

[Jake.Yde 0]

Hi,yes there's an issue with transcoding m4v's in the 4.4 release. we'll be pushing out a 4.4.1 update to resolve this. Thanks.

It should be noted that everything is working as expected in Edge, for whatever reason. Nevermind I take that back. One browser plays one file, another plays another. It's chaos.

Edited March 27, 2020 by Jake.Yde

[Luke 42083]

If the browser can direct play the file it will work just fine. If it can't and some kind of conversion is needed, then that's when you'll run into the issue that I mentioned.