PVRPowerTray for GBPVR - enhanced GBPVR tray application

[reboot]

Rename gbpvrtray.exe to gbpvrtray.exe.old
Rename prvpowertray.exe to gbpvrtray.exe

[jksmurf]

The crash is occuring in the Cyberlink mux. Try a different version of this mux.

Paul K,

Probably completely unrelated, but I (also) had a "gbpvrrecordingservice.exe" crash with the ONLY :-( Mux that I can get to work with my (now first) Tuner (TVWalker Mini). I now also have a PVR-150MCE. Details of this particualr Mux issue are here in case anyone is searching:

http://forums.nextpvr.com/showthread.php?t=7722

I can not unfortunately try a different version of the Mux as Lifeview don't have one. Sub used the same one for testing even though it was from the (older) v2.27 drivers as my v2.28 ones.

Even Honest Technology's (who produce the Mux for Lifeview) own, and current, "TVR2" program has a Filter called HTMpegTimeshift.ax which has the same version number 1.0.0.1 and is the same size as the HTMpgMux.ax 112 KB (114,688 bytes) that Lifeview uses. Please HT make a new version soon ..... :-)

Why write all this? Hopefully someone else will benefit from the research, although at the moment it doesn't help much!

Cheers

k.

[reboot]

A new bug?
Every so often, for no apparent reason, PVRPowertray just quits.
It always happens at the end of a recording, but not every recording, after SA, comclean, and rename recordings have finished.
It only seems to happen on 2+ hour long recordings, but I haven't actually tested that.
When it quits, my preprocessing.bat doesn't work, so SA doesn't get run on new recordings.

[jimh]

A new bug?
Every so often, for no apparent reason, PVRPowertray just quits.
It always happens at the end of a recording, but not every recording, after SA, comclean, and rename recordings have finished.
It only seems to happen on 2+ hour long recordings, but I haven't actually tested that.
When it quits, my preprocessing.bat doesn't work, so SA doesn't get run on new recordings.

Hmm...that's the first I've heard about a problem like this.

If it's only happening on 2+ hour recordings, the only thing I can think of at the moment would be a problem with the "monitor file size" algorithm. Perhaps, when the recording file gets very large, there is an overflow of some type. If you have the monitor file size during recording option ON, please try turning it off and see whether the app. still dies on long recordings.

I will do my own testing to see if I can recreate the problem.

- Jim

[reboot]

I'll do that immediately, and let you know in 2+ hours

[jonmck]

ANy ideas on why it makes my recordings stutter? Without it running they are perfect. I really want this app to run - I formatted my HDD, reinstalled and am recording in DVR-MS.

Thanks

[jimh]

ANy ideas on why it makes my recordings stutter? Without it running they are perfect. I really want this app to run - I formatted my HDD, reinstalled and am recording in DVR-MS.

Thanks

PVR PowerTray really does nothing more than poll the gbpvr.mdb database every few seconds to check on the recording and pending status of programming. It will also check the file size of the recording file if you turn that option on. It does not mess with the GBPVR Recording Service, nor any codecs on your system.

I suppose if the polling activity puts too much of a load on your CPU, then perhaps the codecs you are using to capture your recordings may be dropping frames.

In the next week or two I hope to release an updated version that will allow those experiencing CPU load problems to alter the polling rate (it is currently fixed at every two seconds). Perhaps by lowering this rate, for example to once every 5 or 10 seconds, this problem will go away.

I do not record to DVR-MS so I don't know much about its CPU demands - perhaps if other people on this board who use DVR-MS and PVRPowerTray can report their success or failure, this would be helpful.

- Jim

[linfor]

Currently the listings are time arranged. I would like to be able to see them by tuner since I have to maually set the settop box (haven't gottent the Hauppauge remote to work well yet?

[bgowland]

I do not record to DVR-MS so I don't know much about its CPU demands - perhaps if other people on this board who use DVR-MS and PVRPowerTray can report their success or failure, this would be helpful.

Jim, I haven't tried your app. yet but I can tell you I currently have 3 recordings running - 2 on analogue cards (mpeg obviously) and one on Nova-t in dvr-ms format. CPU usage ranges from 4-10% - mostly floating around 6-8%. So it doesn't look like dvr-ms is particularly heavyweight.

This obviously depends on each system though - I have 2.4GHz P4, 1GB cheapo ram and SATA150 HD w/16MB cache. Others may see different results.

I'll install the app. later when the recordings have finished.

Cheers,
Brian

[gomjabar]

More of a wishlist thing than anything but have one of the options being "showanalyzer is running" in addition to comskip.