Pros and cons of standalone FTA receivers vs. backend system with DVB-S2 tuners

Which do you prefer to use to receive Free-To-Air satellite TV?

  • Standalone Free-To-Air Receiver

    Votes: 17 53.1%
  • Computer running backend system with PCIe or USB satellite tuners

    Votes: 6 18.8%
  • Off-the-shelf backend system (TBS MOI, etc.)

    Votes: 0 0.0%
  • Something other than any of the above choices

    Votes: 5 15.6%
  • None of the above/Undecided

    Votes: 4 12.5%

  • Total voters
    32
Status
Please reply by conversation.

ancient

SatelliteGuys Pro
Original poster
May 12, 2014
419
217
USA
Has there ever been any serious discussion here about the pros and cons of buying a typical standalone receiver vs. running a satellite backend system using DVB-S2 tuner cards or USB-connected tuners? I'll start a list:

Standalone receivers:

PROS:
  • Not as expensive as a computer and tuners
  • No additional frontend systems required - you directly connect your HDTV
  • Generally easier to set up and configure
  • In some cases additional features such as blind scanning are included and are much easier to use
CONS:
  • Virtually every receiver out there has bugs in the software that cannot be fixed by the user
  • Users have no say over the software/firmware, you take what the manufacturer gives you (with rare exceptions)
  • Even if firmware updates are made available, those typically end once newer models are released, or after some finite period of time
  • Live programs and recordings can only be viewed on the TV connected to the receiver - typically there is no provision to stream to other devices on a local network (again with rare exceptions)
  • Few receivers will play 4:2:2 and other very high-bandwidth signals
  • As new formats appear it makes the receiver obsolete, so you may need to buy a new receiver to get all the channels even if your old one works perfectly fine. Even today many receivers will not receive all the available signals (DVB-S2 8PSK or 16PSK).
  • No EPG in North America
  • Far too many receivers do not have accurate clocks, which is a real problem if you are trying to use their PVR features - assuming they even have PVR capability in the first place
  • Many receivers have a nasty habit of simply locking up or otherwise going "out to lunch" at inopportune times
  • (This will be controversial but I will say it anyway) Once you buy a receiver, if you have problems you have to deal with they guy you bought it from. Some dealers are very good, and then there are others that seem to have Jekyll/Hyde personalities, and guess which shows up after they have your money?
Satellite backend systems:

PROS:
  • You can stream the received signals and recordings to frontend systems (and in some cases, directly to computers/tablets/phones) anywhere on your local network
  • If you encounter bugs it it somewhat more likely that the software developers will fix them - eventually.
  • You can have multiple tuners. I've heard apocryphal stories of people having sixteen tuners (four quad tuner cards) in a single system, though the most I've seen personally is six
  • Each tuner can record multiple channels from the same transport stream at the same time, so depending on the throughput limits of the hardware you could be recording from several sources at once
  • If you are really good with hardware and software you can fix your own bugs, or even design your own backend system from the ground up
  • If new formats become available you may only need to buy a new card that support the new formats, not scrap the entire system
  • Generally speaking, the backend will stream or record any unencrypted (in the clear) signal that the card can receive, including bandwidth-intensive formats. If the frontend device has good enough hardware to play it, you can watch it - or after it's recorded, you can use an external program to convert it to a different format that is a bit less resource hungry
  • The computer gets its time from an Internet time source (NTP server) so its clock is always right
  • Much rarer for such a system to totally lock up or stop working, though it's not unheard of. But if that happens and it's not a hardware issue, it can probably be fixed by changing or upgrading software
  • Although it's not an easy thing to set up, it's possible to actually have an EPG that shows what's coming up, though probably not for every channel you can receive
