GT Combo User Data Base

[Feralkiwi]

Hi All

I tested today with a reduced size data base.
I used the XML editor to remove the satellites I do not see.
I also removed all but four DVB-T options and all the ATSC and cable options.
Many of the DVB-T options are incorrect anyway, like the New Zealand one that is set for 6MHz(Europe standard) not 8MHz that is used here.

Note: I suggest leaving one of each, ACTS, Cable and DVB-T as when I when to ATSC it did not find a list and crashed out of the app.

After the first test I also moved the satellite I use the most and DVB-T to the top of the XML list using normal plain PC Notepad.

This makes channel change faster.
This makes DB export and import faster too.
I expect save after a scan is faster too.
Sadly my switching uses both DiSEqC 1.1 and 1.0 and this still needs twice transmission to switch (1.0 is sent first when 1.1 should be), so channel change is still limited by that timing.

Owen

[ghani Ajja]

Hi All

I tested today with a reduced size data base.
I used the XML editor to remove the satellites I do not see.
I also removed all but four DVB-T options and all the ATSC and cable options.
Many of the DVB-T options are incorrect anyway, like the New Zealand one that is set for 6MHz(Europe standard) not 8MHz that is used here.

Note: I suggest leaving one of each, ACTS, Cable and DVB-T as when I when to ATSC it did not find a list and crashed out of the app.

After the first test I also moved the satellite I use the most and DVB-T to the top of the XML list using normal plain PC Notepad.

This makes channel change faster.
This makes DB export and import faster too.
I expect save after a scan is faster too.
Sadly my switching uses both DiSEqC 1.1 and 1.0 and this still needs twice transmission to switch (1.0 is sent first when 1.1 should be), so channel change is still limited by that timing.

Owen

Thank you for your information.
Best Regards

[Feralkiwi]

Another fault is that the Latitude and Longitude are not reloaded correctly after a DB export / import.

The Latitude is replaced with the same value as the Longitude and the decimal places are removed and South is reset to North.

eg; set 123.4 east and 45.6 south and after reload you have 123.0 east and 123.0 north.

This will make USALS not work after reloading a DB, until you correct the lat / long.

Owen

[Tom.w]

hello

we will check it

[kladovchk]

Hi All

I tested today with a reduced size data base.
I used the XML editor to remove the satellites I do not see.
I also removed all but four DVB-T options and all the ATSC and cable options.
Many of the DVB-T options are incorrect anyway, like the New Zealand one that is set for 6MHz(Europe standard) not 8MHz that is used here.

Note: I suggest leaving one of each, ACTS, Cable and DVB-T as when I when to ATSC it did not find a list and crashed out of the app.

After the first test I also moved the satellite I use the most and DVB-T to the top of the XML list using normal plain PC Notepad.

This makes channel change faster.
This makes DB export and import faster too.
I expect save after a scan is faster too.
Sadly my switching uses both DiSEqC 1.1 and 1.0 and this still needs twice transmission to switch (1.0 is sent first when 1.1 should be), so channel change is still limited by that timing.

Owen

Feralkiwi, which program can download and edit the GT Combo database on a PC. Thanks.

[Feralkiwi]

Feralkiwi, which program can download and edit the GT Combo database on a PC. Thanks.

The editor is here.

Owen

[kladovchk]

Feralkiwi, which program can download and edit the GT Combo database on a PC. Thanks.

The editor is here.

Owen

Thanks.