v0.97.9 (maintenance release)

[nightwalker]

Sub:

My test recording went well, i was able to view then delete it. went well.

One problem i'm having and it's a big one for me is the line you gave me to disable the mvp screensaver doesn't seem to work anymore.

<DisableHauppaugeMVPScreenSaver>true</DisableHauppaugeMVPScreenSaver>

I checked the config xml file and it was there, i even cut and pasted it in again but to no avail, that damn bouncing mpp logo is back.

please advise before the wife sees it back again.

[sub]

Hi,



I don't think that it has something to do with the Software Recorder plugin. Just installed 97.9 and external recording plugins (including SkyStar2 Recorder and DboxRecorder) do not appear in the drop down list of the "Edit/Add Recording Source screen" of the config app any more.

A previously configured recording source is working fine, but one has no oppurtunity to edit the capture source or add a new one.

I've attached the logfiles.

-alibert

Can you try the attached patch to see if it helps? I made a small change requested by normanr, which on the surface seemed like it wouldnt cause any problems, but I'm guessing it did.

[venkman]

PriorityRecording.exe is not running in 97.9. It works with 96.12 (from where I upgraded). It looks like PriorityRecordings is still looking at DotNet 1.1 while 97.9 is looking at 2.0 (I think). here are the errors:

Unhandled Exception: System.BadImageFormatException: The format of the file 'GBP
VRBackendCommon' is invalid.
File name: "GBPVRBackendCommon"
at RecordingUtils.Scheduler.schedulePrograms()
at PriorityRecording.RecordingManager.Main(String[] args)

=== Pre-bind state information ===
LOG: DisplayName = GBPVRBackendCommon, Version=1.0.2070.16814, Culture=neutral,
PublicKeyToken=null
(Fully-specified)
LOG: Appbase = E:\Program Files\gbpvr\
LOG: Initial PrivatePath = NULL
Calling assembly : RecordingUtils, Version=1.0.2203.39140, Culture=neutral, Publ
icKeyToken=null.
===

LOG: Policy not being applied to reference at this time (private, custom, partia
l, or location-based assembly bind).
LOG: Post-policy reference: GBPVRBackendCommon, Version=1.0.2070.16814, Culture=
neutral, PublicKeyToken=null
LOG: Attempting download of new URL file:///E:/Program Files/gbpvr/GBPVRBackendC
ommon.DLL.

[sub]

PriorityRecording.exe is not running in 97.9. It works with 96.12 (from where I upgraded). It looks like PriorityRecordings is still looking at DotNet 1.1 while 97.9 is looking at 2.0 (I think). here are the errors:

Unhandled Exception: System.BadImageFormatException: The format of the file 'GBP
VRBackendCommon' is invalid.
File name: "GBPVRBackendCommon"
at RecordingUtils.Scheduler.schedulePrograms()
at PriorityRecording.RecordingManager.Main(String[] args)

=== Pre-bind state information ===
LOG: DisplayName = GBPVRBackendCommon, Version=1.0.2070.16814, Culture=neutral,
PublicKeyToken=null
(Fully-specified)
LOG: Appbase = E:\Program Files\gbpvr\
LOG: Initial PrivatePath = NULL
Calling assembly : RecordingUtils, Version=1.0.2203.39140, Culture=neutral, Publ
icKeyToken=null.
===

LOG: Policy not being applied to reference at this time (private, custom, partia
l, or location-based assembly bind).
LOG: Post-policy reference: GBPVRBackendCommon, Version=1.0.2070.16814, Culture=
neutral, PublicKeyToken=null
LOG: Attempting download of new URL file:///E:/Program Files/gbpvr/GBPVRBackendC
ommon.DLL.

This isnt a GB-PVR bug. PriorityRecordings.exe needs to be updated for compatibility with .net 2.0. I'm sure this has already been discussed in the 'plugin and skin' support forum.

[crossnet]

Can you try the attached patch to see if it helps? I made a small change requested by normanr, which on the surface seemed like it wouldnt cause any problems, but I'm guessing it did.

That did it. Software Recorder 2.7 is working again. Thank you. emr

[Old Dog]

Sub:

My test recording went well, i was able to view then delete it. went well.

One problem i'm having and it's a big one for me is the line you gave me to disable the mvp screensaver doesn't seem to work anymore.

<DisableHauppaugeMVPScreenSaver>true</DisableHauppaugeMVPScreenSaver>

I checked the config xml file and it was there, i even cut and pasted it in again but to no avail, that damn bouncing mpp logo is back.

please advise before the wife sees it back again.

Use a blank transparent for the screensaver image.

[alibert]

Hi,

Can you try the attached patch to see if it helps? I made a small change requested by normanr, which on the surface seemed like it wouldnt cause any problems, but I'm guessing it did.

yes, the patch solves the problem. Thanks a lot once more for the quick response.

-alibert

[nightwalker]

Use a blank transparent for the screensaver image.

I can try, but it comes from the MVP itself as opposed to from GBpvr, I'll have to go take a look in the MVP directories and see what's there. Worth a try though.

[nightwalker]

Well, I've looking for the screensaver image from the MVP, not a lot of luck there. I've upgraded to version 3.0.24088. Stll no luck getting the Screensaver to shut off. Looking at the settings in the MVP software and the resulting data file it should be off and in the MVP application it is. As soon as I shut down Happ services and bring GBpvr back up I get the bouncing MediaMVP screensaver 60 seconds later. Even if i go in and set it to start at 90000 seconds (15minutes) it makes no difference 60 seconds and it's back.

I do get this line in the log every 5 to 10 seconds so i know it's trying, just not succeding.

6/5/2006 9:53:23 AM.656 VERBOSE [18] getValue cached value: /settings/DisableHauppaugeMVPScreenSaver : true

I have no idea how to get rid of it. I don't think i can at this point. I think i'm at Sub's mercy.

Help!

[b00sfuk]

Have not seen anybody else report this but since upgrading I'm seeing some wierd timings in my pending recordings. For example currently I have these 2 pending recordings times (different days):
22:00 23:00
22:00 23:00
If I then go to Ready recordings and play a recording, stop and return to Pending, the times have changed to:
22:00 23:01
21:58 23:00
If I restart the GUI they have reset to the correct times. This is repeatable. My first though was pre/post but that does not fit. Also I can schedule a program beforehand and it does not conflict and in fact corrects the recording. I use the Access d/b, no plugins and there does not seem to be anything in the logs.
Not a big issue but anybody else seen it?