CONS:
  • Typically quite a bit more expensive than a standalone receiver, though this could change
  • These systems can be much more difficult to set up and configure than a standalone receiver
  • If it stops working or doesn't work properly, it's up to you to figure out what the problem is and fix it. For better or worse, you can't dump the problem in the lap of a dealer
  • To play content on a TV you generally need to connect a computer or device running frontend software, which in many cases could be XBMC with an appropriate PVR addon. That also implies that you can stream directly to a computer, tablet, phone, or other device that can run XBMC or other frontend software
  • There is generally no compression of the signal, therefore any recordings made can be huge, depending on the source
  • Those familiar with Windows can use MediaPortal as the backend software but you may encounter a lot of bugs, particularly if you attempt to use DiSEqC or tone switches
  • Those more familiar with Linux can use TVHeadEnd as the backend software, although you have to use the newest unstable versions to get the best hardware support. Which of course means that things might break if/when you upgrade. TVHeadEnd is also a bit non-intuitive until you get the hang of it
  • If you have problems setting up such a system it is often difficult to get assistance. Linux guys in particular seem to have this attitude that you should learn all about Linux and fix your own problems, even though that's not entirely a realistic attitude in these days of user-friendly distributions such as Ubuntu. The attitude toward users in the Linux world is totally different from that in the Windows world
  • Under Linux you may need to manually compile the drivers for your tuner card(s), which although not exceedingly difficult, can be a somewhat daunting task for new Linux users. And worse yet, every time Linux pushes out a new kernel upgrade, which they do rather frequently, and you install it, you may need to recompile the drivers again
  • There are other software choices on both platforms but as far as I can tell none of them have the degree of support or the number of users as the ones I have mentioned above
  • Sometimes the software is designed for free-to-air in other parts of the world and needs adjustments to work in the USA. This is one of the major problems with MediaPortal, which is very Euro-centric
  • If it is possible to do blind scanning at all you will probably need to install a separate program, and even then you may have problems if the software was designed to operate in an environment different than yours, such as a specific custom Linux build. And such software will not automatically map the found channels into your backend program
  • Most of the instructions that are out there for building such system suck, IMHO. They were apparently written by programmers and tend to be way too heavy on the mundane technical details, and light on the questions first-time users are most concerned with, such as "What do I need to do to get this thing to work?"
  • While you can use multiple tuner cards, there may be limitations on the type or number of tuner cards that can be used, that are imposed by the software and/or operating system. For example, in Windows you may not be able to use two or more of the same model card because the Windows drivers won't support it, though that may depend on the brand of card used
  • Just as receiver manufacturers stop supporting older receiver models, tuner manufacturers may stop issuing driver updates for older cards - or sometimes even for current cards that are still being sold. This could be a potential problem if you ever update your operating system
  • Some backend software that works great with OTA tuners (such as the HDHomeRun) may not work very well, or at all, with satellite tuners
Some of the above is from personal experience and some is deduced from threads I have read in various satellite forums. In the end, I think most people who have more than one TV in their home, or that would like to record more than one program at the same time, would be a lot happier with the satellite backend system provided they can get it to work without it becoming the bane of their existence. Sadly, at the present time there are no turnkey backend systems that "just work" with satellite TV tuners, unless perhaps you are looking at a dedicated device such as one of the ones TBS manufactures, and I think even those require configuration of the backend software by the user.

If you think I am wrong about any of the above points or want to add your own, that's the reason I started this thread. I may not have much to add to the above but I would be interested to see what others think.
 
To me the best solution is using a stb for most programming, but having a slaved usb tuner for when there is something 4:2:2 to watch. It is much cheaper than an azbox (if you can find one) and allows decryption of all signals currently available including H264 4:2:2. It is hard to beat the reliability and ease of use of a stb for most viewing and blindscanning, but occasionally I need a usb receiver for some feeds. I would love to see a stb come out that was affordable and played all formats, but am not holding my breath.
 
  • Like
Reactions: N6BY
Thanks for starting this thread, 'ancient', I am very interested in purchasing a satellite backend system. I agree with your pros and cons of standalone receivers. But I don't know enough yet about satellite backend systems yet to comment on that, and I find your post #1 here to be an outstanding starting point for me in my research.

