Log in
Register
Menu
Log in
Register
Home
What's new
Latest activity
Authors
Forums
New posts
Search forums
What's new
New posts
Latest activity
Members
Current visitors
New posts
Search forums
Menu
Log in
Register
Install the app
Install
Forums
Linux Based Receivers
Dreambox Support Forum
New source to build your satellites.xml files
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="Huevos" data-source="post: 847218" data-attributes="member: 301161"><p>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.</p><p></p><p>hxxps://github.com/oe-alliance/oe-alliance-core/commits/master/recipes-multimedia/tuxbox/tuxbox-common/satellites.xml</p><p></p><p>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.</p></blockquote><p></p>
[QUOTE="Huevos, post: 847218, member: 301161"] 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. 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. [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
Linux Based Receivers
Dreambox Support Forum
New source to build your satellites.xml files
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.
Accept
Learn more…
Top