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 Plugins
For The Record 1.6
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="dvdfreak" data-source="post: 506648" data-attributes="member: 21313"><p>In what way? Importing XMLTV guide data is quite a bit slower in MySQL than in SQL Express, we've noticed this as well. But since the exact same code is running for both I'd rather look at MySQL instead of <strong>For The Record</strong> for the reason why...</p><p></p><p></p><p>Did you check your card's cam-limit is set higher than 1 in TV server config? Standard TV server takes a 0 cam-limit as "anything goes", but <strong>For The Record</strong> always looks at the cam-limit and it needs to be set high enough.</p></blockquote><p></p>
[QUOTE="dvdfreak, post: 506648, member: 21313"] In what way? Importing XMLTV guide data is quite a bit slower in MySQL than in SQL Express, we've noticed this as well. But since the exact same code is running for both I'd rather look at MySQL instead of [b]For The Record[/b] for the reason why... Did you check your card's cam-limit is set higher than 1 in TV server config? Standard TV server takes a 0 cam-limit as "anything goes", but [b]For The Record[/b] always looks at the cam-limit and it needs to be set high enough. [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
MediaPortal 1 Plugins
For The Record 1.6
Contact us
RSS
Top
Bottom
