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
Development
Improvement Suggestions
Sort or restrict channels by group in mapping dialog
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="RobW" data-source="post: 1276485" data-attributes="member: 166387"><p>Many thanks CyberSimian for taking the time and trouble to reply to this. Much appreciated! </p><p></p><p>Taking your last point first, I did suspect what you have confirmed, that this being a mature product with very little if any rough edges, there were not likely to be programmers around willing to have a look. Well, I can always work around it by analysing the data using a safe copy of the MySQL database, or the xml export of MP, imported into Access or Excel and processed so I can identify those missing channels by hand every time I do an update scan. I was just hoping not to, but it was a long shot. </p><p></p><p>As to the rest of your message and why I would even want this improvement suggestion, well here is an explanation. Sorry about the length of it!</p><p></p><p>In my experience, satellite is different from terrestrial. Firstly because there are many hundred channels on a satellite and often about 120 muxes, as opposed to only 5 or 6 for terrestrial. There are also loads of encrypted channels. Scanning can take 30 minutes or more. Then, one is faced with a smorgasbord of channels, many of which are not of interest, and many are virtual duplicates e.g. here in the UK, all the regional versions of the BBC, ITV and Channel 4 transmissions are present on the same satellite. Some rationalisation is virtually essential, and rather time consuming. For example for UK channels I locate all the programmes for my region and number them according to the FreeSat numbering, then create a group "UKTV" for them in order to produce a rational TV listing, while keeping those other channels available in the backgound via an "Astra 28.2" Group. This is useful because occasionally I might want to watch, say, something exclusive to BBC1 Scotland, rather than my local channel. So you can see why, although I'm happy to delete and then refresh the tuner mappings, I don't want to interfere with the channel set up itself unless a channel is actually moved in the frequencies or taken off air altogether. </p><p></p><p>The second point about satellite receivers is that, in my experience, they don't always tune to all the channels they are capable of receiving. I'm sure that is the thought behind the comment I quoted from the wiki. This can be for various reasons, but I have a very specific example with my equipment, if you will indulge me a few minutes further ...</p><p></p><p>As I said in the first post, all my tuners are attached to a diseqc A/B switch to choose between satellites. Two of my tuners (DVBSky) are as good as gold with that, and if they were the only ones I had, I'd just re-scan as you describe every 6 months or so to catch any frequency changes, and that would be that. Unfortunately however my other two tuners (TBS) don't play fair with this arrangement, and it took me much head-scratching before I found out what was really going on. These tuners don't seem to cope well with diseqc switching during scanning, even though in normal use they can tune to the required channels without batting an eyelid. I've worked out that during scanning, if satellite A and satellite B have a closely similar or identical tuning frequency for a particular mux, these cards will always go for A even though they are supposed to be scanning B at the time. The result, during a B scan, is that the system thinks the channels found or updated on A are actually on B, and re-marks them as such. Resulting in neither Mux A nor Mux B for that frequency being correctly recorded in MP, a confusion of channels and the loss of those channels on A across all tuners, because they are now marked incorrectly as B so become untunable. </p><p></p><p>Once I'd figured out what was going on, the fix was obvious. I merely have to get the required scan on one of the "well behaved" tuners and apply it to the others, since they all work OK in actual use, some just fall down in scanning, and I'm sure this isn't a problem with MP. But how to be sure I had identified all the correct channels to map? Within over 1500 channels, there is plenty to confuse - there are channels marked "Sky ..." or "BBC ..." on the non-UK satellites, for example. If only I could limit it to groups and map the right groups to the right cards ...</p><p></p><p>And now you hopefully understand where I was coming from!</p></blockquote><p></p>
[QUOTE="RobW, post: 1276485, member: 166387"] Many thanks CyberSimian for taking the time and trouble to reply to this. Much appreciated! Taking your last point first, I did suspect what you have confirmed, that this being a mature product with very little if any rough edges, there were not likely to be programmers around willing to have a look. Well, I can always work around it by analysing the data using a safe copy of the MySQL database, or the xml export of MP, imported into Access or Excel and processed so I can identify those missing channels by hand every time I do an update scan. I was just hoping not to, but it was a long shot. As to the rest of your message and why I would even want this improvement suggestion, well here is an explanation. Sorry about the length of it! In my experience, satellite is different from terrestrial. Firstly because there are many hundred channels on a satellite and often about 120 muxes, as opposed to only 5 or 6 for terrestrial. There are also loads of encrypted channels. Scanning can take 30 minutes or more. Then, one is faced with a smorgasbord of channels, many of which are not of interest, and many are virtual duplicates e.g. here in the UK, all the regional versions of the BBC, ITV and Channel 4 transmissions are present on the same satellite. Some rationalisation is virtually essential, and rather time consuming. For example for UK channels I locate all the programmes for my region and number them according to the FreeSat numbering, then create a group "UKTV" for them in order to produce a rational TV listing, while keeping those other channels available in the backgound via an "Astra 28.2" Group. This is useful because occasionally I might want to watch, say, something exclusive to BBC1 Scotland, rather than my local channel. So you can see why, although I'm happy to delete and then refresh the tuner mappings, I don't want to interfere with the channel set up itself unless a channel is actually moved in the frequencies or taken off air altogether. The second point about satellite receivers is that, in my experience, they don't always tune to all the channels they are capable of receiving. I'm sure that is the thought behind the comment I quoted from the wiki. This can be for various reasons, but I have a very specific example with my equipment, if you will indulge me a few minutes further ... As I said in the first post, all my tuners are attached to a diseqc A/B switch to choose between satellites. Two of my tuners (DVBSky) are as good as gold with that, and if they were the only ones I had, I'd just re-scan as you describe every 6 months or so to catch any frequency changes, and that would be that. Unfortunately however my other two tuners (TBS) don't play fair with this arrangement, and it took me much head-scratching before I found out what was really going on. These tuners don't seem to cope well with diseqc switching during scanning, even though in normal use they can tune to the required channels without batting an eyelid. I've worked out that during scanning, if satellite A and satellite B have a closely similar or identical tuning frequency for a particular mux, these cards will always go for A even though they are supposed to be scanning B at the time. The result, during a B scan, is that the system thinks the channels found or updated on A are actually on B, and re-marks them as such. Resulting in neither Mux A nor Mux B for that frequency being correctly recorded in MP, a confusion of channels and the loss of those channels on A across all tuners, because they are now marked incorrectly as B so become untunable. Once I'd figured out what was going on, the fix was obvious. I merely have to get the required scan on one of the "well behaved" tuners and apply it to the others, since they all work OK in actual use, some just fall down in scanning, and I'm sure this isn't a problem with MP. But how to be sure I had identified all the correct channels to map? Within over 1500 channels, there is plenty to confuse - there are channels marked "Sky ..." or "BBC ..." on the non-UK satellites, for example. If only I could limit it to groups and map the right groups to the right cards ... And now you hopefully understand where I was coming from! [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Development
Improvement Suggestions
Sort or restrict channels by group in mapping dialog
Contact us
RSS
Top
Bottom