OP
Brian Burch
Member
Success! I was back in Brisbane at the weekend and so used dvbsnoop to capture the EPGs on all 5 multiplexes. I then compared the values with those from the Sunshine Coast."select" isn't the right word. I "inherited" them from a successful auto-scan when in Brisbane. Having returned home to the Sunshine Coast I did not realise their significance for EPG data, so I left the existing (Brisbane) values alone while hacking channels.db to get the video and sound to work properly.
Only now am I sufficiently confident to work on the EPG. In other words, my current channels.db EPG data (whatever that might be) does not match dvbsnoop because the current values correspond to Brisbane, while my dvbsnoop data corresponds to the desired region of Sunshine Coast and are taken by dvbsnoop from the aerial.
I need to discover which fields in which tables to hack, given that my proposed ETI/EPG values are available from the aerial, according to the dvbsnoop ETI data for the five multiplexes.
I replaced the usTsId and usOrgNetId values in TBL_TS. I then replaced the usTsId and usOnId values in TBL_SVC. I now have the crummy Australian EPG working as well as expected. It can only render the EPG for the currently-tuned multiplex, so I have too switch channel group to populate another network's EPG and then the previous network's EPG immediately disappears. (Incidentally, some more modern Australian-market TVs and PVRs appear to cache the EPG from each multiplex, but I never expected my humax to do that kind of thing because of the earlier post about England/Wales border transmissions).