Additional xml options for scheduling

[MoeFwacky]

Just wanted to get these requests added so they're not forgotten. These are pretty low priority, I imagine.

The first option I had in mind is a variation on strict-time. I'd like to be able to specify that an item not play any earlier than scheduled but can still start later. So if a show is scheduled for 3pm, with a time-shift of 15 and the movie before ends at 3:10, the show is scheduled for 3:15, but if the movie ends at 2:30, the show would still start at 3. This is basically the opposite of how I imagine overlap-max will work once implemented, which I believe will allow it to start earlier than scheduled but not later than x.

Another xml option I'd like is one that prevents a show from being advanced in the database after being scheduled in that time slot. I would use this in instances where I'd like the same episode of a show to repeat twice in a day, or to show the previous week's episode before the "new" episode back to back (week 1, episode 1 and 2; week 2, episode 2 and 3; week 3, episode 3 and 4 and so on).

[justinemter]

I really like these ideas... The first one using a time-shift limit makes whole lot of sense to me. The latter update - having an option to dismiss the queue advancing for a particular time-slot also makes a lot of sense - in fact I think real channels operate like this too.

[justinemter]

Hey there so, I just added a feature to have xtra args specifically for random movies. I posted this thoroughly here: #41

You need to delete / recreate your local db. Since you are using your db for tv (as am I) be sure to just back it up so if the "-e" / "-i" do not do what you wanted then you can manually copy over the old "shows" table which contains the queue.

Sorry I've been out of the loop but have been a little busy. I'd like to get this darn alpha up relatively bug free soon (maybe this weekend?) I'll hit you up.

[MoeFwacky]

Cool, I'll check out the new functionality once the database finishes updating.