Jump to content


Internaut

Member Since 1 Dec 2020
Offline Last Active 19 Dec 2023 09:06
-----

Posts I've Made

In Topic: GigaBlue UE 4K Bug Report: Sporadic glitchy live video, "FBC automatic...

10 January 2022 - 00:36

This receiver is driving me insane...

 

I tested one more time... And now Tuner I was garbled...And Tuner J was working...

 

And then suddenly both Tuner I and Tuner J started working. Both now working fine. All the programs that reliably caused problems? Now running fine.

 

But I think I have seen enough. I have to decide soon whether I will send the receiver back, so I get my money back. I need two working MultiStream tuners, and this is useless for me.

 

It's sad, otherwise it would be a nice box.


In Topic: GigaBlue UE 4K Bug Report: Sporadic glitchy live video, "FBC automatic...

9 January 2022 - 20:18

If you have a unicable setup, and have configured A and B for a unique SCR, you have only two options for C to H: either FBC SCR, for which you have to assign a unique SCR to the virtual tuner as well, or FBC automatic, which will render the tuner inactive. In the first case tuner C will have its own SCR, in the second case it will not be used.

 

If you say "FBC automatic choses the wrong tuner", you have a configuration issue, because in a unicable setup, a tuner gets a single transponder. So either the second channel is on the same transponder, in which case the tuner can be reused (and no second is needed), or not, in which case a second tuner and second user band is needed. In neither of these scenario's, a virtual tuner is used.

 

If I zap to a channel, press Blue, Blue to open that channel in PiP, then zap again, the PiP uses tuner A, the main screen uses tuner B.

 

My FBC tuner is configured like this:

attachicon.gif1_0_19_283D_3FB_1_C00000_0_0_0_20220109162249.jpg

 

( as my Unicable switch only provides 6 User Bands per port ), tuners G and H are never used.

 

Fresh install of OpenPLI (and fresh GigaBlue install) work OK (as far as I can see same settings for Unicable LNBs).

 

OK behavior is this:

I watch program on Tuner A (Unicable). I select PiP program, and Tuner B (different Unicable channel) is used for PiP. All is fine - hurrah!

 

Buggy behavior is this:

I watch program on Tuner A (Unicable). I select PiP program, and Tuner C (same!!! Unicable channel as Tuner A) is attempted to be used for PiP. DOES NOT WORK


In Topic: GigaBlue UE 4K Bug Report: Sporadic glitchy live video, "FBC automatic...

9 January 2022 - 20:11

OK, this problem was resting on my mind, I could not wait till next week...

 

63% reception is just about 10dB, which is quite marginal for an FBC tuner, which are a lot less sensitive than single DVB-S tuners.

 

 

Have you tried an image with updated ( latest ) drivers.

 

Both good points!

 

First problem (garbled video on Tuner J)

 

I narrowed the first problem down (garbled video) - hurrah!

 

I can reproduce the problem both on OpenPLI and on (newest) original GigaBlue software (so problem is present in latest GigaBlue firmware/driver).

 

Signal strength is not the issue (tested with big and small antenna, and also switched cables).

 

It seems I can reliably reproduce garbled video ONLY on Tuner J.

(Tuner A, Tuner B, and Tuner I seem OK so far - I probably tested sometimes Tuner I, and sometimes Tuner J, that's why I could see the problem only sometimes... bah!).

 

I filed today a support request with GigaBlue for the first problem.

 

 

Second problem (Unicable with FBC Tuner A/C or FBC Tuner B/C)

 

Could not yet addressed the second problem (Unicable with FBC tuner). I could not reproduce the Unicable/FBC problem with fresh install of OpenPLI (fresh GigaBlue install also seems OK).

 

Seems like a imported config problem (config from my SF8008 Twin). Maybe. Maybe not.

 

Signal strength is not the issue.

 

Will see when I find time and energy for the second problem.


In Topic: Setting default Longitude/Latitude for rotor (instead of 005.100 East, 050.76...

9 January 2022 - 16:37


I am against this proposal.

 

I am not proposing anything at the moment. I am asking: What COULD be done in the situation I describe?

 

(I don't know: Is this hardcoded in some cpp? Is there a config I could change via telnet/ftp? Is there a quick fix for me? Is this something I could put in a script, or in a python file? Any suggestion are welcome!)


In Topic: Setting default Longitude/Latitude for rotor (instead of 005.100 East, 050.76...

9 January 2022 - 16:33

Internaut

Your request is very individual.

Even if you have to enter data four times, is that a lot?

I am against this proposal.

 

I have glitchy problems with my new receiver and OpenPLI. So I try to track down this problem (to write something here in the forum that someone here in the forum can investigate). So I install new OpenPlI. I install older OpenPLI. I try old settings. I try fresh settings. Again and again and again. Sometimes the problem is here, sometimes not, sometimes it comes later.

 

I have entered these coordinates about 30 times in the last two days. I forgot to enter it about 4 times, and wasted time until I realized what was wrong. It is really really really annoying.

(Also I have entered in the past these coordinates for both my Octagon receivers, both my Dreamboxes, and I had to reinstall OpenPLI more than once for those: So yeah, it is annoying.)