"el.wubo" wrote:
I have the same problem. Having the server generate the thumbnails on the fly is definitely the most convenient way to tackle this and is what I'd like to do. I've actually got a bit of test code on my machine doing just that but it's not ready for prime time just yet. Hopefully soon! I'd say in a week or so that should be available.
"czarjosh" wrote:
For Mac OSX users I typed up the steps and put them on my blog
http://joshferris.com/2010/02/21/local-media-on-your-roku/
"el.wubo" wrote:
Well, 🙂 that was a long one.
Your line 130 reported in that file is different from the line 130 in the latest version. Best I can tell it's complaining because it's trying to print to standard out but standard out has been closed. If this is actually the problem I'm a bit surprised that we're only seeing it just now. I've updated the latest version to log it's output to my_media_log.txt instead of printing it to the screen. I really should have done this from the beginning but your issue inspired me to do it now.
Please download the latest version, make absolutely sure you've stopped your old server (press alt+ctrl+delete and look for python in the processes tab) and then start up the new one and let me know if you have trouble. You can send me an email (look in the readme for my address) with the backtrace if it's lengthy.
"renojim" wrote:"hammerpocket" wrote:
I noticed an undesirable behavior tonight. For whatever reason (maybe my computer was asleep), My Media couldn't connect to the server, so it brought up the error screen. The only choices are to manually enter the IP address (which was already correct) or try again -- there is no way to cancel or back out. I clicked to try again, but that didn't work. The only thing I could think of was to press the home button, which did work to get me out of that error screen. However, as I was navigating through the other channels I kept being taken back to the My Media error screen after 2-3 seconds. I finally had to just quickly choose a random channel get out of the loop.
BTW, I'm using a602ef2.
That's funny! When I implemented the error screen I knew that was a possibility. I figured 99% of the time one of those two choices would suffice. I guess you're the 1%. 😄 I'm a little surprised you kept getting the error screen popping up. I'll look into adding a cancel option that kicks you out of the mymedia channel.
-JT
"myplanet" wrote:
Please add support for .mov files. I downloaded a podcast via itunes. It was a .mov file. The media channel could not see the file or play it. After changing the extension to .mp4, it worked. I could see and play the video.
"intersys" wrote:
el.wubo:
thanks - that sort of worked. The log was written out to a file. There were no errors in the log file, but I did get the error screen on the Roku box - saying it couldn't connect and retry. I'm thinking that there may be either a timeout problem or a buffering problem as the media library is 72gb of mp3's, including several subfolders.
Thanks again for the replies and suggestions.
"el.wubo" wrote:
Can you give an rough estimate of the number of direct subfolders your Music folder has? I'd expect to be able to enumerate the folders (and search for a bit of album art) in even a collection that big within the timeout -- but maybe I'm being naive.
"el.wubo" wrote:"myplanet" wrote:
Please add support for .mov files. I downloaded a podcast via itunes. It was a .mov file. The media channel could not see the file or play it. After changing the extension to .mp4, it worked. I could see and play the video.
Thanks for the report. renojim looked into the documentation and found that this is actually expected behavior (I was surprised) so we'll be serving up mov's as mp4's later tonight. I'd do it right now but I don't have access to my Roku to test.