2015-05-19, 14:40
It could be network but mine will even buffer on the pc that has the tuners.
2015-05-19, 19:39
I run on a Gateway SX2870 Intel Core i3(2120) @3.30 Ghz with 16Gb memory
running Windows 7 64 bit.
I have 2 HDHomerun Prime devices (6 tuners total) configured with Comcast cablecards.
I have tried running the LiveTV on the C: drive (1 TB drive)
and on the G: drive (5 TB Seagate Expansion)
and even running on the C: drive with Remux directory on the G: drive
and vice versa.
In all cases, I get severe buffering as soon as I got 3 LiveTV kodi client on different TV HD channels.
I know the PC is not high end, but when I monitor the resources, it definitely points to the Disk IO Queue Length
being too high (3 or more) on a consistent basis.
My network is Gigabit and all my clients are connected via ethernet (not a Wifi problem) so I do not see
any problem there. Also if I run the SiliconDust HDHomerun Live TV (kodi add-on) instead of going through serverWMC,
I do not get the buffering issue. However, I do prefer the serverWMC config since that gives me full control of
Pause/Skip...
At this point, I am trying to set up another PC with serverWMC to see if I get the same issues
running Windows 7 64 bit.
I have 2 HDHomerun Prime devices (6 tuners total) configured with Comcast cablecards.
I have tried running the LiveTV on the C: drive (1 TB drive)
and on the G: drive (5 TB Seagate Expansion)
and even running on the C: drive with Remux directory on the G: drive
and vice versa.
In all cases, I get severe buffering as soon as I got 3 LiveTV kodi client on different TV HD channels.
I know the PC is not high end, but when I monitor the resources, it definitely points to the Disk IO Queue Length
being too high (3 or more) on a consistent basis.
My network is Gigabit and all my clients are connected via ethernet (not a Wifi problem) so I do not see
any problem there. Also if I run the SiliconDust HDHomerun Live TV (kodi add-on) instead of going through serverWMC,
I do not get the buffering issue. However, I do prefer the serverWMC config since that gives me full control of
Pause/Skip...
At this point, I am trying to set up another PC with serverWMC to see if I get the same issues
2015-05-20, 02:52
2015-05-20, 19:05
I have done 2 things that seem to have made a huge improvement. The first was updating the NIC drivers.
After that, the buffering continued but would go for a long time without any buffering, then for a minute or more would buffer back and forth constantly. I checked the logs and noticed at around the time of the buffering, one of the clients was requesting to get timers and get recordings. I turned on the option to "prevent updates during playback" on each Kodi client. I will need time to test longer, but so far that seems to have helped. I have mine synchronized with MySQL so I'm not sure if that makes a big difference in performance.
After that, the buffering continued but would go for a long time without any buffering, then for a minute or more would buffer back and forth constantly. I checked the logs and noticed at around the time of the buffering, one of the clients was requesting to get timers and get recordings. I turned on the option to "prevent updates during playback" on each Kodi client. I will need time to test longer, but so far that seems to have helped. I have mine synchronized with MySQL so I'm not sure if that makes a big difference in performance.
2015-05-21, 23:54
Good to hear, I wonder if it's the server side that is slowing down when receiving client requests or the client side. How many channels and recordings do you have? Any evidence in ServerWMC log of excessive time taken to complete any call? We are meant to be multithreaded so receiving a client message shouldn't block the other client messages for live TV (the log suppresses it but when playing back liveTV Kodi sends client requests constantly back and forth to get the file size etc)
Also mysql synchronisation is only for video /audio library fyi not the pvr/Epg databases, so I don't think that will be factored in here
Also mysql synchronisation is only for video /audio library fyi not the pvr/Epg databases, so I don't think that will be factored in here
2015-05-22, 15:26
The buffering is back again. It will be fine with 2 live streams going, but once that third one comes on, the buffering is bad but it seems to be bad only on one client and not always the same client.
I only have 48 channels and about 58 recordings. I have not noticed anything in the log that looks like an excessive time.
I only have 48 channels and about 58 recordings. I have not noticed anything in the log that looks like an excessive time.
2015-05-22, 20:16
Have you checked the network utilization in task manager? I had an issue with a NIC driver and it kept switching between 10, 100, and gig. Just keep an eye on it when you see buffering and make sure it is as expected.
2015-05-23, 00:54
Network utilization is usually less than 30% used. The disk does show 100% Highest Active Time.
I checked the logs and got a bunch of messages similar to the ones below.
2015/05/22 17:11:33.395 WriteChunk> long interval message repeated more than 20 times
2015/05/22 17:11:33.552 WriteChunk> long interval message repeated more than 20 times
2015/05/22 17:11:33.694 StreamFileSize> client localhost(2), count: 5, ts stream size: 229,408,768 (wtv: 971,243,520)
I checked the logs and got a bunch of messages similar to the ones below.
2015/05/22 17:11:33.395 WriteChunk> long interval message repeated more than 20 times
2015/05/22 17:11:33.552 WriteChunk> long interval message repeated more than 20 times
2015/05/22 17:11:33.694 StreamFileSize> client localhost(2), count: 5, ts stream size: 229,408,768 (wtv: 971,243,520)
2015-05-28, 16:09
I have a spinning drive as a secondary so I changed WMC to point to it. I was able to run 3 live TV streams fine for about 30-40 minutes and then the buffering started again. At the time of buffering, the SWMC log showed many entries similar to the ones below. I don't understand what changed after those 30-40 minutes.
2015/05/26 20:54:24.241 WriteChunk> long interval between writes (ms): 2335
2015/05/26 20:54:28.078 WriteChunk> long interval between writes (ms): 2884
2015/05/26 20:54:28.353 StreamFileSize> client TV, count: 5, ts stream size: 3,026,944,000 (wtv: 3,660,840,960)
2015/05/26 20:54:30.343 WriteChunk> long interval between writes (ms): 2265
2015/05/26 20:54:37.994 StreamFileSize> client TV, count: 5, ts stream size: 3,027,730,432 (wtv: 3,660,840,960)
2015/05/26 20:54:24.241 WriteChunk> long interval between writes (ms): 2335
2015/05/26 20:54:28.078 WriteChunk> long interval between writes (ms): 2884
2015/05/26 20:54:28.353 StreamFileSize> client TV, count: 5, ts stream size: 3,026,944,000 (wtv: 3,660,840,960)
2015/05/26 20:54:30.343 WriteChunk> long interval between writes (ms): 2265
2015/05/26 20:54:37.994 StreamFileSize> client TV, count: 5, ts stream size: 3,027,730,432 (wtv: 3,660,840,960)
