Repeating Timer only runs once

[a_team]

Hi

I created a timer recording event for recording the 11pm local news (my life is exciting eh). I set the timer's lifetime to 364 days (it wouldn't save the 365 value) thinking that it would repeat every night, however, it recorded the news the first night and then simply disappeared.

I then went to the 11pm News, set it to Record, found the Timer event and edited it to have a lifetime of 364 days - but it did the same and only recorded the news on the 27th and nothing on the 28th.

Am I doing something wrong?

[reven]

xbmc timers are currently "Record Once" the lifetime is just how many days to keep the recording for before deleting it (which nextpvr doesnt support, many other pvrs support this, so its just kept forever)

[a_team]

Thank you for the quick reply!

It's too bad that it's only a record once feature. Hopefully it changes in the near future.

[mvallevand]

Alternatively you can schedule recurring recordings using NextPVR itself, NEWA from the web browser, and X-NEWA from XBMC.

Martin

[reven]

xbmc had a pretty big debate over how to do the advanced scheduling.

basically there were two options

1. implement advances schedules in xbmc per a common set of rules and all pvr clients create appropriate rules on the server. eg "Record All this Channel"
This has some issues, not every backend supports advancing schedule and some only allow for regex based rules. so you couldnt do things like "no repeats" etc. XBMC gui would still display all recording options, but the addon would then complain or slightly ignore the request and not schedule it

2. let each pvr addon define a list of rules that xbmc displayed. this complicates the GUI and becomes a hassle if using more than one backend.

basically they ran out of time before the frodo release, so just stuck with record once options for now. it will be added in the future, but not likely any time soon, maybe 6 months away.

as suggested use another client (web or nextpvr gui itself) to create your rules.