[advocate99]

I've enable Primetime Recording and told the system to group recordings according to the name that I configured when I set it up.

I've noticed that ALL recordings made during Primetime show up in these groups, even if I set my own series timer to record them.

Can we modify ServerWMC so that when there is already a timer for that show, it doesn't create a one-off timer and doesn't put that show into the Primetime group?

Alternatively, is there a way that I can change the group that a show is assigned to?

[krustyreturns]

It really should be doing what you want now, so if its not it must be a bug. I assume you set the series recording timer before you made the primetime recordings, right? Let me review the code, I might need a log if I can't figure out what is going on.

You can hand edit to change the groups of primetime recordings. Look in
%programdata%\vdsoftware\serverwmc\RecordingStore.xml

there is an entry for each current primetime recording, change the PrimeTimeName field to assign a new group. Restart swmc when done, then kodi.

[krustyreturns]

I think I found my error. If you want to test my fix before release, let me know.

[advocate99]

Yes, I set the series recordings before I activated the PrimeTime Recordings feature.

If you want me to test it, I'm happy to do so. For now, I've turned off the PrimeTime groupings options.

Two other issues/questions:

1. Did you know that PrimeTime Recordings is ENABLED by default upon installation?

This seems like a bad idea! What if one of the samples you've included matches an actual channel number? That would cause someone who doesn't know about the PTR feature to believe that your add-on as screwed up their Windows Media Center. It seems to me that the feature should be DISABLED upon installation.

2. At what time of the day does the PTR feature activate and de-activate the timers? You may wish to include that information in the remarks that are in the configuration file. When I first activated the feature, I was surprised to find that it didn't work the first day, and assumed that something was buggy. I happened to read something in the forums explaining that it only checks once a day. It would be helpful to know what time of day it does that check.

I think I found my error. If you want to test my fix before release, let me know.

[krustyreturns]

1) those PT examples are automatically removed (if unedited by user) so they are never presented to the record service - no worries there. I enabled it by default just to avoid users asking why its not working after they painstakingly set it up.

2) it starts trying to set the recordings up every 10 minutes after midnight- until the recording are successfully scheduled. The thing you saw of them not starting on your first day is a known issue: if when you configure the new PT the interval you specify has already started, it won't execute until the next time it comes around. This is there due to my laziness, it was just easier to code doing it this way.

I'll get a test build to you later in a pm. Thanks for the comments and the bug report.

[advocate99]

Based upon your comments, I have two additional suggestions:

1. I'd still change the enabled to disabled, and then add a remark in the configuration file that tells people that they have to enable it or it won't work. Ignoring the defaults seems like a bad idea because what if the default you suggested is the settings that I want to use?

2. You should add the information about when it sets the recordings to the remarks file as well.

Thank you for your tireless work on this project!