Better Logging and Identification of Tuners Used

[BrettB]

When troubleshooting problem recordings, etc., it is extremely helpful to know which tuner was being used. Therefore, I would love it if GBPVR would record the tuner ID somewhere (either in the database or even in a text/log file).

Also, it would be helpful if the GBPVRRecordingService.exe-native.log file's "checking signal stats" lines identified which tuner the stats correspond to.

[martint123]

It is a bit messy finding it, but AFAIK it is all there.

The tuner used is in the log file GBPVRRecordingService.exe-native.log

Code:

2010-02-19 16:40:00.140    INFO    BDARecorder:::StartRecording(VideoMate DVB-S DVBS Tuner, 1, J:\gbpvr\Relic Guardians of the Museum\Relic Guardians of the Museum_20100219_16451715.mpg, T:10847,V,22000,56~NID:32~ONID:2~TSID:2050~P:6940~V:5500~VTYPE:H264~A:5501~L:eng(AC3)~PMT:258~TXT:5503~PCR:5500~N:>BBC HD (AC3))

And the signal strength in GBPVRRecordingService.exe-native.log can be cross checked with GBPVRRecordingService.exe.log

Code:

GBPVRRecordingService.exe.log
2010-02-22 18:41:39.921    VERBOSE    [5]    Checking signal status on Hauppauge Nova-T-500 DVB-T (1):1
GBPVRRecordingService.exe-native.log
2010-02-19 18:41:40.031    VERBOSE    checking signal stats took total: 62ms (1,1,65,100).....(,0,0,0)

[BrettB]

It is a bit messy finding it, but AFAIK it is all there.

The tuner used is in the log file GBPVRRecordingService.exe-native.log

Code:

2010-02-19 16:40:00.140    INFO    BDARecorder:::StartRecording(VideoMate DVB-S DVBS Tuner, 1, J:\gbpvr\Relic Guardians of the Museum\Relic Guardians of the Museum_20100219_16451715.mpg, T:10847,V,22000,56~NID:32~ONID:2~TSID:2050~P:6940~V:5500~VTYPE:H264~A:5501~L:eng(AC3)~PMT:258~TXT:5503~PCR:5500~N:>BBC HD (AC3))

The problem with this solution is that the GBPVRRecordingService.exe-native.log files get rotated out fairly quickly. So if I don't try watching a recording for a week or two (typical), then I don't discover that there's a problem until long after the log file is gone.

And the signal strength in GBPVRRecordingService.exe-native.log can be cross checked with GBPVRRecordingService.exe.log

Code:

GBPVRRecordingService.exe.log
2010-02-22 18:41:39.921    VERBOSE    [5]    Checking signal status on Hauppauge Nova-T-500 DVB-T (1):1
GBPVRRecordingService.exe-native.log
2010-02-19 18:41:40.031    VERBOSE    checking signal stats took total: 62ms (1,1,65,100).....(,0,0,0)

This solution is OK as long as you only have 1 tuner being used at a time. But when I have all 4 tuners recording things at the same time, there is no way (at least not that I've been able to determine) to tell which "checking signal stats" line corresponds to which tuner.

[martint123]

(1) Sorry, I'm forgetting that I have a months worth of logs available from acronis daily incremental backups.

(2) Agreed, it would be nice to have at least the OID of the tuner in the signal logging line. I have found the timing of the signal check is very consistent and the few times I have needed it, with the 30 second intervals, it wasn't so bad identifying which tuner was which.

[JonnyCam]

(This comes from the paraled utility on the wiki)
This won't help with the signal stats.

You can create a batch file called recording-status.bat in the gbpvr folder.
In it have echo %1 %2 >> c:\recordings.txt

It will then list what each recording source was doing each time a recording starts.

(I can't rember if it has the date & time - but if not, add the lines as below)
Someone on here probably has a smarter way fo doing this, but it should work.
Note sure how to make it all appear on one line though.

Code:

date /t >> c:\recordings.txt
time / t >> c:\recordings.txt
echo %1 %2 >> c:\recordings.txt

[LewE]

When troubleshooting problem recordings, etc., it is extremely helpful to know which tuner was being used. Therefore, I would love it if GBPVR would record the tuner ID somewhere (either in the database or even in a text/log file).

I'm a bit late to this thread but if you use Firefox, the SQLite Manager add-on makes it very easy to view, and even edit, the GBPVR data base.

The Recording Schedule table has the indication (capture_source_oid) of which tuner is associated with each recording.

There are also other free standalone SQLite database managers/browsers available.