2009-10-06, 07:52 AM
This utility is for anyone who is having issues with the channel scanning reporting the wrong video PID or video type for channels found in the scan. It will only work on ATSC/QAM tuning strings and should not be used for DVB.
It can also be used to remove all encrypted channel entries from your scan cache.
Unzip the package to the folder of your choice. The recommended location is:
But it can be installed anywhere. The included System.Data.SQLite.dll is the same as the one in the GB-PVR 1.4.7 package but a copy must be in the same folder as the utility so I included it.
Usage:
Considerations:
Database entry fixes will only apply to capture sources that have a scan cache. If you used JavaWiz's BDA Channel Mapping tool to copy mappings, this tool will not work on the capture sources that did not have a scan performed. You can run the utility on the capture source that you scanned and then use the BDA Channel Mapping tool to propagate the entries to the other capture sources as you did before.
Only unencrypted entries are changed in the scan cache file.
Only database entries that correspond to scan cache entries are changed. If your channels were renamed using the Silicondust lineup server, you may need to remap them from the new scan cache entries. (I may provide a fix for this later.)
It can also be used to remove all encrypted channel entries from your scan cache.
Unzip the package to the folder of your choice. The recommended location is:
Code:
[GBPVR Program Folder]\Third Party\Tuning String Repair
Usage:
- GBPVR scanning should be performed before using the utility (it can't repair tuning strings that don't exist).
- Channels do not need to be mapped.
- If Config is running, exit the channel mapping screen before using the utility.
- Run the utility and select the capture source for which you wish to fix the tuning string information. (Only digital capture sources will be listed.)
- If you have already mapped channels for that capture source, select the "Fix database entries" option to avoid having to remap.
- Selecting "Remove encrypted channels" will clear all encrypted channels from the scan cache file to make mapping easier.
- Press the "Fix" button to apply the changes to the selected capture source.
- A popup will appear informing you of the number of changed entries in the scan cache file and in the database (if applicable).
- Restart the Recording Service. (If Config is running, the service will be restarted automatically when selecting "OK" to exit Config.)
Considerations:
Database entry fixes will only apply to capture sources that have a scan cache. If you used JavaWiz's BDA Channel Mapping tool to copy mappings, this tool will not work on the capture sources that did not have a scan performed. You can run the utility on the capture source that you scanned and then use the BDA Channel Mapping tool to propagate the entries to the other capture sources as you did before.
Only unencrypted entries are changed in the scan cache file.
Only database entries that correspond to scan cache entries are changed. If your channels were renamed using the Silicondust lineup server, you may need to remap them from the new scan cache entries. (I may provide a fix for this later.)