dteirney Wrote:If someone can confirm that the code in XBMC SVN works with a Myth 0.24 backend within the next day or so I will talk to the other XBMC devs and see if I can slip that code in before the next Dharma beta. I don't have time or a system where I can install Myth 0.24 at the moment.

dteirney Wrote:Re the Timer API. Some thinking will have to be done here, because the XBMC interface for scheduling new recordings will need consideration for any changes / improvements to support the different backends that it can talk with based on the plugin being used.

How does the XBMC frontend allow a user to schedule recordings? The frontend in Myth provides the ability to do all of the complex things that the backend supports. I was pondering whether the XBMC frontend allowed the really common things to be done with one interface, and then a separate interface was used for more complicated things that perhaps different backends supported.

For our usage, most of our scheduling rules use:
1) Record This Time Only "Once" - typically for Movies or specific shows that have something interesting in them. I suspect this might end up being used from Live TV as well?
2) Record Weekly On this Channel (we used to use "in this timeslot" but lost a few episodes due to scheduling changes)
3) Record Anytime On this Channel (for shows that are on every night)
4) Record Anytime on Any Channel (for shows that are interesting that often have re-runs, e.g. Mythbusters here in NZ)

What are the common scheduling rules for each of you? What would the XBMC frontend need to support to make it really easy for you? Once we know that it would be good to see how the current Timer API scheduling would fit in with that and then match up with what MythTV supports.

I'm not sure right now, but it might be that any of the really complicated rules that mythbackend can support still needs to be done through Mythweb or Mythfrontend and not XBMC.

PhracturedBlue Wrote:I assume you mean someone other than me, right (i.e. you want independent verification)? Because I've been using it successfully since you checked it in.

Note that I am not set up to verify it in Dharma though.

dubstar_04 Wrote:Scheduling usage:

Any time on this channel
Single recording
Cancel recording / override

I too would like to be able to use just xbmc without the need for mythfrontend or mythweb as its mainly the mrs who does all the tv stuff. If it gets complicated using the laptop to schedule recordings she will get a sad face on

Thanks,

Dubstar_04

dteirney Wrote:Just so it's clear, XBMC PVR addon's will be able to schedule recordings through the XBMC frontend. I was just suggesting that XBMC might not be able to schedule all the complicated things that each different backend can do natively.

XBMC will definitely need to support all the common things that wifes / partners etc. need to be able to do.

A few people have mentioned "Override" as one of the things that gets done often. What does this mean? Perhaps I'm lucky with enough tuners to hardly ever get any conflicts.

tafypz Wrote:I am starting a rewrite of the timer interface, I will make it more metadata driven so that a pvr client can specify the fields to render on the screen and set the data accordingly.
Also anybody understand the MenuHook method usage? I have been a little lazy and didn't look at it yet...

outleradam Wrote:Mythtv uses a recording priority from -100 to +100. Rather then "Vista" the user with every recording change, the backend schedules based upon a recording priority number. It sounds like the two systems are incompatible. Rather then just overriding a single show, it sets a value. After 100 overrides, mythtv would be out of numbers.