Windows 10 Live Playback Issue

[ppasteur]

Just as a follow-up with a bit of new data:

I just updated to the Version 20201214 (APP)/20201216b(UI).
I also updated the AMD drivers a day ago. Still having the problem.

MF_MEDIA_ENGINE_ERR_DECODE : HRESULT - 0xC00D36F2 error window popup. I close the window and get a black screen with "Unable to play channel: white text.

I have tested bandwidth to the tuners and DVR. All a minimum of 500 Mbps.
I sure do miss using the PC for TV.
Nvidia Shield (2) clients working.
LG B7 OLED client working.
I think Nick mentioned passing this along to the developers. Any word on that...
Though I do understand that your people are slammed with fixing the 4k stuff...

[ppasteur]

I need to do some more testing, but I think I solved my problem. I upgraded the PC from 1909 to the latest 20H2 feature upgrade.
So far the problem with the Windows client freezing and throwing the MF_Media_Engine errors has not happened.

EDIT:
This is not the case. I am back to not being able to use the Win 10 HDHR app at all.


I have been using one channel only though. I watched two different times for about an hour each and have seen no problems.

EDIT

It seems the at times when I start the WIN 10 app and do not change the channel, things are OK. But NOT always. Changing channels results in stuttering, freezing, and display of the MF_Media_Engine error message.
Sometimes the app just fails with a black screen and a message that the source cannot be played.

[JDazell]

I am also experiencing this error on three different Windows10 systems. Two wired one WiFi.
Windows10 v20H2(OS Build 19042.685)
Version 20201227(App)/20201221 (UI)
During Live TV viewing, intermittently the following error will pop up on the
screen interrupting the currently displayed channel
MF_MEDIA_ENGINE_ERR_DECODE:HRESULT - 0xC00D36F2

Has there been any resolution on this continual error?

[tinkerguy]

This is a serious issue - on my brand new ASUS Laptop with 10th Gen intel with Nvidia RTX 2070 Super - HDHomerun DVR windows app installs and runs perfectly. However on getting Windows Update 10 version 20H2. the app shows a blank screen with dialog box MF_MEDIA_ENGINE_ERR_DECODE:HRESULT - 0x80070057.

I backed out 20H2 feature update and the app runs again. Reapply 20H2 and the problem returns so it is a compatibility issue the latest Windows feature update and DVR app.

Note: using Windows own Movies & TV App - the stream can be decoded without issues using DLNA from explorer - so this is not a MPEG decoder issue with the 20H2 version.

Please have your developers investigate this as it prevents a lot of us from moving up to the latest Windows 10 feature release.

[ppasteur]

Using the 20210102 client on Win 10 20H2 things now seem to be working fine. I can get all TV channels and change channels without freezing or crashing. Even ATSC 3 channels are working.
The only change was updating the client to the 0102 level.
BTW the UI rev is 20201230. I do have early access to new features enabled.

One unrelated problem (I think) is that the client cannot see the HDHomerun record server on my Synology NAS. It does see the two Nvidia Shield record engines.
All of my other client do see the Synology record engine. Will open a different topic for this one.

[tinkerguy]

On the hope that the latest 20210102 client helps, I reapplied the Windows 20H2 update. Downloaded the HDHomerun updated client and tried - instant MF_MEDIA_ENGINE_ERR_DECODE : HRESULT - 0x80070057.
So that did not work for me. Everything on the laptop has the latest drivers. The only workable way to view HDHomerun Prime for me is to use the flaky Windows "Movies and TV" app over DLNA. Not great as there is no UI nor support for DRM channels. Now interestingly, a much older desktop running Windows 10 20H2 seems to have no problem with the HDHomerun viewer. So why is it that a new laptop with stock Windows 10 with only updated drivers not work with the latest windows build?

[mudma]

I'm also having this issue. Did they find any resolution? I really like the product but the instability can be quite annoying for sure.

I use the HDHomerunPRIME.