Ah, OK thanks.It's in the vim package.
Ah, OK thanks.It's in the vim package.
How truly bizarre. I'm sure there's a good reason for it, but I have to say it completely eludes me. As it does for all the bloat in the rest of that package.It's in the vim package.
Yup. It would be hard to make a more unfriendly editor than vi, but I'm sure there must have been a good reason for it at the time!
How truly bizarre. I'm sure there's a good reason for it, but I have to say it completely eludes me. As it does for all the bloat in the rest of that package.
Yup. It would be hard to make a more unfriendly editor than vi, but I'm sure there must have been a good reason for it at the time!
Edit: I have updated the central file format documentation on the wiki - http://wiki.hummy.tv/wiki/HMT_File_Format
As you correctly suspect, the knowledge here is regarding the HDR-FOX and presumed to apply to the 1800T/2000T. Your feedback will be valuable in extending the knowledge to 1800T/2000T.Does anyone know whether this just applies to the Fox-T2 and/or whether it is accurate for the 2000T?
I know the answer to this of course - it 's all about the limitations of teletypes and VDUs.I'm sure there must have been a good reason for it at the time!
The hmt format as published here applies solely to the HDR Fox T2. The majority of the information it contains was gleaned from a previous analysis I did on the Foxsat HDR hmt format. There is a lot of commonality, but the precise location of each field can differ from box to box. From what I can gather the 2000T hmt format is, in the main, identical to that of the HDR Fox T2. You are correct about the EPG anomolies starting at offset 0x3000. The published format got screwed up somewhere along the way and an entire block is missing from that section. It went unnoticed and was never corrected, since no-one took any interest in the bit at the end (until now, that is). It should look like this:Does anyone know whether this just applies to the Fox-T2 and/or whether it is accurate for the 2000T?
I ask because for the 2000T the first EPG item in the area above 0x3000 apears to be at 0x30c0 and the area 0x3050-0x308C could be a duplicate of 0x0488-0x04c4. 0x3020 is the channel number (4 byte LE ?) and 0x3024 the channel name.
0x1000 4 byte 0x44332211 Number of EPG Blocks following
------ ----- ---------------------------------- EPG Header List Block, Size 8188 bytes (starts at 0x1004) ---------------------
0x0000 32 byte blocks Copy of 32 byte header from EPG blocks following. One entry for each EPG block.
0x0020
0x0040 Next EPG block header (if any)
------ ----- ---------------------------------- EPG Block type 01, Size 192 bytes (starts at 0x3000)---------------------------
0x0000 1 byte 0x01 Constant
0x0009 1 byte 0x30 Constant
0x000C 1 byte 0xA0 Constant
0x0020 4 bytes Channel Number
0x0024 1 byte 0x15 String header.
0x0025 43 bytes Channel name.
0x0050 2 bytes Program ID (SID).
0x0052 2 bytes Transport Stream ID (TSID)
0X0054 2 bytes Originating Network ID (ONID).
0x0056 2 bytes Program Map Table (PMT).
0x0058 2 bytes Video PID.
0x005A 2 bytes 0x0020 Constant.
0x005C 2 bytes Video PID
0x0060 1 byte Video Type MPEG2=0x01, H264=0x02.
0x0064 2 bytes Audio PID.
0x0068 1 byte Audio Type MPEG=0x01 AC3=0x03 AAC=0x07.
0x006D 1 byte 0x20 Constant
0x0075 1 byte 0x20 Constant
0x0080 1 byte 0x01 Constant
0x0084 1 byte Video type flag for Media list. 0x01 = SD. 0x02 = HD.
0x0088 1 byte 0x01 Constant
0x008C 1 byte 0xFF Constant
------ ----- ------------ EPG Block type 02, (event) Size 704 bytes,including 32 byte header (first block starts at 0x30C0) -----------
++++++ Start of 32 byte header +++++++++
0x0000 4 byte 0x02000000
0x0004 4 byte 0x00000000 Time in seconds from start of recording to change the iPlate info to this EPG block
0x0008 4 byte 0x00300000 12288. Byte Offset to start to EPG block.(increments by 704 for each EPG entry.
0x000C 4 byte 0xA0020000
0x0010 16 byte Unused
++++++ End of 32 byte header ++++++++++
It went unnoticed and was never corrected, since no-one took any interest in the bit at the end (until now, that is)
Correction: No-one, except af123 took any interest in the bit at the end...I did but must have used the format you originally sent me. The hmt utility will display summary information for each EPG block and the epgpatch package fixes it up as necessary.
Thanks for the above info (which confirms that I was on the right track when I worked it out!). The reason I flagged up the differences here is because this thread is listed under the 1800T/2000T banner.Correction: No-one, except af123 took any interest in the bit at the end...
Does not setting padding nullify AR. How can you start recording, say 5 mins, before the AR signal has been transmitted?I always use a padded AR setting
Does not setting padding nullify AR. How can you start recording, say 5 mins, before the AR signal has been transmitted?
We ... tend to refer to AR and padding as opposites and mutually exclusive because they have a completely different set of implications, .... So, padding is not an AR setting, AR is a padding setting!
I did qualify my statement by saying "until now, that is". (when the hmt analysis was first published the 2000T didn't even exist). I'm happy that you are now finding it useful in your endeavours on the 2000T. If nothing else, it has highlighted a long unnoticed, but unintentional, omission in the published hmt format. Many thanks..... as such, I (even if nobody else is) was interested in what is at the end of the .hmt file.
I did notice you had qualified the statement. My reply wasn't meant as any critisism, just an observation.I did qualify my statement by saying "until now, that is". (when the hmt analysis was first published the 2000T didn't even exist). I'm happy that you are now finding it useful in your endeavours on the 2000T. .
And I'm sure in the last reply I didn't say it was. Forget AR, I now get what it is, and see that my original description was confusing.That's still confused! AR is not auto-padding.
To clarify: by auto-pad you mean padding added to the recording start/stop times by the padding settings in the menus under Menu >> Settings >> Preferences >> Recording, and manually-pad you mean adjusting the recording schedule directly in Guide >> Schedule (yellow) >> (select entry) >> (edit settings)??However, I was also trying to point out the 2000T seems to store EPG/programme title data differently depending on whether you auto-pad or manually-pad.