That is possible if that is the case then there must be a way to rescheduled canceled or skip recordings. A pass with re-record deleted should be able to reschedule these at a later time.
So if anybody in my House canceled or skip a recording then for all intents and purposes there is no way to re-record them well that is definitely not good.
The behavior was changed a while back when someone cancelled a recording of a sports game before the scheduled finish time and it tried to record it again. Used to be when you skipped something, it was only that airing that was skipped.
Well that sucks ... not sure who skipped these .. I will disable the Pass and Use SageTV. If this is the way it works then ChannelsDVR will not work in my household. I have tons of these, and I know I did not skip them all. What happens if there are no more tuners available and a recording is skipped over?
I also thought a regenerate of DB would clear this but it does not.
"MV000031270000": "skipped",
"MV000039950000": "recorded-7096",
"MV000041860000": "skipped",
"MV000104260000": "skipped",
"MV000124690000": "recorded-6947",
"MV000132230000": "skipped",
"MV000135600000": "skipped",
"MV000155770000": "skipped",
"MV000159450000": "recorded-7294",
"MV000186450000": "skipped",
"MV000186460000": "recorded-7295",
"MV000196900000": "recorded-7379",
"MV000208670000": "recorded-7297",
"MV000210120000": "recorded-7309",
"MV000214430000": "recorded-7400",
"MV000218850000": "recorded-7320",
"MV000225700000": "recorded-7385",
"MV000226120000": "recorded-7222",
"MV000231050000": "skipped",
"MV000234870000": "recorded-7358",
"MV000238660000": "recorded-7200",
"MV000265910000": "skipped",
"MV000268680000": "skipped",
"MV000276180000": "skipped",
"MV000281690000": "recorded-7318",
"MV000317390000": "skipped",
"MV000317690000": "recorded-7209",
"MV000319640000": "skipped",
"MV000325270000": "recorded-7128",
"MV000325960000": "recorded-7359",
"MV000328370000": "recorded-6958",
"MV000343000000": "recorded-7205",
"MV000346590000": "recorded-7009",
"MV000369090000": "recorded-6986",
"MV000372550000": "recorded-7033",
"MV000382500000": "recorded-7360",
"MV000396450000": "recorded-7178",
"MV000420770000": "skipped",
"MV000425670000": "skipped",Pretty sure it's never marked as anything (failed, recorded, skipped, etc.). It should just try to reschedule it.
A Prune DB and Regenerate should take care of this but it does not. I also saw a lot of episodes on my DB that were skipped.
That is a bad there has to be a way to clean them up ... I definitely will not be using Channels DVR to record my Premium Movies or any for that fact.
Sometimes you have to skip a recording to record one that might be a first run... that conflicts with it.
I was wondering why I could not get the Lord of the Rings full collection it refused to record.
What I would like to see is The Mighty Quinn display as Skipped and the dropdown has an option to Un-Skip it. That way the pass can record it. Right now the only option on the dropdown is probably Record, which is like selecting record from the guide, which is a manual recording. If the guide data changes (airs at a different time), that wouldn't work.
I see it in your /dvr/programs
"MV000265910000": "skipped",
There are so many reasons why you would want to skip a recording and want to re-record it at a future date without checking the guide.
"MV000265910000": "skipped",
Agree. I was quite upset when they made that change.
Now you have to issue a curl command to remove each one from the DB.
curl -XDELETE http://127.0.0.1:8089/dvr/programs/MV000265910000
Thanks you answered my questions that release has to be revisited it causes more problems than it fixes.
Not going to use a curl command too many I hate work arounds or having to babysit a DVR. I just will record my movies and series I want to keep using other DVR software.
This what I came up with and I know we did not skip this many. This is as bad as the HDHomeRun DVR that you have to cleanup the database to re-record something.... you might have accidently deleted or skipped for some reason.
Line 2: "184483/S21E18": "skipped",
Line 12: "EP000037101458": "skipped",
Line 13: "EP000047624282": "skipped",
Line 14: "EP000191553337": "skipped",
Line 15: "EP000191907675": "skipped",
Line 17: "EP001340710044": "skipped",
Line 25: "EP017040100191": "skipped",
Line 26: "EP017040100192": "skipped",
Line 47: "EP024970981110": "skipped",
Line 48: "EP024970981116": "skipped",
Line 49: "EP024970981117": "skipped",
Line 50: "EP024970981119": "skipped",
Line 51: "EP024970981121": "skipped",
Line 52: "EP024970981137": "skipped",
Line 53: "EP024970981150": "skipped",
Line 54: "EP024970981151": "skipped",
Line 55: "EP024970981152": "skipped",
Line 57: "EP027577551129": "skipped",
Line 71: "EP029705200079": "skipped",
Line 73: "EP033090100188": "skipped",
Line 74: "EP033090100195": "skipped",
Line 75: "EP033090100196": "skipped",
Line 77: "EP033314780044": "skipped",
Line 78: "EP033462770065": "skipped",
Line 90: "EP035160200050": "skipped",
Line 102: "EP038524030013": "skipped",
Line 135: "EP040370110014": "skipped",
Line 139: "EP042235110239": "skipped",
Line 223: "EP046266920005": "skipped",
Line 239: "MV000031270000": "skipped",
Line 241: "MV000041860000": "skipped",
Line 243: "MV000104260000": "skipped",
Line 245: "MV000132230000": "skipped",
Line 246: "MV000135600000": "skipped",
Line 247: "MV000155770000": "skipped",
Line 249: "MV000186450000": "skipped",
Line 262: "MV000231050000": "skipped",
Line 267: "MV000265910000": "skipped",
Line 268: "MV000268680000": "skipped",
Line 270: "MV000276180000": "skipped",
Line 274: "MV000317390000": "skipped",
Line 276: "MV000319640000": "skipped",
Line 288: "MV000420770000": "skipped",
Line 289: "MV000425670000": "skipped",
Line 302: "MV000521230000": "skipped",
Line 303: "MV000543570000": "skipped",
Line 305: "MV000551550000": "skipped",
Line 309: "MV000661480000": "skipped",
Line 310: "MV000693200000": "skipped",
Line 312: "MV000709610000": "skipped",
Line 313: "MV000709620000": "skipped",
Line 324: "MV001003060000": "skipped",
Line 325: "MV001011260000": "skipped",
Line 329: "MV001060550000": "skipped",
Line 332: "MV001154490000": "skipped",
Line 333: "MV001157440000": "skipped",
Line 343: "MV001313840000": "skipped",
Line 345: "MV001341920000": "skipped",
Line 346: "MV001356130000": "skipped",
Line 347: "MV001357600000": "skipped",
Line 349: "MV001360320000": "skipped",
Line 367: "MV001646640000": "skipped",
Line 373: "MV001800770000": "skipped",
Line 376: "MV001811280000": "skipped",
Line 382: "MV001913830000": "skipped",
Line 386: "MV001923830000": "skipped",
Line 389: "MV001970140000": "skipped",
Line 391: "MV002000700000": "skipped",
Line 394: "MV002036780000": "skipped",
Line 399: "MV002131380000": "skipped",
Line 400: "MV002134860000": "skipped",
Line 403: "MV002151160000": "skipped",
Line 408: "MV002292250000": "skipped",
Line 413: "MV002343710000": "skipped",
Line 414: "MV002372640000": "skipped",
Line 420: "MV002526070000": "skipped",
Line 421: "MV002536040000": "skipped",
Line 424: "MV002601030000": "skipped",
Line 426: "MV002664580000": "skipped",
Line 434: "MV003424420000": "skipped",
Line 438: "MV003752590000": "skipped",
Line 449: "MV004141460000": "skipped",
Line 451: "MV004167480000": "skipped",
Line 474: "MV005385380000": "skipped",
Line 482: "MV005459410000": "skipped",
Line 486: "MV005522570000": "skipped",
Line 488: "MV005540530000": "skipped",
Line 490: "MV005604180000": "skipped",
Line 492: "MV005630850000": "skipped",
Line 498: "MV006059610000": "skipped",
Line 501: "MV006327300000": "skipped",
Line 510: "MV007435850000": "skipped",
Line 516: "MV007770750000": "skipped",
Line 523: "MV008103840000": "skipped",
Line 542: "MV009903790000": "skipped",
Line 557: "MV011806830000": "skipped",
Line 562: "MV012110440000": "skipped",
Line 567: "MV012461360000": "skipped",
Line 570: "MV012575760000": "skipped",
Line 573: "MV012678360000": "skipped",
Line 574: "MV012688620000": "skipped",
Line 576: "MV012792480000": "skipped",
Line 582: "MV013926300000": "skipped",
Line 584: "MV015340300000": "skipped",
Line 587: "MV015857090000": "skipped",
Line 590: "MV016232550000": "skipped",
Line 603: "MV017516120000": "skipped",
Line 605: "MV017672410000": "skipped",
Line 610: "MV018067140000": "skipped",
Line 611: "MV018092640000": "skipped",
Line 615: "MV018415220000": "skipped",
Line 625: "MV018899450000": "skipped",
Line 641: "MV019952840000": "skipped",
Line 652: "placeholder/Testencoder/1684220400": "skipped",
Line 654: "pluto/5ac50b1fea0c647dd15b7c51/1986-01-01T08:00:00.000Z": "skipped",
Like I said, I have to resort to using curl because there is no other way. It's a pain.
You have to decipher what show/movie the entries are for since /dvr/groups doesn't contain the tms id's.
I have to look them up at zap2it to see what show/movie it is.
"EP046266920005": "skipped", == https://tvlistings.zap2it.com/overview.html?programSeriesId=SH04626692
"MV000031270000": "skipped", == https://tvlistings.zap2it.com/overview.html?programSeriesId=MV00003127
Then try to remember why they were cancelled/skipped and decide if I want to mark them as unskipped.
Then to unskip them
curl -XDELETE http://127.0.0.1:8089/dvr/programs/EP046266920005
curl -XDELETE http://127.0.0.1:8089/dvr/programs/MV000031270000
For me, multiply the effort x4 because I run 4 dvr servers.
One of the reasons I stopped using the Homerun DVR is that if you accidently delete a recording and want to re-record it you have to file a trouble TKT to cleanup the DB unless you delete it with re-record which is not the default... In my opinion a Prune and regenerate should clean this up.
This is a deal breaker for me...as I have everything automated etc ... going through the logs and running Curl scripts to re-record a show makes no sense to me. How can a non-technical person handle this ? also a pass that has re-record deleted should be able to handle this.
Guess we're the only two users that have an issue with it.
Makes me wonder how many other users have missed recordings and no clue why they weren't scheduled.
So if a show is recording and I noticed the game has run into overtime and the recording is not the actual show and I cancel it ,,, it will never record again ? even if It airs in the future ?
Good point. I am not aware of missed recordings on my side but I'll keep an eye on it
100% correct.
Well we made our Case waiting on what the developers think.
And it's not straight forward trying to find out what was cancelled or skipped from the dvr log.
You could grep for '[DVR] Skipping job'
2023/06/07 19:00:00.001926 [DVR] Skipping job 1686189600-21 Viewfinder
Now you have have the scheduled job# 1686189600-21 which tells you what time it was scheduled for (1686189600) and what the pass# is (21).
You then have to grep for the job# '1686189600-21' to see when it got scheduled
2023/05/23 09:25:05.342151 [DVR] queued recording job for EP007798310148 @ Wed Jun 7 7:00:00PM on ch=[706] (1686189600-21)
and look at the log to see the lines before it
2023/05/23 09:25:05.305215 [DVR] Rule 'Viewfinder-706 7PM' (21) found 1 new airings
2023/05/23 09:25:05.342151 [DVR] queued recording job for EP007798310148 @ Wed Jun 7 7:00:00PM on ch=[706] (1686189600-21)
That's just for one of them.