Pike Kevin wrote:
> Kodi client on OpenElec + TVH 4.2.8 on Ubuntu 18.04 + HDHomeRun prime
>
> I’ve been having the same issues with 2 hour recording limits. After months of research and fiddling, I believe I have my bug resolved.
>
> Symptoms:
> - Scheduled recordings stop at 2 hours
> - Streaming stops at 2 hours
> - When recording a show in progress, the recording appears to stop at different lengths.
>
> Troubleshooting:
> - Was able to determine that all streams and/or recordings stop at two hours. It didn’t matter when I started or the picture resolution of the stream, it always would simply stop streaming. Did not matter if the stream was on a remote client or VLC on the server machine.
> - Looked at network settings in client, server and HDHomeRun. Updated all. No change.
> - Attempted FTP KeepAlive script. No change
>
> After a lot of snooping around, I found that during the original build, I had erroneously left a line in the Playlist.m3u building script. When I looked in each mux, I found each URL ended with:
>
> “?Duration=7200”.
>
> 7200 seconds = 2 hours
> Doh!
>
> The tutorial that I used for the m3u building script was an awesome time saver. Simply customize the script a little and run it. Takes no time to generate a m3u file. The tutorial does mention that the “duration” is required by some apps. However, it seems it should not be used for TVH. If I’d just researched a little further, I’d have saved myself lots of time.
>
> Resolution:
> - Rewrote the m3u building script to exclude the “duration.”
> - Edited each mux to eliminate the ‘duration.’ For some reason, when I scanned the revised Playlist.m3u, the ‘?Duration=7200’ remained. However, after editing the muxes themselves and rescanning, the URL was correct.
> - Rescanned muxes
> - Remapped services
>
> Note: I did not want to rebuild the channel altogether. I have lots of time in editing and didn’t want to have to do that all over again. Someone here might have a quicker easier way.
> Also, I cloned my HDD prior to fiddling too much. Just a precaution.
>
> 48 hours after the modifications, all appears to be running smoothly.
>
> Hope this helps someone who may have made the same mistake I did.
Now that is BIG! And the 1st explanation that makes sense. I've been muddling through with my workaround, but still unsatisfied that there seemed to be no "clean" solution. I guess that's what happens when you are retired, have too much free time on your hands, and have an engineering background. :-)
At any rate, thanks for that, I'll try it out today on one of my test platforms and let you know how it goes.
