until the virus struck this kinda thing was quite rare.The only way to defend against this kind of thing is to schedule on string match through RS.
That rather depends whether the match system is case sensitive.they seem to be matching
The Humax always uppercases the CRIDs in the rsv database so this isn't the problem, (though it can be when using a crid search via webif or RS)That rather depends whether the match system is case sensitive.
Wondering if 4 would have the exact starting time as 4hd. What is the exact time your recording started?New user so bear with me. (I can't post links, so only have part of the CRID on this post)
Mine recorded fine. The future schedule timer is also fine/still there
Series CRID:
ends with C4EI0020021616215774
But I record the Channel 4 program, and I suspect yours may be the Channel 4 HD? (due to different CRID)
I know, right?Oh no, it's those dam commies again
assuming 4+1 is exactly one hr behind what was your exact starting time?Successful: HL S8E09 from C4+1HD (57 minutes) Xtal Palace. CRIDs: WWW.CHANNEL4.COM/ - series: C41F0020021616215774 - prog: 67536/009.
So yet another s-CRID.
Wondering if 4 would have the exact starting time as 4hd. What is the exact time your recording started?
thanks but i was after the exact second of starting. are you familiar with the redring package and log? i'll take you through it if not.I believe it should have same timings, ie same broadcast but in SD.
These are the recordings I have. So you can tell the start time because I don't use padding
New_ Homeland_20200216_2102.ts (1006.64 MiB) Channel 4 Drama Decrypted Shrunk Indexed by DLNA Server
New_ Homeland_20200223_2100.ts (904.57 MiB) Channel 4 Drama Decrypted Shrunk Indexed by DLNA Server
New_ Homeland_20200301_2100.ts (855.52 MiB) Channel 4 Drama Decrypted Shrunk Indexed by DLNA Server
New_ Homeland_20200308_2100.ts (899.7 MiB) Channel 4 Drama Decrypted Shrunk Indexed by DLNA Server
New_ Homeland_20200315_2100.ts (937.53 MiB) Channel 4 Drama Decrypted Shrunk Indexed by DLNA Server
New_ Homeland_20200322_2100.ts (949.59 MiB) Channel 4 Drama Decrypted Shrunk Indexed by DLNA Server
New_ Homeland_20200329_2100.ts (1.04 GiB) Channel 4 Drama Decrypted Shrunk Indexed by DLNA Server
New_ Homeland_20200405_2110.ts (850.35 MiB) Channel 4 Drama Decrypted Shrunk Indexed by DLNA Server
New_ Homeland_20200412_2100.ts (811.06 MiB) Channel 4 Drama Decrypted Shrunk Indexed by DLNA Server
then what might be the explanation for the orphaned recording not picking up next week's episode?The Humax always uppercases the CRIDs in the rsv database so this isn't the problem, (though it can be when using a crid search via webif or RS)
Which particular recording?thanks but i was after the exact second of starting. are you familiar with the redring package and log? i'll take you through it if not.
Last Sunday's
12/04/2020 21:00:03 RM(32106)- DETECTADS: Checking /media/My Video/New_ Homeland/New_ Homeland_20200412_2100.ts (Channel 4) for channel exclusion
12/04/2020 21:00:04 RM(32106)- DETECTADS: Started /media/My Video/New_ Homeland/New_ Homeland_20200412_2100.ts for chaserun advert detection
12/04/2020 21:00:04 DA(32122)- ==DETECTADS Chase Run: /media/My Video/New_ Homeland/New_ Homeland_20200412_2100.ts
12/04/2020 21:00:05 DA(32122)- Temp Q entry 11215 created
12/04/2020 21:00:05 DA(32122)- Waiting for recording 180 seconds
12/04/2020 21:02:19 DA(22642)- ad break found 55:46-60:37 (3346 - 3637) Frames: 83644 - 90913
12/04/2020 21:02:19 DA(22642)- Hearbeat: Frame 92540 Time: 61:42 Seconds: 3702
12/04/2020 21:03:07 DA(32122)- ffmpeg pid 1847 limited to 65 % of cpu
12/04/2020 21:04:04 DA(32122)- ad break found 0:00-0:54 (0 - 54) Frames: 1 - 1345
12/04/2020 22:00:15 - Recorded: New_ Homeland/New: Homeland (60 minutes - Channel 4)