Plugin: SageTCPServer

[Fonceur]

SageTCPServer is an open source TCP interface to the SageTV API. The original project was started by Beelzerob and used by his SageTV driver for CQC. The source code is accessible through CVS at: SageTCPServer with some descriptions at http://talluscorp.com/mediawiki//ind...=SageTCPServer. Developers should consult: http://talluscorp.com/mediawiki//ind...for_developers .

Starting with version 1.8.8, the actual SageTVPlugin has been implemented, thus breaking the backward compatibility with SageTV 6.

Users of older versions should replace the line:

"load_at_startup_runnable_classes=sagetcpserver.StartServers"

by

"load_at_startup_runnable_classes="

The settings should be automatically imported, except for the software clients. Currently, if you change the server/extender/client settings, you will likely need to restart SageTV for them to take effect...

The compiled file has been attached as well as an XML file (remove the .txt) to load it locally.

[Fonceur]

Version 1.8.9

Fix: Some parameters were not properly read from sage.properties.


I don't plan on posting about every updates, but this one is important...

[PLUCKYHD]

Very nice work Fonceur maybe one day I will have time to take advantage of it

[RandyJohnson]

Prior to 1.8.8 the following parameter was in the sage configuration file:

sageTCPServer/clients=001d6a5ca886.9250,001d6a5dbda0.9251

Now I notice that the following lines are being used:

sageTCPServer/extender=9250,9251,9252,9253
sageTCPServer/server=9250

The problem that I am seeing now is that my bedroom remote (what was port 9250) is now controlling sage UI on the server and not the original extender.

Is there a fix for this problem?

I believe that you are assigning the first port to the sage "localhost" and then to the extenders alphabetically on the id.

Is there a UI to move the port numbers in the event you do not wish to use the default ports?

Thanks in advance...

Randy

[RandyJohnson]

Nevermind I found the configuration page.

That is the one thing that adds some inconsistance to plugins.

Some are configurable from the plugin manager and some via the configuration manager.

Oh well... I agree with Plucky the software is nice and easy to use and solved a number of issues with my prior approach.

Randy

[Fonceur]

Originally Posted by RandyJohnson

sageTCPServer/extender=9250,9251,9252,9253
sageTCPServer/server=9250

Ooops, I didn't think of checking the extenders port when setting up the server side. The extender values should have included the MacID, and not sure why that duplicated stuff...

[RandyJohnson]

You can modify the plugin parameters via the configuration manager.

But... twice I have keyed in the following for the extenders:

001d6a5ca886.9250,001d6a5dbda0.9251

Twice after I rebooted the server all that was displayed was:

9250,9251

So there is definitely a bug where the extender addresses are being stripped.

I checked the sage parameter file prior to the last reboot, and the "extenders" were setup correctly. After the reboot only 9250,9251 is showing up.

After further testing the stripping of the extender address occurs only if you attempt to edit the parameters again.

Randy

[RandyJohnson]

I also needed to remove the "server" port.

So the first time I just blanked out that parameter.

When I check sages' parameter file the port still showed 9250.

So then I changed the server port to 9260.

Then I checked sage's parameter file and the port still showed 9250.

Anyways...

I am going to see if I can manually set these parameters and see if they will hold.

Randy

The parameters hold on the reboot as long as you do not "touch" the configuration screen.

[Fonceur]

OK, try upgrading to 1.9.0, it should address those issues.

[Jason]

Originally Posted by Fonceur

SageTCPServer is an open source TCP interface to the SageTV API. The original project was started by Beelzerob and used by his SageTV driver for CQC. The source code is accessible through CVS at: SageTCPServer with some descriptions at http://talluscorp.com/mediawiki//ind...=SageTCPServer. Developers should consult: http://talluscorp.com/mediawiki//ind...for_developers .

Starting with version 1.8.8, the actual SageTVPlugin has been implemented, thus breaking the backward compatibility with SageTV 6.

Users of older versions should replace the line:

"load_at_startup_runnable_classes=sagetcpserver.StartServers"

by

"load_at_startup_runnable_classes="

Just FYI... Don't forget to remove the runnable_classes entries in both your server and client .properties files.

http://forums.sagetv.com/forums/show...07&postcount=9



-Jason

[Fonceur]

Originally Posted by Jason

Just FYI... Don't forget to remove the runnable_classes entries in both your server and client .properties files.

While it did complain in the SageTV log before I removed mine, that did not seem to be a big problem... Do you mean that SageAlert is making a big fuss about it?

I guess I could try to automatically update that line in sage.properties, though for the sageclient.properties that would still require human intervention...

[wayner]

So now that I have bought the iPad app and installed SageTCPServer, what should I have in sage.properties. I have now gotten rid of the parameters in the load_at_startup line, but what should I have? Currently here is what I have for SageTCP:

