On Sun, 2008-07-13 at 00:26 -0500, Nick Bright wrote: > Andy Walls wrote:
> > With the above channles.conf, I can watch a station with mplayer using > > something like: > > > > $ mplayer dvb://WJLA-HD > > > I've gotten a channels.conf that seems to resemble reality, at least > remotely. But when I tell mplayer to try to play one of the channels > that has both video and audio PID's it complains: > > Playing dvb://[0133] > DVBIN: no such channel "0133" > Failed to open dvb://[0133] > Exiting... The '[' and ']' are special characters to most shells. Try escaping them with a '\' $ mplayer dvb://\[0133\] Or you could just edit the weird names in channels.conf to something without those special characters. > However, I can import the channels.conf to mythtv and it does display > video on those channels, but only some strange pulsing static on the > audio. I probably don't have something configured correctly. Mplayer has a known bug with handling the A52 audio streams used in ATSC if they don't happen to be packed in a particular way (even though the packing mplayer doesn't like is legal). Try another station and see if it's better. Also update to the latest version of mplayer. You could also try adding a "-cache 8192" option to the mplayer command line. > The MythTV > channel scanner also only identifies four of the channels as being > nonencrypted - they happen to be my 'local' stations. However, I do know > that there are several other clear qam channels available such as > Universal HD, Nat. Geo HD, Discovery HD, TNTHD, TBSHD, and a couple others. > > Also, when I do different types of scans, I'm getting different results. > Does it matter if I choose . vs _ vs - for channel separators? That's for personal preference and what's convenient for your remote (if someone other than you manually types in channel codes at the remote). I use "." because that's what my remote has, and it's what my Sony TV does, so we're used to it. > How > important is having the correct QAM (256, 128, 64)? Very. If you've go the modulation wrong, you won't deocde that channel. You can expect a mix of modulations: QAM-256, QAM-128, QAM-64, and maybe even 8-VSB over cable. > All of the options > I've tried have identified channels, but none show the same number of > channels (and mostly, different channel numbers). That sounds right. > Interestingly none of > them seem play in Myth. The only thing that has actually displayed video > is importing channels.conf that was generated by the scan utility. > > If this is getting off topic for ivtv-users please let me know and I'll > take it over to the mythtv mailing lists. It's getting a little off-topic. However on the linux-dvb list, one user did identify a problem wityh scanning QAM channels when the cx18 driver switch from using the mxl500x module to the mxl5005s module for digital tuning. I don't have cable or the datasheet for the mxl5005s, so I can't help there right now. Sorry. You may want to search the linux-dvb list archives and post a question to that list. For that particular HVR-1600 problem. Regards, Andy _______________________________________________ ivtv-users mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-users
