Turns out ZDF releases new event ids for each event instead of status 3 flagging, but they are all using the same pdc time (09:55).
@Klaus: Are you aware, that recording only the 2nd event (12:05-03:55) is impossible in this case? vdr will automatically remove timers with the same pdc time, only one timer is kept, and vdr will start recording immediately, if you're already in the first event's timeframe (09:55-12:00).
Shouldn't different event id make sure this doesn't happen?
On 14.01.2012 10:21, Lou wrote:
I noticed ZDF is boadcasting 3 sports sessions today using the same pdc time for all three events:
09:55 - 12:00 Wintersport 12:00 - 12:05 heute 12:05 - 03:55 Wintersport 03:55 - 04:00 heute 04:00 - 05:00 Wintersport
I'm test-recording this and will keep an eye on what's happening during the "heute journal", maybe they use status 3 as well in this case to remove the journal from vps recording?
On 14.01.2012 13:11, Lou wrote:
Turns out ZDF releases new event ids for each event instead of status 3 flagging, but they are all using the same pdc time (09:55).
@Klaus: Are you aware, that recording only the 2nd event (12:05-03:55) is impossible in this case? vdr will automatically remove timers with the same pdc time, only one timer is kept, and vdr will start recording immediately, if you're already in the first event's timeframe (09:55-12:00).
Shouldn't different event id make sure this doesn't happen?
The idea behind giving these three events the same PDC time *is* to have all three of them recorded ;-) VDR doesn't take event ids into account when handling VPS recordings.
Greetings Klaus
On 14.01.2012 10:21, Lou wrote:
I noticed ZDF is boadcasting 3 sports sessions today using the same pdc time for all three events:
09:55 - 12:00 Wintersport 12:00 - 12:05 heute 12:05 - 03:55 Wintersport 03:55 - 04:00 heute 04:00 - 05:00 Wintersport
I'm test-recording this and will keep an eye on what's happening during the "heute journal", maybe they use status 3 as well in this case to remove the journal from vps recording?
Thanks for pointing this out. That explains some of the problems I experienced with vps timers:
Consider this:
timer #1 scheduled for 22:20-22:50 - no pdc time defined by the broadcaster, so vps time is set to 22:20.
timer #2 scheduled for the following event (22:50-23:20) , but uses a pdc time of 22:20. Both events are not related -> there's no interest in combining these two events like it's done with sports.
You see the problem? vdr won't let you set vps-timer #1 AND #2 , you'll have to switch one of them to manual.
This happens occasionally - I assume it's partly the broadcaster's fault for choosing pdc 22:20 instead of something else like 22:30, but vdr could figure this out using event ids as a second marker. This could add some more flexibility to vps programming.
On 14.01.2012 13:16, Klaus Schmidinger wrote:
The idea behind giving these three events the same PDC time *is* to have all three of them recorded ;-) VDR doesn't take event ids into account when handling VPS recordings.
On 14.01.2012 15:21, Lou wrote:
Thanks for pointing this out. That explains some of the problems I experienced with vps timers:
Consider this:
timer #1 scheduled for 22:20-22:50 - no pdc time defined by the broadcaster, so vps time is set to 22:20.
timer #2 scheduled for the following event (22:50-23:20) , but uses a pdc time of 22:20. Both events are not related -> there's no interest in combining these two events like it's done with sports.
You see the problem? vdr won't let you set vps-timer #1 AND #2 , you'll have to switch one of them to manual.
This happens occasionally - I assume it's partly the broadcaster's fault for choosing pdc 22:20 instead of something else like 22:30, but vdr could figure this out using event ids as a second marker. This could add some more flexibility to vps programming.
PDC times *must* be unique within one channel - otherwise they're no good. It's the provider's duty to choose them correctly.
Klaus
On 14.01.2012 13:16, Klaus Schmidinger wrote:
The idea behind giving these three events the same PDC time *is* to have all three of them recorded ;-) VDR doesn't take event ids into account when handling VPS recordings.
-
Klaus Schmidinger -
Lou