"canaws" wrote:
Here's my late feedback for the latest preview release.
Works awesomely! There's just a few minor things I noticed...
Thanks for the feedback. Better late than never!
"canaws" wrote:
1. Jumpy menu: I had it before, it went away for a couple of release, and now it looks like it's back. Maybe I click too fast or something, but when I go back up to the letter-folder level sometimes it jumps back to 'play all' before returning to where I was or sometimes it will jump back to the folder that I came out after I push over to go to another folder.
I've noticed the jump back to 'play all', but it's strange how it only seems to happen sometimes. I think I know what the problem is there. The "fast click" issue is a little bit tougher. I guess I never tried to go up a level and immediately move over to another folder, but I definitely see it now. That behavior is a result of the new "autorefresh" that happens as you move back up the hierarchy. I'm not sure much can be done about it without getting rid of the "autorefresh" because of the way the "built-in" part of the Roku UI and the event system works. Basically, the built-in UI makes some things happen on the screen quickly and automatically and then sends events to the channel app to inform it that something happened (i.e., after the fact). I'll look into it, but for now, don't be so quick!
😄 "canaws" wrote:
2. I was getting the 'can't access the server' message for a while there this weekend, but I can't get it to repeat itself right now. So, I'm going to assume it was an issue with my computer.
I haven't seen that, so I'm going to assume it was an issue with your computer, too!
😉"canaws" wrote:
3. I noticed that a wmv that I could play before won't play now. It starts but then freezes (distorted picture). It's an OLD video, so I was surprised it worked in the first place and I don't have any other wmv to test to see if it's an issue with all wm videos.
I only have one wmv that I used a long time ago for testing, but it also has problems now. I think I'll try to get an answer from Roku to see if anything changed wrt wmv files.
"canaws" wrote:
Questions:
1. When you say HTTP streaming do you mean of audio (mysteams) or video? How exactly would we test the very limited HTTP streaming support for video, if it exists?
The support is for video. It turns out the support is a little better than I initially intended. I put in special handling for a file named 'mystream.m3u8', but it wasn't necessary. It's still there, but it turns out any .m3u8 file will be handled correctly. Here's an example you can try; just put it somewhere in your 'myVideos' folder (or subfolder):
#EXTM3U
#EXT-X-STREAM-INF:PROGRAM-ID=1, BANDWIDTH=298577
http://liveips.nasa.gov.edgesuite.net/msfc/Edge.m3u8
#EXT-X-STREAM-INF:PROGRAM-ID=1, BANDWIDTH=532383
http://liveips.nasa.gov.edgesuite.net/msfc/3G.m3u8
#EXT-X-STREAM-INF:PROGRAM-ID=1, BANDWIDTH=1132383
http://liveips.nasa.gov.edgesuite.net/msfc/Wifi.m3u8
#EXT-X-STREAM-INF:PROGRAM-ID=1, BANDWIDTH=32000
http://liveips.nasa.gov.edgesuite.net/msfc/Edgeaudio.m3u8
Copy this to a text file named "nasatv.m3u8" and you should be able to try out HTTP Live Streaming. If you find any similar HLS m3u8 files on the internet, you can give them a try.
"canaws" wrote:
2. I've always wanted to ask this. I've always had two instances of python running: one controls the 'stop server' box and the other controls the actual server/feed page. If I click 'stop server' it doesn't actually do anything except close the box. I still have to go to the task manager and kill the second instance of python. Is this normal?
Python is not my area of expertise, but I'm very slowly starting to learn my way around. I assume since you mention 'task manager' you're running under Windows. I don't know if it's strictly a Windows issue, but I figured out a fix that works (I don't have anyway to make sure it works on any other OS).
Edit 'springboard.py' (in the 'server' directory) with notepad or any other text editor and change this:
def spawn_server(self):
import subprocess
cmd = "%s rss_server.py" % config.get("config", "python_path")
return subprocess.Popen([cmd], shell=True)
to this:
def spawn_server(self):
import subprocess
p = "%s" % config.get("config", "python_path")
cmd = [p,"rss_server.py"]
return subprocess.Popen(cmd)
Indentation is very important in Python, so make sure the indentation of the new code matches the old code (you should be able to do a simple copy and paste).
For what it's worth, I never thought it was necessary to use the springboard screen to start the server (although it's really nice for loading the client). You have a couple of options for starting the server:
1. Assuming .py files are associated with Python (which I think it takes care of when you install it), you can just double-click 'rss_server.py'.
2. With the same assumption, you can start it from the command line by typing "start rss_server.py" from within the 'server' directory.
3. Again from the command line and assuming Python is installed in C:\Python26, type "C:\Python26\python rss_server.py".
I usually go with #2, but I understand how some people want to start the server automatically when the server boots.
I hope I've answered everything.
-JT
Roku Community Streaming Expert
Help others find this answer and click "Accept as Solution."
If you appreciate my answer, maybe give me a Kudo.
I am not a Roku employee.