Plugin: SageTCPServer

[Fonceur]

Originally Posted by George M

Restarted twice. Still the same. would it help to see the log file?

Sure, if you can zip up the sagetv_0.txt, sage.properties and some free log collector on the Android side, that would help. You are on SageTCPserver 2.0.2, TaSageTV 1.57 and the latest CQC drivers?

So if you disable CQC, the Android app works fine, and with the Android app not running the CQC drivers are fine?

[George M]

SageTCPserver is 2.0.2
On CQC, SagePlayer is 2.67
taSageTV is 1.57

Server is on port 9250
Extender is on port 9260

Attached is log and property file.

If CQC driver connects (on 9250) then the android remote does not work.
If CQC driver is disonnected then the android remote works.
If CQC driver is moved to 9260 then android works but CQC does not.

EDIT: I just restarted both CQC service and SageTV, and with CQC on 9260 (same as extender) control from both CQC and Android seem to be working. I will play with it some and come back if one of them stops.

[gianpieroizzo]

Hi again,

I wrote on the tiSageTV thread, but I think the problem is here.
My SageTV server is configured WITHOUT using the service mode, and I'd like to control its GUI.

I don't know how to deal with this. If I try this configuration, I cannot connect to the "client", whilst the extender works ok.

sageTCPServer/client=local.9260
sageTCPServer/debugOn=false
sageTCPServer/extender=0023a500025d.9261
sageTCPServer/server=9250

Is it strictly necessary to set up the server as a service and run the client separately ?

thanks again
Gian Piero

[Fonceur]

Originally Posted by gianpieroizzo

sageTCPServer/client=local.9260

Actually try using:

sageTCPServer/client=127.0.0.1:9260

Is it strictly necessary to set up the server as a service and run the client separately ?

No, that should work fine.

[gianpieroizzo]

No, it doesn't work, but I discovered that if the extender is switched on, I can control it correctly. If the extender is switched off, I can control the server on port 9261 !

This is the configuration:

sageTCPServer/client=127.0.0.1\:9260
sageTCPServer/debugOn=true
sageTCPServer/extender=0023a500025d.9261
sageTCPServer/server=9250

And here follows the log, it seems that port 9260 is not initialized.

gio 2/10 3:04:00.994 [SageTV@1f6f0bf] Calling start on plugin: SageTCPServer
gio 2/10 3:04:00.997 [SageTV@1f6f0bf] [[SageTCPServer]]: Start
gio 2/10 3:04:01.000 [SageTV@1f6f0bf] [[SageTCPServer]]: Debug messages on
gio 2/10 3:04:01.003 [SageTV@1f6f0bf] [[SageTCPServer]]: Read current settings
gio 2/10 3:04:01.006 [SageTV@1f6f0bf] [[SageTCPServer]]: Starting media server
gio 2/10 3:04:01.011 [SageTV@1f6f0bf] [[SageTCPServer]]: Starting extender
gio 2/10 3:04:01.014 [Thread-35@bce7c9] [[SageTCPServer-Media:9250]]: Starting a media server on socket 9250
gio 2/10 3:04:01.018 [SageTV@1f6f0bf] [[SageTCPServer-Player:9261]]: TCPServerPlayer
gio 2/10 3:04:01.021 [SageTV@1f6f0bf] [[SageTCPServer]]: Starting client
gio 2/10 3:04:01.024 [Thread-36@17b96a] [[SageTCPServer-Player:9261]]: Starting a player on socket 9261
gio 2/10 3:04:01.028 [SageTV@1f6f0bf] [[SageTCPServer]]: Subscribing to events

[Fonceur]

Originally Posted by gianpieroizzo

And here follows the log, it seems that port 9260 is not initialized.

Hmm, right, for the software client they only get started during the connection, which probably doesn't happen without the service mode... Could you attach the whole sagetv_0.txt?

[baudfather]

The new version has fixed whatever anomaly I was experiencing. Working as it should! I just wish RTSP worked behind a NAT, and the player supported FF/REW. Thanks for the help, and keep up the great work! I like how things are progressing. My only feature request would be to have a visible selection/highlight when an item is touched on the menus.

[gianpieroizzo]

here it is, thank you

[Fonceur]

Originally Posted by baudfather

I just wish RTSP worked behind a NAT, and the player supported FF/REW.

It should... You have the streaming port forwarded and all? Some carriers might be blocking some ports, which is why a few alternatives like 554, 8080, 7070 and so on are mentioned on the wiki.

My only feature request would be to have a visible selection/highlight when an item is touched on the menus.

In principle the Android version has the Haptic feedback, though maybe not everywhere.

[gplasky]

So I installed the TCP server thins morning into SageTV 7. I'm having some issues where nothing shows for the default port after the installation and also after a restart of SageTV. 9250 never shows. When I try to edit the field and put in 9250 I get a null exception java error. When I look in the .properties file it shows the entry for sagetcp server port but it is empty after the =sign. I'm trying an uninstall/reinstall now but shouldn't that show up in there by default and this should just work?

