Reply to thread

Message

<blockquote data-quote="mm1352000" data-source="post: 1157112" data-attributes="member: 82144">Hello again karniemiFirst, I only see TV Server attempting to start recording 2 movies at 21:00 instead of 3: &quot;Elokuva: Star Wars: Pimeä uhka&quot; and &quot;Inception (12)&quot;. The 3rd movie (&quot;Elokuva: The Expendables 2 (16)&quot;) is scheduled to start at 21:30....but the answer to your question is that TV Server does not provide the ability to record accurate to the exact second (eg. 21:00:00). Generally TV Server is only accurate to the correct minute.Normally I would not explain the technical details, but from our last discussion I know you can understand them and might be interested, so...The TV Server scheduler thread cycles every 15 seconds. In each cycle, it first stops the recordings that are due to be stopped, then starts the recordings that are due to start. Based on this implementation, we can see that what happened for you is:<ol>
<li data-xf-list-type="ol">The scheduler thread ran at 20:59:54. It wasn't time to stop or start any recordings yet, so it slept for another 15 seconds as usual.</li>
<li data-xf-list-type="ol">The scheduler thread ran again at 21:00:09. Now it is time to start recordings.</li>
<li data-xf-list-type="ol">The first recording to be started was &quot;Elokuva: Star Wars: Pimeä uhka&quot;. This took 3 seconds.</li>
<li data-xf-list-type="ol">The scheduler thread now tried to start the second recording (&quot;Inception (12)&quot;). However, you only had one tuner available, and it was tuned to a different frequency in order to record &quot;Elokuva: Star Wars: Pimeä uhka&quot;. Therefore the second recording could not be started.</li>
<li data-xf-list-type="ol">The scheduler thread ran again at 21:00:27 (15 seconds after the end of the last cycle). Again, TV Server knows that it is time to record &quot;Inception (12)&quot;, but nothing can be done because there are not enough free tuners.</li>
<li data-xf-list-type="ol">The check (like step 5) is repeated every 15 seconds until 21:30:13. Now it is also time to start recording &quot;Elokuva: The Expendables 2 (16)&quot;. This recording is also on a channel from a different frequency (compared to &quot;Elokuva: Star Wars: Pimeä uhka&quot;), so it also can't be recorded.</li>
<li data-xf-list-type="ol">The check for both &quot;Inception (12)&quot; and &quot;Elokuva: The Expendables 2 (16)&quot; (like step 6) is repeated every 15 seconds until the end of the log.</li>
</ol>As above: this is normal and expected behaviour for TV Server and every other PC recording software that I'm aware of.Based on the technical details that I shared, the worst possible delay for starting the first recording would be 14.999 seconds; delay for other recordings depends on how long it takes to start the earlier recordings (eg. 3 seconds in the case of &quot;Elokuva: Star Wars: Pimeä uhka&quot;).Yes, I can see that. MediaPortal 1 would have warned you.Regards,mm</blockquote>

[QUOTE="mm1352000, post: 1157112, member: 82144"] Hello again karniemi First, I only see TV Server attempting to start recording 2 movies at 21:00 instead of 3: "Elokuva: Star Wars: Pimeä uhka" and "Inception (12)". The 3rd movie ("Elokuva: The Expendables 2 (16)") is scheduled to start at 21:30. ...but the answer to your question is that TV Server does not provide the ability to record accurate to the exact second (eg. 21:00:00). Generally TV Server is only accurate to the correct minute. Normally I would not explain the technical details, but from our last discussion I know you can understand them and might be interested, so... The TV Server scheduler thread cycles every 15 seconds. In each cycle, it first stops the recordings that are due to be stopped, then starts the recordings that are due to start. Based on this implementation, we can see that what happened for you is: [LIST=1] [*]The scheduler thread ran at 20:59:54. It wasn't time to stop or start any recordings yet, so it slept for another 15 seconds as usual. [*]The scheduler thread ran again at 21:00:09. Now it is time to start recordings. [*]The first recording to be started was "Elokuva: Star Wars: Pimeä uhka". This took 3 seconds. [*]The scheduler thread now tried to start the second recording ("Inception (12)"). However, you only had one tuner available, and it was tuned to a different frequency in order to record "Elokuva: Star Wars: Pimeä uhka". Therefore the second recording could not be started. [*]The scheduler thread ran again at 21:00:27 (15 seconds after the end of the last cycle). Again, TV Server knows that it is time to record "Inception (12)", but nothing can be done because there are not enough free tuners. [*]The check (like step 5) is repeated every 15 seconds until 21:30:13. Now it is also time to start recording "Elokuva: The Expendables 2 (16)". This recording is also on a channel from a different frequency (compared to "Elokuva: Star Wars: Pimeä uhka"), so it also can't be recorded. [*]The check for both "Inception (12)" and "Elokuva: The Expendables 2 (16)" (like step 6) is repeated every 15 seconds until the end of the log. [/LIST] As above: this is normal and expected behaviour for TV Server and every other PC recording software that I'm aware of. Based on the technical details that I shared, the worst possible delay for starting the first recording would be 14.999 seconds; delay for other recordings depends on how long it takes to start the earlier recordings (eg. 3 seconds in the case of "Elokuva: Star Wars: Pimeä uhka"). Yes, I can see that. MediaPortal 1 would have warned you. Regards, mm [/QUOTE]

Verification