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
General Support
MP htpc worked great - until rescan
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="mm1352000" data-source="post: 756075" data-attributes="member: 82144"><p>Hi guys</p><p></p><p>So just to set the record straight: like I said yesterday, up until 1.2.0a/b there was a bug that resulted in QAM (and ATSC???) channels being detected as FTA when they were encrypted, and encrypted when they were FTA. It made no difference because as Andrew H said, TV Server detects whether a channel is actually encrypted when it tunes the channel - if it is encrypted and you have no means to decrypt it then TV Server gives up and tells you that the channel is encrypted.</p><p></p><p>Okay, so that was pre-1.2.0b. With 1.2.0b we've kinda created the perfect storm for ATSC/QAM users - completely unintentionally of course. We fixed the encrypted/FTA detection thing, so any channels that are scanned in with 1.2.0b will be set to the correct "state". *However* people that update from <1.2.0b are a little "screwed" - changes somewhere in the tuner allocation logic mean that it is now more important to have the FTA flag set correctly. People with databases full of encrypted channels that are actually FTA will upgrade to 1.2.0b and be unable to view any of their channels until they set them all to FTA (or the correct state). Well that's annoying, I hear you say... and I agree. Completely unforseen. What makes it worse is that we can't suggest deleting the channels and doing a full rescan - 1.2.0b has experimental channel detection speedups included, and unfortunately those speedups don't seem to work very well for *some* ATSC/QAM and IPTV users. The issue is that some channels are no longer identified as TV or radio, which results in them not being added to the channel list -> users get correct "states" for the channels that are found, but some channels are no longer found at all. Some people are severely affected - their entire set of channels can't be found (for example: Dish network users get all their radio channels, but all the TV channels are not found! <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite9" alt=":eek:" title="Eek! :eek:" loading="lazy" data-shortname=":eek:" />).</p><p></p><p>So, we royally screwed up. I'm not sure if there is any sense in apologising here, but I am sorry for the way it has turned out. A real mess...</p><p></p><p>mm</p><p>:sorry:</p></blockquote><p></p>
[QUOTE="mm1352000, post: 756075, member: 82144"] Hi guys So just to set the record straight: like I said yesterday, up until 1.2.0a/b there was a bug that resulted in QAM (and ATSC???) channels being detected as FTA when they were encrypted, and encrypted when they were FTA. It made no difference because as Andrew H said, TV Server detects whether a channel is actually encrypted when it tunes the channel - if it is encrypted and you have no means to decrypt it then TV Server gives up and tells you that the channel is encrypted. Okay, so that was pre-1.2.0b. With 1.2.0b we've kinda created the perfect storm for ATSC/QAM users - completely unintentionally of course. We fixed the encrypted/FTA detection thing, so any channels that are scanned in with 1.2.0b will be set to the correct "state". *However* people that update from <1.2.0b are a little "screwed" - changes somewhere in the tuner allocation logic mean that it is now more important to have the FTA flag set correctly. People with databases full of encrypted channels that are actually FTA will upgrade to 1.2.0b and be unable to view any of their channels until they set them all to FTA (or the correct state). Well that's annoying, I hear you say... and I agree. Completely unforseen. What makes it worse is that we can't suggest deleting the channels and doing a full rescan - 1.2.0b has experimental channel detection speedups included, and unfortunately those speedups don't seem to work very well for *some* ATSC/QAM and IPTV users. The issue is that some channels are no longer identified as TV or radio, which results in them not being added to the channel list -> users get correct "states" for the channels that are found, but some channels are no longer found at all. Some people are severely affected - their entire set of channels can't be found (for example: Dish network users get all their radio channels, but all the TV channels are not found! :o). So, we royally screwed up. I'm not sure if there is any sense in apologising here, but I am sorry for the way it has turned out. A real mess... mm :sorry: [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Support
General Support
MP htpc worked great - until rescan
Contact us
RSS
Top
Bottom