Gerry

[Fonceur]

Originally Posted by gplasky

So I installed the TCP server thins morning into SageTV 7.

Did you install it from the SageTV plugin interface?

When I try to edit the field and put in 9250 I get a null exception java error.

If you edit the sage.properties file directly, make sure that Sage and its service is stopped. Then if you could post the file before and after, as well as sagetv_0.txt file (enable the debugging if not already done).

I'm trying an uninstall/reinstall now but shouldn't that show up in there by default and this should just work?

It should... Someone tried running with just the extender port and it was forcing the server on 9250 anyway.

[gplasky]

Originally Posted by Fonceur

Did you install it from the SageTV plugin interface?

Yes-from the SageTV7 plugin interface.

Originally Posted by Fonceur

If you edit the sage.properties file directly, make sure that Sage and its service is stopped. Then if you could post the file before and after, as well as sagetv_0.txt file (enable the debugging if not already done).

Stopped and edited fine. The issue I'm having is in the SageTV interface. I had listed 3 extenders. I went to clear out all of them. I cleared them and hit entered. They then still existed.

Originally Posted by Fonceur

It should... Someone tried running with just the extender port and it was forcing the server on 9250 anyway.

When 9250 did not show up in the TCPserver configuration the taSage client did not show the server with the antenna icon. Once I edited the .properties file and manually put 9250 there TaSage then showed the antenna and it worked.

So I got the client on the Android Droid 2 working. I streamed a couple of recordings and there weren't bad but they weren't great. I'm testing different profiles now. Works with the Droid 2 default video player.

In the drop downs for the sorts and stuff I have white text on the silver dropdowns. Difficult to see.

Gerry

[Fonceur]

Originally Posted by gplasky

I had listed 3 extenders. I went to clear out all of them. I cleared them and hit entered. They then still existed.

Right, I've seen some funny stuff happening when trying to edit things from there...

Once I edited the .properties file and manually put 9250 there TaSage then showed the antenna and it worked.

Good.

I streamed a couple of recordings and there weren't bad but they weren't great. I'm testing different profiles now.

Right, the first few profiles are mostly aimed at 3g networks.

In the drop downs for the sorts and stuff I have white text on the silver dropdowns. Difficult to see.

Hmm, I'm using the default that is black text on a white background, but I guess some devices might have different default values. So I guess I'll need to make sure to force those values in. You get that for all the option menus from the dropdowns?

[gplasky]

Originally Posted by Fonceur

Hmm, I'm using the default that is black text on a white background, but I guess some devices might have different default values. So I guess I'll need to make sure to force those values in. You get that for all the option menus from the dropdowns?

Yes-all the silver dropdowns have white text.
Another suggestion-in settings where you can actually choose the profiles from 0-6. Any way to actually have some type of short text description of what they are. 15 frame, 30 frame, 3G low, med, high, Wi0fi low, med hi. Just something as a reference.

Droid 2 with Android OS 2.2
System version 2.3.20.A955Verizon.en US

Gerry

[Fonceur]

Originally Posted by gplasky

Another suggestion-in settings where you can actually choose the profiles from 0-6. Any way to actually have some type of short text description of what they are. 15 frame, 30 frame, 3G low, med, high, Wi0fi low, med hi. Just something as a reference.

Welll, in principle they are user configurable, so might not match what I would write about them... Though I could probably describe the default ones from the sageTCPServer plugin configuration, would that do?

[gplasky]

I'm just thinking something. When I go in the drop down to pick a profile all it has is 0,1,2,3,4,5,6. And a large white square area between the number and the radio button (green or blank.) So I don't need all the switch variables but something like

1 3G-low res
2 3G-med res
3 3G-hi res
4 Wi-Fi -Low res
5 Wi-Fi-Hi Res

You get the idea. Just something to reference. Even if the user changes it they can keep relative.

Gerry

[Fonceur]

Originally Posted by gplasky

Yes-all the silver dropdowns have white text.

OK, so that's due to the manufacturer/provider messing with the default style... You would get the same issue with any app using dropdown, unless they used a custom one, which I haven't really found how to do yet... Are you able to change theme/profile or such, maybe you can find one with more contrast.

[gplasky]

I'll see what I can find on the device. Nothing jumped out for me to change.

Gerry

[Fonceur]

Version 2.0.4

- Send the Favorites 25 or less at a time.
- Update to the Client handling.
- Update to the Remote control.

Originally Posted by gianpieroizzo

My SageTV server is configured WITHOUT using the service mode, and I'd like to control its GUI.

See if it's fixed in 2.0.4.

[Fonceur]

Version 2.0.5

- Force the first letter from the JSON strings to upper case.


The code that TiSageTV uses to produce the first letter section headers, crashes with lower cases... In the app I was forcing some to uppercase, but the ones I missed could still crash. By doing it systematically in SageTCPServer, that might slightly speed up the process on iOS devices and will prevent those crashes.