ah.. really.. so how come it won't even come up if i have flash disabled (on the home page)... I'll post my screenshot when i got home... i know i don't have to use webot but it just bothers me that I am the only one that couldn't use it :-)
Cool app! I'm hoping to get this working since I like the interface. I haven't tried Orb yet.
For those of you who are streaming mp3s with Webot, what's the average buffer time until it starts playing? I see one user reports 4 minutes. Maybe I just didn't wait long enough, but if 4 minutes is average, I see less use in this application. When I select a song, it scrolls "LOADING..." and that's all it does.
I also tested it on the Webot host PC, and it plays songs fine. The N800 is on the same network (no firewall/router between devices). I'm running OS2008.
For those of you who are streaming mp3s with Webot, what's the average buffer time until it starts playing? I see one user reports 4 minutes. Maybe I just didn't wait long enough, but if 4 minutes is average, I see less use in this application. When I select a song, it scrolls "LOADING..." and that's all it does.
I also tested it on the Webot host PC, and it plays songs fine. The N800 is on the same network (no firewall/router between devices). I'm running OS2008.
I think it was caused by multiple network interfaces on my Bot PC. I noticed in the WeBot config page that my Bot had a strange IP. This was one of my VMWare VMs. I disabled that interface and restarted the Bot, then it grabbed my VPN one. I disabled that one, restarted the Bot and it grabbed my online X-drive IP. I disabled that, then it worked. Audio started streaming almost immediately (note that this is over a LAN). I'm not sure if it would've worked under any of those other interfaces, but I imagine I'll find out as soon as I need those interfaces back!
How about an option in the Bot software to choose an interface to listen on? Thanks!
There shouldn't have been any cpu spike while streaming. Had you just installed your bot and it was indexing your music and photo collections? That action does use some CPU -- typically 40-65% with some spikes. You can minimize this by right clicking on the bot in your systray and choosing "about Webot." a panel will pop up with general info about your bot and its status with a control slider to minimize or maximize the amount of processor juice it uses when indexing -- if you have a large collection you may wish to turn it way down while you're on your box doing other tasks and then crank it up at night or at times when you're away from your pc and it's just idling.
btw, this indexing happens just one time, so once its done you should have no more cpu problems.
