v0.98.8 available

[spyork]

Anyone have any issues when upgrading. I did an uninstall and then a fresh install of the new version. For whatever reason the new version does not like my old gbpvr.db3 file. The channel changes on the MVP are extremely slow (~30 seconds). My capture sources don't list any channels. I removed and re-added all of those and still nothing is listed. It appears my EPG updated as the TV Guide is populated. The only way I've been able to resolve the problem is too start from scratch with a fresh database file. The errors I were getting in the GBPVRRecordingService logs were as follows:

9/10/2006 10:14:51 AM.281 VERBOSE [9] Getting current programme from cache
9/10/2006 10:14:51 AM.281 VERBOSE [9] Temporary live TV filename: G:\gbpvr\Buffer\The Hand That Rocks the Cradle_2_20060910_08001015-3.mpg
9/10/2006 10:15:22 AM.524 ERROR [9] Encountered unexpected error during AddNewLiveTVFile(): The database file is locked
database is locked
9/10/2006 10:15:22 AM.540 ERROR [9] at System.Data.SQLite.SQLite3.Reset(SQLiteStatement stmt)
at System.Data.SQLite.SQLite3.Step(SQLiteStatement stmt)
at System.Data.SQLite.SQLiteCommand.ExecuteNonQuery()
at GBPVR.RecordingService.xe14ff94ac1bb1522.x44bd982c7593507c(String x8b1d9e3189e6e73d)
9/10/2006 10:15:31 AM.079 VERBOSE [9] Opportunity to reuse capture graph. Attempting quick channel change
9/10/2006 10:15:31 AM.079 ERROR [9] Failure in ChannelFactory::getSourceChannelTuning(): Specified cast is not valid.
9/10/2006 10:15:31 AM.079 ERROR [9] at System.Data.SQLite.SQLiteDataReader.VerifyType(Int32 i, DbType typ)
at System.Data.SQLite.SQLiteDataReader.GetInt32(Int32 i)
at GBPVR.Backend.Common.ChannelFactory.x53d75101a4877d91(Int32 x70cd72e44179c0c2, Int32 xeba3e20435eb0e32)

I'm just curious what may have caused this problem. My database wasn't too big so starting with a fresh database is not a big deal this time, but in the future I would prefer not to run into this problem again. I would appreciate any ideas or suggestions that anyone may have. Thanks...

[roy]

After upgrading, when entering 'settings' from the 'system' menu I get kicked out with the error shown in attached. (same with blue skin)

[HtV]

Anyone have any issues when upgrading. I did an uninstall and then a fresh install of the new version. For whatever reason the new version does not like my old gbpvr.db3 file. The channel changes on the MVP are extremely slow (~30 seconds). My capture sources don't list any channels. I removed and re-added all of those and still nothing is listed. It appears my EPG updated as the TV Guide is populated. The only way I've been able to resolve the problem is too start from scratch with a fresh database file. The errors I were getting in the GBPVRRecordingService logs were as follows:

9/10/2006 10:14:51 AM.281 VERBOSE [9] Getting current programme from cache
9/10/2006 10:14:51 AM.281 VERBOSE [9] Temporary live TV filename: G:\gbpvr\Buffer\The Hand That Rocks the Cradle_2_20060910_08001015-3.mpg
9/10/2006 10:15:22 AM.524 ERROR [9] Encountered unexpected error during AddNewLiveTVFile(): The database file is locked
database is locked
9/10/2006 10:15:22 AM.540 ERROR [9] at System.Data.SQLite.SQLite3.Reset(SQLiteStatement stmt)
at System.Data.SQLite.SQLite3.Step(SQLiteStatement stmt)
at System.Data.SQLite.SQLiteCommand.ExecuteNonQuery()
at GBPVR.RecordingService.xe14ff94ac1bb1522.x44bd982c7593507c(String x8b1d9e3189e6e73d)
9/10/2006 10:15:31 AM.079 VERBOSE [9] Opportunity to reuse capture graph. Attempting quick channel change
9/10/2006 10:15:31 AM.079 ERROR [9] Failure in ChannelFactory::getSourceChannelTuning(): Specified cast is not valid.
9/10/2006 10:15:31 AM.079 ERROR [9] at System.Data.SQLite.SQLiteDataReader.VerifyType(Int32 i, DbType typ)
at System.Data.SQLite.SQLiteDataReader.GetInt32(Int32 i)
at GBPVR.Backend.Common.ChannelFactory.x53d75101a4877d91(Int32 x70cd72e44179c0c2, Int32 xeba3e20435eb0e32)

I'm just curious what may have caused this problem. My database wasn't too big so starting with a fresh database is not a big deal this time, but in the future I would prefer not to run into this problem again. I would appreciate any ideas or suggestions that anyone may have. Thanks...

I don't know if you did, but I'll say it anyway: You can not install 98.08 and then put back the gbpvr.db3 from version 97.13(or whatever).

[HtV]

After upgrading, when entering 'settings' from the 'system' menu I get kicked out with the error shown in attached. (same with blue skin)

Maybe try with the default blus skin?

[Fatman_do]

After upgrading, when entering 'settings' from the 'system' menu I get kicked out with the error shown in attached. (same with blue skin)

ContourHC does not contain the skin for the settings screen. I am not sure why it does not work in blue.

Zip and attach your logs.

[Old Dog]

My system is working. The GBPVRPublic.dll is time stamped 9/9/2006 9:20 AM.

If yours is the same then try rebooting, if not, try reinstalling GBPVR.

[HtV]

Maybe try with the default blus skin?

Edit: sorry I wasn't reading well:o

[lseats]

Sorry I tried that, doesn't make any difference.

I missed that you were using wireless when I first read your post. You are probably correct -- playing live TV generates a lot more network chatter than playing a previously recorded file so it is probably saturating your wireless connection.

[spyork]

I don't know if you did, but I'll say it anyway: You can not install 98.08 and then put back the gbpvr.db3 from version 97.13(or whatever).

I uninstalled gbpvr, but left the gbpvr.db3 in the directory when installing the new version. Wouldn't the installation upgrade the old database file?

[HtV]

I'm still having some problems with clientmode.
Doesn't really matter if I choose filesharing or clientmode.
If play a recording everything is fine, the wlan is used for about 12%=~6Mbps/sec
When I choose Livetv it stutters alot. So you would think the wlan is to slow. Strange thing is it won't use over 7-8%, I've tried all kinds of settings but nothing helps. Anybody an idea. Even stranger: last night it seemed to work better:confused: .

Looks a bit silly quoting yourself but anyway:
It seems that with the client set to streaming, livetv works quite well now.
probably the higher "<ClientModeCachedReadSize>65536</ClientModeCachedReadSize>"setting did the trick.