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
Products
TV-Server
TV Server Plugin: TvWishList
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="huha" data-source="post: 869075" data-attributes="member: 63847"><p>foxbenw,</p><p>from your last trace I believe i got it. Attached is a new test version.</p><p>The problem occured if the EPG start/end time did change <strong>and</strong> the episode information did change.</p><p></p><p>I need the users´s feedback on what to do when the EPG start/end time changes:</p><p></p><p>A) Create a new schedule and email message with the new time and create a conflict message with the old time.</p><p>This will inform the user whenever a EPG time did change, but may create too many schedule messages. This is implemented in the test version.</p><p></p><p>B) Create only a new email message without a new schedule message and keep the old schedule message. In addition a conflict message is created.</p><p>This will inform the user only for email messages when the EPG time is changing. If the user specifies an action "schedule" no new schedule message will be created, but email messages will be resent with the updated start/stop time. </p><p></p><p>C) Create only a conflict message and no new email or schedule message. Here the user is not flooded by messages, but may miss the changed start time of a favourite show.</p><p></p><p></p><p>Now pick your poison <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile :)" loading="lazy" data-shortname=":)" /></p><p>I am slightly in favour of B) but let me hear your opinions.</p><p></p><p></p><p>d3ltoroxp,</p><p></p><p>i do not see any issue. It works as designed. "Die Geissens" on 5/28 are not being scheduled because you have already one </p><p>recording with the same title.</p><p>In your settings you did choose episode criteria "none" and skip repeated episodes "true", so one identical recorded title will prevent the scheduling of another </p><p>episode. If you change to the default setting for episode criteria = "descr. +name+number" it will check for the correct episode, but specifying none will skip </p><p>everything with the same title.</p></blockquote><p></p>
[QUOTE="huha, post: 869075, member: 63847"] foxbenw, from your last trace I believe i got it. Attached is a new test version. The problem occured if the EPG start/end time did change [B]and[/B] the episode information did change. I need the users´s feedback on what to do when the EPG start/end time changes: A) Create a new schedule and email message with the new time and create a conflict message with the old time. This will inform the user whenever a EPG time did change, but may create too many schedule messages. This is implemented in the test version. B) Create only a new email message without a new schedule message and keep the old schedule message. In addition a conflict message is created. This will inform the user only for email messages when the EPG time is changing. If the user specifies an action "schedule" no new schedule message will be created, but email messages will be resent with the updated start/stop time. C) Create only a conflict message and no new email or schedule message. Here the user is not flooded by messages, but may miss the changed start time of a favourite show. Now pick your poison :) I am slightly in favour of B) but let me hear your opinions. d3ltoroxp, i do not see any issue. It works as designed. "Die Geissens" on 5/28 are not being scheduled because you have already one recording with the same title. In your settings you did choose episode criteria "none" and skip repeated episodes "true", so one identical recorded title will prevent the scheduling of another episode. If you change to the default setting for episode criteria = "descr. +name+number" it will check for the correct episode, but specifying none will skip everything with the same title. [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
Products
TV-Server
TV Server Plugin: TvWishList
Contact us
RSS
Top
Bottom