Tvheadend versus MythTV [pdl-inc.info]
MythTV operates in a client-server mode; the server (or "backend") is the device that actually has the DVBs. The clients ("frontends") run the GUI. It requires a configuration file identifying the server and the clients and the spatial relationships between the screens (i.e., which screen is next. Remotely service content to multiple clients from a central server. . ter/slave relationship is established in an abstracted layer that operates between the.
You can ssh into your Mythbox, but since synergyc communicates with the X server to simulate key presses and mouse events, you need proper authorization to do so. I have removed the old. I wonder if some update changed this behavior, or if I just somehow missed that I was already in that group and thought I had to add myself when I first tried this. The latter doesn't seem too likely as I distinctly recall running the xhost program to figure out the correct syntax to add myself to the list of authorized clients.
Anyway, this section X Server Setup may be superfluous now. Here is one way to gain proper authorization. There are probably others.
mysql - Mythbuntu database fail in backend Mythtv to upgrade - Ask Ubuntu
Consulting the user guide is helpful, though, particularly for making sense out of all of the configuration minutiae. After configuring program reception, the next most critical setup task is getting EPG information. In my test, this was TVH's weakest point by far. Although the program supports an array of EPG sources, none of them worked for over-the-air broadcast in the US. Worse, the relevant chapter in the manual is filled with empty sections and the forums are filled with frustrated users asking the same questions and getting no solutions.
Eventually, I tracked down an external blog post that pointed toward a solution; sadly, the solution is an ugly workaround for what is apparently TVH's broken support for the XMLTV guide-data grabber.
It seems, however, that users in DVB regions of the globe have a much easier time with this step. With EPG data in place, one can schedule single or recurring recordings from within the web interface. The UI for doing so is not sophisticated; there is a long list of programs in a spreadsheet-style list XMLTV grabs two weeks' worth of EPG data at a time and one can search or filter it on a number of fields episode titles, service, content tags, etc.
The giant list of programs is less user-friendly than the classic "TV Guide" grid, but at least the search and filter functions are easy to use—which cannot be said for MythTV, where searching and filtering features are split into several sections placed rather far apart from each other in the configuration-screen hierarchy.
As for recordings themselves, TVH does little to nothing with them after they are saved to disk; the intent is that users will access their content through another front-end like Kodi.
On the plus side, this makes managing content easier in some respects: In contrast, MythTV relies on a background process that schedules deletions using a lengthy list of overlapping criteria. TVH also allows complete freedom in where individual recordings are stored and how the files are named; MythTV provides neither feature.
The late night wars Setup and configuration is the hardest part of using MythTV. For starters, MythTV's back-end process which handles EPG and scheduling recordings can only be configured through a GUI application, making it a poor fit for headless systems. More importantly, though, that configuration tool uses a mix of keyboard-only commands that are hard to discover and onscreen elements that can only be accessed with a mouse.
Many of the settings must be altered by stepping sequentially through a lengthy series of screens at times, ten or more. And the interface itself is not the only awkward factor: To give one brief example, the decision of which tuner should be used to record a particular program e.
Client–server model - Wikipedia
How exactly they interact is one of the project's enduring mysteries. On that type of issue, TVH is far ahead of the competition. The desired documentation is clearly missing in places, but setup is certainly simpler and better organized than MythTV's.
For that matter, they could add a third HDHomeRun and antenna to pick up the stations from Hamilton, Ontario, or they could try aiming an antenna halfway between Toronto and Hamilton and connect that to a single HDHomeRun, and hope for the best.
But since a TV can already receive signals from an antenna, that may not by itself be too useful. Oh, and by the way, if someone has told you that it is no longer possible to use an antenna to pick up signals now that television has gone digital, there is no polite way to say this: They flat-out LIED to you.
There are two components to MythTV, a backend and a one or more frontends. You can almost think of the backend and frontend as two separate programs that are installed as part of the same package. The frontends depend on having access to a backend. One web page server can serve pages to many web browsers, but a web browser is useless if there are no web servers. In the same way, you can have many MythTV frontends on a local network, but they need to be able to connect to a MythTV backend somewhere on the network.
The backend is what actually receives the signal from any connected tuners, such as the previously-mentioned HDHomeRun Dual. If the signal is being recorded, it is the backend that stores the recorded program to a storage device.
It is the backend that actually runs the schedules that record programs. The backend also can receive program guide information, which is then made available to the frontend clients. It also allows you to access the schedule information on the back end, and schedule the recording of future programs.
There is actually a LOT more that both the backend and frontend can do — MythTV is a VERY capable program — but this is simply a high-altitude overview of how the two components relate to each other.
What many MythTV users might not realize is that the MythTV backend offers a web interface called MythWeb that allows you to schedule programs, and do much more, from a web browser on your local network.
One thing it offers is the ability to download files of recorded content.
For example, if all you ever want to do is record shows off the air so you can view them later on your phone or tablet, you can do that by running the backend only, and interacting with it solely via the MythWeb interface.
If you also want to use it as a frontend, then the requirements are probably a bit more stringent. So maybe the requirements are even lower than what we believe. A few months ago, we mentioned where you could find A complete guide for setting up MythTV from start to finish plus a few other helpful links, and we also told you How to get free TV schedule information for MythTV. The FCC says so disclaimer: But, not all landlords recognize that federal law allows this, so you may need to pick your battles.
And, you do not have the right to place an antenna in an area you do not control, such as the roof of your apartment building. Put a dish or antenna on your apartment balcony. If you own a home but it is in a development that has deed or covenant restrictions that forbid you from erecting an antenna, we first of all will say that you were very dumb to buy into such a development but, you probably already realize that!
For example, with a little ingenuity it might be possible to hide a flat antenna underneath vinyl siding, though obviously such mounting would make it difficult to point the antenna at the stations you want to receive.
Some people have disguised antennas as a piece of deck furniture, or even as an artistic item. Sometimes you can place a small indoor antenna such as one of the Mohu Leaf or Terk indoor HDTV antennas in a window or on a wall and get adequate reception some people have found that less expensive models such as those offered by Homeworx will do the job, but read the reviews before purchasing any indoor antenna.
Well, think about what we said earlier about having have a close family member or good friend, or better yet, another property that you own or control, in a strong reception area. There is an issue with that, though. Quite simply, the recordings are HUGE! For example, we recorded a high definition half hour newscast and the resulting file size was 3.
And while MythTV has a built-in transcoding option, that is more for changing the container format than shrinking the file size. So, you may want to figure out some way to compress the video prior to downloading it possibly using ffmpeg or HandBrakeCLIor maybe you know of something even better.
Then you can upload or download the compressed files using SFTPwhich works over a ssh connection.
mythtv source package in Cosmic
For HandBrakeCLI users, we found that a line of this form will compress a p or p source file significantly, producing a p output and only 2-channel stereo sound: It transcodes the DVB recordings mpeg files using Handbrake. If you want to use this script, be sure to read the entire Wiki page because you WILL need to make some changes to the script, especially if you do not live in Germany.
However, we do not know if MythTV can handle the compressed stream at this time. If MythTV has the ability to work with the compressed stream, that might mean that the files sizes would already be reduced and there may not be a need to run additional compression software, and it also introduces the possibility that the compressed stream could be sent to another location in real time. You can only compress video just so much before it starts to look like crap. What we instead suggest is that you forward a different port, such as a higher, more obscure port to port 22 on your backend alternately you could change the ssh port on the backend if you know how to do that, and then open that port in the router.
That will at least slow down some of the bad guys.
You should only open the obscured ssh port as described above.