(2015-05-06, 12:00)JasonPell Wrote: Leaving live tv paused overnight causes kodi to freeze. I have to kill it from command line severely effects waf and son acceptance factor too.
I am using latest pvr client mythtv 0.28-pre from mid april and kodi 14.2. is live fast forward rewind implemented by mythtv or locally by plugin? If by mythtv why would leaving it paused cause local freeze of kodi?
Janbar (the developer) is on vacation until the 20th of May, so immediate comments from that perspective probably won't be forthcoming.
(I wish I lived in Europe and had REAL vacation, not this sorry excuse for vacation time we get in the U.S.)
If you have wife and kid acceptance issues (as do I) I would recommend running the stable version of MythTV, not the 0.28 alpha version.
I am not an expert on the overall MythTV architecture, but the way I THINK it works is that the backend simply records files to disk, and hosts them for the frontend. In the case of scheduled recordings this is simple, but in the case of live TV it gets more complicated. When you start watching, it wites a file to the livetv folder, and then the frontend streams the playback from that file. It gets complicated as th backend needs to monitor the front end to know when it stops watching and it can stop recording.
So while skipping back and forward in the video file is a front end activity, when it does so it is reading from the hosted video file on the backend, with all the complications of timing that get added when accessing something remotely via the network.
In the pausing overnight scenario, I would imagine the backend gets confused regarding frontend activity as it has remained dormant for so long.
My first recommendation here would be to simply not do it. If you know you are coming back to it tomorrow, click the record button and stop watching instead.
Other than that, I would wonder about how large your backend storage directories are. Whenever you watch live tv, it is recording that file to the storage directory. I'm assuming that when you pause the front end, the back end just keeps on recording on the current channel. Could you be filling the storage directory, prompting MythTV to autoexpire old content, and could that old content be the live TV you are paused in?
Also, make sure your frontend is wired gigabit ethernet to the backend Anything that reduces latencies will help. I wouldn't use Wifi under any circumstances.
That is all that I can think of. If you post your logs when it happens, someone else might be able to read through them and help.
But as I mentioned up top, I don't understand why anyone would be running an alpha version of the backend, in a "production" environment where wife and kids have expectations. Especially when even the "stable" .27.4 release, isn't the paragon of stability...
.28 should only be for people who are actively bug testing, and don't care about crashes, freezes and other glitches IMHO.
?
, so please do not update mythtv until 20 may.