I too am very frustrated by the bugs and clunky interfaces of most existing standalone receivers -- especially because I make a living developing and selling software and would be thrilled at the chance to improve upon / replace existing interfaces. In addition, I have several ideas in mind for some very nice features for feed hunting and ease of use. With a programmable DVB-S2 tuner there is a lot of potential to create a powerful and flexible system.

I recently obtained obtained my Ham 'Extra' license because the exam material covered much of the material I need to know to work with SDR (software defined radio), digital transmission modes, and radio electronics. I have worked with Ham radio since 1998, off and on. Anyway, I am studying the possibility of using my USRP B200 SDR to process DVB-S2 and convert it to ATSC or QAM.

'Ancient', which DVB-S2 tuner would you recommend that I start with? Also, is there an existing DVB-S2 tuner with both user programmability and ATSC or QAM output?
 
  • Like
Reactions: ZandarKoad
I use DVB cards. Three kinds of cards. DVB(S)atellite DVB(C)able DVB(T)errestrial aka ATSC. Havn't seen any combo cards, but that would be redundant. I use MyTheatre with TeVii DVBS2 and a Hauppauge ATSC tuners. Prof or TBS make some good tuners. But they don't work with MyTheatre. The trick is to find a software/hardware combo you like. Or write your own. :)
 
I use DVB cards. Three kinds of cards. DVB(S)atellite DVB(C)able DVB(T)errestrial aka ATSC.

I need to clarify something here. DVB-T (and now, also T2) has a well-defined meaning in the world outside of North America, and it's not ATSC. ATSC may use DVB packetization (or whatever the correct word is), but the modulation is completely different. So if you're buying a card to use for terrestrial TV in North America, make sure it says ATSC and not DVB-T. (I would not be surprised if a similar situation prevailed for cable, but the point is probably moot as cable systems are moving toward 100% encryption.)
 
Good point Jim S. They are similar in that I can use DVBT or ATSC settings in MyTheatre with my ATSC tuner and tune my OTA channels. The DVBT 6m range is real close to the ATSC frequencies and the locals here match up.
 
I am very interested in setting up a backend system, I have the house wired with cat6 and TVs have network capability. My next satellite reception investment will likely be a card. Have a fast computer with linux Fedora currently installed but will likely change to something lighter for this endevour. Been playing with various forms of unix and linux for many years. A good boxing day deal might cause this to occur soon. My AzBox receivers are getting old and there is nothing to replace them with.
 
I have bought 5 STBs this year. None of them do 100% of what i want. Some have the features, but are so bug infested it cancels out the features. I want an DVBs2 system that i can watch 4:2:2 signals, watch on TV, and stream to any network system, ie Windows,Android,Mac etc.

AmikoHDSE - Won't play 4:2:2 . So far, it appears i can only stream to Android. It would be great if i could stream to my computer up stairs that i have on my night stand.

AZboxMiniMe - Plays 4:2:2 and can stream to any system. It has a webportal and then can switch channels and stream your video. So, i could watch full screen on my laptop upstairs on my VLC media player. Awesome. Problem - Box corrupts SO OFTEN, it renders the box unreliable as a functional system.

I don't own the Amiko A3, but it doesn't yet do 4:2:2 and i don't know about streaming to non android devices.

My Dream setup would be the following :

A Linux/Android based mini box that has 2-3 PCIe express slots to handle independent tuner cards.
The minibox support both an IR and FlyMouse Remote. The mini box has usb / network and hdmi ports. The mini box has XMBC on it to handle LAN media. Has built in Satellite software to control your tuner cards. Say one for DVBs2 and one for ATSC. It might be a better method for the satellite software to not actually play the tv channel your on, but stream it. Whether your calling it from another PC, Android system or what ever. Even internally, then that way you could choose to install any linux/android based media player that plays raw streams. That way, you could pick the best media player out there that would handle all the different stream types. 4:2:2 etc. So, basically, the satellite software would handle everything but the actual playing of the media. The way to go might be that the satellite software is 100% controls through http and when you click a channel, it starts the stream.
 
