Exposing what GBPVR is doing

[liteswap]

How about dumping the details of what GBPVR is doing into a text file at the start and end of each recording and playback operation? It could go into a special directory that external apps could check and pick up on.

For example, what I'd do with that info is pump those details into the front display on my media PC using AutoIt and LCD Smartie, as I'm not a C programmer nor ever likely to make the effort to become one.

[McBainUK]

iMONVFD is a plugin that displays GBPVR information directly to the iMONVFD. Additionally, the data can be written to a text file which can be read by other LCD programs such as LCDSmartie.

iMONVFD is a plugin that gets information from GBPVR such as currently playing video file, livetv channel, audio file, and recording and either displays this information on the 2x16 iMONVFD or writes this information to a text file. There are many custom config settings including the default display, scroll speed and characteristics. iMONVFD also monitors disk space on the hard drive you specify and uses the VFD to warn when the space is below a user specified threshold.

http://gbpvr.com/pmwiki/pmwiki.php/Utility/IMONVFD

[dennit]

How about dumping the details of what GBPVR is doing into a text file at the start and end of each recording and playback operation? It could go into a special directory that external apps could check and pick up on.

You can pick up the start and end of each recording with parallel/postprocessing.bat. Log files can be parsed for playback info.

[zehd]

You could just parse the log file. The different log files have more than enough info. Just open the txt file, shoot to the end read and close --- very often!

[liteswap]

Thanks for the heads-up, fellow users! Yes, I have iMonVFD but the info you get from it is limited. The logfile route looks more promising. Not sure why I didn't think of that.

This may be the start of a new little utility....

[JonnyCam]

also try taking a look at slimm GBPVR, it has a program called slimmCLI which exposes quite a bit of info.
You can write the batch files to put that out to a text file.

Or you can also use the EWA RSS feeds to show all recording type things, not sure if it can tell you what tuner it's recording on though.

[liteswap]

Jonny - many thanks for that tip. Looks like Mr Slimm's work will save me (and the PC!) a lot of duplicated logfile parsing.