On Apr 30, 2008, at 11:24 PM, Michael Krufky wrote:
Eric Cronin wrote:On Apr 30, 2008, at 8:20 PM, Michael Krufky wrote:Eric Cronin wrote:On Apr 30, 2008, at 2:36 PM, Michael Krufky wrote:Eric, When you use the scan command to scan for QAM channels, you must specify -a2, to signify that you are scanning digital cable. Try that -- does that work?My bad -- I meant, "-A 2" (capitol A, space, 2)scan -A 2 -vvv dvb-apps/util/scan/atsc/us-Cable-Standard-whatever > channels.conf Is THAT what you're doing to scan ?It looks like what you were doing was scan a tuned frequency for pids.If you want to do THAT, then you must actually be tuned to the given frequency. you need to azap SOME_CHANNEL -r, and keep that runningbefore attempting to run 'scan -c' ... I think you should try the scancommand that I mentioned above. HTH, MikeI was only using one -v, but the scan file isn't the problem. It is just the single line out of/usr/share/doc/dvb-utils/examples/scan/atsc/us-Cable-Standard- center-frequencies-QAM256 corresponding to a known good frequency. Otherwise it scans from 0-70which are all NTSC and gets annoying on repeated attempts... Adding two more -v's doesn't change anything, status is always 0x00 and nothing gets written to STDOUT (channels.conf) ~$ scan -A 2 -vvvThe -v is just for verbosity.My question should have been, "did you give it a chance to scan throughthe entire scan file? -Mike
Yes. Thanks, Eric
Attachment:
PGP.sig
Description: This is a digitally signed message part
_______________________________________________ linux-dvb mailing list linux-dvb@xxxxxxxxxxx http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