AmikoHDSE - Won't play 4:2:2 . So far, it appears i can only stream to Android
Didn't know where to put this question, but have been thinking about it for some time.
Has anyone emulated android in windoze, or Linux, and installed the amiko app with success???
 
I recently obtained obtained my Ham 'Extra' license because the exam material covered much of the material I need to know to work with SDR (software defined radio), digital transmission modes, and radio electronics. I have worked with Ham radio since 1998, off and on. Anyway, I am studying the possibility of using my USRP B200 SDR to process DVB-S2 and convert it to ATSC or QAM.

'Ancient', which DVB-S2 tuner would you recommend that I start with? Also, is there an existing DVB-S2 tuner with both user programmability and ATSC or QAM output?
Given your level of experience and expertise, I am probably not the best person to ask about this, because you probably have far more overall knowledge than I do.

I've had good luck with a TBS6985 DVB-S2 Quad Tuner PCIe Card but I only used that because I saw that others have had success with it. There may be better cards out there but I just don't know about them. One thing to be aware of is that there are a number of cards that are widely available in Europe that for whatever reason are not marketed in the USA.

I don't know what you mean by "user programmability" but I'm guessing the answer is no. In some cases alternative open source drivers are available, but given my almost nonexistent comfort level in Linux I have not used anything other than the official TBS drivers, which for me have worked pretty well. I suppose if you are really good at coding you might be able to modify the drivers to add certain specific features, as I believe others have done.

As far as I am aware, there is no such thing as a single card with both DVB-S2 and ATSC tuners. As others have mentioned there are cards that support both DVB-S2 and the European TV standards (DVB-T or DVB-C) but those OTA tuners are useless here. By the way, there are DVB-S2 tuners with conditional access card slots and while those tuners will work to receive unencrypted DVB-S2 signals, as far as I know the card slots are useless in this part of the world because they will not accept cards from Dish/Direct/Bell/Shaw (if I am wrong about that, I am sure someone will correct me). But, again as far as I know, there is nothing to stop you from having a separate ATSC tuner card, as long as you have sufficient card slots and you pick a card that is compatible with the backend software you are using. Sorry that I don't have better knowledge of the subject so I could answer your questions with more certainty.
 
Didn't know where to put this question, but have been thinking about it for some time.
Has anyone emulated android in windoze, or Linux, and installed the amiko app with success???

Actually i tried last night. There are some articles out how you can install Chrome browser and then install a few extensions that then allow you to run Android apps on Windows. I spent many hours on it and ran into a dead end. I gave for the time being.
 
  • Like
Reactions: FaT Air
I might try to install the Chrome web browser in the Linux distro I am currently using just for fun... Will look for extensions and apps... which apps would be the ones to try? Since Android is closer to Linux (or derivative) it might have a better chance of working.
Have to do web page updates for some groups I host web pages for... Hopefully I can get that all running and tested tonight and have time to play.
 
  • Like
Reactions: northgeorgia
...

I don't know what you mean by "user programmability" but I'm guessing the answer is no. In some cases alternative open source drivers are available, but given my almost nonexistent comfort level in Linux I have not used anything other than the official TBS drivers, which for me have worked pretty well. I suppose if you are really good at coding you might be able to modify the drivers to add certain specific features, as I believe others have done.
I should have said "open source" software, available to programmers for study and modification.

...
As far as I am aware, there is no such thing as a single card with both DVB-S2 and ATSC tuners. ...
Just to clarify, I was wondering about the existence of a card which takes DVB-S2 input (from an LNB), and produces ATSC output. That would make the DVB-S2 card extremely versatile -- with the ability to use the ATSC output as input to, say for example, a TiVo DVR, an HDTV, and all other devices that accept ATSC input. This would make the TiVo, or whatever device think that the DVB-S2 converted to ATSC was just a regular TV channel.

