Doug Larrick wrote:
The attached patch fixes a longstanding difficulty in setting up an HDTV
Myth box, namely that you needed to go in and manually set the freqid
field in your database as appropriate for each of your stations.
Look back in this thread for the rest of the details.
This version
The attached patch fixes a longstanding difficulty in setting up an HDTV
Myth box, namely that you needed to go in and manually set the freqid
field in your database as appropriate for each of your stations. This
information is provided by datadirect, and thanks to Daniel's recent
work in the
Am I missing something on the channel majorminor part? What if I
have the following channels:
hdtv channel 2 subchannel 1
ntsc channel 21
Won't both of these channels be channel 21?
On Thu, 09 Dec 2004 08:28:11 -0500, Doug Larrick [EMAIL PROTECTED] wrote:
The attached patch fixes a
The ultimate result of parsing the control tables in ATSC (and DVB) is a
set of video, audio, and other PIDs in the TS stream to process and/or
pass through to the recording on disk. This set of PIDs typically
remains constant for a given channel, and so storing it in the database
would
bill peck wrote:
Am I missing something on the channel majorminor part? What if I
have the following channels:
hdtv channel 2 subchannel 1
ntsc channel 21
Won't both of these channels be channel 21?
Yes, they will, assuming you have both an ATSC and an NTSC tuner in the
same system. If 21 is
Kyle Rose wrote:
Doug, what will this patch do to my existing channel setup? Should I
blow away the rows in the channel and program tables associated with
the HDTV input before I run mythfilldatabase?
No need. For existing channels mythfilldatabase will simply rewrite the
freqid field. If you
]PID caching:
]The ultimate result of parsing the control tables in ATSC (and DVB) is a set of
]video, audio, and other PIDs in the TS stream to process and/or pass through to
]the recording on disk. This set of PIDs typically remains constant for a given
]channel, and so storing it in the
Daniel Thor Kristjansson wrote:
Should those be HDTV channel 2-1 and NTSC channel 21? That way if there
is a HDTV channel 2-10 and 21-0 there is no ambiguity. (Channel 21-0
would be NTSC channel 21 in the HDTV naming system.)
But the infrastructure in Myth to allow non-numeric channel numbers
On Thu, 9 Dec 2004, Doug Larrick wrote:
]Daniel Thor Kristjansson wrote:
] Should those be HDTV channel 2-1 and NTSC channel 21? That way if there is a
] HDTV channel 2-10 and 21-0 there is no ambiguity. (Channel 21-0 would be NTSC
] channel 21 in the HDTV naming system.)
]
]But the infrastructure
On Thursday 09 December 2004 12:59 pm, Joe Barnhart wrote:
--- Doug Larrick [EMAIL PROTECTED] wrote:
But the infrastructure in Myth to allow non-numeric
channel numbers
(i.e. with a hyphen) is just not there; nor do
remotes not designed for
HDTV sets have a hyphen button. I hit my head
Its a little more typing on the remote but we could require 5 digits
be entered in the remote if you don't have a hyphen key
channel 21 program 2 would be entered as 02102 on a non hyphen remote.
or entered as 21-2 on a hyphen remote.
channel 21 ntsc would be entered 02100 on a non hyphen
On Thu, 2004-12-09 at 13:35 -0500, bill peck wrote:
Its a little more typing on the remote but we could require 5 digits
be entered in the remote if you don't have a hyphen key
What seems logical to me is to default to the first subchannel and
provide a function mappable to a remote button to
Joshua M. Thompson wrote:
What seems logical to me is to default to the first subchannel and
provide a function mappable to a remote button to flip between the
subchannels.
Actually, this doesn't make sense at all, at least in my area. The
subchannels are not really related.
I have 3 channels
[EMAIL PROTECTED] wrote:
And it must not break the database/setup for those of us who cannot run
mythfilldatabase as there is no feed/info available (eg perth)
These changes only affect the built-in zap2it DataDirect grabber.
Though if you're manually setting up freqid's for HDTV in the database,
14 matches
Mail list logo
