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.3.3 Released
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: 324796" data-attributes="member: 21313"><p>Everything in life is a matter of give and take. We need to outweigh the effort and added complexity against the beneft.</p><p></p><p>Currently <strong>For The Record</strong> is perfect for multi-seat use, since the whole architecture is multi-seat from the ground up. You can even install the Web Access site or the IM-Bot on a different machine than your Core Services, and of course as many clients or even recorder/tuners as you wish on any machine on your LAN. Clients can even connect from anywhere in the world over HTTPS (except for watching/streaming of course, but you can edit schedules to your heart's content <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>So we prefer to keep the flexibility like that.</p><p></p><p>So far <strong>For The Record</strong> users are <u>very</u> enthousiastic about its stability, and this is certainly in part due to the fact that the architecture is solid and patch-free. So adding specific things for single seat situations may add complexity we prefer to avoid. Just saying that all this needs to be looked at carefully. Stability comes first, features come next. And features on their own need to be outweighed as well of course, because we love killer features as much as the next guy <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite8" alt=":D" title="Big Grin :D" loading="lazy" data-shortname=":D" /></p></blockquote><p></p>
[QUOTE="dvdfreak, post: 324796, member: 21313"] Everything in life is a matter of give and take. We need to outweigh the effort and added complexity against the beneft. Currently [b]For The Record[/b] is perfect for multi-seat use, since the whole architecture is multi-seat from the ground up. You can even install the Web Access site or the IM-Bot on a different machine than your Core Services, and of course as many clients or even recorder/tuners as you wish on any machine on your LAN. Clients can even connect from anywhere in the world over HTTPS (except for watching/streaming of course, but you can edit schedules to your heart's content :)). So we prefer to keep the flexibility like that. So far [b]For The Record[/b] users are [U]very[/U] enthousiastic about its stability, and this is certainly in part due to the fact that the architecture is solid and patch-free. So adding specific things for single seat situations may add complexity we prefer to avoid. Just saying that all this needs to be looked at carefully. Stability comes first, features come next. And features on their own need to be outweighed as well of course, because we love killer features as much as the next guy :D [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
MediaPortal 1 Plugins
For The Record 1.3.3 Released
Contact us
RSS
Top
Bottom