lv128 wrote:I know this is necroposting, but I just wanted to know if this project is still being worked on, I did download the latest available script and fixed a bug or two in it, but since I've never worked on AWS, I don't know how to fix the parsing of the lineup download to get it to proceed any farther. Instead of parsing and saving the lineup zip file, it creates a plain text file with the response from the server inside it, and that response from the server has a URL which downloads a zip file containing onl server.ID file.
Maybe this project has been deprecated, is there something else that is available that I haven't seen?
Yes, the project is being worked on. But what we've discovered is that trying to bolt-on QAM data as an "extra" to the data which is downloaded directly from Tribune is difficult.
The beta JSON service incorporates the QAM information directly into the headend data, so it becomes an integral part of the data you get from the service.
Here's an example of IL58819 (lots of stuff cut out)
"X":{"map":[{"stationID":32046,"channel":"001"},{"stationID":11299,"channel":"002"},{"stationID":11438,"channel":"003"},{"stationID":11848,"channel":"004"},{"stationID":116
70,"channel":"005"},{"stationID":22219,"channel":"006"},{"stationID":11653,"channel":"007"}
{"name":"WLS","callsign":"WLS","affiliate":"ABC
Affiliate","broadcaster":{"city":"Chicago","state":"IL","zipcode":"60601","country":"United
States"},"language":"English","stationID":11653}
"QAM":{"map":[{"virtualChannel":"66-7","channel":"7","qamType":"QAM256","qamFreq":477000000,"qamProgram":7,"stationID":11653},{"virtualChannel":"77-200","channel":"200","qamType":"QAM256","qamFreq":543000000,"qamProgram":200,"stationID":20644}],"metadata":{"modified":"2013-05-20T13:53:48Z"}}
"metadata":[{"device":"Analog","modified":"2013-05-12T20:02:43Z"},{"device":"R","modified":"2013-05-12T20:02:43Z"},{"device":"X","modified":"2013-05-16T19:55:01Z"}]}
The file has much more than just that in it, but it breaks down:
- the Map of "X" gives you "Channel 7 is stationid 11653".
- StationID 11653 is "WLS, it's an ABC affiliate, etc".
- there's a QAM map, and stationID 11653 has {foo} QAM mapping and a
modified date, so that if the QAM map is changed the application can see
that the local copy is date "X", and the modified is date "Y", so need
to do something like prompt the user, or run a confirm scan or whatever.
- a lineup modified date, so that if the lineup for "X" changes, and the
local date is different then the server date, then there have been
channel move/add/changes, so better do something.
Discussion of the new format is in the "Developers Corner"
I just haven't had the cycles lately to fix the errors in the qam scanner because I've been focusing on the JSON service.
