https://bugs.kde.org/show_bug.cgi?id=364860
--- Comment #6 from Mauro Carvalho Chehab <mchehab+...@kernel.org> ---
(In reply to Rolf Pedersen from comment #5)
> (In reply to Mauro Carvalho Chehab from comment #3)
> I've been at work all day. When I got home, I cloned and built from
> git://anongit.kde.org/kaffeine
> If I got the right thing, it's worse than before, for me. After a channel
> scan, most are listed like:
>
> Channel Number
> #0 321:6 27
> #0 377:5 26
>
> Some are listed like:
> Channel Number
> 026-1 26 San Francisco, CA 4
That is an unrelated problem. Channel names are stored at the VCT table, with
is handled on a different part of the Kaffeine's code.
> I did blunder onto a productive dvbv5-scan command:
>
> dvbv5-scan -O ZAP -C US -I channel us-ATSC-center-frequencies-8VSB
>
> which gave me dvb-channel.conf
>
> then
>
> dvbv5-zap -c dvb_channel.conf -I ZAP -t 60 -o atsc.m2t KTVU-HD
>
> so it worked when channel, not frequency, was given.
Ah, there's one parameter missing there: "-P". (or " --all-pids"). When this
parameter is used, dvbv5-zap records the full content of the stream and accepts
both frequency or channel. So, it can work with the frequency tables file
directly.
So, please take another record with:
dvbv5-zap -c dvb_channel.conf -I ZAP -t 60 -o atsc.m2t -P KTVU-HD
or:
dvbv5-zap -I channel -c us-ATSC-center-frequencies-8VSB -t 60 -o atsc.m2t
-P 653028615
(if you're using the channel file with the legacy formats)
> FWIW, here's the clean-looking content of the ZAP dvb_channel.conf with
> nearly all my tunable channels present:
Thanks! I'll use it to compare it with the VCT parser at Kaffeine once you make
me available the all-pids record.
--
You are receiving this mail because:
You are watching all bug changes.
