Ffmpeg Chrome/IE 80% CPU vs Edge Chromium 1% CPU

[StreamingJoe 0]

Hi all,

 

First post here.

I'm just noticed that ffmpeg with chrome and IE on windows 10 (latest version of both navigators) use 80% cpu when transcoding while a test with Edge (new chromium based version) does not put ony load on the CPU. FFmpeg is not even running when edge is running.

I'm probably missing something here. I haven"t done any research on the subject yet. I just did a few tests to confirm I'm not having visions :-)

I'll look around for some explanation but if you guys have anything to explain this you're welcome.

 

 

[Luke 42092]

Each browser supports it's own set of media formats. Did you explore the stats feature in the video player to learn why it was transcoding?

[StreamingJoe 0]

Not yet. I'll take a look at that. Thanks

[StreamingJoe 0]

Here is what I see in dashboard.

[Luke 42092]

Does this answer your question?

[StreamingJoe 0]

yep. I haven't touched video formats in a long time. I'm getting back in.

Found a similar issue. I have an intel Graphics 4600 and an i7-4770k. 

https://emby.media/community/index.php?/topic/72848-server-does-not-detect-hardware-decoding-support-h265-on-i5-haswell-qs4600/

[Luke 42092]

It's not an issue, it's just that the browser doesn't support HEVC so that's transcoding.