Huevos
Satellite Freak
- Joined
- Sep 11, 2008
- Messages
- 6,036
- Reaction score
- 1,273
- Points
- 113
- My Satellite Setup
- 57E to 58W, C-band and Ku, DVB-S2, 4:2:2 and blindscan.
- My Location
- 38.5ºN, 0.5ºW
Weekly seems reasonable to me. If you look at OpenViX on GitHub you can see the weekly commits on there. That file is active transponders and contains about 4000 entries. Typical changes for a week are 40 additions and 40 deletions. Many are minor changes and the majority are in C-band.RimaNTSS said:Question to author of this great product: How often you update database? And second question: On 36.0E Eutelsat 36A/36B there are circular and linear transponders, basically similar to C and Ku band they should be received with separate LNBs. How can I better make separation between Circular and Linear transponders?
hxxps://github.com/oe-alliance/oe-alliance-core/commits/master/recipes-multimedia/tuxbox/tuxbox-common/satellites.xml
Circular and Linear transponders: only a problem when the satellite is mixed. Most people in western Europe running Ku band are not within range of a circular polarised footprint so to be honest I thought it just wasn't worth the bother to code this. And then for C-band everyone is doing something different (some take the plate in and out, others run 2 LNBs, etc) and anyway the majority of sats don't run mixed polarisation (at least not for the same audience), so it has been left to the user to edit these few cases by hand to 2 positions. But 2 positions and USALS aren't compatible anyway. So if you wanted to use USALS for the offset LNB you would need to know the position of the second LNB before you edit the satellites.xml file so the dish stopped at the right place, and this would be unique to every setup.