Help selecting a low cost receiver.

[moonbase]

double check if 8pks can in fact work with TBS drivers. So I am going to bed.....

I will save you the time, TBS drivers support scanning 8PSK, TBS drivers can also support blind scan.
These two points I confirm 100%.

Here is a picture that shows a TBS card using EBSPro to blind scan QPSK, 8PSK and 32APSK without any problem.
If you cannot get it to work then the problem is on your side, not TBS.

.

 

[cayoenrique]

@moonbase

...TBS drivers support scanning 8PSK, TBS drivers can also support blind scan...

8PSK most likely all DVB-S2, yes.
Blind-Scan In some models not ALL, Yes I am 100% agree with you.

Now for Qbox family TBS behave weird. For some TBS hide the models, no TBS-XXXX. if you ask a TBS agent in the past, he may tell you it is nor their product.
In the present you can not fine info in TBS-5920, it seems they refers it as QBOX II S2. And the driver as I posted show 2 models

"QBOX DVB-S2 BDA"= QBOXS2BDA.Device, USB\VID_734C&PID_5920
"QBOX DVB-S2 BDA"= QBOXS2BDA.Device, USB\VID_734C&PID_5928

The previous ones where the low cost devices.

Of the old ones there is a third one called "TBS5980 QBOX CI DVB-S2".
And this was the expensive one that they offered as capable of doing Blind-Scan and many other thing.

Now in my case the unit I received Never was capable of doing 8pks. But I admit that almost from the beginning I used cracycat mods to force the device to do FAST blind-scan.

I should stress that ALL receivers, if use with special programs can in fact do blind scan, An external program can try to tune to different frequencies, if it get Lock then it note a new transponder scan. But doing this in an external fashion can take LONGGGGG Time. Fast blind-scan is a feature that perform internally on the Tuner chip. Noe My TBS-5920 do have a chip STV0903 capable of doing internal blind-scan as pointed by mdkgr . But the TBS Official drivers where manipulated as to not allow it.... If you even try!! O guess all of us did, we end up with a Windows Critical Error that ends up in the so called Critical Blue Screen.

To resume what I said, TBS-5920 internal chop is capable of doing blid-scan, and it does with Prof7500 firmware or crazycat drivers, that I believe are in fact from Prof7500.
OLD/Original TBS OFFICIAL drivers from TBS will NOT allow TBS-5920 to do blind-scan.

Now the ONLY question I have, was a proposed by mdkgr, and is that, If I go back to Official TBS driver, Will I get better Signal so that my TBS-5920 can do 8psk?

And let me tell you, I seen in the past how different drivers do in fact show different Gain and RF Levels. But as I used my Qbox II for Satellite Dish alignment I did always used none official drivers.

I guess I will be installing a new Win7 in an old PC, and test the original TBS driver.


WOOPS I had become my own HiJacker, PLEASE remember if you have a Low cost receiver that you think I should consider, I like to know about that.

 

[EnoSat]

I guess I will be installing a new Win7 in an old PC, and test the original TBS driver.

Good idea

 

[cayoenrique]

@EnoSat

I have a last suggestion request from you. I know moonbase said there has to be a "compromise". But PLEASE ignore that for this last suggestion.
EnoSat the question is, what will be the suggested receiver if I want to receive all this none common Multi Protocol Encapsulations that you are so enthusiasts (DSM-CC).
See this will be by Top of the line. Then I see what I can compromise.

@all
I like to inform you that I spent 1 week without any real luck.
In general none of the windows drivers work for me now. For reasons I can not comprehend only crazycats drivers work for me in Windows!.

https://sourceforge.net/p/crazyscan/wiki/Info/  
http://crazycat69.narod.ru/sattelite/wip/CrazyBDA.zip

Any other driver will result in a Critical Error Windows Blue Screen. Just to let you understand, just opening any Sat program will crash, it has nothing to do with blind-scan or any spacial program. Just simple tune will make Windows crash.

Now this brought me to think a little and search for Original in Package CD Driver. And it was an interesting Experience!!
So as result I found out I been all wrong from the beginning. In various posts I have written that I started more or less in Satellite about 2015. And I thought that I did purchase the QBox2 around that time. Well that is half true. In 2015 I started to learn in deep Satellite protocols. But I was in Satellite long before as a user of official providers, In America that was Dishnetwork. So It turns out I may have purchase one of the original QBox2 models around maybe 2008-10. I said this because at that time I was using Windows XP and Windows 7 was some what new. The original package drivers where build with XP/Vista in mind. So the original drivers may not work for Win7.

In any case, I guess I will stop searching on improving my QBox instead going back at what I will purchase next.

 

[EnoSat]

One thing is what the input tuner can process, and the second thing is whether individual teams can incorporate it into their images, since most teams use a driver that was developed maybe 5-10 years ago. The best cooperation so far was with Availink support. In 3 days they solved the ShortFrameRate problem by updating the FW for the input tuner. Personally, I currently prefer EDISION OSmio 4K with the new FW (SFR support), unfortunately the new driver with direct T2MI support in this receiver is not as sensitive as the old without T2MI support (used mainly in the image for the US community). But that's everyone's business, what they prefer in their devices. As for DSM-CC in my region, it is not used much yet (maybe 10-15 percent of the total number of available signals).

 

[cayoenrique]

EnoSat
So only receiver you presented is EDISION OSmio 4K. I will look into it.

Now YOU have raise a very Important Issue. At least important to me.

One thing is what the input tuner can process, and the second thing is whether individual teams can incorporate it into their images..

Yes I want normal capabilities of official software in a receiver that has open sources.
I do not give importance to custom Images. Hopefully if a receiver have a custom Image it may also means there are opensources some where.

Unless you tell me you have found a Multi Protocol provider that is a most have. I do not need this as part of a standard part of an image. What I want is to be able to tune any of this special transponder and have the capability to Save a log and/or been able to sent the stream to one of my programs for further process.

Now this is a very interesting thing. You know we mention of receivers that in the process of blind-scan that they fail to lock. Well I wanted but never did to mention exactly this. That I believe that blind scan most likely work as intended in the original/official firmware. In other words that problems my arise only with new custom images not the original stock firmware.

 

[EnoSat]

Since something is added to the receivers for which they were not prepared at the time of design, it usually ends up in such a way that the other is impoverished at the expense of one.
In my case, for example, a driver without T2MI will also process SR-500, but a driver with T2MI support has a minimum SR of around 1200-1500 (officially, however, the manufacturer guarantees a minimum of SR-2000). Attention, I am not talking about blind-scan, where the parameters for capturing and processing an unknown signal are much stricter.

 

[cayoenrique]

Yes Yes I totally understand.

Like I said, most likely official software will have BEST or ALL options. As they intent to convince us to buy their product. It makes common sense.

I figure that I did also said previously something wrong, I said I did not have PCI-E on my PCs, and that is wrong. I saw the picture of the PCI-E that is flat with Main PC Board and that confuse me. By the way, I do not see that post any more. Nor I can find those special pcboards on TBS. Weird.

I really appreciate all those nice suggestion from all of you. I am studying my options. THANKS