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
Multiple setups
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: 789142" data-attributes="member: 82144"><p>Hi and welcome Stephen <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile :)" loading="lazy" data-shortname=":)" /></p><p></p><p></p><p>We need more developers from your part of the world. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite2" alt=";)" title="Wink ;)" loading="lazy" data-shortname=";)" /></p><p></p><p></p><p>Okay let me try to clarify. With MP you can have multiple clients connecting to a *single* TV Server. The clients can use the tuners in the TV Server to view and record TV. Anything else is really independent of our software. By that I mean that if you host your music, DVD and recording collections on the TV Server machine as well then the clients access those directly (the TV Server has nothing to do with it) - you set up shares so that the clients can access these. TV Servers can't talk to eachother, so we recommend you put all your tuners in one TV Server.</p><p></p><p></p><p>MP uses SQL Lite databases on the client side for video, music and picture databases. Each client has its own databases. You can share them between clients but you run the risk of corrupting them.</p><p>With TV Server, the settings, recording DB, channel lists, tuning details... everying is stored in either a MySQL or SQL Server database. Usually TV Server requires an XML metadata file to allow you to import recordings. Considering that you know SQL, you can almost certainly write yourself a script to either generate the XML files (sample attached) or populate the DB directly. If you go the XML file route, the XML files must exist in the same directory as the recordings themselves, and they must be given the same name as the recordings they are associated with (ignoring the extension of course).</p><p></p><p>Hope that helps. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile :)" loading="lazy" data-shortname=":)" /></p><p>mm</p></blockquote><p></p>
[QUOTE="mm1352000, post: 789142, member: 82144"] Hi and welcome Stephen :) We need more developers from your part of the world. ;) Okay let me try to clarify. With MP you can have multiple clients connecting to a *single* TV Server. The clients can use the tuners in the TV Server to view and record TV. Anything else is really independent of our software. By that I mean that if you host your music, DVD and recording collections on the TV Server machine as well then the clients access those directly (the TV Server has nothing to do with it) - you set up shares so that the clients can access these. TV Servers can't talk to eachother, so we recommend you put all your tuners in one TV Server. MP uses SQL Lite databases on the client side for video, music and picture databases. Each client has its own databases. You can share them between clients but you run the risk of corrupting them. With TV Server, the settings, recording DB, channel lists, tuning details... everying is stored in either a MySQL or SQL Server database. Usually TV Server requires an XML metadata file to allow you to import recordings. Considering that you know SQL, you can almost certainly write yourself a script to either generate the XML files (sample attached) or populate the DB directly. If you go the XML file route, the XML files must exist in the same directory as the recordings themselves, and they must be given the same name as the recordings they are associated with (ignoring the extension of course). Hope that helps. :) mm [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Support
General Support
Multiple setups
Contact us
RSS
Top
Bottom
