pdeliot 10 Posted August 4, 2022 Author Posted August 4, 2022 On 8/1/2022 at 5:42 PM, Luke said: 4.7.6 is up. Doesn’t look to solve thé problèm...
Luke 42077 Posted August 4, 2022 Posted August 4, 2022 2 minutes ago, pdeliot said: Doesn’t look to solve thé problèm... Hi, why do you think that? Can we please look at a specific example? Thanks.
revengineer 142 Posted August 4, 2022 Posted August 4, 2022 Interesting, I just installed and the number of scheduled recordings is reduced substantially and I conclude that this is because shows already in the database are now properly recognized. While I am still testing, I am cautiously optimistic. 1
pdeliot 10 Posted August 5, 2022 Author Posted August 5, 2022 May I have to "reset" the scheduling by any fashion.. or any other action to avoid this occuring anymore. But still have unxpected behavior. Maybe solved some cases... But still having ignored cases: Here an example.. We can see here the new recordings: All already identified as "READ" I just have delted, then rescheduled the serie: And all broadcasting are immediately planned for recording: Even if all these episodes are allready in the library: I have no other example yey, as I have made some cleanup .. But some other series are planned ans should not be (but I cannot check if id are correct for them).
pdeliot 10 Posted August 5, 2022 Author Posted August 5, 2022 (edited) I cannot find any scheduling where the option is working. The only skipped episode recording are those where the guide explicity tag them as "already aired" I have also checked the build: Looks right Edited August 5, 2022 by pdeliot
revengineer 142 Posted August 6, 2022 Posted August 6, 2022 I remember deleting my recording schedule upon install of 4.7.x for unrelated reasons. I setup all series recordings fresh in 4.7.x. Perhaps see if that works for you. You may be able to test this with a single show. Make sure you set the often to skip duplicate recording.
Luke 42077 Posted August 7, 2022 Posted August 7, 2022 On 8/5/2022 at 3:13 AM, pdeliot said: May I have to "reset" the scheduling by any fashion.. or any other action to avoid this occuring anymore. But still have unxpected behavior. Maybe solved some cases... But still having ignored cases: Here an example.. We can see here the new recordings: All already identified as "READ" I just have delted, then rescheduled the serie: And all broadcasting are immediately planned for recording: Even if all these episodes are allready in the library: I have no other example yey, as I have made some cleanup .. But some other series are planned ans should not be (but I cannot check if id are correct for them). Please Try refreshing the guide data in the server and see if that helps. Thanks.
pdeliot 10 Posted August 8, 2022 Author Posted August 8, 2022 Re-creating the scheduling, or update the guide ores not like to change anything... I'm trying to dig a little bit on the behavior. It seems that it is working when the existiong expisode are stored in the recording folders.. But not when stored elsewhere... I'm performaing some more tests and will let you know if I'm able to identify somethign else.
pdeliot 10 Posted August 8, 2022 Author Posted August 8, 2022 (edited) Humm... I have: reloaded the guide, dropped the scheduling, recreated the scheduling for this serie et and face the same strange behavior... For this one, non episode are in the "recording" folder.. All are in another folder, all read. Most of the episodes are re-scheduled for recording, that is unexpected... But few are skipped.. And I do not understand why... No "double scheduling".. Same status, folder, naming... in existing recodings. No divergeancy in the guide. Looks with same attribues in the guide: All already existing in the library (other folder): I've found something different for this S4E10 episode. An attached ".ttml" file exist in the folder.. and not for other episodes. In previous checks I was suspecting something about ".nfo" files in the folder.. Maybe we should have look to this...even if I have no evidence of the link. For another serie... it is even more strange... Asking for removing "already in library" is removing S4E12... wich is NOT in my libary... (And the only one marked as "New" in the guide) Removing S4E4: Expected Not removing S4E5: Wich shoud be removed as it is already in my library... All file ins same folder (not the recording target folder) Edited August 8, 2022 by pdeliot
Luke 42077 Posted August 24, 2022 Posted August 24, 2022 Are you saying that you have the same series in both the recordings library as well as another library?
pdeliot 10 Posted August 24, 2022 Author Posted August 24, 2022 5 hours ago, Luke said: Are you saying that you have the same series in both the recordings library as well as another library? Hi Luke, Yes.. I have three libraries One library with two folers for Series (Downloaded and re-encoded recordings) One for recordings (that may contain mlovies.. even if all is detected as series, but this is not the current topic there) One for Windows Media Center recording Then yes, a serie can be in several of these libraries... Aditionnely I have a "Film" (Movie) and DVD library. All this was working pretty wel in the past. And the read/unread status is working well "cross library"....
Luke 42077 Posted August 26, 2022 Posted August 26, 2022 Ok so that's the reason. It's checking all libraries.
pdeliot 10 Posted September 2, 2022 Author Posted September 2, 2022 (edited) Do this means this regression will be fixed? Edited September 23, 2022 by pdeliot
pdeliot 10 Posted October 16, 2022 Author Posted October 16, 2022 Any plan to fix this regression / breaking change? Before 4.70.60 the detection was "cross library", and it is not the case anymore. A fix would be best than wellcome.. Or at leat on option to choose the "legacy beahvior", or the "new" one...
Luke 42077 Posted October 17, 2022 Posted October 17, 2022 Hi, yes more options to control it are certainly possible. Thanks.
pdeliot 10 Posted November 6, 2022 Author Posted November 6, 2022 Any plan to include this option to get back to previous behavior and solve this regression? I'm struggeling in devlopping batches to manage double recordings...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now