BLU Discuss list archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
another Comcast head-end goes digital
- Subject: another Comcast head-end goes digital
- From: tmetro-blu-5a1Jt6qxUNc at public.gmane.org (Tom Metro)
- Date: Thu, 01 Apr 2010 01:47:36 -0400
- In-reply-to: <z2h2d6a9f6f1003311328x8d5501fau7f0620e827b3a5d8-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
- References: <4B590A40.2020209@vl.com> <2d6a9f6f1001220029t5911140v3d36f6018eeffed2@mail.gmail.com> <4BB2F59F.3000800@vl.com> <z2h2d6a9f6f1003311328x8d5501fau7f0620e827b3a5d8@mail.gmail.com>
Bill Bogstad wrote: > Have you run the hdhomerun_config_gui and verified that you have > clear QAM signals which are viewable? Hadn't recently, but yup, still getting clear QAM for extended basic channels. As far as scte65scan is concerned, that shouldn't matter, right? > I'm currently using the rev28 SVN version. I just checked and there > is apparently a rev29 as well. OK, I checked out the trunk from svn. Looks like it is still necessary to patch the makefile for the newer HDHR library. >> 3. determine the right scte65scan command line options to get it to produce >> just the right SQL (referencing the correct tuner IDs, etc.) to load into >> MythTV's database. Sounds like there's a potential for conflicting channel >> IDs too, if you have multiple digital tuners. > > The svn version has the -f n,m option which let's you specify the > source id. That's your listing source id rather then tuner id. OK. Are the sources numbered sequentially from zero? Short of digging in the DB, can you determine the ID of a source? (It may be obvious from the UI. I haven't checked.) > I have two HDHomeRuns (4 tuners) and they all use the same set of > entries in the channel table. That makes sense. I don't know hat scenario the README was describing then. Multiple digital tuners, each with a different lineup? Not important, I guess. > I THINK if the channel callsigns match up between what your listings > source (SchedulesDirect) and Comcast sends via scte65 that no extra > effort will be required. I think I had to manually change the > callsigns in order to make them match. I believe I did this via the > MythWeb channel editor so it wasn't so bad. Ah. I was wondering how the MythWeb channel editor came into play, as it has no mechanism to identify which channels go with which sources, but I guess it doesn't need to, as it reflects the aggregated collection of available channels. Though wouldn't modifying the call signs mess up mappings for any existing sources? I suppose the channels with variances are likely not on the old analog lineup. > I'm sorry about so many "I thinks". It was all > kind of trial and error... No problem. Any clues towards the easiest path are helpful. > I believe that my system is HRC as well and I have no problem using > that file for scte65 scans. Really? Misleading documentation, then. > Have you tried scanning for PSIP data as well (-p)? I hadn't. % ./scte65scan -H FFFFFFFF,1 -p -s 30 PID 0x1ffc timeout PID 0x1ffb timeout PSIP channels VC NAME FREQUENCY MODULATION PROG =========================================== % ./scte65scan -p -H FFFFFFFF,1 us-Cable-Standard-center-frequencies-QAM256 tuning 57000000hz.....no lock tuning 63000000hz.....no lock tuning 69000000hz.....no lock tuning 79000000hz.....no lock [...] tuning 795000000hz.....no lock tuning 801000000hz.....no lock PSIP channels VC NAME FREQUENCY MODULATION PROG =========================================== > Even if Comcast isn't sending SCTE65 data in your area you should at > least be able to see PSIP data. I don't see why they wouldn't be. I'm pretty sure they are using the STBs here that make use of it. I'm still leaning towards it being a frequency table problem. I don't get why it is so hard to find the other common tables. >> Did I see a post from you more recently on MythTV users indicating that you >> had received notice from Comcast that the clear QAM was going away? > > Yes. I haven't received any such letter. So what's the idea behind this? Provide clear QAM during the analog to digital transition, then once people are watching via the QAM tuners built-in to their TVs, turn on encryption to annoy everyone? Was it their idea of making the transition easier, so you didn't have to a STB by the analog cut over? But now that the transition period has passed, they'll encrypt everything to prevent theft of all those commercial filled extended basic cable channels? > I've already reinstalled my PVR-150 into my backend and have a USB IR > blaster on order. My cutoff date is April 7. What fun. So your HDHR boxes get relegated to being OTA tuners? (OTA channels via cable.) I guess still useful for OTA HD. Have you looked up recommendations for which STBs are the best to get from Comcast for automation? I still plan to try controlling the Motorola STB I have via serial. In theory that should be more reliable than IR. Thanks Bill. -Tom -- Tom Metro Venture Logic, Newton, MA, USA "Enterprise solutions through open source." Professional Profile: http://tmetro.venturelogic.com/
- Next by Date: another Comcast head-end goes digital
- Next by thread: another Comcast head-end goes digital
- Index(es):