Stuttering playing back from Centos 8 to Chromecast Google TV

[silencerny 0]

Here are the logs:

2020-11-04 00:29:48.480 Info SessionManager: Playback start reported by app AndroidTv 1.8.28g playing ******************. Started at 1860592 ms
2020-11-04 00:29:48.481 Info HttpServer: HTTP Response 204 to 192.168.1.101. Time: 1ms. http://192.168.1.192:8096/emby/Sessions/Playing. ConnectionId: 0HM406NF3TTAL
2020-11-04 00:29:48.599 Info HttpServer: HTTP GET http://192.168.1.192:8096/emby/videos/45851/stream.mkv?DeviceId=efa439dcf2081ac3&MediaSourceId=15545861271425de474e88f69e165ea5&Static=true&PlaySessionId=bbcbd782b15741c8863551f273a4ef03. Connection=Keep-Alive, Accept-Encoding=identity, Host=192.168.1.192:8096, User-Agent=Emby/1.8.28g (Linux;Android 10) ExoPlayerLib/2.11.4, Icy-MetaData=1
2020-11-04 00:29:48.614 Info HttpServer: HTTP GET http://192.168.1.192:8096/emby/Items/45851/ThumbnailSet?format=json. UserAgent: Dalvik/2.1.0 (Linux; U; Android 10; Chromecast Build/QTS2.200917.005)
2020-11-04 00:30:13.611 Info HttpServer: HTTP GET http://192.168.1.192:8096/emby/videos/45851/stream.mkv?DeviceId=efa439dcf2081ac3&MediaSourceId=15545861271425de474e88f69e165ea5&Static=true&PlaySessionId=bbcbd782b15741c8863551f273a4ef03. Connection=Keep-Alive, Accept-Encoding=identity, Host=192.168.1.192:8096, User-Agent=Emby/1.8.28g (Linux;Android 10) ExoPlayerLib/2.11.4, Icy-MetaData=1
2020-11-04 00:30:39.628 Info HttpServer: HTTP GET http://192.168.1.192:8096/emby/videos/45851/stream.mkv?DeviceId=efa439dcf2081ac3&MediaSourceId=15545861271425de474e88f69e165ea5&Static=true&PlaySessionId=bbcbd782b15741c8863551f273a4ef03. Connection=Keep-Alive, Accept-Encoding=identity, Host=192.168.1.192:8096, User-Agent=Emby/1.8.28g (Linux;Android 10) ExoPlayerLib/2.11.4, Icy-MetaData=1
2020-11-04 00:30:41.353 Info HttpServer: HTTP Response 500 to 192.168.1.101. Time: 52740ms. http://192.168.1.192:8096/emby/Items/45851/ThumbnailSet?format=json. ConnectionId: 0HM406NF3TTAL
2020-11-04 00:30:41.353 Info HttpServer: HTTP Response 500 to 192.168.1.101. Time: 52754ms. http://192.168.1.192:8096/emby/videos/45851/stream.mkv?DeviceId=efa439dcf2081ac3&MediaSourceId=15545861271425de474e88f69e165ea5&Static=true&PlaySessionId=bbcbd782b15741c8863551f273a4ef03. ConnectionId: 0HM406NF3TTCM
2020-11-04 00:30:41.353 Info HttpServer: HTTP Response 500 to 192.168.1.101. Time: 27743ms. http://192.168.1.192:8096/emby/videos/45851/stream.mkv?DeviceId=efa439dcf2081ac3&MediaSourceId=15545861271425de474e88f69e165ea5&Static=true&PlaySessionId=bbcbd782b15741c8863551f273a4ef03. ConnectionId: 0HM406NF3TTCN
2020-11-04 00:30:41.793 Info HttpServer: HTTP Response 200 to 192.168.1.101. Time: 2165ms. http://192.168.1.192:8096/emby/videos/45851/stream.mkv?DeviceId=efa439dcf2081ac3&MediaSourceId=15545861271425de474e88f69e165ea5&Static=true&PlaySessionId=bbcbd782b15741c8863551f273a4ef03. ConnectionId: 0HM406NF3TTCO
2020-11-04 00:30:41.804 Info HttpServer: HTTP GET http://192.168.1.192:8096/emby/videos/45851/stream.mkv?DeviceId=efa439dcf2081ac3&MediaSourceId=15545861271425de474e88f69e165ea5&Static=true&PlaySessionId=bbcbd782b15741c8863551f273a4ef03. Connection=Keep-Alive, Accept-Encoding=identity, Host=192.168.1.192:8096, Range=bytes=7973357428-, User-Agent=Emby/1.8.28g (Linux;Android 10) ExoPlayerLib/2.11.4, Icy-MetaData=1
2020-11-04 00:30:41.805 Info HttpServer: HTTP Response 206 to 192.168.1.101. Time: 1ms. http://192.168.1.192:8096/emby/videos/45851/stream.mkv?DeviceId=efa439dcf2081ac3&MediaSourceId=15545861271425de474e88f69e165ea5&Static=true&PlaySessionId=bbcbd782b15741c8863551f273a4ef03. ConnectionId: 0HM406NF3TTCP
2020-11-04 00:30:42.121 Info HttpServer: HTTP GET http://192.168.1.192:8096/emby/videos/45851/stream.mkv?DeviceId=efa439dcf2081ac3&MediaSourceId=15545861271425de474e88f69e165ea5&Static=true&PlaySessionId=bbcbd782b15741c8863551f273a4ef03. Connection=Keep-Alive, Accept-Encoding=identity, Host=192.168.1.192:8096, Range=bytes=7048-, User-Agent=Emby/1.8.28g (Linux;Android 10) ExoPlayerLib/2.11.4, Icy-MetaData=1
2020-11-04 00:30:43.440 Info HttpServer: HTTP GET http://192.168.1.192:8096/emby/Items/45851/ThumbnailSet?format=json. UserAgent: Dalvik/2.1.0 (Linux; U; Android 10; Chromecast Build/QTS2.200917.005)
2020-11-04 00:30:43.441 Info HttpServer: HTTP Response 200 to 192.168.1.101. Time: 1ms. http://192.168.1.192:8096/emby/Items/45851/ThumbnailSet?format=json. ConnectionId: 0HM406NF3TTCK
2020-11-04 00:30:43.561 Info HttpServer: HTTP Response 206 to 192.168.1.101. Time: 1440ms. http://192.168.1.192:8096/emby/videos/45851/stream.mkv?DeviceId=efa439dcf2081ac3&MediaSourceId=15545861271425de474e88f69e165ea5&Static=true&PlaySessionId=bbcbd782b15741c8863551f273a4ef03. ConnectionId: 0HM406NF3TTCP
2020-11-04 00:30:43.639 Info HttpServer: HTTP GET http://192.168.1.192:8096/emby/videos/45851/stream.mkv?DeviceId=efa439dcf2081ac3&MediaSourceId=15545861271425de474e88f69e165ea5&Static=true&PlaySessionId=bbcbd782b15741c8863551f273a4ef03. Connection=Keep-Alive, Accept-Encoding=identity, Host=192.168.1.192:8096, Range=bytes=4765815551-, User-Agent=Emby/1.8.28g (Linux;Android 10) ExoPlayerLib/2.11.4, Icy-MetaData=1
2020-11-04 00:30:44.221 Info HttpServer: HTTP POST http://192.168.1.192:8096/emby/Sessions/Playing/Progress. UserAgent: Dalvik/2.1.0 (Linux; U; Android 10; Chromecast Build/QTS2.200917.005)
2020-11-04 00:30:44.222 Info HttpServer: HTTP Response 204 to 192.168.1.101. Time: 1ms. http://192.168.1.192:8096/emby/Sessions/Playing/Progress. ConnectionId: 0HM406NF3TTCK
2020-11-04 00:30:54.185 Info HttpServer: HTTP POST http://192.168.1.192:8096/emby/Sessions/Playing/Progress. UserAgent: Dalvik/2.1.0 (Linux; U; Android 10; Chromecast Build/QTS2.200917.005)
2020-11-04 00:30:54.185 Info HttpServer: HTTP Response 204 to 192.168.1.101. Time: 1ms. http://192.168.1.192:8096/emby/Sessions/Playing/Progress. ConnectionId: 0HM406NF3TTCK
2020-11-04 00:31:04.213 Info HttpServer: HTTP POST http://192.168.1.192:8096/emby/Sessions/Playing/Progress. UserAgent: Dalvik/2.1.0 (Linux; U; Android 10; Chromecast Build/QTS2.200917.005)
2020-11-04 00:31:04.214 Info HttpServer: HTTP Response 204 to 192.168.1.101. Time: 1ms. http://192.168.1.192:8096/emby/Sessions/Playing/Progress. ConnectionId: 0HM406NF3TTCK
2020-11-04 00:31:10.903 Info HttpServer: HTTP GET http://192.168.1.192:8096/emby/videos/45851/stream.mkv?DeviceId=efa439dcf2081ac3&MediaSourceId=15545861271425de474e88f69e165ea5&Static=true&PlaySessionId=bbcbd782b15741c8863551f273a4ef03. Connection=Keep-Alive, Accept-Encoding=identity, Host=192.168.1.192:8096, Range=bytes=4781588359-, User-Agent=Emby/1.8.28g (Linux;Android 10) ExoPlayerLib/2.11.4, Icy-MetaData=1
2020-11-04 00:31:11.759 Info HttpServer: HTTP GET http://192.168.1.192:8096/emby/Users/dab1ac8d094043d1a3c1188ff001aae1/Items/45851?format=json. UserAgent: Dalvik/2.1.0 (Linux; U; Android 10; Chromecast Build/QTS2.200917.005)
2020-11-04 00:31:11.761 Info HttpServer: HTTP Response 200 to 192.168.1.101. Time: 2ms. http://192.168.1.192:8096/emby/Users/dab1ac8d094043d1a3c1188ff001aae1/Items/45851?format=json. ConnectionId: 0HM406NF3TTCL
2020-11-04 00:31:11.796 Info HttpServer: HTTP POST http://192.168.1.192:8096/emby/Sessions/Playing/Stopped. UserAgent: Dalvik/2.1.0 (Linux; U; Android 10; Chromecast Build/QTS2.200917.005)

