Open Gideop opened 9 years ago
themacks
commented
9 years ago I'm not really sure why you are having those problems. I'd check that you are using the latest firmware on your HDHomeRun (http://www.silicondust.com/support/downloads/). Then check that you can watch the stream directly with something like VLC. I've actually had pretty good success using a RaspberryPi B with Rasbian running ply, so you should be able to get it to work.
Gideop
commented
9 years ago Thanks for the reply. I'll try that when I get back from travel and will post the results/progress.
Gideop
commented
9 years ago Ok, i've updated firmware on the homerun, i've reinstalled Ubuntu 14.04 LTS, reinstalled python, hdhomerun software (that's how i updated the firmware), reinstalled ply and reinstalled webpy... same results.
I haven't tried moving to the Raspberry Pi yet, but i guess i'll give that a shot too. In the mean time, do you have any ideas of how i can trouble shoot? I will say, it appears to be problematic only with the higher resolution channels. It appears to be dropping frames and doesn't play sound at all.
I'm also trying to install MythTV on Ubuntu just to verify that the HDHomeRun unit is operating correctly. Is there any easier way to do this? (MythTV seems to be a lengthy install process).
Thanks, Mike
On Fri, Feb 27, 2015 at 8:55 AM, themacks notifications@github.com wrote:
I'm not really sure why you are having those problems. I'd check that you are using the latest firmware on your HDHomeRun ( http://www.silicondust.com/support/downloads/). Then check that you can watch the stream directly with something like VLC. I've actually had pretty good success using a RaspberryPi B with Rasbian running ply, so you should be able to get it to work.
— Reply to this email directly or view it on GitHub https://github.com/themacks/ply/issues/7#issuecomment-76406412.
themacks
commented
9 years ago Not sure how I missed it the first time, but the Connect is going to take a lot of horsepower to use with a Roku because it only outputs an MPEG 2 stream and the Roku won't play that natively. Ply was really made to work with an Extend/HDTC which outputs an H264 stream that the Roku can play almost directly.
Gideop
commented
9 years ago My bad... I have a HDTC-12 USAF which is an Extend. Sorry for the confusion. On Mar 14, 2015 10:12 PM, "themacks" notifications@github.com wrote:
Not sure how I missed it the first time, but the Connect is going to take a lot of horsepower to use with a Roku because it only outputs an MPEG 2 stream and the Roku won't play that natively. Ply was really made to work with an Extend/HDTC which outputs an H264 stream that the Roku can play almost directly.
— Reply to this email directly or view it on GitHub https://github.com/themacks/ply/issues/7#issuecomment-80817281.
Gideop
commented
9 years ago Ok, let's try this again (on my PC and not my "smart" phone that tries to "correct" all my spelling):
I have a HDTC-2US which is an Extend. Sorry for the confusion.
Mike
On Sat, Mar 14, 2015 at 10:42 PM, Mike Gideons geezmaneti@gmail.com wrote:
My bad... I have a HDTC-12 USAF which is an Extend. Sorry for the confusion. On Mar 14, 2015 10:12 PM, "themacks" notifications@github.com wrote:
Not sure how I missed it the first time, but the Connect is going to take a lot of horsepower to use with a Roku because it only outputs an MPEG 2 stream and the Roku won't play that natively. Ply was really made to work with an Extend/HDTC which outputs an H264 stream that the Roku can play almost directly.
— Reply to this email directly or view it on GitHub https://github.com/themacks/ply/issues/7#issuecomment-80817281.
themacks
commented
9 years ago The only thing I can think of is that it might be your Wifi. Try plugging your laptop in with ethernet and see if it changes.
Gideop
commented
9 years ago I will do that tonight. I also got the Pi 2 up and running Raspbian and installed ply, though not exactly like i did on my laptop. To start, Raspbian had access to ffmpeg by default, no need to add a ppa repository as i did on my Ubuntu laptop. Not sure if i ended up with the exact same version or not. Also, i think my Pi python version was 2.7.3 while my laptop is 2.7.6. Not sure if that makes a difference. I forgot to check the version of make and gcc, but i'll do that tonight.
The result was that i was able to configure ply (used epiphany to navigate to the localhost:[port], add the HD and scan channels). When i pointed my Roku to the new IP address, it displays all the channels, but won't "play" any, that is, i highlight a channel, hit OK on the remote and i hear the little confirmation noise from the roku, but then it just sits there. The server is reporting that it's sending info (as displayed in the shell from which i launched ply), but nothing is happening on the Roku.
I will say that i am running the Pi in a "headless" configuration, connecting to it from my Ubuntu laptop with ssh. I eventually want to auto-login to the Pi upon power up and run a shell script (not sure how to do this, maybe as a cron job???) to launch ply. I'm not sure how i will handle the addition of the HD device and the scanning of the channels. But this is a ways off. And, since the Pi is on a battery backup, for now, i can connect a monitor and keyboard and start everything, then unplug the monitor and keyboard after it's up and running. The only time i'd need to restart it is if power goes out long enough to drain my UPS.
Thanks for all the help. If nothing else, it has been fun tinkering around with this stuff. I just really wanted this to work as it would be a great solution for a compact installation as only the Roku is located at the TV while everything else is in a closet. Worst case scenario, i load Kodi on the Pi and it sits next to the Roku. The TV is hung from the wall with a bracket that is sunk into a cubby in the wall. The Roku fits in the cubby easily, but adding the Pi might make things tight. Plus, it's just not as cool as having everything through the Roku (and having only one remote to navigate through Netflix, Movie Library and TV).
Thanks again, Mike
On Tue, Mar 17, 2015 at 7:13 AM, themacks notifications@github.com wrote:
The only thing I can think of is that it might be your Wifi. Try plugging your laptop in with ethernet and see if it changes.
— Reply to this email directly or view it on GitHub https://github.com/themacks/ply/issues/7#issuecomment-82314634.
I tried setting up ply on a lenovo e520 (Core i5) laptop running Ubuntu 14.04.1 LTS connected to my router via WiFi (less than 10 feet from my router). I scanned my HDHomeRun Connect and got it all working, but when i connected my roku 3 (using ethernet), and launched the HD app (channel... whatever) some channels have no sound and look "chopy" while some looked ok but had no sound. This was supposed to be a "proof of concept test", with the ultimate goal of replacing the laptop with a raspberry pi running snappy ubuntu. Question is, would you have any idea why i had the issues that i saw during my proof of concept test run? If it's compute capability of my laptop (which wasn't "doing" anything else at the time), then i doubt the raspberry pi would handle it any better. If it was a setup issue, or perhaps a python issue, then it'b be better to correct that as i'm building the rPi setup (which i've admittedly stalled on because i'm new to rPi and snappy ubuntu and didn't realize how different the environments were... no apt-get on snappy!). Any ideas/comments?