home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 1
MediaPortal 1 Talk
Hauppauge HD-PVR & Colossus Support
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="mm1352000" data-source="post: 752020" data-attributes="member: 82144"><p>Like I said, I really have no idea about this stuff. I *think* what most people are using is IRSS, but I'm not sure about that. If I'm right then <a href="http://wiki.team-mediaportal.com/1_MEDIAPORTAL_1/17_Extensions/3_Plugins/IRSS_%28IR_Server_Suite%29" target="_blank">this</a> wiki page (or maybe <a href="http://wiki.team-mediaportal.com/1_MEDIAPORTAL_1/17_Extensions/3_Plugins/IRSS_(IR_Server_Suite)/MP1_Plugins/TV3_Blaster_Plugin" target="_blank">this one</a> more specifically) and the <a href="https://forum.team-mediaportal.com/ir-server-suite-irss-165/ir-server-suite-aka-irss-releases-75092/" target="_blank">IRSS</a> release thread might be a starting point. IRSS has <a href="https://forum.team-mediaportal.com/ir-server-suite-irss-165/" target="_blank">its own forum section</a> - I'm certain that would make for interesting reading, however I'm not certain that I wouldn't be sending you on a "wild goose chase".</p><p></p><p>@<other readers>: Any advice would be *much* appreciated! <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite2" alt=";)" title="Wink ;)" loading="lazy" data-shortname=";)" /></p><p></p><p></p><p>Okay - sorry I'll try and go slower. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite8" alt=":D" title="Big Grin :D" loading="lazy" data-shortname=":D" /></p><p></p><p></p><p>Let's be clear: there are two mapping processes:</p><p><strong>1. Linking the channels that you create to the Colossus</strong></p><p>Channels have to be mapped to tuners so that MP knows which tuners to use when you want to view those channels. Creating and editing this mapping is ***really*** easy. See <a href="http://wiki.team-mediaportal.com/1_MEDIAPORTAL_1/141_Configuration/TV-Server_Configuration/03_TV_Channels/2_Mapping" target="_blank">here</a> for info. This only has to be done <strong>once</strong>, and is as quick as clicking one button.</p><p><strong>2. Linking the channels in the guide info to the channels in MP</strong></p><p>In order to know how to populate the guide correctly MP has to know where to get the data for each channel from. That is why there is a mapping in the XMLTV plugin - to explicitly link MP channels to guide channels. This also only has to be done <strong>once</strong>, as long as the guide channel names don't change. The plugin is "smart" in that it can guess the mappings automatically if the MP channel name closely matches the guide channel name. It would be smart to make use of that so you don't have to manually set the mappings for 100's of channels. That is why I suggested creating your MP channels with the same names as the guide channels to start with.</p><p></p><p></p><p>Yep, that is sensible. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile :)" loading="lazy" data-shortname=":)" /></p><p></p><p></p><p>I think you've missed the point of the MySQL and PHP. The purpose is to *create the channels in MP*. If you don't have channels then you don't see any guide info and you can't create either of the two kinds of mappings. You have to create the channels before anything else.</p><p></p><p>This is also a one time thing. You already know how to do it from the instructions I gave you earlier (the messing around in the TV channels list), so you could do it manually. However, like you said it would take all day for hundreds of channels. Since you know MySQL and PHP you may be able to write a script that can *create the channels* in the MP DB (which is what the UI does behind the scenes).</p><p></p><p></p><p>I guess you could think of that as a third kind of mapping. A channel (as you see it in the UI) consists of a channel record + one or more tuning details. A channel record in the DB is the logical representation of channels in the UI. Tuning details are ways to access/tune a channel - you need separate tuning details because some people can get the same "logical" channel from satellite, digital terrestrial and/or analog terrestrial broadcasts. With your Colossus there is only going to be one tuning detail per channel. The tuning detail tells MP how to "tune" the channel on the Colossus.</p><p></p><p></p><p>I *think* you're getting the data from "somewhere" and putting it into the tables. I say "I think" because I'm not 100% sure that the list of guide channels is not somewhere in the DB. The most straightforward answer is to assume that the data is not in the DB and you have to create the records.</p><p></p><p></p><p>The date is irrelevant as you're only creating channels. If you are smart enough with your PHP you could extract the channel names and numbers from the XML. That is all that would be relevant - just the channel names and numbers. For all intents and purposes this has nothing to do with getting the guide working. It just might be convenient (if you are able) to use the guide data as a source for your channel list.</p><p></p><p></p><p>Channel names and numbers. For example:</p><p></p><p>CBS, 1</p><p>NBC, 42</p><p>ABC, 13</p><p></p><p>(numbers made up)</p><p></p><p></p><p>You are creating one record in the Channel table and one record in the TuningDetail table for each channel that you want in MP.</p><p></p><p></p><p><strong>For the TuningDetail records:</strong></p><p>You copy the tuning detail for the YRYBY channel and use your preferred channel number in the "lcn" column.</p><p></p><p><strong>For the channel records:</strong></p><p>1. Your own knowledge of the channels that you can receive.</p><p>2. The channel list in your STB.</p><p>3. A website/magazine listing the channels that are available in your area.</p><p>4. The channels in the guide data.</p><p>...</p><p>There are many options. It is all about what is most convenient for you. If you're going to create the channels in the DB with a PHP script then it makes sense to me to use data that is already electronic and easily usable so you don't have to type out a list of 100's of channel names and numbers. That is why I suggested the guide data as a potential source. Not only that - if you take the names from the guide data then creating the 2nd mapping mentioned above (MP channels to guide channels) should be automatic.</p><p></p><p>The channels records in the guide data will look very roughly like:</p><p></p><p></p><p>(taken from <a href="http://wiki.xmltv.org/index.php/XMLTVFormat" target="_blank">XMLTVFormat - XMLTV</a>)</p><p></p><p>The data that you might choose to use as the name and number will depend on what your data looks like and whether there is even a number available. I can't really second-guess how "rich" your XML file will be (having full guide info with [for example] actor or host names, release years etc. is rare - most data is bare minimum).</p><p></p><p></p><p>No problem - its what I'm here for. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile :)" loading="lazy" data-shortname=":)" /></p><p>I'm hoping other people will benefit from our discussions in the future. This is almost turning into a patchy sort of guide...</p></blockquote><p></p>
[QUOTE="mm1352000, post: 752020, member: 82144"] Like I said, I really have no idea about this stuff. I *think* what most people are using is IRSS, but I'm not sure about that. If I'm right then [URL="http://wiki.team-mediaportal.com/1_MEDIAPORTAL_1/17_Extensions/3_Plugins/IRSS_%28IR_Server_Suite%29"]this[/URL] wiki page (or maybe [URL="http://wiki.team-mediaportal.com/1_MEDIAPORTAL_1/17_Extensions/3_Plugins/IRSS_(IR_Server_Suite)/MP1_Plugins/TV3_Blaster_Plugin"]this one[/URL] more specifically) and the [URL="https://forum.team-mediaportal.com/ir-server-suite-irss-165/ir-server-suite-aka-irss-releases-75092/"]IRSS[/URL] release thread might be a starting point. IRSS has [URL="https://forum.team-mediaportal.com/ir-server-suite-irss-165/"]its own forum section[/URL] - I'm certain that would make for interesting reading, however I'm not certain that I wouldn't be sending you on a "wild goose chase". @<other readers>: Any advice would be *much* appreciated! ;) Okay - sorry I'll try and go slower. :D Let's be clear: there are two mapping processes: [B]1. Linking the channels that you create to the Colossus[/B] Channels have to be mapped to tuners so that MP knows which tuners to use when you want to view those channels. Creating and editing this mapping is ***really*** easy. See [URL="http://wiki.team-mediaportal.com/1_MEDIAPORTAL_1/141_Configuration/TV-Server_Configuration/03_TV_Channels/2_Mapping"]here[/URL] for info. This only has to be done [B]once[/B], and is as quick as clicking one button. [B]2. Linking the channels in the guide info to the channels in MP[/B] In order to know how to populate the guide correctly MP has to know where to get the data for each channel from. That is why there is a mapping in the XMLTV plugin - to explicitly link MP channels to guide channels. This also only has to be done [B]once[/B], as long as the guide channel names don't change. The plugin is "smart" in that it can guess the mappings automatically if the MP channel name closely matches the guide channel name. It would be smart to make use of that so you don't have to manually set the mappings for 100's of channels. That is why I suggested creating your MP channels with the same names as the guide channels to start with. Yep, that is sensible. :) I think you've missed the point of the MySQL and PHP. The purpose is to *create the channels in MP*. If you don't have channels then you don't see any guide info and you can't create either of the two kinds of mappings. You have to create the channels before anything else. This is also a one time thing. You already know how to do it from the instructions I gave you earlier (the messing around in the TV channels list), so you could do it manually. However, like you said it would take all day for hundreds of channels. Since you know MySQL and PHP you may be able to write a script that can *create the channels* in the MP DB (which is what the UI does behind the scenes). I guess you could think of that as a third kind of mapping. A channel (as you see it in the UI) consists of a channel record + one or more tuning details. A channel record in the DB is the logical representation of channels in the UI. Tuning details are ways to access/tune a channel - you need separate tuning details because some people can get the same "logical" channel from satellite, digital terrestrial and/or analog terrestrial broadcasts. With your Colossus there is only going to be one tuning detail per channel. The tuning detail tells MP how to "tune" the channel on the Colossus. I *think* you're getting the data from "somewhere" and putting it into the tables. I say "I think" because I'm not 100% sure that the list of guide channels is not somewhere in the DB. The most straightforward answer is to assume that the data is not in the DB and you have to create the records. The date is irrelevant as you're only creating channels. If you are smart enough with your PHP you could extract the channel names and numbers from the XML. That is all that would be relevant - just the channel names and numbers. For all intents and purposes this has nothing to do with getting the guide working. It just might be convenient (if you are able) to use the guide data as a source for your channel list. Channel names and numbers. For example: CBS, 1 NBC, 42 ABC, 13 (numbers made up) You are creating one record in the Channel table and one record in the TuningDetail table for each channel that you want in MP. [B]For the TuningDetail records:[/B] You copy the tuning detail for the YRYBY channel and use your preferred channel number in the "lcn" column. [B]For the channel records:[/B] 1. Your own knowledge of the channels that you can receive. 2. The channel list in your STB. 3. A website/magazine listing the channels that are available in your area. 4. The channels in the guide data. ... There are many options. It is all about what is most convenient for you. If you're going to create the channels in the DB with a PHP script then it makes sense to me to use data that is already electronic and easily usable so you don't have to type out a list of 100's of channel names and numbers. That is why I suggested the guide data as a potential source. Not only that - if you take the names from the guide data then creating the 2nd mapping mentioned above (MP channels to guide channels) should be automatic. The channels records in the guide data will look very roughly like: (taken from [url=http://wiki.xmltv.org/index.php/XMLTVFormat]XMLTVFormat - XMLTV[/url]) The data that you might choose to use as the name and number will depend on what your data looks like and whether there is even a number available. I can't really second-guess how "rich" your XML file will be (having full guide info with [for example] actor or host names, release years etc. is rare - most data is bare minimum). No problem - its what I'm here for. :) I'm hoping other people will benefit from our discussions in the future. This is almost turning into a patchy sort of guide... [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
MediaPortal 1 Talk
Hauppauge HD-PVR & Colossus Support
Contact us
RSS
Top
Bottom
