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
General Development (no feature request here!)
TBS: CI/CAM support and other improvements
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: 1019353" data-attributes="member: 82144"><p>@<a href="https://forum.team-mediaportal.com/members/freakyj.106003/" target="_blank">FreakyJ</a></p><p>Here is a hint that may or may not be helpful (I don't know the solution for sure)... <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile :)" loading="lazy" data-shortname=":)" /></p><p>You may need to use the DvbTextConverter class in the TVLibrary to read this content. I only anticipated ANSI when I originally wrote the code, because the encoding of text received from the TBS interface was not clear. Now I see it is probably passed straight through from the CAM. This issue could easily apply for some of the other custom device plugins where it is not 100% clear whether the tuner driver has parsed and changed the encoding of the CAM response.</p></blockquote><p></p>
[QUOTE="mm1352000, post: 1019353, member: 82144"] @[URL='https://forum.team-mediaportal.com/members/freakyj.106003/']FreakyJ[/URL] Here is a hint that may or may not be helpful (I don't know the solution for sure)... :) You may need to use the DvbTextConverter class in the TVLibrary to read this content. I only anticipated ANSI when I originally wrote the code, because the encoding of text received from the TBS interface was not clear. Now I see it is probably passed straight through from the CAM. This issue could easily apply for some of the other custom device plugins where it is not 100% clear whether the tuner driver has parsed and changed the encoding of the CAM response. [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Development
General Development (no feature request here!)
TBS: CI/CAM support and other improvements
Contact us
RSS
Top
Bottom