{"action":"created","issue":{"url":"https://api.github.com/repos/enternoescape/opendct/issues/295","repository_url":"https://api.github.com/repos/enternoescape/opendct","labels_url":"https://api.github.com/repos/enternoescape/opendct/issues/295/labels{/name}","comments_url":"https://api.github.com/repos/enternoescape/opendct/issues/295/comments","events_url":"https://api.github.com/repos/enternoescape/opendct/issues/295/events","html_url":"https://github.com/enternoescape/opendct/issues/295","id":171304177,"number":295,"title":"Chanel Scanning seems bugged for Native HDHR ATSC","user":{"login":"CraziFuzzy","id":3046737,"avatar_url":"https://avatars.githubusercontent.com/u/3046737?v=3","gravatar_id":"","url":"https://api.github.com/users/CraziFuzzy","html_url":"https://github.com/CraziFuzzy","followers_url":"https://api.github.com/users/CraziFuzzy/followers","following_url":"https://api.github.com/users/CraziFuzzy/following{/other_user}","gists_url":"https://api.github.com/users/CraziFuzzy/gists{/gist_id}","starred_url":"https://api.github.com/users/CraziFuzzy/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/CraziFuzzy/subscriptions","organizations_url":"https://api.github.com/users/CraziFuzzy/orgs","repos_url":"https://api.github.com/users/CraziFuzzy/repos","events_url":"https://api.github.com/users/CraziFuzzy/events{/privacy}","received_events_url":"https://api.github.com/users/CraziFuzzy/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":41,"created_at":"2016-08-16T01:58:56Z","updated_at":"2016-12-23T20:44:42Z","closed_at":null,"body":"When doing a channel scan from sage for ATSC tuning, there is some issue in the data returned, resulting in a junked up lineup in sage.  Looks like it is not detecting and returning actual program information.  Example:\n\n```\n17:04:06.271 [SageTVRequestHandler-123:HDHomeRun HDHR-US Tuner 10173AD8-0 Digital TV Tuner] DEBUG SageTVRequestHandler - SageTV sent: 'AUTOINFOSCAN HDHomeRun HDHR-US Tuner 10173AD8-0 Digital TV Tuner|10'\n17:04:06.272 [SageTVRequestHandler-123:HDHomeRun HDHR-US Tuner 10173AD8-0 Digital TV Tuner] INFO  HDHRNativeCaptureDevice - Capture device is was already locked.\n17:04:06.272 [SageTVRequestHandler-123:HDHomeRun HDHR-US Tuner 10173AD8-0 Digital TV Tuner] DEBUG HDHomeRunControl - key: '/tuner0/channel' value: 'auto:213000000' lockKey: '1062706233' sendLength: 49 address: 192.168.99.31\n17:04:06.523 [SageTVRequestHandler-123:HDHomeRun HDHR-US Tuner 10173AD8-0 Digital TV Tuner] DEBUG HDHomeRunControl - key: '/tuner0/status' value: 'null' lockKey: '0' sendLength: 25 address: 192.168.99.31\n17:04:06.525 [SageTVRequestHandler-123:HDHomeRun HDHR-US Tuner 10173AD8-0 Digital TV Tuner] DEBUG HDHomeRunControl - key: '/tuner0/streaminfo' value: 'null' lockKey: '0' sendLength: 29 address: 192.168.99.31\n17:04:06.776 [SageTVRequestHandler-123:HDHomeRun HDHR-US Tuner 10173AD8-0 Digital TV Tuner] DEBUG HDHomeRunControl - key: '/tuner0/streaminfo' value: 'null' lockKey: '0' sendLength: 29 address: 192.168.99.31\n17:04:06.777 [SageTVRequestHandler-123:HDHomeRun HDHR-US Tuner 10173AD8-0 Digital TV Tuner] DEBUG SageTVRequestHandler - Replied: '13-0;13-0;13-0;13-0'\n```\n\nI'll be looking into it, just wanted to see if you've done much (or any) testing of ATSC tuners.\n"},"comment":{"url":"https://api.github.com/repos/enternoescape/opendct/issues/comments/269043665","html_url":"https://github.com/enternoescape/opendct/issues/295#issuecomment-269043665","issue_url":"https://api.github.com/repos/enternoescape/opendct/issues/295","id":269043665,"user":{"login":"CraziFuzzy","id":3046737,"avatar_url":"https://avatars.githubusercontent.com/u/3046737?v=3","gravatar_id":"","url":"https://api.github.com/users/CraziFuzzy","html_url":"https://github.com/CraziFuzzy","followers_url":"https://api.github.com/users/CraziFuzzy/followers","following_url":"https://api.github.com/users/CraziFuzzy/following{/other_user}","gists_url":"https://api.github.com/users/CraziFuzzy/gists{/gist_id}","starred_url":"https://api.github.com/users/CraziFuzzy/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/CraziFuzzy/subscriptions","organizations_url":"https://api.github.com/users/CraziFuzzy/orgs","repos_url":"https://api.github.com/users/CraziFuzzy/repos","events_url":"https://api.github.com/users/CraziFuzzy/events{/privacy}","received_events_url":"https://api.github.com/users/CraziFuzzy/received_events","type":"User","site_admin":false},"created_at":"2016-12-23T20:44:42Z","updated_at":"2016-12-23T20:44:42Z","body":"I did look through the parsing logic, and the QAM parsing looked much more appropriate to CableCard use than the 'Other' parsing (which is essentially for DVB, but is not really refined), which is what is being used now.  QAM parsing will look through the existing lineup for the scanned channel by name, and if it finds it, will match that.  If it doesn't find it's match by name, it will also compare the number, and if that matches to a station that is a zap2it station (StationID >10000), it will match it to that.\r\n\r\nI made a test JAR that adds QAM to the results, to force it to use that method, and the results were pretty reliable.  The HBO thing above was still an issue, and it had a real problem with Music Choice channels.  This is because before it even tries matching things, the QAM tests drop the digit off the end - so all the MC20-MC29 channels are matching to MC2 by name, and then doing some weird things to add an incrementing number to the end to match it from there - really sort of a pain, and an easy fix in sage would be to test for an exact match (physical number AND name) before doing any massaging of the info.\r\n\r\nConclusion, really, is that a new Broadcast type should probably be set and returned in the results.  CC or DCT maybe.  Technically, some of the issues I'm seeing with using QAM would be issues for actual QAM scans as well, but I think the 'correct' way is to not call the scan results from a cablecard tuner 'QAM'.  Calling them CC or DCT will keep things the same as the status quo (because if Sage doesn't recognize the BroadcastType as ATSC, DVB, or QAM, it will use the Other/Blank logic), but specific improvements could be made on the sage end to deal with these CC scans a bit differently (putting the physical number match as a priority above matching to a name or altered name)."}}
{"actor":{"display_login":"CraziFuzzy"}}