gbpvr.db3

[DanielP]

Is it possible to export a capture source and its channels from one database file and import it into a different installation of GBPVR?

The reason I ask is that I spend ages getting all the UK sat / freeview channels right on my downstairs media centre, then have to do the same thing upstairs. Recently, I have found that I can simply copying the whole database to the upstairs machine, which saves hours. However, soon I will be putting my 13/19E sources back in upstairs and this will make a simple database copy impossible.

If I could export the UK sat and freeview sources from downstairs and import them upstairs, I would be laughing!!

Daniel

[gEd]

might this do what you want?

WizBdaChannelTool

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

[mmatheny]

However, remember that apparently the scan-x.cache file holds info for all tuners, so if you map one tuner, and save it and then load that into the other tuner, if you go back into the 2nd tuner to map digital channels, it wants to scan for channels. BUT, this app works great - I just wish there was some way to print or save the data (with channel names) for future reference.

[JonnyCam]

However, remember that apparently the scan-x.cache file holds info for all tuners

I thought the cache file was numbered depending on the source number you were scanning?

[JavaWiz]

I just wish there was some way to print or save the data (with channel names) for future reference.

New version (v1.0.4.0) on the Wiki. When you save the mappings (Save Channels Tab), the mapping file (.chn) AND a report file (.txt) is now created.

[martint123]

I thought the cache file was numbered depending on the source number you were scanning?

It is. Each cache file only holds data for one tuner. But no data on any mappings is held there, that is only in the database.

[DanielP]

That looks great. I'll have a good play around with that.

Thanks for your help.

FYI- the scan cache is only a reference when mapping channels, all the mapped tunings are in the database file. The only thing I needed to do when copying the database file to a different install was alter the capture sources to point to the correct device drivers (I have different hardware on each machine).