Not sure if this is a Wiz or IceTV question. I ended up with two recordings of Jamie & the Nonnas
What would cause this?
They aren't quite the same - one is 5 minutes longer than the other.
I'd guess that there's been a mishandling of a schedule change, but without more information, it's hard to say even which end was responsible.
This has been seen before. I've posted about what I saw happening, and I believe the IceTV server "forgets" it has the existing timer to update and creates a new timer for the scheduling change (as in 'Created by Scheduler SERIES' -- it's not an "Updated by").
http://forum.icetv.com.au/iceforum/beyonwiz/17/u4-schedule-change-produces-multiple-timers-for-same-program/5844/msg31214#msg31214
I have had a look at this one and it looks like a mistake back on the 19th caused the second timer to occur, and for some reason the original timer was not deleted because of this.
The guide team are already aware of what happened and are taking steps to ensure this doesn't happen again, and we will check the keyword handling (as it was in this that the original timer was not deleted) to try and get this one fixed.
Quote from: Daniel Hall at IceTV on November 22, 2018, 10:53:22 AM
I have had a look at this one and it looks like a mistake back on the 19th caused the second timer to occur, and for some reason the original timer was not deleted because of this.
The original Beyonwiz timer will only be deleted if the Beyonwiz gets a "forget" for the original ice_timer_id.
Quote from: prl on November 22, 2018, 02:22:26 PM
Quote from: Daniel Hall at IceTV on November 22, 2018, 10:53:22 AM
I have had a look at this one and it looks like a mistake back on the 19th caused the second timer to occur, and for some reason the original timer was not deleted because of this.
The original Beyonwiz timer will only be deleted if the Beyonwiz gets a "forget" for the original ice_timer_id.
Sorry, thats what I meant, for some reason the server did not create the forget timer correctly, I am currently looking into this.
And this particular bug has been found and fixed on the IceTV server end, but there looks to still be some cases that can cause duplicate timers, but will have to deal with each when we can get examples of each.
Thsnks for the feedback.
Yes, thank you for the feedback from me too
Quote from: Daniel Hall at IceTV on November 22, 2018, 05:29:58 PM
And this particular bug has been found and fixed on the IceTV server end, but there looks to still be some cases that can cause duplicate timers, but will have to deal with each when we can get examples of each.
Here is another example :-)
Quote from: Daniel Hall at IceTV on November 22, 2018, 05:29:58 PM
And this particular bug has been found and fixed on the IceTV server end, but there looks to still be some cases that can cause duplicate timers, but will have to deal with each when we can get examples of each.
And another example. Seems ti happen about once a week, haven't bothered to write here every time it happens as there was no acknowledgement of the examples given
I didn't even notice on the above that Graham Norton was about to double up as well
Just noticed something else...
C31 doesn't mark things as repeats, so often several versions of the same show get scheduled for recording each week
I noticed last night that Regional Italian Cuisine was set to record several times. I was sure that I have already deleted the extras, but figured i must have forgotten, so deleted them all last nigh.
I now notice that it hasn't been deleted off the Wiz, even though it is still shown as deleted in IceTV
I am working on this problem with Daniel Hall.
Thank you. It seems to be getting worse :-)
Do you want me to add each new example as it happens, or are the current examples enough?
Thanks, Judy. What Daniel's given me from your information and logging information from IceTV is enough to go on.
Is your Beyonwiz on a WiFi network connection or on wired Ethernet? The problem appears to be being triggered by network dropouts.
Quote from: prl on February 24, 2019, 06:12:15 PM
Thanks, Judy. What Daniel's given me from your information and logging information from IceTV is enough to go on.
Is your Beyonwiz on a WiFi network connection or on wired Ethernet? The problem appears to be being triggered by network dropouts.
I am on wired Ethernet
Another question. Can I delete the doubled up recordings, or should I keep them until you figure it out?
You can delete any double recordings and any duplicated timers that aren't marked with the blue IceTV "star".
Quote from: prl on February 24, 2019, 07:45:19 PM
You can delete any double recordings and any duplicated timers that aren't marked with the blue IceTV "star".
Hmm. This caused me to have a look at the timers. There ARE some doubled up timers there, where only one has the blue IcetV star, however there are also some single timers without the star. What does that mean?
I had doubling up on one of my T2 some weeks back. Relatively certain not happening with U4. I have ethernet connection, not wifi, but I recall having some other network issues about the same time (caused by power outage).
Ian
Quote from: csutak40 on February 24, 2019, 08:27:37 PM
Quote from: prl on February 24, 2019, 07:45:19 PM
You can delete any double recordings and any duplicated timers that aren't marked with the blue IceTV "star".
Hmm. This caused me to have a look at the timers. There ARE some doubled up timers there, where only one has the blue IcetV star, however there are also some single timers without the star. What does that mean?
One thing it means is that I was missing some information about the problem. I though that the visible issue was that you'd end up with doubled (or multiple) recordings of the same show, with all but one without the "IceTV star". I was puzzled by that because I thought that the underlying cause might also sometimes leave recordings without the star and no duplicates, and now I know that it does.
The problem underlying this is a bit nasty, because it seems to be a two-step thing.
- The enabling bug is that when IceTV sends a full list of timers, rather than just the ones that have changed since the last update, all timers are processed as though they have changed, even if they haven't.
- The visible bug is that sometimes that only part of the update process (delete old PVR recording timer/add updated recording timer) is done.
I can easily replicate part 1 of the problem, but I haven't been able to replicate part 2. The hint from the screenshot may help me replicate part 2 of the problem. If I can do that I can be more certain about whether I've fixed the bug completely. Fixing part 1 alone would probably help with reducing how often part 2 happens, but that would leave everyone with this weird bug that happens very infrequently.
Another oddity is that some people seem to see this problem quite a bit (like yourself), but others (like me) pretty much never see it. That means that there's something to do with the particular usage patterns between the two groups that can trigger the problem. One thing that can trigger both part 1 and part 2 of the bug is a network dropout, which is why I asked about whether you have WiFi.
BTW: I'm sure you've worked this out already, but the simplest thing to do in cases where you have a timer for a recording, but it's not marked with the blue star, just leave it to record, unless its times are wrong enough that your padding won't take care of it.
Quote from: prl on February 25, 2019, 01:24:24 PM
BTW: I'm sure you've worked this out already, but the simplest thing to do in cases where you have a timer for a recording, but it's not marked with the blue star, just leave it to record, unless its times are wrong enough that your padding won't take care of it.
Yeah, that's what I've been doing.
Incidentally, about to change to NBN, wonder if that will improve things?
Incidentally, about to change to NBN, wonder if that will improve things?
[/quote]
Depends on the version of nbn - FTTH is best, and FTTN is the worst (can be worse than ASDL). As far as I can work out FTTC should be better. HFC theoretically should be as good as FTTH (in short term), but some (few?) users are having problems with modem rebooting (and generally causing havoc). The cause can be hard to pin down, making it difficult in some cases to resolve. On the other hand, Telstra HFC is much more reliable and does not exhibit these issues. The only outages I have had recently have been due to power failures or network maintenance (latter probably related to work for nbn).
Quote from: IanL-S on February 25, 2019, 05:23:53 PM
Incidentally, about to change to NBN, wonder if that will improve things?
Depends on the version of nbn - FTTH is best, and FTTN is the worst (can be worse than ASDL). As far as I can work out FTTC should be better. HFC theoretically should be as good as FTTH (in short term), but some (few?) users are having problems with modem rebooting (and generally causing havoc). The cause can be hard to pin down, making it difficult in some cases to resolve. On the other hand, Telstra HFC is much more reliable and does not exhibit these issues. The only outages I have had recently have been due to power failures or network maintenance (latter probably related to work for nbn).
[/quote]
It will be FTTC It is ready to be installed, just going through my emails to change all the ones that are registered with my ISP as I intend to go to a different RSP
There is something going on with my current router (and it isn't the router - tested another) when doing a speed test, it often crashes during the upload test. Spent hours on the phone with TPG, got nowhere. Naturally, it is working fine ATM :-) https://www.speedtest.net/result/8067558958.png
BTW, I really think it must have something to do with old timers not being deleted.
Just started watching the Blacklist and I saw there were two recordings, which I presumed was correct (they often show two episodes) Turns out it wasn't :-)
Quote from: csutak40 on February 25, 2019, 03:21:31 PM
Incidentally, about to change to NBN, wonder if that will improve things?
It may. I don't really have a "smoking gun" for the exact triggers for the problem. The unnecessary delete/recreate of the timers can also be triggered by a Send all timers from the IceTV side, but I don't yet know how it goes from that issue to the messed up timer lists.
Just for something different. >:( It is now happening on the T2 as well (hardly record anything on that)
I don't think there's anything about the bug that would restrict it to one Beyonwiz model. The number of IceTV recordings you have for a device may influence how often the problem happens.
Have you gotten any further with this Peter?
It is still happening. Rather, not so much doubling up as shows being recorded under a different name (the name is the show I had scheduled, but the actual show recorded is something different.) No way of knowing of course if the show was on at a different time and I've missed it or just got cancelled
For instance (just got around to watching it today) Changing Rooms supposedly recorded on Friday and Saturday at 7.30, but what actually recorded was Graham Norton and Ambulance Australia. (no great loss with this particular show ;D) Come to think of it, Graham Norton also recorded under its correct title, watched that days ago.
Quite possibly Changing Rooms has been axed (not really surprised :D) as it is not scheduled at all for this week
Another thing that I am not sure about... Just watched Counterpart that was on last Thursday. I am convinced that I've missed an episode, as things just weren't making sense :P I seem to remember that one of the "problem" shows the previous week was Counterpart
Hi, Judy.
There are two (probably related) bugs here. One is that there's a bug that whenever IceTV sends all of your current timers (e.g. after a "Resend all timers"), the Beyonwiz does delete/recreate operations with the IceTV server on all timers in the list sent from the server, even ones that are unchanged by the new lot of "set timer" messages. As well as being triggered by "Resend all timers", this can also be triggered if an IceTV update fetch fails (e.g. because of a network problem). This bug is only apparent from looking at the debug logs either on the Beyonwiz or on the IceTV server. You'd normally not see any effect on the Beyonwiz user interface, other than it running a bit slower than it should.
The second bug is that it appears that sometimes when a delete/recreate operation is done for a timer, one or other part of the pair can fail. If the delete fails, you get two recording timers, one with the IceTV "star", and the other (the older one) without it. If the "recreate" fails, then the old timer loses its IceTV "star" and the new timer isn't created. I think you've seen both of those cases. This bug may also be being triggered by a network failure.
The possibility of the cause being a network dropout is why I asked about whether you were using WiFi to connect your T2.
I've been able to replicate the first bug. However, I tried forcing the first bug on a realistic timer load (47 timers - the timer load that was then current on our in-use T4) doing the unnecessary delete/recreate of all those timers 100 times over (yes, it was a bit tedious :)) without seeing any instance of the second bug. It may be that the second bug can only be triggered by a network problem.
My current state on this is that I've fixed the bug that causes unnecessary delete/recreates for IceTV timers on the Beyonwiz on my test version of the Beyonwiz IceTV plugin. That was relatively simple. On the way I also found two other minor and unrelated bugs and fixed them. I could not find any cause for the second bug other than the possibility of a networking error, either by stress-testing (as above), or by examining the code.
However, because the fix of the first bug will remove unnecessary delete/recreates I hope that the likelihood of the second error happening will be much reduced. I'm sorry that I can't promise more.
The current state is that I intended to test my modifications on our in-use T4 today, but other things have intervened. I will try to get that going on tomorrow. I'll also make the new version available to Daniel to try if he wants to.
Once I've run that for a few days without problems, I'll submit the fix to the code repository. From there it will need to wait until peteru accepts the changes and builds a firmware release containing them. He's very busy with other stuff at the moment, but I'll ask him if he could make time. In the short term, you may need to run public beta firmware for a while to take advantage of the changes. It will depend on how long it takes between having the changes in public beta to when they are released as official firmware.
Daniel - please get in touch if you'd like a patch kit with the changes.
Thank you, Peter. I should be changing to NBN (and a new router) in the next week or two, so will be intrested to see if anything changes (for the better or worse :-\)
Since you're getting FTTC delivery of NBN, you'll probably get reasonably reliable networking.
Hi, Judy.
I just installed a test version of my IceTV fixes on our in-use Beyonwiz T4. I'll submit the changes in a few days if the tests go OK.
Thank you, Peter
I've submitted a fix to eliminate the unnecessary delete/recreate operations that happen when IceTV sends a timer update, but the timer details have not changed.
Daniel, the version number for the updated Beyonwiz IceTV plugin is 20190308. If IceTV sends the Beyonwiz a "record" timer but the timer id already exists and the message from the IceTV server doesn't change the Beyonwiz timer, the Beyonwiz response for the "record" timer is
iceTimer["state"] = "pending"
iceTimer["message"] = "Timer already up to date Show Name"
If the timer is in fact already running, its state will be updated to "running" shortly after this response.
Thanks for the update. Look for to the new version.
Ian
My changes have been merged into the Beyonwiz source code repository, but I'm not sure when they will be available in a release (beta or official).
I am not sure if I am misunderstanding things, or if this is something different. I was looking at the timers to see if there is anything doubled up and delete one of them.
Then I did something i haven't done before (I usually only notice something doubling up after it has recorded) I looked on the IceTV web page and it is doubled up there as well! Has this always been the case, or is this something new?
Also, it is really weird. It has been behaving reasonably well lately, then last Thursday there were four shows doubled up. Then it stopped again
Judy I have seen this before; but my recollection is that it is not always limited to Beyonwiz - I am sure I've had it happen on a Toppy.
Ian
Quote from: csutak40 on March 19, 2019, 12:09:43 AM
I am not sure if I am misunderstanding things, or if this is something different. I was looking at the timers to see if there is anything doubled up and delete one of them.
Then I did something i haven't done before (I usually only notice something doubling up after it has recorded) I looked on the IceTV web page and it is doubled up there as well! Has this always been the case, or is this something new?
Also, it is really weird. It has been behaving reasonably well lately, then last Thursday there were four shows doubled up. Then it stopped again
This can happen if there is incorrectly two timers that overlap for a given show, and for this show I can definitely see it was affected by the particular issue that was fixed in the update from prl.
For these ones it would likely be that each of the timers within the IceTV database had to have had different durations (it won't allow having multiple timers for the same channel, start time and duration in the database at once), and it was displaying both of these timers on the website for you.
This one should hopefully fixed when the new plugin is pushed out via a firmware update.
Hi Peter,
It has been behaving ever since, but it is playing up today. Both timers have a star though. Thought I'd forward it, in case it means something to you
Just thought I'd pop back here again. Been noticing for the last few days lots of doubled up recordings and also noticed that most aren't marked with the blue IceTV "star", FWIW (I have already deleted all the shows marked to double up, before deciding to make the screen shot)
This is what my timers look like
This has happened twice over the last 24 hours ... overnight with the cricket on 9Gem and tonight with Interview on 7HD.
Hasn't happened before these 2 occurrences. Nor did it occur for several other recordings made today (Tuesday 4th).
I haven't made any changes to the shows that I'm recording via IceTV.
For the cricket on 9Gem, I did edit the timer via the Beyonwiz OpenWebif EPG function. I did so because I noticed that the match was running late (Pak innings ran over time) and the original end time (as per the Nine network guide) would have meant that I would miss the end of the match. So I added an extra 45 mins.
It was after I edited the timer that I noticed that there were 2 recordings running.
When I watched the English innings after getting up ... sure enough 1 recording ended before the match had finished, while they other recording recorded the whole match. Both recordings had the same start time.
As to the 2 recordings of Interview ... I didn't change or edit anything. Both recordings started at the same time, are the same length, have the same EIT data, etc. If I play 1 recording, stop it and then start the 2nd recording I'm asked if I want to resume ... Yes or No.
Looking at the directory via Windoz, I see 2 recordings with the 2nd having "_001" to differentiate the 2 recordings.
Relative new Beyonwiz U4 running the current FW release, etc.
So is there an updated IceTV app for the Beyonwiz U4? Or do I need to do something else to prevent this from occurring again ... If so, what?
Quote from: BazzaG on June 04, 2019, 11:45:51 PM
As to the 2 recordings of Interview ... I didn't change or edit anything. Both recordings started at the same time, are the same length, have the same EIT data, etc. If I play 1 recording, stop it and then start the 2nd recording I'm asked if I want to resume ... Yes or No.
FWIW Interview
was one of the doubled up recordings for me as well
I had two doubled-up recordings on my U4 last night - same programs scheduled on my T2 only had one instance. Start times differ by 5 or 10 minutes suggesting failure to delete old timer when timer updated.
Ian
This one is definitely a weird one, we have had a couple of reports now of a similar issue issue happening on at least two different U4's.
The current advice we have is to reinstall the current firmware using the USB update method (especially if the update to the current version was via an online update).
Thanks Daniel
I will give it a try when I have an opportunity to do so.
Ian
I've had a bunch of these "duplicate" timers too, for me it appears to have started with timers dated a week ago.
One of the "duplicate" timer pairings has the exact same Ice Timer ID value, implying the delete of the original timer failed to occur.
The remainder have an Ice Timer ID value for one of the "duplicate" pairing whilst the other does not, even though they both came from IceTV.
Some of the pairings have the exact same start/end times.
RecordTimerEntry(name=MasterChef Australia, begin=Wed May 29 19:20:00 2019, end=Wed May 29 21:10:00 2019, serviceref=1:0:19:684:607:1014:EEEE0000:0:0:0:, justplay=0, isAutoTimer=0)
RecordTimerEntry(name=MasterChef Australia, begin=Wed May 29 19:20:00 2019, end=Wed May 29 21:10:00 2019, serviceref=1:0:19:684:607:1014:EEEE0000:0:0:0:, justplay=0, isAutoTimer=0, ice_timer_id=16503460931876180420)
RecordTimerEntry(name=The Bay, begin=Wed May 29 21:50:00 2019, end=Wed May 29 23:25:00 2019, serviceref=1:0:19:564:506:1013:EEEE0000:0:0:0:, justplay=0, isAutoTimer=0, ice_timer_id=16503460931993620935)
RecordTimerEntry(name=The Bay, begin=Wed May 29 21:50:00 2019, end=Wed May 29 23:25:00 2019, serviceref=1:0:19:564:506:1013:EEEE0000:0:0:0:, justplay=0, isAutoTimer=0)
RecordTimerEntry(name=The Good Fight, begin=Wed May 29 21:25:00 2019, end=Wed May 29 22:55:00 2019, serviceref=1:0:19:325:320:3202:EEEE0000:0:0:0:, justplay=0, isAutoTimer=0)
RecordTimerEntry(name=The Good Fight, begin=Wed May 29 21:25:00 2019, end=Wed May 29 22:55:00 2019, serviceref=1:0:19:325:320:3202:EEEE0000:0:0:0:, justplay=0, isAutoTimer=0, ice_timer_id=16503460931993620934)
RecordTimerEntry(name=Blindspot, begin=Wed May 29 23:20:00 2019, end=Thu May 30 00:55:00 2019, serviceref=1:0:19:564:506:1013:EEEE0000:0:0:0:, justplay=0, isAutoTimer=0, ice_timer_id=16503460934963188169)
RecordTimerEntry(name=Blindspot, begin=Wed May 29 23:20:00 2019, end=Thu May 30 00:55:00 2019, serviceref=1:0:19:564:506:1013:EEEE0000:0:0:0:, justplay=0, isAutoTimer=0)
RecordTimerEntry(name=Hawaii Five-0, begin=Wed May 29 23:00:00 2019, end=Thu May 30 00:30:00 2019, serviceref=1:0:19:684:607:1014:EEEE0000:0:0:0:, justplay=0, isAutoTimer=0, ice_timer_id=16503460934963188168)
RecordTimerEntry(name=Hawaii Five-0, begin=Wed May 29 23:00:00 2019, end=Thu May 30 00:30:00 2019, serviceref=1:0:19:684:607:1014:EEEE0000:0:0:0:, justplay=0, isAutoTimer=0)
RecordTimerEntry(name=MasterChef Australia, begin=Thu May 30 19:20:00 2019, end=Thu May 30 21:10:00 2019, serviceref=1:0:19:684:607:1014:EEEE0000:0:0:0:, justplay=0, isAutoTimer=0, ice_timer_id=16503460934963188170)
RecordTimerEntry(name=MasterChef Australia, begin=Thu May 30 19:20:00 2019, end=Thu May 30 21:05:00 2019, serviceref=1:0:19:684:607:1014:EEEE0000:0:0:0:, justplay=0, isAutoTimer=0)
RecordTimerEntry(name=Blue Bloods, begin=Thu May 30 22:25:00 2019, end=Thu May 30 23:55:00 2019, serviceref=1:0:19:684:607:1014:EEEE0000:0:0:0:, justplay=0, isAutoTimer=0)
RecordTimerEntry(name=Blue Bloods, begin=Thu May 30 22:30:00 2019, end=Thu May 30 23:55:00 2019, serviceref=1:0:19:684:607:1014:EEEE0000:0:0:0:, justplay=0, isAutoTimer=0, ice_timer_id=16503460934996742608)
RecordTimerEntry(name=Chimerica, begin=Thu May 30 21:20:00 2019, end=Thu May 30 22:55:00 2019, serviceref=1:0:19:325:320:3202:EEEE0000:0:0:0:, justplay=0, isAutoTimer=0)
RecordTimerEntry(name=Chimerica, begin=Thu May 30 21:20:00 2019, end=Thu May 30 22:55:00 2019, serviceref=1:0:19:325:320:3202:EEEE0000:0:0:0:, justplay=0, isAutoTimer=0, ice_timer_id=16503460934979965388)
RecordTimerEntry(name=The Voice Australia, begin=Sun Jun 2 18:50:00 2019, end=Sun Jun 2 21:00:00 2019, serviceref=1:0:19:462:460:1012:EEEE0000:0:0:0:, justplay=0, isAutoTimer=0, ice_timer_id=16503460935248400865)
RecordTimerEntry(name=The Voice Australia, begin=Sun Jun 2 18:50:00 2019, end=Sun Jun 2 20:55:00 2019, serviceref=1:0:19:462:460:1012:EEEE0000:0:0:0:, justplay=0, isAutoTimer=0)
RecordTimerEntry(name=MasterChef Australia, begin=Mon Jun 3 19:20:00 2019, end=Mon Jun 3 21:10:00 2019, serviceref=1:0:19:684:607:1014:EEEE0000:0:0:0:, justplay=0, isAutoTimer=0, ice_timer_id=16503460935483281906)
RecordTimerEntry(name=MasterChef Australia, begin=Mon Jun 3 19:20:00 2019, end=Mon Jun 3 21:05:00 2019, serviceref=1:0:19:684:607:1014:EEEE0000:0:0:0:, justplay=0, isAutoTimer=0)
RecordTimerEntry(name=MasterChef Australia, begin=Tue Jun 4 19:20:00 2019, end=Tue Jun 4 21:10:00 2019, serviceref=1:0:19:684:607:1014:EEEE0000:0:0:0:, justplay=0, isAutoTimer=0, ice_timer_id=16503460935483281910)
RecordTimerEntry(name=MasterChef Australia, begin=Tue Jun 4 19:20:00 2019, end=Tue Jun 4 21:05:00 2019, serviceref=1:0:19:684:607:1014:EEEE0000:0:0:0:, justplay=0, isAutoTimer=0, ice_timer_id=16503460935483281910)
Cheers,
Geoff
I have had the same issue on my U4 as Judy reported over the last week with a few duplicate recordings and the ICETV symbol gone missing. It has also happened on my T3. I have just reflashed the U4 so will keep an eye on it.
New weirdness
I noticed that Masterchef was doubled up, so I thought I'd delete/stop one of them. (both started at the same time) This is what I ended up with
Have never seen this before. Does this mean it is still recording? I doubt it, the time elapsed hasn't changed since I've deleted the other one
Quote from: csutak40 on June 05, 2019, 07:45:04 PM
Have never seen this before. Does this mean it is still recording? I doubt it, the time elapsed hasn't changed since I've deleted the other one
You're chase-playing that file (it's currently recording) and you've then pressed MEDIA to enter the media selection list.
If you exit the media selection list and immediately re-enter it, you'll see the elapsed time of the recording change.
Quote from: grumpy_geoff on June 05, 2019, 08:12:01 PM
Quote from: csutak40 on June 05, 2019, 07:45:04 PM
Have never seen this before. Does this mean it is still recording? I doubt it, the time elapsed hasn't changed since I've deleted the other one
You're chase-playing that file (it's currently recording) and you've then pressed MEDIA to enter the media selection list.
If you exit the media selection list and immediately re-enter it, you'll see the elapsed time of the recording change.
Yes, you are right - that's what's happening. So, basically, when I stopped the recording for one of them I stopped it for both
2 recordings of Five Bedrooms on 10HD are now running, however, the 2 recordings have started 5 mins apart ... 1 at 20:35 & the 2nd at 20:40.
I also have several recordings setup across 2 ABC channels since 6pm and ALL of 'em have only been recorded once ... so far.
Also, my U4 is only a few weeks old and was updated to the latest FW by Jai before delivery. I have no idea which method he used.
Five Bedrooms
Wed 05.06.2019 20:35 - 05.06.2019 21:55
10 HD
Series 1, Episode 4
running
------------------------
Five Bedrooms
Wed 05.06.2019 20:40 - 05.06.2019 22:05
10 HD
Series 1, Episode 4
running
------------------------
On the IceTV website it has:
Five Bedrooms
'Series 1, Episode 4'
10 HD, 8:45pm, Wed, 5 Jun 2019, 65 minutes
-------------------------
The FTA embedded EPG data has: 20:46 -> 21:50.
Given that I start the recording 5 min early and end after 15 mins that would make the 2nd of the timers above correct.
The 1st would be correct if the start/end times as shown by the YourTV guide.
What it looks to me like a timer was initially added probably 7 days ago and then was updated as the Ten published better times. For whatever reason the 1st timer wasn't replaced or updated by the new start/end times.
Quote from: csutak40 on June 05, 2019, 08:33:06 PM
...So, basically, when I stopped the recording for one of them I stopped it for both
No, you stopped one - the other was still recording (as per the red part of the status icon).
Quote from: grumpy_geoff on June 05, 2019, 10:33:41 PM
Quote from: csutak40 on June 05, 2019, 08:33:06 PM
...So, basically, when I stopped the recording for one of them I stopped it for both
No, you stopped one - the other was still recording (as per the red part of the status icon).
But I have never seen this status icon before. Usually, it has a red dot when a show is being recorded. Had I not watched it while chase playing, would it have saved it? I am not being argumentative, just trying to understand
Before I deleted the other recording, both were showing the red circle as usual, the status icon changed to what is shown on the screen shot, only after I deleted the other one
Quote from: csutak40 on June 05, 2019, 11:19:55 PM
Quote from: grumpy_geoff on June 05, 2019, 10:33:41 PM
Quote from: csutak40 on June 05, 2019, 08:33:06 PM
...So, basically, when I stopped the recording for one of them I stopped it for both
No, you stopped one - the other was still recording (as per the red part of the status icon).
But I have never seen this status icon before. Usually, it has a red dot when a show is being recorded.
Yes, because "usually" you do not chaseplaying a recording do you?
See
'Movie Player Icons - basic recording state' in http://beyonwiz.com.au/forum/viewtopic.php?f=42&t=9220#p123075
Quote from: csutak40 on June 05, 2019, 11:19:55 PM
Had I not watched it while chase playing, would it have saved it? I am not being argumentative, just trying to understand
Yes, chaseplaying a current recording doesn't cause it to be deleted.
Quote from: csutak40 on June 05, 2019, 11:19:55 PM
Before I deleted the other recording, both were showing the red circle as usual, the status icon changed to what is shown on the screen shot, only after I deleted the other one
I don't think so, I think it changed to the
'Being played while it's recording' icon because - (i) you entered the media selection list, (ii) chose this rcecording and played it, (iii) pressed MEDIA button whilst still playing that recording, and (iv) then observed this previously unseen (to you) icon.
One question I have for the people experiencing this, do you have the USB tuner installed and enabled?
A just looked at my timers.
I have numerous timers doubled up.
each duplicate has a small difference in either/ or startimes end times
eg heartbeat 1600 and 1610 start times 1750, 1755 end time. 9gem
touch of frost start times 2015 start time for both timers but end time 2215 Nd 2315 72 melb
Graham Norton start times 2045 on both, but 2225 and 2230 end times. 10 peach
Blue Bloods. Start times 2225 and 2230. end times 2355 and 0005 10hd
All timers re today.
All duplicates are on their same service
And yes I am using a USB tuner installed and enabled.
just an addition to the last post
My Ice log shows just regular 15 minute downloads and updates.
no other entries..
U4. ice version 20180601, f/w. 17.5. 20190207
Quote from: Daniel Hall at IceTV on June 06, 2019, 01:50:50 PM
One question I have for the people experiencing this, do you have the USB tuner installed and enabled?
I'm getting it on our T4 which doesn't allow the use of the USB tuner (demuxer limit).
I know Judy is also getting it on her T4 (and also on her T2 going by the thread).
Quote from: Daniel Hall at IceTV on June 06, 2019, 01:50:50 PM
One question I have for the people experiencing this, do you have the USB tuner installed and enabled?
Yes it's installed & enabled on my U4.
I checked my timers for today early this morning and there are no duplicate timers. Just checked again and still no duplicates.
Hi Guys,
As an update on this, there are two specific issues that we are aware of, to try and differentiate them lets call them 'duplicate recordings' and 'split recordings'.
The duplicate recording issue is shown when you have two timers for a specific show, but either the start time or duration are slightly different between the two. One of them will show the IceTV blue star and the other one will not. This occurs when a timer update is downloaded by the Beyonwiz but then the next update to the server fails the Beyonwiz will be left with two timers listed with both the new and old details. This has been worse in the last week or so due to an issue on the server that was causing some requests to take longer than normal and would then cause some requests to time out.
Now that the server load issue is sorted you will see significantly less of this issue, and any duplicate timers that don't have the IceTV blue star in the timer list can be safely deleted without issues.
The second issue that we will call 'split recordings' is where a recording will be split into multiple files for some unknown reason, we have seen at least a U4 with this issue and have no known cause as yet.
Daniel,
Thanks for the update.
I hadn't taken notice the Ice logo difference on the timers.
but having said that, currently, I have a number of times that are not duplicated that don't have the logo.
Current plane would be to delete all timers and resend them.
On the split recording, I have had this on a T3 and U4.
Currently only using the U4
This problem appeared to be an unbidden GUI restart. Reason unknown.
I went through a few iterations of add ons to see if that was the issue.
Generally it seems to me to be associated with Series to folder, and directory number count add ons
But. after going back to square one. Initialise the box U4, then reinstall 20190207 17.5 f/w. then add n the series to folder, and numcount, all has seemed to be stable since then. a couple of months now..
Oops put my foot in it there. it'll rear its ugly head after I said that.
Thanks for the update Daniel.
Hi Grampus,
I've had this issue on my U4 for a few months. Last Wednesday at about 9:30pm I did just as you did with a re-install of the firmware and a re-install of the series folder on Saturday, but I don't use the number count. This Wednesday my first recording - ABC News split into two and the following Masterchef did too. In the past a recording of Masterchef once split into about 12 (!) but interestingly my logs, when examined by Dan, didn't show all 'split' episodes. So keep your fingers crossed!! I have seen random GUI restarts whilst watching a recording but we wondered if that was due to updating the last software update via on-line update, hence the USB update re-install last week.
Quote from: MD on June 06, 2019, 05:13:28 PM
...This Wednesday my first recording - ABC News split into two and the following Masterchef did too. In the past a recording of Masterchef once split into about 12 (!) but interestingly my logs, when examined by Dan, didn't show all 'split' episodes.
Your "split-recording" issues may be the result of a GUI crash, and there may have been crash logs written at the time.
Have a look in
/home/root/logs/ for crash logs (of the form Enigma2_crash_{date/time}.log).
Cheers,
Geoff
Quote from: Daniel Hall at IceTV on June 06, 2019, 01:50:50 PM
One question I have for the people experiencing this, do you have the USB tuner installed and enabled?
There is n USB tuner on the T4 (AFIK)
Quote from: grumpy_geoff on June 06, 2019, 03:23:44 PM
I'm getting it on our T4 which doesn't allow the use of the USB tuner (demuxer limit).
I know Judy is also getting it on her T4 (and also on her T2 going by the thread).
The T2 (which does have the USB tuner enabled) seems to behaving ATM
I now checked. Up till next Tuesday 99% of my timers have no IceTV Icon. After Tuesday, the icon has re-appeared for all of them. That must have to do with Daniel's fix.
I also noticed something else. I deleted a series recording yesterday, but none of the times have gotten deleted off the Wiz.
So, would the best course of action be to delete all the times with no icon an see if they get re-sent with the icon?
Quote from: csutak40 on June 06, 2019, 09:07:13 PM
I also noticed something else. I deleted a series recording yesterday, but none of the times have gotten deleted off the Wiz.
That's because the associated timers are missing the 'ice_timer_id' attribute so they can't be identified to delete.
Quote from: csutak40
So, would the best course of action be to delete all the times with no icon an see if they get re-sent with the icon?
I wouldn't bother as the timers are there and you've got a lot to delete. If there is a time change then IceTV will send an update through and this will generate a new timer for that event, but the old timer can't be identified to delete so you can then simply delete the matching "non-Ice" timer.
I suggest that anyone who's having problems with these doubled up timers update to newer firmware - 20190630 or later.
Those versions have a fix that should help with the problems.
20190630 is the release firmware for the V2, but it's still being marked as "public beta" for other models.
If you're upgrading from any 17.5 series firmware version, just save your settings, upgrade and restore settings.
If you're upgrading from 16.1 series firmware, you'll need to redo your settings from scratch.
Quote from: prl on July 30, 2019, 09:19:46 AM
I suggest that anyone who's having problems with these doubled up timers update to newer firmware - 20190630 or later.
I just know I'm going to regret asking...
Firstly, is it safe to install, or should I wait for the official release?
Secondly, (if yes) where do I find it? (yes, I did look, I did find the download for V2, but I don't know if you meant we should use that for the T series, or the beta version for those are hidden somewhere I can't find? I would appreciate a link
Quote from: csutak40 on July 30, 2019, 03:43:02 PM
Quote from: prl on July 30, 2019, 09:19:46 AM
I suggest that anyone who's having problems with these doubled up timers update to newer firmware - 20190630 or later.
I just know I'm going to regret asking...
Not sure why. They're all perfectly reasonable questions.
Quote from: csutak40 on July 30, 2019, 03:43:02 PM
Firstly, is it safe to install, or should I wait for the official release?
I'm running the latest public beta on the T4 we actually use for recordings (I have a bunch of test machines, too). That version is 20190718. But it's up to you, really.
Quote from: csutak40 on July 30, 2019, 03:43:02 PM
Secondly, (if yes) where do I find it? (yes, I did look, I did find the download for V2, but I don't know if you meant we should use that for the T series, or the beta version for those are hidden somewhere I can't find? I would appreciate a link
The V2 firmware won't install on your T2 or T4, and shouldn't be used on them anyway.
The 20190718 firmware for the T2 and T4 are hidden away a bit, but you can find them here (https://www.beyonwiz.com.au/forum/viewtopic.php?f=56&t=13422&start=100#p180210). (In the Beyonwiz forum in Public Beta (Enter at your own Risk) > beyonwiz-19.3 20190630). The 20190630 is in the first post in that topic.
However, if you're going to go with the 19.3 series firmware, I recommend going straight to 20190718, because there are problems doing an online upgrade from 20190630 to more recent versions. Those problems are fixed in 20190718.
Thank you
No problem :)
Quote from: Daniel Hall at IceTV on November 22, 2018, 05:29:58 PM
And this particular bug has been found and fixed on the IceTV server end, but there looks to still be some cases that can cause duplicate timers, but will have to deal with each when we can get examples of each.
This is happening again (still?)
I am now on the V2 and has been happening a few times, but was having other (teething) problems, so didn't worry about mentioning it. In some cases I noticed it before it actually recorded, so deleted one
It seems to be becoming more frequent
I have not seen doubled up recordings for a long time on either my U4 or T2s.
Am I correct in assuming that they are all on 10 Network (Ten). If they are on 10, are they both on HD, both on SD one one of each. I had a similar issue some months back on one of Toppys, in that case sheduled for both ABC and ABC HD. I have removed all the SD LCN for which there is a HD version so no longer prone to the problem.
Ian
Quote from: IanL-S on December 25, 2020, 07:27:49 AM
I have not seen doubled up recordings for a long time on either my U4 or T2s.
Am I correct in assuming that they are all on 10 Network (Ten). If they are on 10, are they both on HD, both on SD one one of each. I had a similar issue some months back on one of Toppys, in that case sheduled for both ABC and ABC HD. I have removed all the SD LCN for which there is a HD version so no longer prone to the problem.
Ian
They were both on 10 FWIW (will take more notice if it happens again) Both on the same channel. The only difference is that their starting end/or ending time changed and the first entry wasn't deleted when the second one got added