[silencerny 0]

Forgot to mention 4k playback.

[Luke 37244]

Hi there, please attach the complete emby server log. thanks.

[silencerny 0]

here is the log.

embyserver.txt

[Luke 37244]

Hi, try lowering the Chromecast quality setting from the app that you're casting with. Please see if that helps. Thanks.

[silencerny 0]

So this occurs even using the Emby Theatre from my laptop.  4k and 1080p.

I'm running Emby Server from a Centos 8 machine with 128GB of RAM.  After running several movies I see that i'm buffering 95GB of my memory.  This number continues to rise even when I stop the stream and close the Theatre app on my laptop.  I'm pretty certain that the Emby server should release the memory after i close the Theatre app.

[silencerny 0]

So after 4 hours it's still holding 95G,

[root@localhost ~]# systemctl status emby-server.service
● emby-server.service - Emby Server is a personal media server with apps on just about every device.
   Loaded: loaded (/usr/lib/systemd/system/emby-server.service; enabled; vendor preset: disabled)
   Active: active (running) since Mon 2020-11-09 22:37:27 EST; 5 days ago
 Main PID: 1277 (EmbyServer)
    Tasks: 21 (limit: 823586)
   Memory: 97.0G
 

[Luke 37244]

On 11/15/2020 at 9:22 AM, silencerny said:

