TimerEvents

From openPMA
Jump to: navigation, search

== TimerEvents - format (holding the VideoCorder plans) ==


check it out in /root/Applications/VideoCorder/TimeEvents

a new dataset always starts with 00

00 25 72 64 startday in days-since-format (257264(this is a hex value) is 15.01.07) proof: 257265 is 16.01.07

04 66 19 40 starttime in ([hours]*1000+[minutes]*100/6)*3600

                   proof: 4661940 in dec is 73800000
                          73800000 / 3600  = 20500
                          (one hour has 60 minutes but the format is using "1000" for 1 hour) 
                          -> 60 * (100/6) is 1000 so 500 must be the for the minutes and the rest for the hours
                          20000 / 1000 = 20 <-- hour : 20
                          500 / (100/6) = 30 <-- minutes : 30
                          --> 20:30 is the starting time

00 25 72 64 stopday (in this case set to the same day as the startday )

04 81 90 80 stoptime if this is before the starttime the next day is selected to stop (even if the stopday is set) --> 21:00

00 00 00 00 channel number in hex and 0 is for "Current Channel"

00 00 00 00 empty (??? or maybe for BIG titles)

00 00 00 08 number if chars to follow *2 (so in this case we await 4 chars) (in hex of course)

00 74 00 65 --> t e

00 73 00 74 --> s t --> the title is "test"

the dataset ends with the last title char or the information about containing 0 chars

bad datasets are causing the VideoCorder to crash

Google ads
Personal tools