Plugin: SageTCPServer

[baudfather]

I'm not too sure what happened, but the latest version of TCPserver broke my system - upon startup, the Sagetv service and client pin the CPU, then after 1 minute, the service crashes. I managed to uninstall the TCPserver plugin, and all seems well again. Tried several variations of editing sage.properties, resetting config settings for TCPserver, no luck. Not too sure what happened.

Here's the settings from sage.properties:
sageTCPServer/client=/127.0.0.1\:9260
sageTCPServer/debugOn=true
sageTCPServer/extender=
sageTCPServer/server=9250
sageTCPServer/streamingRTSPType=mp4a-latm
sageTCPServer/streamingTranscodeOptions=fps\=15,vcodec\=mp4v,vb\=512,scale\=1,width\=352,height\=240,acodec\=mp4a,ab\=128,channels\=2,samplerate\=44100,deinterlace,audio-sync
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 --no-sub-autodetect-file --one-instance --rtsp-caching\=5000 -f
sageTCPServer/streamingVLCPath=C\:/Program Files/VideoLAN/VLC/vlc.exe
sageTCPServer/streamingVLCPort=554
sageTCPServer/streamingVLCType=rtsp

Any ideas?

[Fonceur]

Originally Posted by baudfather

Any ideas?

There is nothing wrong with those settings, so I would need the various sagetv_*.txt log files to see what is going on...

Also make sure there is no sageTCPServer.StartServers in the line "load_at_startup=...".

[baudfather]

Originally Posted by Fonceur

There is nothing wrong with those settings, so I would need the various sagetv_*.txt log files to see what is going on...

Also make sure there is no sageTCPServer.StartServers in the line "load_at_startup=...".

The system's a bit active tonight, but I'll try it again tomorrow... Should I just pm you the log file? The load_at_startup has already been cleared.

[baudfather]

Here's the logfiles... It seemed to be working ok for a few mintues, then the server crashed again... Any help is much appreciated!

[Fonceur]

Originally Posted by baudfather

Any help is much appreciated!

Well, I'm seeing that you have launched many VLC streaming in a short time, so if you are using a version with the "one instance" busted, like VLC 1.10, you might have had 6+ simultaneous copies of VLC eating away all the CPU at the same time, which could probably crash the server...

[baudfather]

Checked that, I'm using 1.1.5, and only one instance is running, and only at ~35%. The strange thing is that yesterday I wasn't even trying to stream (not even connected with TaSageTV) and the server would crash.

[Fonceur]

Well, SageTCPServer 2.0.0 should be ready in the next few days, it is a major rewrite, so might not be experiencing whatever is going on currently in your system...

[Halstead]

Originally Posted by baudfather

I'm not too sure what happened, but the latest version of TCPserver broke my system - upon startup, the Sagetv service and client pin the CPU, then after 1 minute, the service crashes.

I'm having exactly the same problem! The SageTV service seems to crap out after a minute or so, or any time I go to the plugin list. As soon as I turned the plugin off (enabled=false), everything was fine again.

Logs attached.

[baudfather]

Originally Posted by Fonceur

Well, SageTCPServer 2.0.0 should be ready in the next few days, it is a major rewrite, so might not be experiencing whatever is going on currently in your system...

Sweet! Looking forward and keeping fingers crossed!

[Fredo44]

same issue here.
after 1 minute or so the server crashes. Does not leave enough time to manually navigate to plugin-settings to de-activate. So, this had to be done manually ind the propoerties-file. As soon as plugin is disabled, everything is fine.
looking forward to next release


...should you need logs, kindly let me know.

[Fonceur]

Version 2.0.0

- MAJOR UPDATE
- Single access port for each server/client/extender.
- Mostly event driven instead of using polling.
- Can name the clients/extenders.


If you were using multiple devices/plugins/drivers to connect the SageTCPServer, before you had to duplicate ports like local.9250,local.9251, now you don't. Since a single port will be used, you might need to reconfigure some extra devices/plugins/drivers.

Technically, I still had more testing to do, but I'm releasing it earlier due to issues reported with 1.9.0...

[Fredo44]

yes, that new release seems to do a good job.
everything is working like a charm .
Thumbs up ! Good work !!
Thank you

[RandyJohnson]

We are using sageTCP to control extenders via TCP/IP.

Under the pre 2.0 system we determine which extender to control by talking to the specific port (i.e. 9250 or 9251).

If only 1 port is being used how do we indicate which extender we want to control if both are using the same port?

Thanks in advance...

Randy

[Fonceur]

Originally Posted by RandyJohnson

If only 1 port is being used how do we indicate which extender we want to control if both are using the same port?

It's still one port for each SageTV client/extender/server... The change is only for people trying to connect multiple devices/drivers/plugins to a single extender, like say from one iPhone and one iPad...

[Fonceur]

Version 2.0.1

- Fix: the keep alive was broken.
- Fix: original client status was not sent.

[TR3 Driver]

First off, let me say I love this plugin. I'm on Windows Home Server and had it working, but unfortunately had to re-install my operating system and therefore had to re-install and reconfigure everything in Sage. Since then I have updated all of the plugins and have everything working except the streaming. Each time I try I get the message: "Cannot connect to server".

I am attaching my properties file as well as sagetv_0.txt. I'm sure there's something simple that I just cannot find. Would you mind looking this over when you have a chance and let me know what you think?

Thanks.

[Fonceur]

Originally Posted by TR3 Driver

Since then I have updated all of the plugins and have everything working except the streaming.

Off hand, the following line got truncated, so stop SageTV and its service mode, then delete the line to get back the default one...

sageTCPServer/streamingTranscodeOptions=vcodec\=h264,venc\=x264{no-cabac,level\=12,

[George M]

Thanks for trying to simplify this program.
I have been using it for both CQC and an adroid phone. Now I can only get one to work at a time. It is probably something simple that I am not doing on my end but if you could clarify a little.

I have one extender. I want to control that extender with both an android phone and CQC. I have:
Server on port 9250.
The extender is 9260.

The android phone has
server:9250
client:9260

If I have CQC on 9250, it will not work
If I have CQC on 9260 it will work - but the android phone will not work.

I tried to set the Server as 9250,9251 and then connect CQC to 9251, but again it will not control the extender.

In this case how should CQC be set up?

Thanks

[Fonceur]

Originally Posted by George M

Server on port 9250.
The extender is 9260.

The android phone has
server:9250
client:9260

If I have CQC on 9250, it will not work
If I have CQC on 9260 it will work

You might need to restart SageTV, as it sounds like it's still running an older copy of SageTCPServer... It should work as you tried.

[George M]

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