Reply to thread

Message: <blockquote data-quote="mm1352000" data-source="post: 988297" data-attributes="member: 82144">Hello again breese Once again a sincere thanks for the time you're putting in. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite24" alt="(y)" title="Thumbs Up    (y)" loading="lazy" data-shortname="(y)" /> As I said to you previously, I think there are quite severe limitations on what we can do to solve or even improve most of the points you've raised. I've made comments on each one below. I know this is a long post, but please read carefully. I feel like I'm starting to repeat the same things @<a href="https://forum.team-mediaportal.com/members/hello_joe.139074/" target="_blank">hello_joe</a> already explained to you... and that is a little frustrating. I'd remind you that many cable providers hate clear QAM, and they do their utmost to make it really difficult to use anything other than their set-top-box. They are overjoyed that clear QAM is going away:<a href="http://www.engadget.com/2012/10/14/fcc-to-allow-encryption-of-basic-cable-with-a-few-strings-that/" target="_blank">http://www.engadget.com/2012/10/14/fcc-to-allow-encryption-of-basic-cable-with-a-few-strings-that/</a> Here we go... ----------------------------------------------------------------------------------------- Yes, preview and rename is the standard response.Having access to a lineup listing with "QAM channel numbers" puts you in a privileged minority.Really, most other people have no choice but to use preview and rename.As far as I know, this applies in every other piece of HTPC software that supports clear QAM, except maybe WMC... because they pay for channel and EPG info. MythTV, N-PVR, WinTV... we're all in the same boat. SUMMARY: WE CAN CHANGE THE NAMING CONVENTION OF UNKNOWN CHANNELS  ----------------------------------------------------------------------------------------- This is a known issue that doesn't only apply to cable TV. For discussion:<a href="https://forum.team-mediaportal.com/threads/wrong-detection-of-fta-disables-watching-channel.109326/" target="_blank">https://forum.team-mediaportal.com/threads/wrong-detection-of-fta-disables-watching-channel.109326/</a>We will find a way to fix this eventually, but it is non-trivial. SUMMARY: LONG STANDING ISSUE, VERY DIFFICULT TO FIX ----------------------------------------------------------------------------------------- This is a really complex topic. I'll do my best to try and keep the explanation simple. First, I don't know what "LUN" stands for, but in the rest of the world we call that field an LCN (= logical channel number).We use it to change channels (zap) with our remotes.In North America my understanding is that most people would call it a "virtual channel" (VCN).The standard for transmitting LCN/LUN/VCN data depends on location. Briefly... In North America, ATSC and SCTE standards (ANSI SCTE 65 and ATSC A-65) define one-part (eg. xxx) and two-part (eg. xx.yy) VCNs. For OTA ATSC and SCTE cable, we support retrieving the two-part channel number from the L-VCT (virtual channel table - PSIP). When available, you'll see these numbers in the "major channel" and "minor channel" fields. In the world outside North America DVB is the most widely used broadcast standard. DVB does not specify a standard way of transmitting LCNs, so many broadcasters use proprietary methods. Having said that, there is a de-facto standard from Nordig (which we support). (Note: all the links that you gave reference DVB related issues, so they are irrelevant for your situation.) Lets compare and contrast OTA ATSC and cable... By FCC regulation, OTA broadcasters must transmit PSIP. PSIP includes the L-VCT. Hence you should expect to receive channel names and numbers in this scenario. In complete contrast, cable TV has no such regulation. In fact, SCTE 65 specifies that channel names and VCNs should be carried in an out of band signal. Receiving that signal requires a QPSK tuner. Clear QAM tuners physically cannot demodulate QPSK by nature of the fact that they are QAM tuners, so there is absolutely no way that you can receive this data with your current tuner. Impossible, period. Now here is where it gets complicated. There is a bit of an exception to the cable rule...As you know, you have names and VCNs (major/minor channel) for a handful of your channels like ABCHD. Why?Well, my understanding is that there is some kind of regulation that requires cable providers to transmit ATSC PSIP in very specific scenarios related to local channels and clear QAM. However if I recall correctly, the regulation only applies if the ATSC broadcaster supplies the required info to the cable provider. As such, it is sometimes possible to receive limited information about some clear QAM channels. MP does its best to receive and show this info. SUMMARY: EXCEPT IN EXCEPTIONAL CIRCUMSTANCES IT IS LITERALLY IMPOSSIBLE TO RECEIVE CHANNEL NAMES AND LCN/VCN/LUNs WITH A CLEAR QAM TUNER. YOU MUST MANUALLY SET THESE NUMBERS IF YOU DON'T HAVE A CABLECARD TUNER ----------------------------------------------------------------------------------------- Changing the TVService priority is not a relevant or useful way to deal with this problem. Increasing the SDT/VCT timeout only makes sense if the information that you're hoping to receive (ie. channel names and "LUNs") are actually available in the broadcast stream. In the case of your cable provider, they're clearly not available (independently confirmed with WinTV), ergo increasing the timeout is pointless. SUMMARY: INCREASING THE VCT TIMEOUT IS A VALID WAY TO TROUBLESHOOT ISSUES WITH MISSING CHANNEL NAMES, HOWEVER IT IS NOT A SILVER BULLET - IF THE INFORMATION IS NOT AVAILABLE, THEN IT IS POINTLESS  ----------------------------------------------------------------------------------------- This is something I'm not able to explain or investigate without specific examples and log files. More info required. SUMMARY: (MORE INFO REQUIRED)  -----------------------------------------------------------------------------------------  MP does not support using xx.yy channel numbers for changing channels. This is something that could be added... however...The cable TV standards that I've read don't mention anything about a "QAM channel number". The closest thing I've seen would be the ATSC two-part channel number... but at this point I'm not convinced they're the same thing. So I'm not sure if that is specific to WOW... in which case I question whether it would be a good thing for us to support. SUMMARY: IT WOULD BE POSSIBLE TO ADD SUPPORT FOR ZAPPING WITH XX.YY LCNS, HOWEVER THE EFFORT REQUIRED TO SUPPORT THIS IS NOT INSIGNIFICANT     mm</blockquote>

Verification