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
MediaPortal 1 Talk
Teletext subtitles
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="J-B-N" data-source="post: 151316" data-attributes="member: 17587"><p>It is very good to hear you are planning to improve the entire teletext module!</p><p></p><p></p><p></p><p>It would naturally be very good to have the teletext caching start directly (soon) after a channel change. I don't know the CPU requirements and the potential impact of having the chaching start during the channel change but just after playback has started a chaching should be able to run with minimal impact on system performance. </p><p></p><p>Why is the chache built as a memory bound parameter? Ie why not store the cache in the database? From my experience a teletext page doesn't change that often, and if you zap between two channels you don't need to rebuild the entire chache. Storing the teletext chache in a database would cost some harddisk but all things considered not that much and there would be a fraction higher latancy to retrieve the pages. </p><p></p><p>Anyhow just something I have been thinking about. </p><p></p><p></p><p></p><p>Oh, I see, excellent!</p></blockquote><p></p>
[QUOTE="J-B-N, post: 151316, member: 17587"] It is very good to hear you are planning to improve the entire teletext module! It would naturally be very good to have the teletext caching start directly (soon) after a channel change. I don't know the CPU requirements and the potential impact of having the chaching start during the channel change but just after playback has started a chaching should be able to run with minimal impact on system performance. Why is the chache built as a memory bound parameter? Ie why not store the cache in the database? From my experience a teletext page doesn't change that often, and if you zap between two channels you don't need to rebuild the entire chache. Storing the teletext chache in a database would cost some harddisk but all things considered not that much and there would be a fraction higher latancy to retrieve the pages. Anyhow just something I have been thinking about. Oh, I see, excellent! [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
MediaPortal 1 Talk
Teletext subtitles
Contact us
RSS
Top
Bottom