Collecting QAM data to supplement listing information - scan

Re: Collecting QAM data to supplement listing information -

Postby rkulagow » Sun Dec 30, 2012 6:14 pm

oneadvent wrote:I get:

oneadvent@XBMC:~/source/qamscanner$ (git::master) ./qamscanner.pl --verify=mpg --end=1700 --start=1
Can't locate File/HomeDir.pm in @INC (@INC contains: /etc/perl /usr/local/lib/perl/5.12.4 /usr/local/share/perl/5.12.4 /usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.12 /usr/share/perl/5.12 /usr/local/lib/site_perl .) at ./qamscanner.pl line 24.
BEGIN failed--compilation aborted at ./qamscanner.pl line 24.


From the README:

You need to install libfile-homedir-perl in order to run the script:
$ sudo apt-get install libfile-homedir-perl

Have you done that?
rkulagow
SD Staff
 
Posts: 890
Joined: Tue Aug 14, 2007 3:15 pm

Re: Collecting QAM data to supplement listing information -

Postby rkulagow » Sun Jan 27, 2013 5:41 pm

oneadvent wrote:That was the problem.

It also seems only cable cards are supported, and I have the one that does not have a cable card.


Right - the issue is "how do we correlate the qam information with a callsign / stationID"? With a cable card HDHR and a non-CC, it's easy to first determine the mapping of QAM channels and programs, and then run a second scan with a non-CC to confirm that they're actually viewable with a non-CC device.

It's still possible to do manually, but that's a whole lot of work.
rkulagow
SD Staff
 
Posts: 890
Joined: Tue Aug 14, 2007 3:15 pm

Re: Collecting QAM data to supplement listing information -

Postby rkulagow » Mon Jan 28, 2013 9:29 pm

The scanner has been re-written to take advantage of Schedule Direct's new JSON service, which will speed up the process of integrating QAM data into the live data.

If you would like to test the new scanner, please let me know so that you can be added to the beta server.

The client is located at https://github.com/rkulagowski/qamscanner
rkulagow
SD Staff
 
Posts: 890
Joined: Tue Aug 14, 2007 3:15 pm

Re: Collecting QAM data to supplement listing information -

Postby rkulagow » Mon Jun 17, 2013 9:17 am

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.
rkulagow
SD Staff
 
Posts: 890
Joined: Tue Aug 14, 2007 3:15 pm

Re: Collecting QAM data to supplement listing information -

Postby rkulagow » Mon Jun 17, 2013 1:06 pm

Yes, you can send it to [url]qam-info@schedulesdirect.org[/url]
rkulagow
SD Staff
 
Posts: 890
Joined: Tue Aug 14, 2007 3:15 pm

Previous

Return to Announcements

Who is online

Users browsing this forum: No registered users and 2 guests

cron