I don't agree. It's causing a lot of extra processing on each pass and is filling up the log file. It makes sense to check whether it needs doing and skip the recording early if not.It's more trouble than it's worth.
I don't agree. It's causing a lot of extra processing on each pass and is filling up the log file. It makes sense to check whether it needs doing and skip the recording early if not.It's more trouble than it's worth.
What does that mean?updated in-place.
I just copy/pasted the aboveYou could explicitly look for the right pattern of numbers - this should be enough (for the next 85 years at least!):
Code:filename {*20[0-9][0-9][0-9][0-9][0-9][0-9]-*}
Thanks - will be fixed in the next version, which I'm just preparing now.There is something a bit odd about the handling of the \s in the regsub.
It seems to be present on the text edit page, but the \ seems to vanish from the interactive page; both in the interactive rule and its raw text equivalent.
Yep - sweeper 2.0.8-5 adds a global rule type, just put the keyword global at the start of the rule or in the GUI select the 'process files & folders' option when creating a rule.I know this ought to be in the sweeper thread, but the above reminded me: would you please consider some sort of "global" flag to allow the creation of rules that shoudl apply equally to folders, and to standalone files, so that the repetition above isn't required?
# Remove New: prefix.
global title New:* action {settitle {%orig%regsub,New:\s*,,}}
Yes, just one level.The name 'global' implies more, but I presume that we are still talking about folders as just one level, not fully recursive.
What I meant was that the whole thing is more trouble than it's worth. Trev doesn't like having a system time string in the file name - when actually it doesn't really matter. When it was processed is of no real interest, it can just be ignored.I don't agree. It's causing a lot of extra processing on each pass and is filling up the log file. It makes sense to check whether it needs doing and skip the recording early if not.
Yep - sweeper 2.0.8-5 adds a global rule type [...]
23/12/2015 15:39 - ==== folder /media/My Video/Border Security_ Canada's___ ====
23/12/2015 15:39 -
23/12/2015 15:39 - --- Considering /media/My Video/Border Security_ Canada's___/Border Security_ Canada's____20151219_0015.ts
23/12/2015 15:39 - Processing [!flag New foldername Border action {setguidance {Global rule applied}}]
23/12/2015 15:39 - !flag(New)
23/12/2015 15:39 - MATCH
23/12/2015 15:39 - foldername(Border)
23/12/2015 15:39 - MATCH
23/12/2015 15:39 - action(setguidance {Global rule applied})
23/12/2015 15:39 - ACTION: setguidance(Global rule applied) [1]
23/12/2015 15:39 - Applying action to recordings in /media/My Video/Border Security_ Canada's___
23/12/2015 15:39 - + folder_apply processing /media/My Video/Border Security_ Canada's___/Border Security_ Canada's____20151219_0015.ts
23/12/2015 15:39 - Setting guidance for /media/My Video/Border Security_ Canada's___/Border Security_ Canada's____20151219_0015.ts to Global rule applied
23/12/2015 15:39 - + folder_apply processing /media/My Video/Border Security_ Canada's___/Border Security_ Canada's____20151218_2345.ts
23/12/2015 15:39 - Setting guidance for /media/My Video/Border Security_ Canada's___/Border Security_ Canada's____20151218_2345.ts to Global rule applied
23/12/2015 15:39 -
I just made a rule to remove the New_ prefix on the filenames and much to my surprise it worked.
Nice - I'll have to add that to the template too.
The syntax for doing the string replacements is a bit clunky but I think that's the only really non-intuitive part.
I'll do that in the next version, thanks.Suggestion ... Perhaps the ruleset for disappearing the "New_" in filenames might be added to the Sweeper drop-down option also?
Hi there! Much longer time, no hear .... 8 years this timeApart from all that stuff. Welcome back DelftBlue. Long time no hear.