Will do. Am I looking for the first time it happens?
TV Server Plugin: TvWishList (1 Viewer)
- Thread starter huha
- Start date
Is that the right attachment?
- June 1, 2008
- 3,272
- 212
- Home Country
-
Germany
Hey Huha, i have a problem. I will search for Die Geissens - ... But he do not shedule an record, at the first time, view last weeks one record was greated through your tool. But now he did nothing with this entry. Here are my logs !!
- January 3, 2008
- 890
- 556
- Home Country
-
Germany
- Thread starter
- Moderator
- #514
foxbenw,
sorry, it was not. Please go back and download again, i uploaded tvwishlist this time.
d3ltoroxp, can you give me some more info on the expected behaviour and point me to the log line where you think tvwishlist did not behave correctly.
f.y.i. I will be out the next days and follow up after the weekend.
sorry, it was not. Please go back and download again, i uploaded tvwishlist this time.
d3ltoroxp, can you give me some more info on the expected behaviour and point me to the log line where you think tvwishlist did not behave correctly.
f.y.i. I will be out the next days and follow up after the weekend.
do i need to use verbose debug?
i have turned it on. let me know if i don't need to.
if you don't answer i will leave it on and let you know when something happens.
i have turned it on. let me know if i don't need to.
if you don't answer i will leave it on and let you know when something happens.
Last edited:
Hi
it happened on the first day. several examples within the wishlist called family guy.
episode names are 'padre de familia', 'peter's daughter', 'mcstroke', and 'seahorse seashell party'
the last one is different to the others because it has already been scheduled but not recorded yet. it had already been scheduled on 20/5. today, as the data appeared for the 27/5, it was kept even though it was already in the schedules somewhere else.
the other 3 examples have already been recorded, so are like the swarley example above.
Ben
it happened on the first day. several examples within the wishlist called family guy.
episode names are 'padre de familia', 'peter's daughter', 'mcstroke', and 'seahorse seashell party'
the last one is different to the others because it has already been scheduled but not recorded yet. it had already been scheduled on 20/5. today, as the data appeared for the 27/5, it was kept even though it was already in the schedules somewhere else.
the other 3 examples have already been recorded, so are like the swarley example above.
Ben
Three more days attached
Ben
Ben
- January 3, 2008
- 890
- 556
- Home Country
-
Germany
- Thread starter
- Moderator
- #520
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 and 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.
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 and 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.