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
Improvement Suggestions
TV Server
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="Inker" data-source="post: 6460" data-attributes="member: 10541"><p>ob2,</p><p></p><p>first, i didnt really understand that last post of urs about SBE.....anyways, inspired by ur response I gave this some more thought.</p><p></p><p>so ok, wmv reencoding is out, i agree its too much cpu usage if the server is also being used as a htpc of its own, otherwise it wouldnt be a problem</p><p></p><p>so, with the timeshifting mpegs (plural) , granted i dont know how it really works, but, given that the htpc understands these files, and knows how to put them together etc., shouldnt it be possible that the client 8also running mp understands them? maybe the server tells the client how to handle them.</p><p></p><p>so on the server (with the tv-card): the user simply runs mp (maybe in the option configure port etc.)</p><p></p><p>on the client, the user also runs mp, and this time goes into myTV, mp has a new option called SharedTV (or something), upon that, the client contacts the server and tells it to start timeshifting, the server does so and tells the client where the timeshifting mpegs are (if necessary mapping a windows network share should work too), so, it should be as if the timeshifting mpegs were created by the client (if on a windows network share it should appear as if they were stored locally even), but in reality they are done by the server, now playback is of course done by the client(s), maybe the same code since the server understands these files, the client should do, if it needs data from the tv-card to understand them, the server could tell this data to the client.</p><p></p><p>once the client has found a server, it will request the channel list and epg, when the user changes the channel, the client tells the server aobut it and the server does so</p><p></p><p>i realize there will be a bit of delay, however this should be no more than a few seconds i recon</p><p></p><p>make sense? just a quick thought, maybe it can help u a bit.</p><p></p><p>about network usage........well 100 mbit should be enough i guess and thise seems to be the standard today, even wlan (54 mbit version) should easily do i suppose.</p><p></p><p>Ok, thnx for ur time</p></blockquote><p></p>
[QUOTE="Inker, post: 6460, member: 10541"] ob2, first, i didnt really understand that last post of urs about SBE.....anyways, inspired by ur response I gave this some more thought. so ok, wmv reencoding is out, i agree its too much cpu usage if the server is also being used as a htpc of its own, otherwise it wouldnt be a problem so, with the timeshifting mpegs (plural) , granted i dont know how it really works, but, given that the htpc understands these files, and knows how to put them together etc., shouldnt it be possible that the client 8also running mp understands them? maybe the server tells the client how to handle them. so on the server (with the tv-card): the user simply runs mp (maybe in the option configure port etc.) on the client, the user also runs mp, and this time goes into myTV, mp has a new option called SharedTV (or something), upon that, the client contacts the server and tells it to start timeshifting, the server does so and tells the client where the timeshifting mpegs are (if necessary mapping a windows network share should work too), so, it should be as if the timeshifting mpegs were created by the client (if on a windows network share it should appear as if they were stored locally even), but in reality they are done by the server, now playback is of course done by the client(s), maybe the same code since the server understands these files, the client should do, if it needs data from the tv-card to understand them, the server could tell this data to the client. once the client has found a server, it will request the channel list and epg, when the user changes the channel, the client tells the server aobut it and the server does so i realize there will be a bit of delay, however this should be no more than a few seconds i recon make sense? just a quick thought, maybe it can help u a bit. about network usage........well 100 mbit should be enough i guess and thise seems to be the standard today, even wlan (54 mbit version) should easily do i suppose. Ok, thnx for ur time [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Development
Improvement Suggestions
TV Server
Contact us
RSS
Top
Bottom