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
Electronic Program Guide
Soft padding for EPG recordings
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="CyberSimian" data-source="post: 1255432" data-attributes="member: 141969"><p>I have just tried this on my test system. There does seem to be at least one problem, and possibly more than one. My result differs slightly from [USER=88623]@divxmaster[/USER]. Some points:</p><p></p><p>(1) I disabled all but one tuner and rebooted.</p><p></p><p>(2) I scheduled a series to record 13.45-14.15.</p><p></p><p>(3) I attempted to schedule a single programme 14.15-16.00. The scheduled start and end times mean that there is no overlap, but once pre-padding (1 min) and post-padding (5 mins) is included, the recordings do overlap. This was diagnosed and the following pop-up appeared:</p><p></p><p>[ATTACH]200585[/ATTACH] </p><p></p><p>(4) Selecting "Skip new recording" worked correctly -- the new recording was not scheduled.</p><p></p><p>(5) Selecting "Keep conflict" also worked correctly -- the new recording was scheduled to record.</p><p></p><p>(6) Selecting "Skip conflicting recording(s)" partly worked. It displayed another popup with <strong>two</strong> choices: "Cancel this recording" and "Delete entire schedule". The latter worked correctly, but the former did not -- it seemed to act the same as "Skip new recording". Note that my test case schedules the single programme to follow the series, whereas [USER=88623]@divxmaster[/USER]'s single programme preceded the series (I don't know whether that is significant).</p><p></p><p>(7) With the two recordings scheduled, I then tried to schedule another single programme starting at 14.15. The conflict was diagnosed, but MP displayed only one conflicting recording, whereas I would have expected two conflicting recordings. Possibly "TV Server" remembers for each recording whether "Keep conflict" was specified for that recording, and does not consider it in subsequent conflict detection.</p><p></p><p>-- from CyberSimian in the UK</p></blockquote><p></p>
[QUOTE="CyberSimian, post: 1255432, member: 141969"] I have just tried this on my test system. There does seem to be at least one problem, and possibly more than one. My result differs slightly from [USER=88623]@divxmaster[/USER]. Some points: (1) I disabled all but one tuner and rebooted. (2) I scheduled a series to record 13.45-14.15. (3) I attempted to schedule a single programme 14.15-16.00. The scheduled start and end times mean that there is no overlap, but once pre-padding (1 min) and post-padding (5 mins) is included, the recordings do overlap. This was diagnosed and the following pop-up appeared: [ATTACH]200585[/ATTACH] (4) Selecting "Skip new recording" worked correctly -- the new recording was not scheduled. (5) Selecting "Keep conflict" also worked correctly -- the new recording was scheduled to record. (6) Selecting "Skip conflicting recording(s)" partly worked. It displayed another popup with [b]two[/b] choices: "Cancel this recording" and "Delete entire schedule". The latter worked correctly, but the former did not -- it seemed to act the same as "Skip new recording". Note that my test case schedules the single programme to follow the series, whereas [USER=88623]@divxmaster[/USER]'s single programme preceded the series (I don't know whether that is significant). (7) With the two recordings scheduled, I then tried to schedule another single programme starting at 14.15. The conflict was diagnosed, but MP displayed only one conflicting recording, whereas I would have expected two conflicting recordings. Possibly "TV Server" remembers for each recording whether "Keep conflict" was specified for that recording, and does not consider it in subsequent conflict detection. -- from CyberSimian in the UK [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Support
Electronic Program Guide
Soft padding for EPG recordings
Contact us
RSS
Top
Bottom