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
Support
Electronic Program Guide
WebEPG
Channel importing in WebEPG
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="arion_p" data-source="post: 518175" data-attributes="member: 45945"><p>Like I said using a unique ID is not a good solution. You still have no way to tell which Channel 1 is the state channel and which is the regional. Naming them accordingly is a better choice i.e. <strong>Channel 1 (state)</strong> and <strong>Channel 1 (regional)</strong>.</p><p></p><p></p><p>Groups in WebEPG config are meant to allow people that have thousands of channels only import the ones they need. Other than that, all mapping are visible at all times in the list. Your proposed usage does not make much sense, since mapping channels to grabbers is done most probably only once (you don't remap your channels every day now, do you?) and you should map all of the channels you have imported. I don't see how it would help to only see channels in a specific group when mapping, in fact it is almost certain you are going to miss some.</p><p>Perhaps you misunderstood the usage of groups in WebEPG configuration. You cannot map different grabbers to the same channel based on which group you have selected. The group selection is there to limit what channels get imported when you press the <strong>Import</strong> button.</p><p></p><p></p><p>Rescanning and renaming are totally different things. When you rescan you delete all channels and creates new ones based on the scan. The new channels have new IDs. If WebEPG were to use IDs as you suggest, all your existing mappings would be lost because all channel IDs will change after a rescan.</p><p>Renaming a channel on the other hand preserves the channel id but since the name changes, the mapping is broken. In this case I believe a button to remove non existent channels is needed (automatically removing them is not a good choice as the rename may be accidental).</p></blockquote><p></p>
[QUOTE="arion_p, post: 518175, member: 45945"] Like I said using a unique ID is not a good solution. You still have no way to tell which Channel 1 is the state channel and which is the regional. Naming them accordingly is a better choice i.e. [B]Channel 1 (state)[/B] and [B]Channel 1 (regional)[/B]. Groups in WebEPG config are meant to allow people that have thousands of channels only import the ones they need. Other than that, all mapping are visible at all times in the list. Your proposed usage does not make much sense, since mapping channels to grabbers is done most probably only once (you don't remap your channels every day now, do you?) and you should map all of the channels you have imported. I don't see how it would help to only see channels in a specific group when mapping, in fact it is almost certain you are going to miss some. Perhaps you misunderstood the usage of groups in WebEPG configuration. You cannot map different grabbers to the same channel based on which group you have selected. The group selection is there to limit what channels get imported when you press the [B]Import[/B] button. Rescanning and renaming are totally different things. When you rescan you delete all channels and creates new ones based on the scan. The new channels have new IDs. If WebEPG were to use IDs as you suggest, all your existing mappings would be lost because all channel IDs will change after a rescan. Renaming a channel on the other hand preserves the channel id but since the name changes, the mapping is broken. In this case I believe a button to remove non existent channels is needed (automatically removing them is not a good choice as the rename may be accidental). [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Support
Electronic Program Guide
WebEPG
Channel importing in WebEPG
Contact us
RSS
Top
Bottom