-
Notifications
You must be signed in to change notification settings - Fork 137
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
GigaBlue UHD QUAD 4K blindscan not working with GIGA DVB-S2X NIM (TS3L10) #657
Comments
I can ask the new driver engineer |
Thanks, I should have also pointed out that the exception is from C-band blind-scan with the embedded FBC tuner.
Attempting any blind-scan with the add-on tuner never starts. That is what I need to debug. |
As far as I know there has never been binary support from the manufacturers for any FBC tuner, and that is assuming the hardware is even capable. |
It sometimes seems to work with the FBC tuner, perhaps because it is skipping it and going directly to the TS3L10? However, please ignore the FBC issue, I want to debug the GIGA DVB-S2X NIM (TS3L10) tuner, which is not FBC. How do I build the plug-in? I would like to only build the plug-in and not the entire STB image (if possible). A pointer to a URL describing the process is all that I require. A web search yielded confusing results. |
I would like to help with blind-scan, but I need build instructions first. I guess it is a closed community... :( |
You need nothing special if you want to debug the plugin because it’s python only. |
The blindscan plugin isn't working with the add-on tuner for the GigaBlue UHD QUAD 4K receiver. Note that this is on C-band as well as Ku-band. I am running OpenATV 7.1 (12/28/2022).
I am willing to debug it, but I am not sure how start? First I want to build the existing code and add some debug logging.
There is also the following exception when performing blindscan on C-band, I suspect that this is in the gigablue_blindscan driver:
Is the source for the GigaBlue driver available or is is proprietary?
The text was updated successfully, but these errors were encountered: