[mythtv-users] HDHR3 recording fails, "wrong PMT"?
Hika van den Hoven
hikavdh at gmail.com
Wed Dec 3 20:31:39 UTC 2014
Hoi Eric,
Wednesday, December 3, 2014, 9:20:35 PM, you wrote:
> On Wed, Dec 3, 2014 at 2:54 PM, Hika van den Hoven <hikavdh at gmail.com> wrote:
>> Hoi Eric,
>>
>> Wednesday, December 3, 2014, 8:45:37 PM, you wrote:
>>
>>> On Wed, Dec 3, 2014 at 2:32 PM, Hika van den Hoven <hikavdh at gmail.com> wrote:
>>>> But what are the new settings for that channel? And do they match
>>>> with what you found outside MythTV?
>>
>>> They mostly match, but the transportid (if that's the same as TSID) is
>>> different. I don't know the importance of this information, or
>>> exactly what a "transportid" is.
>>
>> Again a little google:
>> http://www.interactivetvweb.org/tutorials/dtv_intro/dtv_intro
>>
>> What I understand is that it's an important part of identifying the
>> channel, so ...
> That page doesn't say anything about a "transport id", though. It
> says the transport stream contains substreams, each with their own id.
> I already knew that. But the id for the transport stream as a whole
> isn't mentioned.
> When using the hdhomerun_config command line utility to manually
> record something, you tune the channel using the frequency and program
> id (aka packet id/service id) only, there's no need to (or opportunity
> to) specify any "transport id".
> Eric
> _______________________________________________
I didn't read it fully, but it came up with others when I googled
"transportid dvb". I looked at the DB definition and in
https://www.mythtv.org/wiki/Channelscan_dtv_multiplex_table I find
it's the internal ID of that table. So the values in that table
probably contain invalid values for that transport.
Tot mails,
Hika mailto:hikavdh at gmail.com
"Zonder hoop kun je niet leven
Zonder leven is er geen hoop
Het eeuwige dilemma
Zeker als je hoop moet vernietigen om te kunnen overleven!"
De lerende Mens
More information about the mythtv-users
mailing list