Not good news, as I said before, the RS shows the Dragons' Den episode removed.
Unfortunately, the box itself shows the 3 programmes scheduled (both EPG and schedule).
The WebIf agrees with the box... all 3 scheduled.
I can try skipping the episode again, but anything before I do?
I have just re-visited the RS; as suggested, the episode now has gone from the schedule and the visual (removing the conflict).
I will check the box's own view when I get home this evening.
I still have the conflicting (and un-skipped) episode in my schedule, any logs that would help... I can run tests this evening.
For what it is worth, the conflict is this Sunday's The Voice/Call the Midwife/Dragon's Den (all HD). I was trying to skip Dragon's Den (which I can schedule on my...
I seem to be having the same problem (RS & WebIf). It is not a feature that I use very often, but trying it several times (using both interfaces) over the last day or two to avoid a conflict. However, like cdmackay, it initially shows as pending unschedule, but after a refresh it is back. The...
Hadn't realised that was a button... it just looked like a heading to an empty table. Thanks.
I got all greens :thumbsup:
{edit} should have said... Netgear DGN2200v4
I had a similar problem recently... I uninstalled the drivers for the network hardware and re-installed it (get latest drivers from the motherboard supplier before starting uninstall!).
I think that we used (or maybe I mis-advised you to use :() %filename before.
Try disabling rule 4 recurse 1 filename _ action {renamefile {%filename%replace,_, ,}}.
If that solves the logging problem, then maybe %filename should be %orig (like the other rules).
I liked the idea of having just one processing queue for both detectads plus decrypt (for BBC channels), furthermore, the new queue seems to offer the type of job control that I was looking for; which would finally get me away from having to run the detectads rule manually when I know that the...
I had entered the rule via the GUI and I obviously didn't copy and paste into the post, this time I have
# Remove Title "The " prefix
recurse 1 title {The *} action {settitle {%orig%replace,The ,,}}
# Remove "The " in Filename
recurse 1 filename {The *} action {renamefile {%orig%replace,The ,,}}
Your problem was that the condition "filename The action" didn't care about spaces, so happily finds Their. The "%orig%replace,The ,," was then searching for a "The " to replace, couldn't find one so tried to rename back to the original filename and reported the error. Then, ten minutes later...
Its not perfect, but changing the search to "The *" (without the quote marks) should eliminate the error reports that you had through mis-matching Them or Their...
# Remove "The " in Filename
recurse 1 filename The * action {renamefile {%orig%replace,The ,,}}
# Remove Title "The " prefix
recurse...
OK, so it just depends where you cut the text from, Windows or Linux. In any case, Trev had already mentioned searching in W10, so he was as likely to want the Windows form as not.
I was just trying some tests... What I said in the first post is probably ok, (except I cannot find a way of setting "The " as the initial search.
As for what I said about %orig in the second post... at least some of that is B***, but there is certainly something cyclic going on.
The log files...
I think that another part of the problem is that several of the rules rename from %orig, which means that (for example) in one rule the _ is replaced, but then the The rule shifts the The but puts the original _ back again. A hazzard of renames that consist of a series of rules, executed one...
Not good news, as I said before, the RS shows the Dragons' Den episode removed.
Unfortunately, the box itself shows the 3 programmes scheduled (both EPG and schedule).
The WebIf agrees with the box... all 3 scheduled.
I can try skipping the episode again, but anything before I do?
I have just re-visited the RS; as suggested, the episode now has gone from the schedule and the visual (removing the conflict).
I will check the box's own view when I get home this evening.
I still have the conflicting (and un-skipped) episode in my schedule, any logs that would help... I can run tests this evening.
For what it is worth, the conflict is this Sunday's The Voice/Call the Midwife/Dragon's Den (all HD). I was trying to skip Dragon's Den (which I can schedule on my...
I seem to be having the same problem (RS & WebIf). It is not a feature that I use very often, but trying it several times (using both interfaces) over the last day or two to avoid a conflict. However, like cdmackay, it initially shows as pending unschedule, but after a refresh it is back. The...
Hadn't realised that was a button... it just looked like a heading to an empty table. Thanks.
I got all greens :thumbsup:
{edit} should have said... Netgear DGN2200v4
I had a similar problem recently... I uninstalled the drivers for the network hardware and re-installed it (get latest drivers from the motherboard supplier before starting uninstall!).
I think that we used (or maybe I mis-advised you to use :() %filename before.
Try disabling rule 4 recurse 1 filename _ action {renamefile {%filename%replace,_, ,}}.
If that solves the logging problem, then maybe %filename should be %orig (like the other rules).
I liked the idea of having just one processing queue for both detectads plus decrypt (for BBC channels), furthermore, the new queue seems to offer the type of job control that I was looking for; which would finally get me away from having to run the detectads rule manually when I know that the...
I had entered the rule via the GUI and I obviously didn't copy and paste into the post, this time I have
# Remove Title "The " prefix
recurse 1 title {The *} action {settitle {%orig%replace,The ,,}}
# Remove "The " in Filename
recurse 1 filename {The *} action {renamefile {%orig%replace,The ,,}}
Your problem was that the condition "filename The action" didn't care about spaces, so happily finds Their. The "%orig%replace,The ,," was then searching for a "The " to replace, couldn't find one so tried to rename back to the original filename and reported the error. Then, ten minutes later...
Its not perfect, but changing the search to "The *" (without the quote marks) should eliminate the error reports that you had through mis-matching Them or Their...
# Remove "The " in Filename
recurse 1 filename The * action {renamefile {%orig%replace,The ,,}}
# Remove Title "The " prefix
recurse...
OK, so it just depends where you cut the text from, Windows or Linux. In any case, Trev had already mentioned searching in W10, so he was as likely to want the Windows form as not.
I was just trying some tests... What I said in the first post is probably ok, (except I cannot find a way of setting "The " as the initial search.
As for what I said about %orig in the second post... at least some of that is B***, but there is certainly something cyclic going on.
The log files...
I think that another part of the problem is that several of the rules rename from %orig, which means that (for example) in one rule the _ is replaced, but then the The rule shifts the The but puts the original _ back again. A hazzard of renames that consist of a series of rules, executed one...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.