sageTCPServer/clients=local.9250,001a6afdb847.9262
sageTCPServer/debugOn=true
sageTCPServer/server=9250
sageTCPServer/streamingTranscodeOptions=soverlay,ab\=100,samplerate\=44100,channels\=2,acodec\=mp4a,vcodec\=h264,width\=352,height\=240,vfilter\="canvas{width\=352,height\=240,aspect\=16\:9}",fps\=29,vb\=200,venc\=x264{vbv-bufsize\=500,partitions\=all,level\=12,no-cabac,subme\=7,threads\=4,ref\=2,mixed-refs\=1,bframes\=0,min-keyint\=1,keyint\=50,trellis\=2,direct\=auto,qcomp\=0.0,qpmax\=51,deinterlace}
sageTCPServer/streamingTranscodeOptions1=fps\=15,vcodec\=mp4v,vb\=512,scale\=1,width\=352,height\=240,acodec\=mp4a,ab\=192,channels\=2,samplerate\=44100,deinterlace,audio-sync
sageTCPServer/streamingTranscodeOptions2=fps\=15,vcodec\=h264,venc\=x264{no-cabac,level\=12,vbv-maxrate\=300,vbv-bufsize\=1000,keyint\=75,ref\=3,bframes\=0},width\=352,height\=240,acodec\=mp4a,ab\=64,vb\=300,samplerate\=44100,audio-sync
sageTCPServer/streamingTranscodeOptions3=fps\=29,vcodec\=mp4v,vb\=512,scale\=1,width\=352,height\=240,acodec\=mp4a,ab\=192,channels\=2,samplerate\=44100,deinterlace,audio-sync
sageTCPServer/streamingTranscodeOptions4=fps\=29,vcodec\=h264,venc\=x264{no-cabac,level\=12,vbv-maxrate\=300,vbv-bufsize\=1000,keyint\=75,ref\=3,bframes\=0},width\=352,height\=240,acodec\=mp4a,ab\=64,vb\=300,samplerate\=44100,audio-sync
sageTCPServer/streamingTranscodeOptions5=fps\=29,vcodec\=mp4v,vb\=512,scale\=1,width\=576,height\=384,acodec\=mp4a,ab\=192,channels\=2,samplerate\=44100,deinterlace,audio-sync
sageTCPServer/streamingTranscodeOptions6=fps\=29, vcodec\=h264,venc\=x264{no-cabac,level\=12,vbv-maxrate\=300,vbv-bufsize\=1000,keyint\=75,ref\=3,bframes\=0},width\=576,height\=384,acodec\=mp4a,ab\=64,vb\=300,samplerate\=44100,audio-sync
sageTCPServer/streamingVLCOptions=-I dummy --one-instance --extraintf oldhttp --sout-keep --no-sout-rtp-sap --no-sout-standard-sap --rtsp-caching\=5000 -f
sageTCPServer/streamingVLCPath=C\:/Program Files/VideoLAN/VLC/vlc.exe
sageTCPServer/streamingVLCPort=-1
sageTCPServer/streamingVLCType=rtsp

Should any of this be deleted?

[Fonceur]

Originally Posted by wayner

sageTCPServer/clients=local.9250,001a6afdb847.9262

This one shouldn't be there, the update procedure should split it out into:

sageTCPServer/extender=001a6afdb847.9262
sageTCPServer/server=9250

I see the server line, but the extender one seems to be missing... Or maybe that wasn't copied with SageTV and its service shutdown.

[vividweb]

I don't think an extender can be added until has been turned on once.

[Fonceur]

Originally Posted by vividweb

I don't think an extender can be added until has been turned on once.

It depends, if there was an old configuration, it's supposed to get updated automatically. Though there might still be issues in the current implementation.

[RandyJohnson]

It looks like there is still a problem.

If you leave the "server" field blank and upon entering the configuration manager it will insert a port number.

Is this by design or a bug?

Randy

[Fonceur]

It is by design. I suspect that the persons only interested in controlling the UI's will be a small fraction.

[Fonceur]

This mostly affects any third-party developers that might be using this plugin... I am doing a major rewrite and will be dropping the text mode (ANS:TXT). Most stuff will still be sent as plain text like before, but you will have to decide between JSON or XML for the list of Recordings and such.

The major rewrite itself is to drop the need for multiple entry points (i.e. port 9250,9251) for simultaneous access (like say from an iPhone and an iPad). Instead you will simply have a server on port 9250 and connect any number of devices to it.

[George M]

[QUOTEThe major rewrite itself is to drop the need for multiple entry points (i.e. port 9250,9251) for simultaneous access (like say from an iPhone and an iPad). Instead you will simply have a server on port 9250 and connect any number of devices to it.[/QUOTE]

Does that mean then that on the taSAgetv configuration, the port should be the same for the server and the client? i.e.
Previously was Server:9250, Client:9260. Should that now be Server:9250, Client:9250?

[Fonceur]

Originally Posted by George M

Does that mean then that on the taSAgetv configuration, the port should be the same for the server and the client? i.e. Previously was Server:9250, Client:9260. Should that now be Server:9250, Client:9250?

No, it means that if you have 2 Android devices, both could be connected simultaneously to the pair 9250/9260, while currently one would connect to 9250/9260 and the other could connect to 9251/9261.

BTW, that change is not live yet, it will only be in SageTCPServer 1.9.1+.