Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix dvbs2 #291

Closed
wants to merge 3 commits into from
Closed

Fix dvbs2 #291

wants to merge 3 commits into from

Conversation

oliv3r
Copy link
Contributor

@oliv3r oliv3r commented Aug 14, 2013

When not using auto-detect to find muxes, DVB-S2 gets skipped on load. This is due to the 5th field being incorrectly used as hierachy, when in fact, it is rolloff. Additionally, if it would have passed as such, the delivery system never gets set to DVB-S2.

Finally, in scan files, there is no such think as PSK_8, it's 8PSK.

When adding a DVB-S2 mux, the delsys field should be set accordingly.

Signed-off-by: Oliver Schinagl <oliver@schinagl.nl>
Scanfiles produced by hand or by w_scan set the constalation field as
8PSK, 16APSK or 32APSK, not as PSK_8, APSK_16 or APSK_32.

Because these strings appear to be used in other code and more
importantly current config files, keeping the old tables to not break
everybodies config.

Signed-off-by: Oliver Schinagl <oliver@schinagl.nl>
Currently, TV-Headend assumes that the 5th field is hierachy. This is
incorrect, the 5th field in a scanfile for DVB-S[2] is rolloff.

This patch adds support for rolloff on scan and sets it approperatly.

Signed-off-by: Oliver Schinagl <oliver@schinagl.nl>
@oliv3r
Copy link
Contributor Author

oliv3r commented Aug 20, 2013

Updated to keep backwards compatibility.

@adamsutton
Copy link
Contributor

Closing this, fixed in rewrite.

@adamsutton adamsutton closed this Oct 11, 2013
@oliv3r oliv3r deleted the fix_dvbs2 branch September 27, 2015 13:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants