v0.94.8 (afternoon)

[Cape-City]

Does it do it every time you scan?

Yes, when i scan with the Version 93.10 everything is correct, when i scan
with the new version it has these strange caracters within it.

As i told, i had the same error in the version before 93.10 ...

[Cape-City]

A next thing i found out is, i created a special dvb-t.ini for only the channels in bremen (germany)

Code:

[TERTYPE]
1=Germany
2=Bremen

[DVB]
;Position = Channelname,Frequency(KHz),Inversion(0,1),0,Bandwidth (7MHz=1, 8MHz=2)

0=7
1=C22,482000,0,0,8
2=C29,538000,0,0,8
3=C32,562000,0,0,8
4=C42,642000,0,0,8
5=C45,666000,0,0,8
6=C49,698000,0,0,8
7=C55,746000,0,0,8

The 93.10 Version found everything with this and its more quicker, `coz he didnt have
to scan where nothing is to scan.
The newest Version only finds the channels when using the complete freq scan list ?!?

[smelcher]

Sub,

The biggest problem for me has always been the MVP screensaver that pops up after a minute. I noticed that in v0.94.8 you somehow got rid of the MVP screensaver or at least prevented it somehow. However, in the versions since then, the screensaver has come back. Do you have any idea why? Any idea on how I can prevent it? I know the latest version of MVP has screensaver settings but they dont seem to work for me.

Thanks,
Scott

[nightwalker]

The screensaver turn off function has been added in the 94.8 version. All you need to do is add this line to your config.xml

<DisableHauppaugeMVPScreenSaver>true</DisableHauppaugeMVPScreenSaver>

It worked like a charm and i haven't seen that blasted jumping happauge logo since

[AOSandman]

Installed v0.94.8 late last night (an upgrade from v0.93.10) and the recording service has now crashed for the second time (screen shot attached). I'm not sure of the exact timing of the crash, but as best I can tell, it crashed just as it was starting a new recording. Here's a brief snippet from the log:

9/15/2005 11:29:00 AM.088 INFO [35] Found new programme requiring recording: I Love Lucy
9/15/2005 11:29:00 AM.119 VERBOSE [35] Changing to channel (GBPVR.Backend.Common.NullTunerController): 60
9/15/2005 11:29:00 AM.119 VERBOSE [35] Requesting IRecordingSource to start recording: D:\PVR\Recordings\I Love Lucy\I Love Lucy_20050915_11301200.mpg
9/15/2005 11:29:00 AM.134 VERBOSE [35] DirectRecordingSource about to start recording oid:1 channel:60
9/15/2005 11:29:01 AM.431 VERBOSE [35] recording started
9/15/2005 11:29:01 AM.431 VERBOSE [35] Programme is now recording
9/15/2005 11:29:01 AM.431 VERBOSE [35] RecordingFactory.save()
9/15/2005 11:29:01 AM.447 VERBOSE [35] Save(): Updated existing scheduled recording
9/15/2005 11:29:01 AM.478 VERBOSE [35] getValue() loading new key/value into cache: /settings/ProcessCommercialsDuringRecording
9/15/2005 11:29:01 AM.478 VERBOSE [35] getValue: /settings/ProcessCommercialsDuringRecording : false
9/15/2005 11:29:01 AM.478 VERBOSE [35] Adding D:\PVR\Recordings\I Love Lucy\I Love Lucy_20050915_11301200.mpg to parallel processing queue
9/15/2005 11:29:01 AM.478 VERBOSE [35] RecordingFactory.getExtrasForGroup(1)
9/15/2005 11:29:01 AM.525 VERBOSE [2553] getValue() loading new key/value into cache: /settings/CommercialDetectionScheme
9/15/2005 11:29:01 AM.525 VERBOSE [2553] getValue: /settings/CommercialDetectionScheme : 0
9/15/2005 11:29:01 AM.525 INFO [2553] Parallel Processing thread starting...
9/15/2005 11:59:00 AM.026 INFO [35] Found new programme requiring recording: The Last Don
9/15/2005 11:59:00 AM.041 VERBOSE [35] Changing to channel (GBPVR.Backend.Common.NullTunerController): 29
9/15/2005 11:59:00 AM.057 VERBOSE [35] Requesting IRecordingSource to start recording: D:\PVR\Recordings\The Last Don\The Last Don_20050915_12001800.mpg
9/15/2005 11:59:00 AM.088 VERBOSE [35] DirectRecordingSource about to start recording oid:2 channel:29
9/15/2005 11:59:00 AM.088 VERBOSE [35] Stopping recording oid:2

Let me know if you need any other info...

[sub]

Can you post your GBPVRRecordingService.exe-native.log?

[AOSandman]

There seems to be a problem with season recordings. When I add a new season recording, it does not schedule the first occurance of that show, but WILL schedule future occurances. For example, "Threshold" premieres tomorrow night. So I go into TV Guide for tomorrow night, click on Threshold, & set it to record the season. Tomorrow night's episode is not scheduled, but next week's is. I believe this was introduced in 9310, but I've been out of the loop for awhile & was not able to post earlier. I've noticed in the RECORDING_SCHEDULE table of the db that newly added reoccurring recordings (type 5) now have a programme_oid listed. Could this be causing the new "don't record duplicates" feature to skip the first episode, thinking it's a duplicate?

[bigbus01]

Sub,

I have written to you about netradio in the past. In the latest version, it seems to be worse. When I go to netradio and click on a station, both my PC AND MVP go back to the main screen and I get a dialog box that tells me that the station definition could not be downloaded. About every 10th time I go to configuration and restart the server, netradio will work and it will work until something goes wrong and the mvp goes back to contacting server (which is quite often).

I also have problems with videos that I watch. When I hit stop or get to the end of the mpg, the MVP drops to the startup contacting server screen. Anytime the MVP gets interrupted, I lose netradio and sometimes I lose the audio completely and have to restart everything (which kills netradio). (My capture cards are ATI AIW cards and I use their software to record).

Any ideas, I love GBPVR and all of the plugins but I am considering giving it up for the old standard Hauppage software because these issues have been so frustrating. I have two servers and two MVPs and it acts exactly the same with all combinations.

Thanks for any help,

Bigbus

[AOSandman]

Can you post your GBPVRRecordingService.exe-native.log?

Attached.

Just as an FYI, the system had been rock solid since being rebuilt from scratch about 4 weeks ago. I changed absolutely nothing other than installing the new version.

[sub]

There seems to be a problem with season recordings. When I add a new season recording, it does not schedule the first occurance of that show, but WILL schedule future occurances. For example, "Threshold" premieres tomorrow night. So I go into TV Guide for tomorrow night, click on Threshold, & set it to record the season. Tomorrow night's episode is not scheduled, but next week's is. I believe this was introduced in 9310, but I've been out of the loop for awhile & was not able to post earlier. I've noticed in the RECORDING_SCHEDULE table of the db that newly added reoccurring recordings (type 5) now have a programme_oid listed. Could this be causing the new "don't record duplicates" feature to skip the first episode, thinking it's a duplicate?

Ah, right you are. Fixed for next release.