2006-05-22, 12:14 AM
Hi Sub,
The base is SQL, I will reproduce with debug level tomorrow. Now it's late night.
The base is SQL, I will reproduce with debug level tomorrow. Now it's late night.
2006-05-22, 12:14 AM
Hi Sub,
The base is SQL, I will reproduce with debug level tomorrow. Now it's late night.
2006-05-22, 01:03 AM
sub Wrote:You guys that have had failures, which database are your using? I converted from the old db to the new format, and imported my old data to the new SQLite format with the migration tool provided with 97.7. I'll get mine switched to Debug ASAP.
2006-05-22, 01:05 AM
Can you zip and email your gbpvr.db3 file to me at support@devnz.com?
2006-05-22, 01:12 AM
sub Wrote:Can you zip and email your gbpvr.db3 file to me at support@devnz.com? On its way.
2006-05-22, 07:47 AM
Hi Sub,
here is my test: 9.11 recording scheduled to 9.15-9.30 within EWA 9.12 GbPvr started and LiveTV 9.22 LiveTV exit, record started immediately 9.25 GbPvr exit 9.40 record finished (correctly: 9.30+post-show padding) pre-show padding set to 2min, post-show padding: 10min. Jacek
2006-05-23, 12:10 AM
Hi Sub,
have you managed to replicate LiveTV/recording problem? In my opinion logs don't show anything at the time when record should have started.
2006-05-23, 12:28 AM
No, I havnt really looked at it in any detail yet. Its on my list of things to do when I've got time.
Your logs did contain the same error as the others though: Quote:2006-05-22 09:12:09.656 ERROR [3] Unexpected error loading record schedule for next 24hours: Indeks jest spoza zakresu. Musi mieć wartość nieujemną i mniejszą niż rozmiar kolekcji.
2006-05-24, 08:13 PM
I'm think this is related to an error in the data migration to SQLite. Can you some of you please send your gbpvr.db3 file over to me at support@devnz.com so I can take a look at your database?
2006-05-25, 01:27 AM
I'm fairly sure I've found and corrected this problem. It didnt relate the data conversion as I suspected above, but rather a small difference in behaviour between SQLite and Access for a particular DB call.
I've attached a patch that should resolve the issue.
2006-05-25, 11:20 PM
I'll test this over the next 24 hours and see what happens!
|
|