So after 4 hours it's still holding 95G,

[root@localhost ~]# systemctl status emby-server.service
● emby-server.service - Emby Server is a personal media server with apps on just about every device.
   Loaded: loaded (/usr/lib/systemd/system/emby-server.service; enabled; vendor preset: disabled)
   Active: active (running) since Mon 2020-11-09 22:37:27 EST; 5 days ago
 Main PID: 1277 (EmbyServer)
    Tasks: 21 (limit: 823586)
   Memory: 97.0G
 

Can you please attach the emby server log from when this happened? Thanks.

[silencerny 0]

embyserver (1).txt

[silencerny 0]

i also restarted the emby-server.service

 

[root@localhost ~]# systemctl status emby-server.service
● emby-server.service - Emby Server is a personal media server with apps on just about every device.
   Loaded: loaded (/usr/lib/systemd/system/emby-server.service; enabled; vendor preset: disabled)
   Active: active (running) since Mon 2020-11-16 19:00:38 EST; 13s ago
 Main PID: 387352 (EmbyServer)
    Tasks: 31 (limit: 823586)
   Memory: 162.9M
 

Now Memory is down, but the free -g still shows:

[root@localhost ~]# free -g
              total        used        free      shared  buff/cache   available
Mem:            125           0          21           0         103         123
 

 

[Q-Droid 670]

It looks like the memory is in use as file buffer/cache which is normal because free memory is wasted memory. Memory used for buff/cache is borrowed and gets reclaimed when needed. Also why mem available is approx = free + buff/cache.

 

[silencerny 0]

i understand the memory usage but why is the memory not reclaimed when the emby server is stopped or restarted?

[Q-Droid 670]

Memory is reclaimed when needed. Your previous post is showing 123GB available out of 125GB total so there's no pressure to do so.

Unless there is a memory leak in Emby or a plug-in and the system is swapping then it's very unlikely that the stuttering playback has anything to do with memory. Systemd is likely showing more than just process space for the main server process and threads that are part of the service. So the numbers look inflated, even when accurate, and higher than what you'd see from other tools.

 

[Q-Droid 670]

You're playing media with a bitrate of 80mbps that's stored on a NAS. Have you made sure that everything in the path is up to the task? Your network, wifi devices, laptop, Chromecast, etc.