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
Installation, configuration support
1.3.0 Final and Digital Channel Scans
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="hello_joe" data-source="post: 981784" data-attributes="member: 139074"><p>Yeah, wikipedia numbers use MHz units. The tuning files are using kHz. There are 1000 kHz in 1 MHz, so the conversion is simple.</p><p>The 135 is just a dummy value, because there is no physical channel 1 in the "standard" frequency plan. Physical channel 2 is 73.25 MHz (73250 kHz).</p><p> </p><p>These frequency plans are standardised by regulation and standardization bodies like the FCC. I've attached a document that may help you. This document was assembled independently of MPs XML files using information from the regulations that I found on the internet. Feel free to cross check MPs files if you want.</p><p> </p><p>Let me be clear: the only thing that changing the XML files will do is change the frequencies that are scanned. This won't give you correct channel names or virtual channel numbers.</p><p> </p><p> </p><p></p><p>I'm sorry, I don't really understand this question. I think you're asking how MP is scanning?</p><p>When MP scans, it scans physical channels 1 through 135, or something like that.</p><p>The frequencies for each of those physical channels depend on the QAM frequency plan that you select.</p><p>For each physical channel, the tuner is instructed to tune to the corresponding frequency.</p><p>MP checks if the tuner has locked onto a signal. If it has, MP then looks for channels and records the details of the channels that it finds.</p><p>Assuming that the MP tuning files are correct, the only thing that can really go wrong there in terms of finding or not finding channels is the selection of the correct QAM frequency plan. This is why I said I highly recommend you ask your cable provider what frequency plan they use.</p><p> </p><p> </p><p></p><p>I can't comment about Hauppauge's software - never used it.</p><p>Although it would be nice to be able to match up the details in MP with the Hauppauge software and your WOW info, my question would be... does it actually matter if you're getting all the channels that you're expecting to find?</p><p>At this point it is not clear to me whether you're still saying that you're missing channels, whether you're just investigating for your own satisfaction/interest... or something else. Keep in mind what I said previously: if you think you're missing channels, they're most likely just named as "Unknown...". No amount of fiddling with the tuning detail files and rescanning will fix that. You'll have to manually fix the names. If you've gone through all the "Unknown..." channels and still can't find one or more of the channels that you're expecting to get then I'd understand why you're looking at the tuning detail files, but you haven't said that... so I'm confused.</p><p> </p><p>What is your zip code?</p><p>I'd like to look up your cable provider here:</p><p><a href="http://www.silicondust.com/support/channels/" target="_blank">http://www.silicondust.com/support/channels/</a></p><p>I will hopefully be able to better help once I can do that. Right now it is not clear whether those numbers you're quoting are ATSC virtual channel numbers or truly physical channel and service IDs. That makes a big difference.</p><p> </p><p> </p><p> </p><p></p><p> </p><p>What this means is that physical channel 60 in the frequency plan (ie. the QAM file) that you scanned with is 433.262 MHz. Those are the first two numbers.</p><p>(Side note: that frequency is from the IRC frequency plan. Unless your cable provider told you that they use IRC, I would suggest you are almost certainly scanning with the wrong QAM setting if you're using IRC.)</p><p> </p><p>The next two would usually hold the ATSC (over-the-air digital TV) virtual channel number. That's the channel number that a TV guide would usually show as as x-y or x.y where x is the major channel number and y is the minor channel number. MP doesn't use them or display them anywhere other than there. The fact that they're both zero indicates MP didn't find the virtual channel number when you scanned.</p><p> </p><p> </p><p>Modulation 256 QAM is common for US cable. It is just a technical tuning parameter. It is almost certainly correct.</p><p> </p><p>Network ID is not actually relevant for ATSC or clear QAM channels. MP shouldn't have such a field. It is a hangover from DVB (the standard used in Europe).</p><p> </p><p>Transport ID and service ID are the technical identifier for the channel. The combination of those two numbers are meant to uniquely identify the channel on the cable system. They're not usually displayed on a TV or set-top-box.</p><p> </p><p>So if you compare the WOW and MP info at face value, the physical channel number matches. I have no idea what the "preset" is. It is a little strange that the service IDs don't match, but it isn't out of the realms of possibility.</p><p> </p><p> </p><p></p><p>Yes, absolutely.</p><p> </p><p>I have to confess I don't really understand why you're so interested in the tuning files.</p><p>Changing them will not give you correct channel names or numbers for the reasons that I've previously explained.</p><p>Many many MANY people have used MP over the years, and if there were blatant problems with the tuning files then I'd hope they would have been discovered. There could be a few mistakes here and there, but on the whole I'd expect they're roughly correct. Therefore, I'd expect that <strong>if you're selecting the correct frequency plan for your cable provider then MP should find most if not all of the channels that are available.</strong></p></blockquote><p></p>
[QUOTE="hello_joe, post: 981784, member: 139074"] Yeah, wikipedia numbers use MHz units. The tuning files are using kHz. There are 1000 kHz in 1 MHz, so the conversion is simple. The 135 is just a dummy value, because there is no physical channel 1 in the "standard" frequency plan. Physical channel 2 is 73.25 MHz (73250 kHz). These frequency plans are standardised by regulation and standardization bodies like the FCC. I've attached a document that may help you. This document was assembled independently of MPs XML files using information from the regulations that I found on the internet. Feel free to cross check MPs files if you want. Let me be clear: the only thing that changing the XML files will do is change the frequencies that are scanned. This won't give you correct channel names or virtual channel numbers. I'm sorry, I don't really understand this question. I think you're asking how MP is scanning? When MP scans, it scans physical channels 1 through 135, or something like that. The frequencies for each of those physical channels depend on the QAM frequency plan that you select. For each physical channel, the tuner is instructed to tune to the corresponding frequency. MP checks if the tuner has locked onto a signal. If it has, MP then looks for channels and records the details of the channels that it finds. Assuming that the MP tuning files are correct, the only thing that can really go wrong there in terms of finding or not finding channels is the selection of the correct QAM frequency plan. This is why I said I highly recommend you ask your cable provider what frequency plan they use. I can't comment about Hauppauge's software - never used it. Although it would be nice to be able to match up the details in MP with the Hauppauge software and your WOW info, my question would be... does it actually matter if you're getting all the channels that you're expecting to find? At this point it is not clear to me whether you're still saying that you're missing channels, whether you're just investigating for your own satisfaction/interest... or something else. Keep in mind what I said previously: if you think you're missing channels, they're most likely just named as "Unknown...". No amount of fiddling with the tuning detail files and rescanning will fix that. You'll have to manually fix the names. If you've gone through all the "Unknown..." channels and still can't find one or more of the channels that you're expecting to get then I'd understand why you're looking at the tuning detail files, but you haven't said that... so I'm confused. What is your zip code? I'd like to look up your cable provider here: [url]http://www.silicondust.com/support/channels/[/url] I will hopefully be able to better help once I can do that. Right now it is not clear whether those numbers you're quoting are ATSC virtual channel numbers or truly physical channel and service IDs. That makes a big difference. What this means is that physical channel 60 in the frequency plan (ie. the QAM file) that you scanned with is 433.262 MHz. Those are the first two numbers. (Side note: that frequency is from the IRC frequency plan. Unless your cable provider told you that they use IRC, I would suggest you are almost certainly scanning with the wrong QAM setting if you're using IRC.) The next two would usually hold the ATSC (over-the-air digital TV) virtual channel number. That's the channel number that a TV guide would usually show as as x-y or x.y where x is the major channel number and y is the minor channel number. MP doesn't use them or display them anywhere other than there. The fact that they're both zero indicates MP didn't find the virtual channel number when you scanned. Modulation 256 QAM is common for US cable. It is just a technical tuning parameter. It is almost certainly correct. Network ID is not actually relevant for ATSC or clear QAM channels. MP shouldn't have such a field. It is a hangover from DVB (the standard used in Europe). Transport ID and service ID are the technical identifier for the channel. The combination of those two numbers are meant to uniquely identify the channel on the cable system. They're not usually displayed on a TV or set-top-box. So if you compare the WOW and MP info at face value, the physical channel number matches. I have no idea what the "preset" is. It is a little strange that the service IDs don't match, but it isn't out of the realms of possibility. Yes, absolutely. I have to confess I don't really understand why you're so interested in the tuning files. Changing them will not give you correct channel names or numbers for the reasons that I've previously explained. Many many MANY people have used MP over the years, and if there were blatant problems with the tuning files then I'd hope they would have been discovered. There could be a few mistakes here and there, but on the whole I'd expect they're roughly correct. Therefore, I'd expect that [B]if you're selecting the correct frequency plan for your cable provider then MP should find most if not all of the channels that are available.[/B] [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Support
Installation, configuration support
1.3.0 Final and Digital Channel Scans
Contact us
RSS
Top
Bottom