What you need before you start: TV Set-top box What's in the box. Complete your Slingbox set-up from your TV screen by following these steps: What you need before you start: Computer that is connected to the same network as your Slingbox Set Up Your Slingbox On your computer, open a browser and go to watch.
Click Start. Choose your Location and Language. Follow the prompts to install the Sling Player Plugin for your browser. Click Next after going back to watch. Enter your Location and ZIP code. Then click Next. Choose the TV provider you are using then click Next. Click Next after checking your channel lineup. Set up your remote by choosing the manufacturer and model of your set-top box.
Test your 'virtual' remote control on the computer. Click Next to continue. Setup is now complete. The power LED on the front of the Slingbox will glow steadily. Wait 2 minutes to allow the box to finish starting up.
Set Up Your Slingbox On your chosen device, open a browser and go to www. If the Program does not specify a version number of this License, you may choose any version ever published by the Free Software Foundation. If you wish to incorporate parts of the Program into other free programs whose distribution conditions are different, write to the author to ask for permission. For software which is copyrighted by the Free Software Foundation, write to the Free Software Foundation; we sometimes make exceptions for this.
Our decision will be guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the sharing and reuse of software generally. Version 2. By contrast, the GNU General Public Licenses are intended to guarantee your freedom to share and change free software--to make sure the software is free for all its users.
This license, the Lesser General Public License, applies to some specially designated software packages--typically libraries--of the Free Software Foundation and other authors who decide to use it. You can use it too, but we suggest you first think carefully about whether this license or the ordinary General Public License is the better strategy to use in any particular case, based on the explanations below. When we speak of free software, we are referring to freedom of use, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software and charge for this service if you wish ; that you receive source code or can get it if you want it; that you can change the software and use pieces of it in new free programs; and that you are informed that you can do these things.
To protect your rights, we need to make restrictions that forbid distributors to deny you these rights or to ask you to surrender these rights. These restrictions translate to certain responsibilities for you if you distribute copies of the library or if you modify it.
For example, if you distribute copies of the library, whether gratis or for a fee, you must give the recipients all the rights that we gave you. If you link other code with the library, you must provide complete object files to the recipients, so that they can relink them with the library after making changes to the library and recompiling it. To protect each distributor, we want to make it very clear that there is no warranty for the free library. Also, if the library is modified by someone else and passed on, the recipients should know that what they have is not the original version, so that the original author's reputation will not be affected by problems that might be introduced by others.
Finally, software patents pose a constant threat to the existence of any free program. We wish to make sure that a company cannot effectively restrict the users of a free program by obtaining a restrictive license from a patent holder. Therefore, we insist that any patent license obtained for a version of the library must be consistent with the full freedom of use specified in this license.
We use this license for certain libraries in order to permit linking those libraries into non-free programs. When a program is linked with a library, whether statically or using a shared library, the combination of the two is legally speaking a combined work, a derivative of the original library.
The ordinary General Public License therefore permits such linking only if the entire combination fits its criteria of freedom. The Lesser General Public License permits more lax criteria for linking other code with the library. It also provides other free software developers Less of an advantage over competing non-free programs. These disadvantages are the reason we use the ordinary General Public License for many libraries.
However, the Lesser license provides advantages in certain special circumstances. For example, on rare occasions, there may be a special need to encourage the widest possible use of a certain library, so that it becomes a de-facto standard.
To achieve this, non-free programs must be allowed to use the library. A more frequent case is that a free library does the same job as widely used non-free libraries. In this case, there is little to gain by limiting the free library to free software only, so we use the Lesser General Public License.
In other cases, permission to use a particular library in non-free programs enables a greater number of people to use a large body of free software. Although the Lesser General Public License is Less protective of the users' freedom, it does ensure that the user of a program that is linked with the Library has the freedom and the wherewithal to run that program using a modified version of the Library.
The precise terms and conditions for copying, distribution and modification follow. Pay close attention to the difference between a "work based on the library" and a "work that uses the library". The former contains code derived from the library, whereas the latter must be combined with the library in order to run. This License Agreement applies to any software library or other program which contains a notice placed by the copyright holder or other authorized party saying it may be distributed under the terms of this Lesser General Public License also called "this License".
The "Library", below, refers to any such software library or work which has been distributed under these terms. For a library, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the library. The act of running a program using the Library is not restricted, and output from such a program is covered only if its contents constitute a work based on the Library independent of the use of the Library in a tool for writing it.
Whether that is true depends on what the Library does and what the program that uses the Library does. You may copy and distribute verbatim copies of the Library's complete source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice and disclaimer of warranty; keep intact all the notices that refer to this License and to the absence of any warranty; and distribute a copy of this License along with the Library.
You may modify your copy or copies of the Library or any portion of it, thus forming a work based on the Library, and copy and distribute such modifications or work under the terms of Section 1 above, provided that you also meet all of these conditions:. For example, a function in a library to compute square roots has a purpose that is entirely well-defined independent of the application. Therefore, Subsection 2d requires that any application-supplied function or table used by this function must be optional: if the application does not supply it, the square root function must still compute square roots.
If identifiable sections of that work are not derived from the Library, and can be reasonably considered independent and separate works in themselves, then this License, and its terms, do not apply to those sections when you distribute them as separate works. But when you distribute the same sections as part of a whole which is a work based on the Library, the distribution of the whole must be on the terms of this License, whose permissions for other licensees extend to the entire whole, and thus to each and every part regardless of who wrote it.
Thus, it is not the intent of this section to claim rights or contest your rights to work written entirely by you; rather, the intent is to exercise the right to control the distribution of derivative or collective works based on the Library. In addition, mere aggregation of another work not based on the Library with the Library or with a work based on the Library on a volume of a storage or distribution medium does not bring the other work under the scope of this License.
To do this, you must alter all the notices that refer to this License, so that they refer to the ordinary GNU General Public License, version 2, instead of to this License. If a newer version than version 2 of the ordinary GNU General Public License has appeared, then you can specify that version instead if you wish. Do not make any other change in these notices. Once this change is made in a given copy, it is irreversible for that copy, so the ordinary GNU General Public License applies to all subsequent copies and derivative works made from that copy.
This option is useful when you wish to copy part of the code of the Library into a program that is not a library. You may copy and distribute the Library or a portion or derivative of it, under Section 2 in object code or executable form under the terms of Sections 1 and 2 above provided that you accompany it with the complete corresponding machine-readable source code, which must be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange.
If distribution of object code is made by offering access to copy from a designated place, then offering equivalent access to copy the source code from the same place satisfies the requirement to distribute the source code, even though third parties are not compelled to copy the source along with the object code.
A program that contains no derivative of any portion of the Library, but is designed to work with the Library by being compiled or linked with it, is called a "work that uses the Library". Such a work, in isolation, is not a derivative work of the Library, and therefore falls outside the scope of this License. However, linking a "work that uses the Library" with the Library creates an executable that is a derivative of the Library because it contains portions of the Library , rather than a "work that uses the library".
The executable is therefore covered by this License. Section 6 states terms for distribution of such executables. When a "work that uses the Library" uses material from a header file that is part of the Library, the object code for the work may be a derivative work of the Library even though the source code is not. Whether this is true is especially significant if the work can be linked without the Library, or if the work is itself a library.
The threshold for this to be true is not precisely defined by law. If such an object file uses only numerical parameters, data structure layouts and accessors, and small macros and small inline functions ten lines or less in length , then the use of the object file is unrestricted, regardless of whether it is legally a derivative work. Executables containing this object code plus portions of the Library will still fall under Section 6.
Otherwise, if the work is a derivative of the Library, you may distribute the object code for the work under the terms of Section 6.
Any executables containing that work also fall under Section 6, whether or not they are linked directly with the Library itself. As an exception to the Sections above, you may also combine or link a "work that uses the Library" with the Library to produce a work containing portions of the Library, and distribute that work under terms of your choice, provided that the terms permit modification of the work for the customer's own use and reverse engineering for debugging such modifications.
You must give prominent notice with each copy of the work that the Library is used in it and that the Library and its use are covered by this License. You must supply a copy of this License. If the work during execution displays copyright notices, you must include the copyright notice for the Library among them, as well as a reference directing the user to the copy of this License.
Also, you must do one of these things:. It is understood that the user who changes the contents of definitions files in the Library will not necessarily be able to recompile the application to use the modified definitions.
A suitable mechanism is one that 1 uses at run time a copy of the library already present on the user's computer system, rather than copying library functions into the executable, and 2 will operate properly with a modified version of the library, if the user installs one, as long as the modified version is interfacecompatible with the version that the work was made with.
For an executable, the required form of the "work that uses the Library" must include any data and utility programs needed for reproducing the executable from it. However, as a special exception, the materials to be distributed need not include anything that is normally distributed in either source or binary form with the major components compiler, kernel, and so on of the operating system on which the executable runs, unless that component itself accompanies the executable.
It may happen that this requirement contradicts the license restrictions of other proprietary libraries that do not normally accompany the operating system. Such a contradiction means you cannot use both them and the Library together in an executable that you distribute. You may place library facilities that are a work based on the Library side-byside in a single library together with other library facilities not covered by this License, and distribute such a combined library, provided that the separate distribution of the work based on the Library and of the other library facilities is otherwise permitted, and provided that you do these two things:.
This must be distributed under the terms of the Sections above. You may not copy, modify, sublicense, link with, or distribute the Library except as expressly provided under this License. Any attempt otherwise to copy, modify, sublicense, link with, or distribute the Library is void, and will automatically terminate your rights under this License.
TVH is awesome with none of the BS. Then some MBA decided. Let me stop you right there. No that wasn't some MBA that decided. That was years of fucking inaction by tech companies that led to the development of NAT and the breaking of the end-to-end concept of internet connected devices.
You product is instantly too difficult to deal with an decried as utter garbage not suitable for consumption by a non-technical audience. I think you're partly right, though maybe not with SlingBox which used to work when I pointed it directly to an IP and port - worked great via VPN back to my house. Then someone decided to require not optional a cloud account, but cloud couldn't traverse my firewall and wouldn't relay so I would have to open a port in the firewall in order to use the cloud.
So, I had to VPN back into the home, connect from. Slingbox smarts are all in the device - the hardware encoders and all that are on device, and the cloud service maps a slingbox serial number to an IP address so the app can connect to your slingbox. There's only one real piece of information - how the slingbox app communicates with the slingbox - the cloud service isn't needed.
And the app is what makes it useful, but there's nothing much beyond taking a data stre. Switching to ipv6 isn't going to help the problem. You still have a firewall to deal with, only now it's more critical that it is configured properly.
The end user would still have to allow a connection in to the device even if NAT is not part of the equation. The real technical problem was never 1 IP per household it was the fact those IPs are not very stable, thus required dynamic DNS - again forcing users to do something to hard as opposed to just learning 1 ipv4 number. The real practical issues bandwidth to the edge largely meant radically asymmetric connections.
Were lots. UPNP is not a solution, it's not bi-directional. You can't negotiate a connection between two endpoints using just UPNP to help get through a firewall, one side needs to be accessible and setup in a way that the other side knows.
That's why the entire frigging cloud servers exist, long before we even started calling them "cloud". When Skype introduced a central server it was precisely a solution to this problem. Slingbox used to not require cloud, you could just open your own firewall port. None of the hardware I own including my Nokia N phone requires cloud servers in order to work. I pretty much agree with you and do similar things, but I make an exception for the open-source-only SchedulesDirect [schedulesdirect.
Do you just get show information from the broadcast side-channel stream? I get schedule information from the schedules that come over-the-air as part of the DVB-T digital signals and its good enough to use for those occasions when I want to record something although if the show is available to stream on the TV network's website its easier to watch it there than to try and remember to record it :.
That's the problem right there. I was screwed over by this company when I bought it and it didn't have any cloud services. They then removed the good software they had and replaced it with software that had mandatory ads. I believe a lawsuit was launched over this, but I never heard anything about it. I even filed a BBB complaint that I, and many others had bought this product under certain expectations and those expectations and the company had purposefully and fundamentally changed the product to be worse.
Phillips made an internet radio. After a while they got bored with the idea and shutdown the channel server. The radios were rendered useless. Happy Ending: The radios were hacked to be able to use your own channel server. No thanks to Philips. Seems that had been a bit early for the Disruptive Communications Technology Award which had been granted by the Financial Times.
Still, it turns out it definitely wasn't undeserved after all! This is really sad to hear but I have not used my Slingbox since dropping cable. Can I send in my device for paid repair service? A: Slingbox is not shipping any new product, and most authorized resellers have been out of stock for a couple years. Power adapters may be available by calling customer service. A: For immediate support, customers still under warranty should call our regular support number at Please have your device serial number ready.
For all other issues, please take a look at our help section at slingbox.
0コメント