Recording does not stop at end of show

[keith_leitch]

If someone can reproduce this with 1.3.11 and post the logs, I'll take another look.

Looking more closely at the 1.3.11 description, it seems that this would have a chance of fixing my problem, which seems to occur only during multiple recordings. However, I can't install this newest version, due to the installer "rolling back changes" as described here: http://forums.nextpvr.com/showthread.php...post318831 .

I have tried the download three times to no avail. Have you seen this problem before?

[sub]

Looking more closely at the 1.3.11 description, it seems that this would have a chance of fixing my problem, which seems to occur only during multiple recordings. However, I can't install this newest version, due to the installer "rolling back changes" as described here: http://forums.nextpvr.com/showthread.php...post318831 .

I have tried the download three times to no avail. Have you seen this problem before?

Sorry I'm no expert when it comes to diagnosing MSI installer problems. It works in strange and mysterious ways...

[carpeVideo]

Usually this means you are missing the required VC redistributable. It could also mean you need to do a complete uninstall (save your gbpvr.db3 because you can still copy it back in after the install.

[keith_leitch]

Usually this means you are missing the required VC redistributable. It could also mean you need to do a complete uninstall (save your gbpvr.db3 because you can still copy it back in after the install.

I had already followed advice found here: http://forums.nextpvr.com/showthread.php?t=3260

1.3.11 installed...but guess what? GraphRecorder no longer responds to it.

Sigh. This is a frigging full-time job.

[keith_leitch]

I had already followed advice found here: http://forums.nextpvr.com/showthread.php?t=3260

1.3.11 installed...but guess what? GraphRecorder no longer responds to it.

Sigh. This is a frigging full-time job.

Stranger, now. I reinstalled 1.3.07, and Graphrecorder still doesn't respond...just as though it isn't installed. I then copied my entire GBPVR folder structure (which I had backed up), but it still doesn't respond. Then, I tried a system restore...still no good.

Everything was fine this morning. Why do I upgrade?

Does anyone know why Graphrecorder might be ignoring recording service events?

[keith_leitch]

Stranger, now. I reinstalled 1.3.07, and Graphrecorder still doesn't respond...just as though it isn't installed. I then copied my entire GBPVR folder structure (which I had backed up), but it still doesn't respond. Then, I tried a system restore...still no good.

Everything was fine this morning. Why do I upgrade?

Does anyone know why Graphrecorder might be ignoring recording service events?

I've made some progress here, in a way. It turns out that Graphrecorder IS responding to recording service events, and probably always was. What threw me is that the executables are now running invisibly. Turning the "Hide" option on or off in the config makes no difference whatsoever.

This is causing me no end of problems, as I am using a program that needs another program to be visible in order to capture its stream. Also, the streamer plays very loudly when it is invisible, despite being muted otherwise.

This problem occurred when I installed version 1.3.11, and did not revert when i reinstalled 1.3.7 nor went back to an earlier restore point.

OK, problem solved, in this thread: http://forums.nextpvr.com/showthread.php?t=37457

It appears that the recording service resets itself to "invisible" after an installation. I don't know why mine was "visible" to begin with.

Now to reinstall my reinstallation. Determined to use the newest version!

[sub]

When the app is installed, the recording service runs in its own entirely seperate background session. You can go into the windows->control panel->administrative tools->services, then view the properties of the GBPVR Recording Service, and enable the 'allow service to interact with desktop'. Microsoft recommends against apps using this, so its not enabled in a normal install.

[terencedactyl]

This happened to me today with 1.3.11, but is slightly different to those already reported.
On a very few occasions in the past if I press the record button whilst watching live TV and then tell it to record until the end of the current show it doesn't stop unless the service is restarted. The shows are always watchable, may have recorded for 12 hours and I only have SD :-(.
Until today this had only happened when watching the last scheduled show of the day, so I stopped doing it.
Today it happened in the middle of the day and will check if I still have the logs (my m/c is set to start new every time) and upload if so, if not will try and recreate.

Terence

[sub]

I'd need to logs to have something to go on.

[keith_leitch]

If someone can reproduce this with 1.3.11 and post the logs, I'll take another look.

It took some effort and help from you guys, but I finally got 1.3.11 installed. Unfortunately, it did not solve the problem with simultaneous recordings, at least not entirely.

Attached are the logs that Sub requested. Here is a summary:

I set two simultaneous recordings. I deleted any buffering, so they were both set to record from 7:00 AM to 7:10 AM on 19-January-2009. The stations were in different tuners, so both queued normally. The first recording (station "SBS") started on schedule. There was no EPG entry for the second recording, so it queued as a manual recording ("KPIX"). However, it did not start and stayed in the "Pending" queue. Meanwhile, the "SBS" recording continued to record well after the stop time. Slimm-GBPVR reported it as having "-5 minutes" remaning, then "-6", etc. I attempted to cancel it from the guide and from the "Pending" list, to no avail. When it got to "-14" minutes remaining, I restarted the recording service, and this terminated the recording. The "KPIX" recording was already 14 minutes past its end time, so never started.

When I get home from work I am planning a partial workaround until a fix is available. I will put in a Windows scheduled task that checks Slimm's GBPVR-CLI app for recordings with negative amounts of time until they finish. If the task finds one, it will restart the recording service. If I create something helpful, I will post it here.

Otherwise, I think (but am not sure) that if the recordings don't have EXACTLY the same start time that things work better. I will experiment with this as well.