ok then, we need scannin logs from WinTV and from MP - maybe then we can figure out how WinTV detects them...
You're basically right Vasilich@Pat Clark
as mm described above - if channel provider marks channels as encrypted - then those channels will get red bubbles, as the decision will be made while scanning.
But if provider encrypt channels without marking them properly while transmitting - then MP recognizes this only after tuning and trying to get streams from it. And this seems to be the case for breese. So - discrepancy comes from provider not following standards, not from MP.
@mm1352000 correct me if i'm wrong, please.
You're basically right Vasilich There are currently limitations on TV Server's ability to determine whether a channel is encrypted or not. This applies to all transmission standards based on MPEG 2. In other words, DVB-S, DVB-S2, DVB-T... etc. etc. It applies to both ATSC OTA and ATSC/SCTE cable in North America. I suspect @breese hasn't noticed it with ATSC previously because I don't think there are any encrypted OTA transmissions in the US.
Once again a sincere thanks for the time you're putting in.I have worked for hours on gathering info I think might help.
I have spent a great deal of time comparing WinTV channel findings and MP Findings. I have read more threads on issues from Unknown xxx.yy and answers are almost always “preview and rename”
...
Channel scans produce an Unknown xxxx.yyy that is not human readable for end users.
Encrypted Red Balloons not showing up...
...
Channel scans are not distinguishing encrypted channels (this one seems to come and go over time and MP updates).
...LUN being set to 10000 for all channels.
...
Channel scans set LUN to 10000 for all channels found
LCN Issues have been raised multiple times going back to 2008 and as recent as 2012
https://forum.team-mediaportal.com/threads/one-mux-only-gives-me-10000-for-lcn.39647/
http://mantis.team-mediaportal.com/view.php?id=1367
https://forum.team-mediaportal.com/threads/scanning-satellite-19-2-is-naming-the-channels-10000-only.117301/
In an effort to help find the issues, I have done everything from creating new Freq Scan Files to changing SDT/VCT settings from Default to 120 seconds, doing multiple rescan’s., and setting TVService to everything from Default to Realtime.
All the SDT/VCT has done is make the scans take a lot longer.
This is something I'm not able to explain or investigate without specific examples and log files. More info required.Multiple scans do find more channels (also as Unknown xxx.yy) but doing this also makes it take longer for a completely ready system.
MP does not support using xx.yy channel numbers for changing channels. This is something that could be added... however...In the US QAM world, channels are Channel.SubChannel (xx.yy) that are also usable for changing channels on a QAM ready TV.