United States of America
- Thread starter
- Moderator
- #11
I've not gone mad ..... 
Not all scheduled recordings are shown in EPG (1 Viewer)
- Thread starter 2BitSculptor
- Start date
No changes were made to this area in 1.2.3, so I can't see how it can be worse than 1.2.2.
However, if you are able to provide side by side comparisons of 1.2.3 and 1.2.2 with the same data (logs and screenshots) then if something has got worse in 1.2.3 it should be relatively easy to find, which in turn might help finding the general cause.
For me, I have never seen this at all, so we need to know what is triggering it.
If you see this problem, how many recordings do you have scheduled? Maybe it only happens with a lot of schedules.
Do you also use schedulesdirect?
Does schedulesdirect replace any core MP files? I don't want to install it myself just to test, but if you are both using it and seeing the problem, and no-one else is, then you need to report it to the schedulesdirect author.
- Thread starter
- Moderator
- #14
Schedules Direct only has 2 dlls in TV-Server plugins. One for Schedules Direct lineup and one to get TVDB Season/episode numbers.
I'm using Schedules Direct. Paul must be using something else.
Paul Shirley said,
Schedules Direct only populates the guide... it seems to be something (not) happening afterwards, after programs are scheduled to record.
I too noticed it in 1.2.2, but not in 1.1.1, and it didn't go away in 1.2.3 as I was hoping.
Last edited:
- Thread starter
- Moderator
- #15
I also have my start and ending times for recording padded by 1 min, both ends.
- November 3, 2008
- 68
- 3
No plugins at all, just the built in DVB EPG support on a singleseat setup with mySQL. I only use the front end to set recordings, about 300 series set at the moment, all playback and file management done externally.
This started happening when sql query caching was introduced to speed up the EPG display, whichever build that was - before 1.2.2. Just been happening more consistently in 1.2.3 - until today!
That looks like a clue though: last night I finally killed protected file protection in Comodo Internet Security, which was adding about 18sec delay every time I set a recording, it's too soon to be sure but I've not seen it cock up so far today. Maybe the caching query is just timing out?
This started happening when sql query caching was introduced to speed up the EPG display, whichever build that was - before 1.2.2. Just been happening more consistently in 1.2.3 - until today!
That looks like a clue though: last night I finally killed protected file protection in Comodo Internet Security, which was adding about 18sec delay every time I set a recording, it's too soon to be sure but I've not seen it cock up so far today. Maybe the caching query is just timing out?
300 series, wow! Maybe that is the common factor. Seems a lot to have at any one time.
Clearly if this was happening for a lot of people, we would have more reports. We just need to identify the common factors.
Clearly if this was happening for a lot of people, we would have more reports. We just need to identify the common factors.
- Thread starter
- Moderator
- #18
Sorry... don't have quite that many.... closer to 18 series (6 daily, 12 weekly), and not more than 5 regular recordings each week. and the series seasons are pretty much over for the summer.
I have a DSL connection, but it is a slow one at best, with frequent delays.
Not running any firewall (other than MS) and no anti-virus on the TV-Server
I have a DSL connection, but it is a slow one at best, with frequent delays.
Not running any firewall (other than MS) and no anti-virus on the TV-Server
Last edited:
- November 3, 2008
- 68
- 3
What I suspect was happening before killing Comodo is a large random latency being added to each SQL query, while Comodo pointlessly scanned for file system changes. In ordinary use that wouldn't be very noticeably but any time MP fires off a lot of queries that could cause problems. I was seeing recordings take 2.8x longer to set and having so many schedules made it take a LONG time (hence easy to time).
If the initial EPG initialisation gets hit the same way would it time out and miss some schedules? The huge schedule list is probably half the problem even though its a beast that should be able to cope.
If the initial EPG initialisation gets hit the same way would it time out and miss some schedules? The huge schedule list is probably half the problem even though its a beast that should be able to cope.
