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
About to record, but already have it! Wakes server too. Why?
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: 1228097" data-attributes="member: 82144"><p>Hello</p><p></p><p></p><p>You're right that the server checks for the existence of a previous recording just before starting a new recording. For a variety of reasons - both technical and practical - it would be quite difficult and perhaps even undesirable to change this.</p><p></p><p>A couple of practical examples:</p><ul> <li data-xf-list-type="ul">For some providers and/or EPG sources, the program/episode details can change right up to the time the program starts. If TV Server determined whether it was necessary to record or not at the time the schedule was created (or for series: at the time the EPG is first received), there'd be a reasonable risk of skipping recordings that should be skipped.<br /> </li> <li data-xf-list-type="ul">People sometimes decide to delete the previous recording "at the last minute" if they discover some kind of problem with it (eg. poor reception). Deleting may enable TV Server to record the same episode on a "plus one" channel just one hour later.</li> </ul><p>The technical reasons relate to the way the scheduler works. Without getting into the nitty gritty detail (too complex and time-consuming), it would be "significant and challenging" to change how the scheduler operates.</p><p></p><p>My advice to you would be to consider this choice:</p><p></p><p>Choosing a more "precise" schedule type (eg. record every week at this time) would presumably cut down on unnecessary sleep/wake cycles.</p><p></p><p></p><p>My personal opinion is that 6 spin-ups per day isn't particularly excessive. However, if it concerns you, perhaps you could consider configuring them to never spin down (or if your NAS has the flexibility: not to spin down during the busiest recording hours)? Sure, there's a bit of an energy cost [to not spinning down] (...though "spin up" actually uses significantly more energy than "keep spinning"). On the other hand, "keep spinning" is arguably similar to spun down in terms of drive longevity considerations.</p><p></p><p>Ultimately it's always going to be a trade off. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile :)" loading="lazy" data-shortname=":)" /></p></blockquote><p></p>
[QUOTE="mm1352000, post: 1228097, member: 82144"] Hello You're right that the server checks for the existence of a previous recording just before starting a new recording. For a variety of reasons - both technical and practical - it would be quite difficult and perhaps even undesirable to change this. A couple of practical examples: [LIST] [*]For some providers and/or EPG sources, the program/episode details can change right up to the time the program starts. If TV Server determined whether it was necessary to record or not at the time the schedule was created (or for series: at the time the EPG is first received), there'd be a reasonable risk of skipping recordings that should be skipped. [*]People sometimes decide to delete the previous recording "at the last minute" if they discover some kind of problem with it (eg. poor reception). Deleting may enable TV Server to record the same episode on a "plus one" channel just one hour later. [/LIST] The technical reasons relate to the way the scheduler works. Without getting into the nitty gritty detail (too complex and time-consuming), it would be "significant and challenging" to change how the scheduler operates. My advice to you would be to consider this choice: Choosing a more "precise" schedule type (eg. record every week at this time) would presumably cut down on unnecessary sleep/wake cycles. My personal opinion is that 6 spin-ups per day isn't particularly excessive. However, if it concerns you, perhaps you could consider configuring them to never spin down (or if your NAS has the flexibility: not to spin down during the busiest recording hours)? Sure, there's a bit of an energy cost [to not spinning down] (...though "spin up" actually uses significantly more energy than "keep spinning"). On the other hand, "keep spinning" is arguably similar to spun down in terms of drive longevity considerations. Ultimately it's always going to be a trade off. :) [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Support
General Support
About to record, but already have it! Wakes server too. Why?
Contact us
RSS
Top
Bottom