I doubt if such a card with ATSC output exists. However, I am pretty sure that it can be done with software defined radio cards, such as the USRP B200. But it would take a lot of work to implement.

Anyway, this is a great thread and it seems that there is a consensus among us that we are frustrated with the bugs and missing capabilities of existing standalone satellite receivers.
 
Just to clarify, I was wondering about the existence of a card which takes DVB-S2 input (from an LNB), and produces ATSC output.

I would think that would be a very expensive card, as I believe it would have to, on the fly, re-encode the signals to the codec that is expected in an ATSC signal.

From WIKI :
The ATSC A/53 standard used in the United States, uses MPEG-2 video at the Main Profile @ High Level (MP@HL), with additional restrictions such as the maximum bitrate of 19.4 Mbit/s for broadcast television and 38.8 Mbit/s for cable television, 4:2:0 chroma subsampling format, and mandatory colorimetry information.

I don't believe that would allow DVBs2 and other signal types to translate to ATSC. I might be wrong.
 
I don't own the Amiko A3, but it doesn't yet do 4:2:2 and i don't know about streaming to non android devices.

It streams to a VLC browser plugin -- but there's a catch. It doesn't use the normal VLC plugin, but something called FireBreath. I'm not sure what that is, because I haven't had time to research it much. It sounds like it's supposed to be some sort of wrapper system for plugins, but I have NO idea why they deemed it necessary, because the previous Amiko models used the VLC plugin directly! It has binaries for Windows and Apple, and I think the source is available but I don't know if anyone's compiled it for Linux or whether it would install if it would. Very stupid decision on the Amiko developers' part.
 
Has anyone emulated android in windoze, or Linux, and installed the amiko app with success???

On another board, someone tried running a commercial Android emulator (I don't remember the name of it) on Windows, and the Amiko Big2Small app failed because it uses "ARM native code." I thought that most Android emulators were supposed to have ARM-to-X86 translation built in, so I assume they must mean that it's accessing the hardware directly rather than using the Android API. I thought that doing that sort of thing in a userspace program stopped decades ago...
 
I have NO idea why they deemed it necessary, because the previous Amiko models used the VLC plugin directly!

By chance, would that include the Amiko HDSE? Can i stream to VLC with it? I didn't think so being we are all trying to run big2small Android on a windows system.
 
No, sorry, I meant the Alien and Alien2.
 
Can i stream to VLC with it? I didn't think so being we are all trying to run big2small Android on a windows system.
What I don't understand, is why lock out all other OS's, in favor of android? VLC has been my media player, of choice, since Win98. I can only think of one reason VLC can't play it - a closed source, proprietary, codec.
Think, but not sure, the B2S app also lets you control the receiver from your android device.
That could also be be done via http if the developers would develop that capability. But then it would also be OS friendly, but it seems they are in favor of only supporting android.
Since android is, I think I have this right, Linux on arm architecture, I would think 'emulation' would be a piece of cake in Linux on 32 or 64 bit architecture.

I got 6 different 'flavors ' of windoze(3) and Linu:mad:3) OS's running on different laptops and desktops. I'm not interested in adding another, especially just to stream,basically, one 'thing'.

My mobile phone is a MOBILE TELEPHONE. No games or internet. Text msgs are very low on the priority list. ( My list and the carriers list. I've had test msgs 'appear' 3 to 4 days after they were sent.) I got better things to do with my time. If it's an emergency, call, don't text.
Not interested in getting a 'more featured' type just for this. Not worth the cost as they wouldn't be used.
STOP_ Turning into a RANT. OK -
BaDee BaDee BaDee, that's all folks.
 
Last edited:
Status
Please reply by conversation.

Users Who Are Viewing This Thread (Total: 0, Members: 0, Guests: 0)

Who Read This Thread (Total Members: 2)

Latest posts