bertgilb wojtek xandee
Silvana Fleischacker
These scripts were designed for the keys on a Windows-compatible remote control.You may have to adjust the LIRC configuration for other models.Full integration requires arrow buttons and a BACK button and a number keypad.
First download the patch file netflix.patch.Then apply the patch with the following command.Where it says --directory=/usr/local, substitute the PREFIX of your existing installation.For example, if your frontend files are found in /usr/share/mythtv and /usr/bin/mythtv, then specify --directory=/usr.
The arrows can be used to control the mouse.Mouse acceleration is supported, meaning that the cursor will speed up as long as you hold the button down.This is ideal for both fine and large pointer adjustments.The OK button acts as a mouse click.
The number buttons can be used to enter alphabetic characters.This is necessary for entering a name into a search box.Use the multi-tap system like on old mobile phones.For example, to enter the letter L, press 555.To enter an actual number 5, press 5555.To enter a space, press 0.The ENTER and CLEAR buttons act as enter and backspace, respectively.
The menu options can be customized in your sources by modifying some XML files.If you use the default menus, then you should edit mythtv/themes/defaultmenu/library.xml.If you use the classic menus, then you should edit mythplugins/mythnetvision/theme/menus/netvisionmenu.xml.(If you aren't sure which one you use, then it doesn't hurt to edit both).You can add new menu options for different web pages.Just copy those lines and change the type and text and description to whatever you want.The action line should start with EXEC /usr/local/bin/lircfirefox.py /usr/bin/firefox and then include the URL for your desired page.
After you make any changes, run sudo make install again.You should run the installation from the mythtv directory if you made changes under it, and from the mythplugins directory if you made changes under it.
Up to this point I see Channels and the Channels DVR as unique in the market. Channels hits all the right buttons for me. I get top notch OTA HD content, it is a joy to use, low cost, family friendly, stable and I get almost immediate support. Nothing else comes close.
I feel that $8 per month or $96 a year is a lot compared to a free Windows Media Center (or already paid for and no monthly). On the other hand the development of this product is unbelievable, especially compared to all the other failed projects that I paid for (hdhr dvr kickstarter, plexpass dvr, emby and others). My take is this may not be for everybody however if these guys are going to keep developing, improving and growing this product they need to have the financial resources and rewards to keep them motivated. I would rather have this product and pay a premium for its level of development than dump a smaller amount into another product that does not live up to its potential.
Clearly the Channels team need to be able to make a living, and for such a quality product I am happy to pay more initially to get it going while the team develop their user-base. However, I do think it is too high to be attractive long-term, especially in light of the up-front costs (tuner hardware plus app costs), but if that price were to include full cablecard support it would be reasonable. I would like to see a commitment towards the intent of lowering costs to $5/mo., in line with the Plex Pass service (which includes DVR and much more), either once the more intense initial development is complete or once the user base yields sufficient revenues. I fear that the current price is going to limit that user-base growth in the context of cheaper competition from Plex (which offers broader functionality). I appreciate that it is a tricky balancing act.
For those comparing the Channels DVR service with Hulu, I would add that the fair comparison in the US (only) is with Hulu + CBS All Access (+ the free CW and PBS apps) - up-front costs (hardware + apps). Once commercial skipping works better then the extra cost for Hulu Ad-free should be figured in. But bear in mind that the streaming TV game is changing rapidly, and so all of this may change soon.
Until I dropped Directv sat service I was paying per receiver. A dvr was $10 and a reciever was $5 per month. Now I pay $8 for a dvr that can be viewed on many more televisions and devices then before.
I recently dumped uverse tv for direct now and channels dvr. Sports are the only reason I still have directv now. I have been able to get all the content I need with OTA tv to fill my entertainment needs. Obviously, this a personal issue that varies from person to person.
This is why I think channels dvr is worth $8 a month. One, it gives me the option to own and control content on my own terms. Streaming services are always change what content is available. With Channels dvr I can do whatever I want with the content and no one can ever take it away. I can watch it wherever I want. I can download it to any device I want. Two, I realize I am helping to fund the development of this product. The development team is constantly making improvements (more than I can say for at&t and directv now). No large app developer or company will have incentive to develop anything like this because of the ownership listed above. Forth, while this is the most expensive dvr option I have seen (more than plex dvr (pass) or HDHR dvr), it is clearly far superior to either of those products.
I have always been interested in Netflix streaming, but I could not get over not being able to adjust the playback speed. That and the movie selection stinks (out of 159 titles in my queue only 40 are available to be streamed). I stilltried streaming for 30 days and really liked some of the original content Netflix had. During that time I did not find anynative way to adjust the playback speed in their html5 player. This really stinks as I am used towatching video with Vlc, YouTube, and MythTV all of which allow for playback speed adjustment up to 2x. It is hard towatch anything at lower speeds anymore. After a bit more searching I finally found a way to change the playback speed inNetflix streaming video.
After much searching I found an Google Chrome extension calledVideo Speed Controller,which allows for the speedup of html5 video streams in the browser. Netflix has an html5 player so this works withNetflix streams. Hooray!! The speedup stream does not have any buffering issues and I've watched many things onwith 2x playback without issue. Unfortunately you can't use this anywhere other than the browser. Come on Netflixplease add playback speed adjust to all of your players on all platforms!!!
Beware that when speeding up video you will need to make sure your video card can handle the higher frame rates.When I stream a video file from local storage with a local program like Vlc at 2x, it is very smooth, without muchjitter or video tearing. When streaming content from Netflix or YouTube or other sites using this browser plugin you are using the browser as the video player, and it might not be as clean of an experience. You might notice some morejitter in the video and some frame tearing on fast moving scenes. This usually happens if your hardware can't keep uprendering the video or if hardware acceleration is not enabled.
My testing for this is being done on Linux with Google Chrome using the accelerated Nvidia Drivers with a GeForceGT 520 a video card from 2011. What I had to do to get rid of the jitter and tearing is turn hardware accelerationon in Chrome. Google seems to be very careful about whether or not they turn on hardware acceleration. They usually don'tturn it on unless they know for sure it will work. Mine was not turned on even though I had a video card that supportedacceleration and the correct drivers. Chromes detection of this might not be the best or Google did not think the drivers for this were stable enough. What is great is you can turn this on anyways and it works great.
To see if your hardware acceleration is already turned on or not type "chrome://gpu" in your Chrome URL bar. If it'sturned off you will likely see lots of red text indicating so. Look for "Video decode" and see if it says "Disabled". If so you will need to turn it on. If it says "Hardware accelerated" then your good and can skip the rest of thisparagraph. To turn on the hardware acceleration in the Chrome URL bar type "chrome://flags". The first setting says"Override software rendering list". Click the "Enable" to turn on the override. Then restart Chrome. Go back to"chrome://gpu" and see if it says "Video decode: Hardware accelerated". If so go try to watch a movie again or a YouTube video and it should be much smoother and likely have less tearing. If you don't have less tearing, go intoyour video driver config and make sure you have Sync to VBlank enabled. Mine is in my Nvidia X server settings managerthen under "OpenGL settings"-> Performance. Check the box "Sync to VBlank".
It's something that will need to be added eventually, but for now there's likely not an immediate need for it. Since Roku devices are never connected directly to the Internet, the user's router can handle the internal IPv4 traffic without much bother. Based on an article I just read, it's likely going to be close to 2050 before the world is fully IPv6. I think we have some time...
@iXe8ta seems odd behavior. I have IPv4 and IPv6 enabled on both of my media PCs, and RMP sees them both without a problem. Both of my servers are running Windows 10, so perhaps it's an OS issue. Perhaps MythTV can't/won't run both protocols at the same time.
Actually, this support is needed much much sooner than later, as in now. There are three examples I can think of immediately: T-Mobile home internet, Starlink internet and Starry internet... there are undoubtedly many more. The problem is these new internet services use CGNAT for ipv4 traffic and are using or will shortly be using ipv6 for public facing traffic. If Roku doesn't support ipv6 then that basically means applications that run on the Roku platform that require public addressing (one example is Plex) just won't work properly. Roku may have gotten away with this in the past (as have many other vendors), but their time has basically run out. Apple TV and Android TV support ipv6. I'm a big fan of Roku, but if I change to an ISP that requires ipv6 for public facing traffic (and all of the new technology based ISPs will require it, simply because there aren't any more ipv4 addresses available), then I'll be forced to switch to Android or Apple - and once I switch, I'm not coming back. Roku isn't stupid, I'm sure they are well aware of the situation - but they need to get in front of this, because the train has already left the station.
90f70e40cf