Plugin: Mobile Web Interface Version 2

[wayner]

This is kind of OT but I would usually recommend going cable modem>router>vonage box unless the vonage box really has to go next to the cable modem. I would then hang a switch off of the router to attach all of your devices to.

[Comitizer]

Originally Posted by Brent

Make sure you close out the browser window on any device when done using it. I wonder if it was still running when you saw the higher CPU usage. Either way, you should check the logs and report back what you find.

Thanks Brent.

The odd thing is that I didn't know about the mobile streaming until I read about it on geek tonic. (great blog BTW). I hadn't had a chance to test that feature so I'm pretty sure it wasn't anything relating to that issue.

Which logs should I be checking? Jetty? Sage?

[jreichen]

Originally Posted by LehighBri

Yes you're right, I'm using iOS 4.1 on my iPhone. Sounds like iOS 4.2 is coming out on Friday so Brent may have limited time to test and react to this if he upgrades. My request would be to take a look at how this works in iOS 4 and try to get it working the same there as it works in iOS 3.

Or perhaps there's a way in your jsp or javascript to detect what version of iOS is running and tailor the code accordingly from there? Not sure if that's possible but just a suggestion. Nonetheless, this plugin is still an incredible start and working great in most of my use cases.

I looked into it for a little while and didn't see what the problem was. It's on my todo list but the list is growing rapidly

[mayamaniac]

Is there a way to lower the bitrate so it streams better on 3G connection?

[Taddeusz]

Can ffmpeg leverage edl files to incorporate comskip?

[jreichen]

Originally Posted by mayamaniac

Is there a way to lower the bitrate so it streams better on 3G connection?

I'm using a minimum of 150Kbps, which is the recommendation from Apple. I haven't tried anything lower but I think the quality would be poor. Can you do a speed test and see what your throughput is?

[jreichen]

Originally Posted by Taddeusz

Can ffmpeg leverage edl files to incorporate comskip?

I'm not sure what ffmpeg's support is for edl, etc files. I'm pretty sure I'd have to control that from the client side so I'm not sure that matters anyway. Take a look at the FAQ for what I have to say about Sage-related playback features.

[jreichen]

Originally Posted by clayfree

I really like the ability to stop playback on another client. I wish this was a feature on SageTv extenders.

Stopping playback on a Placeshifter was already possible, but until the SageTV core added support for controlling clients from the server in v7 it wasn't possible to stop playback for clients.

[Fonceur]

Originally Posted by jreichen

until the SageTV core added support for controlling clients from the server in v7 it wasn't possible to stop playback for clients.

Sure it was, you just had to send a Stop to the right context...

[stuckless]

Originally Posted by Fonceur

Sure it was, you just had to send a Stop to the right context...

I think what is meant here, is in Sage7 you can send events directly to a Sage Client (not an extender, but a pc client). It was not possible to do this before, without running some extra software on the pc client. Now, in S7, you can use the context, like any other placeshifter or extender.

[Fonceur]

Originally Posted by stuckless

It was not possible to do this before, without running some extra software on the pc client.

Right, for a client I did need to run SageTCPServer.jar on it, my bad.

[TechBill]

I understand it need Safari browser to stream in but I was wondering if it will work on Safari browser that is installed on Windows XP or 7?

I tried it on Windows 7 and it does show a video box but clicking play button does nothing.


I am a Android user myself and will be willing to donate for an Android streaming feature.


But I love the new Mobile Interface GUI


Bill

[Fonceur]

Originally Posted by TechBill

I understand it need Safari browser to stream in but I was wondering if it will work on Safari browser that is installed on Windows XP or 7?

If you read the streaming thread, you can see that it won't work as they don't have quicktime x.

I am a Android user myself and will be willing to donate for an Android streaming feature.

Unfortunately, Apple's HTTP Live streaming isn't available on Android...

[mistergq]

jreichen,

Thank you for this plugin! It is awesome and a must have for Ipad and Iphone.

Now once ios4.2 finally comes out, things will be great!

[Chriscic]

Originally Posted by Carlton Bale

Very nice - thank you for the hard work!

Here are a few things to add to the initial instructions to help other newbies like me get it working:

• After installing the "SageTV Mobile Web Interface" plug-in and all the dependencies, go to the jetty web server plug-in and configure it to change the user name, password, and port.
• The default user name is sage, the default password is frey, the default server port is 8080.
• The initial URL to enter in your safari mobile web browser when on your home WiFi network is http://192.168.x.x:8080/sagem/m/, where the IP address is that of your SageTV server.
• To access this away from home, you need to go into your router configuration and forward public port 8080 on your router to private port 8080 of your of your SageTV server IP address. You will then be able to access remotely (via 3G) by going to http://your_router_public_ip_address:8080/sagem/m .
• Use a dynamic DNS service such as DynDNS to turn your public router IP address into an easy to remember domain name, and to automatically update it if the IP address changes.

Why do you say "/sagem/m" when the plug-in faq says "/stream"?

I can't get it to work either way... I keep getting:

"HTTP ERROR: 404

Problem accessing /stream/. Reason:

NOT_FOUND"

Note that I have configured the jetty plug-in and changed my username and password, used automatic Up&p config, and left the port at 8080.

Very frustrating. Any quick suggestions before I try to figure out all the logging stuff? Hard to slog through stuff with little kids around!

[Fonceur]

Originally Posted by Chriscic

Why do you say "/sagem/m" when the plug-in faq says "/stream"?

Because you're not supposed to access the stream directly, you go through /sagem/m and navigate from there...

[Chriscic]

Ah, thank you. That makes sense. However, I am not doing a good job of finding the official instructions on what http:/ or web page to go to run this on my mobile device. I followed Carlton's instructions, but there must be something "official" somewhere... want to see if if I can figure out what I've missed. Even using sagem/m I get the Http not found error.

Any help appreciated. Thanks,
-Chris

P.S. - To be clear, I'm looking for the official instructions on how to install and access this thing. I'm guessing this is one of those cases where most folks were already using older versions of the plug-in, so nobody is providing the "explain it to me like I'm a 7-year old version." Or maybe that's what Carlton provided and maybe I need the 5-year old explanation : )

I seemed to have installed and configured thee plug-in correctly, and it says "enabled." There's just nothing there when I try to access via the web (I'm on wifi). I did notice that when I put in a made-up port # in my web browser instead of 8080 it says "can't connect" rather than HTTP not found, so maybe the port part is working correctly, but something else is amiss.

[Fonceur]

Originally Posted by Chriscic

However, I am not doing a good job of finding the official instructions on what http:/ or web page to go to run this on my mobile device.

It should be something like:

http://sagetvserver:8080/sagem/m

First try on your SageTV server itself, then on your phone.

[Chriscic]

This is exactly what I entered on the server, except I hid a few #'s with x's

http://192.168.0.xxx:8080/sagem/m/

The ip address is the ip for the server itself, per the router config screen.

Still http not found.

[kricker]

No need to hide those numbers. That is a standard internal ip address it's not giving anything away by showing it.

Anyhow, have you restarted sage and or the sage server after installing the jetty webserver and mobile interface?