MXYetvzxd4jkc 2 Posted April 30 Share Posted April 30 My users still have buffering/playback pauses and sound desync issues. These issues happen both on LAN and WAN connections. Generally a quick pause and unpause fixes most of them, but sometimes playback, on mobile espescially, can get stuck and i have to restart the app basically. Hardware: Ryzen 9 7900 32gb ram 3TB SSD Raid1 array. (btrfs) Arc a380 Ubuntu server (6.8.0-31-generic, 24.04) WAN is 1000mbit full duplex. Iv tried a few things: Emby in Docker (This is what I normally run). emby-server standard deb install. Tried both with and without using nginx proxy manager. Tried SSL/Non SSL connections. Transcoding is picking up the intel arc fine, so I don't think its that. Iv added a few transcode logs also. Any thoughts? ffmpeg-transcode-48db80e1-d49b-4344-ac65-0b5c8522bbd5_1.txt ffmpeg-transcode-2fe91c0f-4682-4a8d-b349-12bb5acf70d4_1.txt ffmpeg-transcode-294f8784-dd0e-49a2-abc1-efd411697d17_1.txt Link to comment Share on other sites More sharing options...
Luke 37272 Posted April 30 Share Posted April 30 HI, have you tried turning off hardware transcoding as a test? And/or, have you tried lowering the playback quality setting? Link to comment Share on other sites More sharing options...
MXYetvzxd4jkc 2 Posted May 1 Author Share Posted May 1 Thanks for the response! Hilariously I actually got the Arc as I was having issues without it and thought it might help! Same issues without it unfortunately. I will get some users to try different quality settings to see if it make a difference. What is odd is, the issues persisted on different clients, say browser vs emby ios/android or emby windows. 1 Link to comment Share on other sites More sharing options...
jaycedk 401 Posted May 1 Share Posted May 1 (edited) Try disable QuickSync and only use vaapi. I had some issues when using QS, but worked great with only vaapi. I don't have the same GPU as you, so can't be sure. Edited May 1 by jaycedk Link to comment Share on other sites More sharing options...
MXYetvzxd4jkc 2 Posted May 1 Author Share Posted May 1 @jaycedkI can give that a try too! Thank you! Link to comment Share on other sites More sharing options...
MXYetvzxd4jkc 2 Posted May 5 Author Share Posted May 5 @jaycedkNo difference with disabling quicksync Seems im just stuck! Link to comment Share on other sites More sharing options...
Luke 37272 Posted May 5 Share Posted May 5 Hi, have you tried Chrome to see how that compares? Link to comment Share on other sites More sharing options...
MXYetvzxd4jkc 2 Posted May 6 Author Share Posted May 6 @LukeIndeed! Tried Firefox, Chrome and Safari. Firefox and Chrome do tend to be slightly better. Due to how fast downloads are, people have just been using that option. Also I tried the emby desktop client on my windows pc, it has the same issue. I will work to collect more logs! 1 Link to comment Share on other sites More sharing options...
MXYetvzxd4jkc 2 Posted May 13 Author Share Posted May 13 Unsure if this is helpful, but the worst buffering happens at the start and end. The end especially seems to be very bad. I added a some transcodes that were really bad, but doesn't seem like anything out of order? Only thing I saw was: 22:14:41.006 [hevc_qsv @ 0x14762c0] error parsing SEI type: 4 Numbits 560 error: -1094995529 ffmpeg-transcode-9bb5f874-e720-49ac-a5bb-a88bd11334c2_1.txt ffmpeg-transcode-cca9b5b4-92d4-4aa8-825c-d067efa12565_1.txt Link to comment Share on other sites More sharing options...
Lessaj 83 Posted May 13 Share Posted May 13 Please include the server log that corresponds to these because that will indicate the time taken to deliver each TS segment. The transcode speed is perfectly fine over 9x. Link to comment Share on other sites More sharing options...
MXYetvzxd4jkc 2 Posted May 14 Author Share Posted May 14 @LessajApologies, iv added those now for the time period. embyserver-63851068799.txt Link to comment Share on other sites More sharing options...
Lessaj 83 Posted May 14 Share Posted May 14 The transcode logs are from the 12th but this log is from the 11th. Unfortunately there's no mention of TS segments in this log either so no point of comparison even if it's the wrong one. Though I do see some really long response times for playing progress which doesn't seem right, I expect to see some delays in delivering TS segments with the correct log based on this. On that note though what is this 30 second check for the URI /health? It just returns a 404. Link to comment Share on other sites More sharing options...
MXYetvzxd4jkc 2 Posted May 14 Author Share Posted May 14 @LessajReally appreciate you taking a look! Ahh indeed odd, I have attached the log from the 11th also, apologies from the confusion. As to the health, I'm going to assume thats a docker thing. As docker usually pings that URL to test if the container is alive. embyserver-63851028087.txt Link to comment Share on other sites More sharing options...
Lessaj 83 Posted May 14 Share Posted May 14 (edited) That log is still from the 11th. Need the 12th. Edited May 14 by Lessaj Link to comment Share on other sites More sharing options...
MXYetvzxd4jkc 2 Posted May 14 Author Share Posted May 14 @LessajI think we are going a bit crazy here 12th is embyserver-63851068799.txt is for 11th embyserver-63851028087.txt Link to comment Share on other sites More sharing options...
Lessaj 83 Posted May 14 Share Posted May 14 embyserver-63851068799.txt goes from 2024-05-11 12:41:27.828 until 2024-05-11 23:59:45.259 embyserver-63851028087.txt goes from 2024-05-11 09:29:50.149 until 2024-05-11 12:34:38.873 The log rotates every time you restart the server, or daily at midnight. Link to comment Share on other sites More sharing options...
MXYetvzxd4jkc 2 Posted May 14 Author Share Posted May 14 @Lessaj17th Times a charm! embyserver-63851155199.txt Link to comment Share on other sites More sharing options...
Lessaj 83 Posted May 14 Share Posted May 14 Hm, that's interesting. There's no mention in this log of the delivery of TS segments. I can see a transcode start at 2024-05-12 22:20:17, same as one of the transcode logs, but there's no indication that the client is requesting segments. I was expecting to see something like this: 2024-05-14 13:31:01.169 Info Server: http/1.1 Response 200 to host7. Time: 154ms. GET https://emby_remote_ip/emby/videos/201222/hls1/main/35.ts?PlaySessionId=a55e1751031640129119c5f33a316374 For this particular case, do you know if this was a local user or a remote user? There may not have been a reason to transcode depending on that. 2024-05-12 22:20:17.744 Info App: Bitrate exceeds DirectPlay limit: media bitrate: 28569538, max bitrate: 15000000 2024-05-12 22:20:17.744 Info App: Bitrate exceeds DirectStream limit: media bitrate: 28569538, max bitrate: 15000000 Link to comment Share on other sites More sharing options...
MXYetvzxd4jkc 2 Posted May 15 Author Share Posted May 15 @LessajI believe that was someone on my LAN, yes. Most of my other users have just resorted to downloading to avoid the buffering. Link to comment Share on other sites More sharing options...
Lessaj 83 Posted May 15 Share Posted May 15 Certainly for LAN users there shouldn't be a bitrate cap, you might need to manually enter networks into LAN Networks on the Networking tab to resolve that, or at least set the bitrate higher on the device. If you have gigabit upload your remote users should be able to direct play as well. I'm still confused why I don't see any requests for TS segments in your log. Does your nginx instance log the durations for each request? You might be able to find the information there but those wouldn't be anonymized so I wouldn't post that publicly it might contain API keys in the URI. Link to comment Share on other sites More sharing options...
Luke 37272 Posted Wednesday at 04:57 PM Share Posted Wednesday at 04:57 PM 3 hours ago, MXYetvzxd4jkc said: @LessajI believe that was someone on my LAN, yes. Most of my other users have just resorted to downloading to avoid the buffering. Can you find out for sure? Link to comment Share on other sites More sharing options...
MXYetvzxd4jkc 2 Posted Wednesday at 05:31 PM Author Share Posted Wednesday at 05:31 PM @LukeTo be sure I cross referenced with the Activity list, and the only user around that time was a LAN user. Weirdly though, the times don't line up that closely, they are about an hour off. Link to comment Share on other sites More sharing options...
MXYetvzxd4jkc 2 Posted Saturday at 01:32 PM Author Share Posted Saturday at 01:32 PM Got 2 more logs. Weirdly this seems to happen even if there is no transcoding, this was a LAN Apple TV. embyserver-63851587200.txt embyserver-63851500800.txt Link to comment Share on other sites More sharing options...
Lessaj 83 Posted Sunday at 02:28 AM Share Posted Sunday at 02:28 AM (edited) How is this device connected to your network? I see response times for playing progress near instantly, 1-2ms, and then durations randomly get really long. Quote 2024-05-16 12:10:23.626 Info Server: http/1.1 Response 204 to host4. Time: 1ms. POST http://192.168.3.100:8096/emby/Sessions/Playing/Progress?X-Emby-Client=Emby for Apple TV&X-Emby-Device-Name=Apple TV&X-Emby-Device-Id=EA574502-FE15-466D-8593-0B39B09046C7&X-Emby-Client-Version=1.8.8 (2)&X-Emby-Token=x_secret4_x&reqformat=json 2024-05-16 12:10:33.637 Info Server: http/1.1 Response 204 to host4. Time: 1ms. POST http://192.168.3.100:8096/emby/Sessions/Playing/Progress?X-Emby-Client=Emby for Apple TV&X-Emby-Device-Name=Apple TV&X-Emby-Device-Id=EA574502-FE15-466D-8593-0B39B09046C7&X-Emby-Client-Version=1.8.8 (2)&X-Emby-Token=x_secret4_x&reqformat=json 2024-05-16 12:10:43.648 Info Server: http/1.1 Response 204 to host4. Time: 1ms. POST http://192.168.3.100:8096/emby/Sessions/Playing/Progress?X-Emby-Client=Emby for Apple TV&X-Emby-Device-Name=Apple TV&X-Emby-Device-Id=EA574502-FE15-466D-8593-0B39B09046C7&X-Emby-Client-Version=1.8.8 (2)&X-Emby-Token=x_secret4_x&reqformat=json 2024-05-16 12:10:53.662 Info Server: http/1.1 Response 204 to host4. Time: 1ms. POST http://192.168.3.100:8096/emby/Sessions/Playing/Progress?X-Emby-Client=Emby for Apple TV&X-Emby-Device-Name=Apple TV&X-Emby-Device-Id=EA574502-FE15-466D-8593-0B39B09046C7&X-Emby-Client-Version=1.8.8 (2)&X-Emby-Token=x_secret4_x&reqformat=json 2024-05-16 12:11:24.757 Info Server: http/1.1 Response 204 to host4. Time: 21045ms. POST http://192.168.3.100:8096/emby/Sessions/Playing/Progress?X-Emby-Client=Emby for Apple TV&X-Emby-Device-Name=Apple TV&X-Emby-Device-Id=EA574502-FE15-466D-8593-0B39B09046C7&X-Emby-Client-Version=1.8.8 (2)&X-Emby-Token=x_secret4_x&reqformat=json 2024-05-16 12:11:24.757 Info Server: http/1.1 Response 204 to host4. Time: 11030ms. POST http://192.168.3.100:8096/emby/Sessions/Playing/Progress?X-Emby-Client=Emby for Apple TV&X-Emby-Device-Name=Apple TV&X-Emby-Device-Id=EA574502-FE15-466D-8593-0B39B09046C7&X-Emby-Client-Version=1.8.8 (2)&X-Emby-Token=x_secret4_x&reqformat=json 2024-05-16 12:11:25.072 Info Server: http/1.1 Response 204 to host4. Time: 1ms. POST http://192.168.3.100:8096/emby/Sessions/Playing/Progress?X-Emby-Client=Emby for Apple TV&X-Emby-Device-Name=Apple TV&X-Emby-Device-Id=EA574502-FE15-466D-8593-0B39B09046C7&X-Emby-Client-Version=1.8.8 (2)&X-Emby-Token=x_secret4_x&reqformat=json 2024-05-16 12:11:35.110 Info Server: http/1.1 Response 204 to host4. Time: 2ms. POST http://192.168.3.100:8096/emby/Sessions/Playing/Progress?X-Emby-Client=Emby for Apple TV&X-Emby-Device-Name=Apple TV&X-Emby-Device-Id=EA574502-FE15-466D-8593-0B39B09046C7&X-Emby-Client-Version=1.8.8 (2)&X-Emby-Token=x_secret4_x&reqformat=json 2024-05-16 12:11:45.165 Info Server: http/1.1 Response 204 to host4. Time: 1ms. POST http://192.168.3.100:8096/emby/Sessions/Playing/Progress?X-Emby-Client=Emby for Apple TV&X-Emby-Device-Name=Apple TV&X-Emby-Device-Id=EA574502-FE15-466D-8593-0B39B09046C7&X-Emby-Client-Version=1.8.8 (2)&X-Emby-Token=x_secret4_x&reqformat=json Quote 2024-05-16 13:10:47.150 Info Server: http/1.1 Response 204 to host4. Time: 1ms. POST http://192.168.3.100:8096/emby/Sessions/Playing/Progress?X-Emby-Client=Emby for Apple TV&X-Emby-Device-Name=Apple TV&X-Emby-Device-Id=EA574502-FE15-466D-8593-0B39B09046C7&X-Emby-Client-Version=1.8.8 (2)&X-Emby-Token=x_secret4_x&reqformat=json 2024-05-16 13:10:48.046 Info Server: http/1.1 Response 204 to host4. Time: 0ms. POST http://192.168.3.100:8096/emby/Sessions/Playing/Progress?X-Emby-Client=Emby for Apple TV&X-Emby-Device-Name=Apple TV&X-Emby-Device-Id=EA574502-FE15-466D-8593-0B39B09046C7&X-Emby-Client-Version=1.8.8 (2)&X-Emby-Token=x_secret4_x&reqformat=json 2024-05-16 13:10:49.510 Info Server: http/1.1 Response 204 to host4. Time: 1ms. POST http://192.168.3.100:8096/emby/Sessions/Playing/Progress?X-Emby-Client=Emby for Apple TV&X-Emby-Device-Name=Apple TV&X-Emby-Device-Id=EA574502-FE15-466D-8593-0B39B09046C7&X-Emby-Client-Version=1.8.8 (2)&X-Emby-Token=x_secret4_x&reqformat=json 2024-05-16 13:10:50.484 Info Server: http/1.1 Response 204 to host4. Time: 1ms. POST http://192.168.3.100:8096/emby/Sessions/Playing/Progress?X-Emby-Client=Emby for Apple TV&X-Emby-Device-Name=Apple TV&X-Emby-Device-Id=EA574502-FE15-466D-8593-0B39B09046C7&X-Emby-Client-Version=1.8.8 (2)&X-Emby-Token=x_secret4_x&reqformat=json 2024-05-16 13:10:50.656 Info Server: http/1.1 Response 204 to host4. Time: 0ms. POST http://192.168.3.100:8096/emby/Sessions/Playing/Progress?X-Emby-Client=Emby for Apple TV&X-Emby-Device-Name=Apple TV&X-Emby-Device-Id=EA574502-FE15-466D-8593-0B39B09046C7&X-Emby-Client-Version=1.8.8 (2)&X-Emby-Token=x_secret4_x&reqformat=json 2024-05-16 13:11:10.989 Info Server: http/1.1 Response 204 to host4. Time: 10313ms. POST http://192.168.3.100:8096/emby/Sessions/Playing/Progress?X-Emby-Client=Emby for Apple TV&X-Emby-Device-Name=Apple TV&X-Emby-Device-Id=EA574502-FE15-466D-8593-0B39B09046C7&X-Emby-Client-Version=1.8.8 (2)&X-Emby-Token=x_secret4_x&reqformat=json 2024-05-16 13:11:10.989 Info Server: http/1.1 Response 204 to host4. Time: 300ms. POST http://192.168.3.100:8096/emby/Sessions/Playing/Progress?X-Emby-Client=Emby for Apple TV&X-Emby-Device-Name=Apple TV&X-Emby-Device-Id=EA574502-FE15-466D-8593-0B39B09046C7&X-Emby-Client-Version=1.8.8 (2)&X-Emby-Token=x_secret4_x&reqformat=json 2024-05-16 13:11:42.242 Info Server: http/1.1 Response 204 to host4. Time: 21540ms. POST http://192.168.3.100:8096/emby/Sessions/Playing/Progress?X-Emby-Client=Emby for Apple TV&X-Emby-Device-Name=Apple TV&X-Emby-Device-Id=EA574502-FE15-466D-8593-0B39B09046C7&X-Emby-Client-Version=1.8.8 (2)&X-Emby-Token=x_secret4_x&reqformat=json 2024-05-16 13:11:42.242 Info Server: http/1.1 Response 204 to host4. Time: 1511ms. POST http://192.168.3.100:8096/emby/Sessions/Playing/Progress?X-Emby-Client=Emby for Apple TV&X-Emby-Device-Name=Apple TV&X-Emby-Device-Id=EA574502-FE15-466D-8593-0B39B09046C7&X-Emby-Client-Version=1.8.8 (2)&X-Emby-Token=x_secret4_x&reqformat=json 2024-05-16 13:11:42.242 Info Server: http/1.1 Response 204 to host4. Time: 11535ms. POST http://192.168.3.100:8096/emby/Sessions/Playing/Progress?X-Emby-Client=Emby for Apple TV&X-Emby-Device-Name=Apple TV&X-Emby-Device-Id=EA574502-FE15-466D-8593-0B39B09046C7&X-Emby-Client-Version=1.8.8 (2)&X-Emby-Token=x_secret4_x&reqformat=json 2024-05-16 13:11:50.725 Info Server: http/1.1 Response 204 to host4. Time: 1ms. POST http://192.168.3.100:8096/emby/Sessions/Playing/Progress?X-Emby-Client=Emby for Apple TV&X-Emby-Device-Name=Apple TV&X-Emby-Device-Id=EA574502-FE15-466D-8593-0B39B09046C7&X-Emby-Client-Version=1.8.8 (2)&X-Emby-Token=x_secret4_x&reqformat=json 2024-05-16 13:12:00.738 Info Server: http/1.1 Response 204 to host4. Time: 1ms. POST http://192.168.3.100:8096/emby/Sessions/Playing/Progress?X-Emby-Client=Emby for Apple TV&X-Emby-Device-Name=Apple TV&X-Emby-Device-Id=EA574502-FE15-466D-8593-0B39B09046C7&X-Emby-Client-Version=1.8.8 (2)&X-Emby-Token=x_secret4_x&reqformat=json 2024-05-16 13:12:16.434 Info Server: http/1.1 Response 204 to host4. Time: 2ms. POST http://192.168.3.100:8096/emby/Sessions/Playing/Progress?X-Emby-Client=Emby for Apple TV&X-Emby-Device-Name=Apple TV&X-Emby-Device-Id=EA574502-FE15-466D-8593-0B39B09046C7&X-Emby-Client-Version=1.8.8 (2)&X-Emby-Token=x_secret4_x&reqformat=json Edited Sunday at 02:30 AM by Lessaj Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now