Search the Community

There seems to be an issue with ¿rendering the last couple of minutes of an episode while steaming to another location. Playback cuts off and I can't get the stream to continue on any time frame. Attached, server log Server log is 61 MB!? https://1drv.ms/t/s!Asn6NNog54FdjIVX35DTwZ8UFJE-Dw Also, see my previous post: http://emby.media/community/index.php?/topic/36884-server-3059850-high-cpu-usage-when-browsing-libraries/ Still not sure if this might be (partially) an new Windows function (probably one of the futures where all so excited about , for anybody remembering the Windows 8.x and 10 introduction mumbo-jumbo ) As a trail I'll start streaming using the latest Pale Moon browser. In my experience one of the most reliable and least resources intensive for the past 5 years.

I update my Emby Server to version 3.0.5985.0 recently and my CPU usage while browsing with Edge has more than doubled. Windows 10 x64 10586.494 Phenom x6 @ 4,1 GHZ 16 GB RAM Furthermore, FYI, I use PhenomMsrTweaker. Under average conditions my PC doesn’t use more power then 170 W, now when browsing Emby it jumps to ~260 W. Also, I keep a close eye on Process Explorer. UPDATE: I seem to have the same issue on my ThinkPad T530 (i5 3230). However it occurred during streaming. Previously I used Emby Server with Emby Theather (old version) on my Server. The high CPU usages occurred while clicking trough serie episodes, about 1 episode every 3s. The high CPU usage on my laptop was gone when I closed Edge. After that Emby Server (the server webpage) streamed 720p/4 MBps without any hiccups or glitches. This might indicate that it has something to do with the Windows 10 x.420 update to x.494? Is anybody here on the Windows 10 'fast ring'? If so what is your experience with Edge while comparing the different builds? UPDATE 2: I had an recurring streaming issue. Attempted to uploud the server log however it's 61 MB. Here is an Onedrive link: https://1drv.ms/t/s!Asn6NNog54FdjIVX35DTwZ8UFJE-Dw.This log includes the time frame where I experienced the 'high CPU usage' issue.