robweber Wrote:Fair enough. I'm not arguing per say that XBMC should be able to handle the task, I just wanted to see if you were really using the data or if it was a misunderstanding about how the addon really related to the data already stored in the backend.
Actually it was good to clarify this for me, because I wasn't exactly sure about that. So thanks! (I figured the backend would still record those later events, but glad to have it confirmed).
Unfortunately scaling back the number of days in the EPG to 2-3 days didn't fix my crashes (although they are less frequent). I also noticed that when I do have more days (like 10-14 days), the "Timeline" EPG view is considerably slower to load (compared with 1-2 days), which leads me to suspect that it's attempting to load the entire 14 days into memory, even though you can only ever see a sliding "window" of about 4-5 hours.
Another difference with respect to mythfrontend (and Mythbox) is that you can't scroll back a few hours from the present to see what was just playing previously: those events are gone. I find it useful when you catch the tail end of an interesting program (let's say you're watching Live TV) to go back and see the program details, and/or schedule subsequent recordings of that program. But once the next hour comes, those events are inaccessible. It would be nice, therefore, to be able to set a window for caching old EPG events (e.g. maybe 4-5 hours or so) before they disappear from display. I'm guessing this might be a PVR-wide issue, not specific to this myth add-on.
Quote:I've never actually used the mythfrontend exclusively - I've always found it kind of ugly and cumbersome. For me a combination of xbmc (via script or myth:// access) and the mythweb application have always been enough.
Actually I don't use mythfrontend much anymore myself. I'm actually fairly happy with the Mythbox add-on for Dharma (which works fine with myth 0.23-fixes) for the moment. But I'll be switching to this add-on once Eden (and by extension dushmaniac's and tsp's PVR branches) gets a bit more stable. Mythbox exposes all the scheduling data in the backend (i.e. 14 days worth), and can be used for scheduling all but the most obscure rules. The only time I really need to go to mythfrontend is to play a particularly cantakerous recording (sometimes xbmc doesn't like fast-forwarding), or to tweak something in the backend like obscure transcoding rules.