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 2
General
MediaPortal TV Server and Kodi media source issues
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="Lehmden" data-source="post: 1263246" data-attributes="member: 109222"><p>Hi.</p><p></p><p>Yes, tiny, at least compared to the media database. The TVE database (including all EPG data) is only about 10-20 Mbyte where the (my) media database is around 4-6 GByte of size... In MP2 you can easily see the size of the db as MP2 uses SQLite and here the database is a single file (ok, two files, a tiny one for the TVE and a huge one for the media library)... </p><p></p><p>SQLite is capable of handling Terrabyte sized databases with ease. But MP2 can't handle this big databases due to performance issues. My media database is on the edge of what MP2 can handle on a low to mid- range PC. If you have a lot bigger database than mine you need a high- end CPU for the server.</p><p></p><p>MP1 can not use the much faster (about 10 times as fast as MySQL) SQLite database engine as the MP1 TV client plugin has not very good code and does some direct database accesses instead of using the TV engine for all access (as it has to be). Those nasty direct access from outside is the only real reason for the need of a full blown database server in MP1 and it also is the only reason why MP1 can not access MP2 TV engine. </p><p></p><p></p><p>For this the [] are there. substitution codes in [] are optional and the filename still is valid even if some things are missing. The season and episodes numbers are only very seldom included in EPG data. This is one of the reasons why I wrote EPG-Buddy as EPG-Buddy adds season and episodes numbers for most (some episodes can not be recognized and for this they get no numbers) of the episodes in the EPG data. And this way nearly all recordings will have proper season and episodes numbers and could easily be scrapped...</p></blockquote><p></p>
[QUOTE="Lehmden, post: 1263246, member: 109222"] Hi. Yes, tiny, at least compared to the media database. The TVE database (including all EPG data) is only about 10-20 Mbyte where the (my) media database is around 4-6 GByte of size... In MP2 you can easily see the size of the db as MP2 uses SQLite and here the database is a single file (ok, two files, a tiny one for the TVE and a huge one for the media library)... SQLite is capable of handling Terrabyte sized databases with ease. But MP2 can't handle this big databases due to performance issues. My media database is on the edge of what MP2 can handle on a low to mid- range PC. If you have a lot bigger database than mine you need a high- end CPU for the server. MP1 can not use the much faster (about 10 times as fast as MySQL) SQLite database engine as the MP1 TV client plugin has not very good code and does some direct database accesses instead of using the TV engine for all access (as it has to be). Those nasty direct access from outside is the only real reason for the need of a full blown database server in MP1 and it also is the only reason why MP1 can not access MP2 TV engine. For this the [] are there. substitution codes in [] are optional and the filename still is valid even if some things are missing. The season and episodes numbers are only very seldom included in EPG data. This is one of the reasons why I wrote EPG-Buddy as EPG-Buddy adds season and episodes numbers for most (some episodes can not be recognized and for this they get no numbers) of the episodes in the EPG data. And this way nearly all recordings will have proper season and episodes numbers and could easily be scrapped... [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 2
General
MediaPortal TV Server and Kodi media source issues
Contact us
RSS
Top
Bottom