Network Encoder No Signal

[mechling-burgh]

I'm trying to setup a network encoder in sage 9 so I can have a sage occurrence running in windows 10 for my HDPVR2 and then setup a VM of sage linux to run opendct and the HD Homeruns and have more than the 1024 java limit for java 32 bit. I got the two sage installs working and I got the network encoders setup and the sage Linus box sees the HDpvr network encoder, I setup a video source without any problems. The problem occurs when I try and record a channel. It selects the HDpvr and changes the channel with out problems but then all I get is a "no signal". I then setup the HD Homerun as a network encoder and got the same error message for both. I also tried sage windows to sage windows and get the same error message. So I have ruled out the linux being the problem, I opened the port on the sage server and client but still get the no signal.

Does anyone have any ideas why the no signal and has anyone setup the network encoder in sage 9 with an HDpvr

[mechling-burgh]

Was doing some more work on this and I can get the network encoder to work when using the preview pane in channel setup but when I use the program guide and select the same channel I get the no signal error. I increased the encoder_delay to 4000 and still get the no signal error. Has anyone else got network encoders working in SageTV 9 from another server?

Thank You

[BobPhoenix]

Originally Posted by mechling-burgh

Was doing some more work on this and I can get the network encoder to work when using the preview pane in channel setup but when I use the program guide and select the same channel I get the no signal error. I increased the encoder_delay to 4000 and still get the no signal error. Has anyone else got network encoders working in SageTV 9 from another server?

Thank You

Had the same exact problem myself. I did get it to work (sort of anyway) but I had to mix SageTV versions and I ultimately went another route. Basically I setup the encoding server on SageTV V7.1.9 Windows to a SageTV V9 Linux. It was able to record but the recordings had problems. It looked like what you get when you have a bad signal but it easily COULD have been actual signal loss problems. Anyway you might try a Windows V7.1.9 encoding server to a Linux V9 master server and see what results you get.

[mechling-burgh]

You are correct there is a problem with SageTV version 9. I uninstalled all of sagetv on my windows test computer and reinstalled version 7 on it it. I then installed the video source and made sure it worked. I then started the the VM of Linux on another computer and was able to use the SageTV Client version 9 to connect to the SageTV version 9 server running on the vm Linux. I added the encoder from the version 7 and it worked perfectly. I then upgrade to Version 9 on the windows computer and the network encoder got the no signal error, but I could still preview in the channel setup. Not sure if its a windows version 9 problem only since I have not tried it with a Linux server with encoder shared. That is the next test I guess. I hope this helps anyone trying to setup a Linux server but has to run a windows machine to to use tv cards that don't work in Linux.

[Fuzzy]

This is interesting. The network encoder bits of the code have been touched quite a bit, but I think primarily on the receiving end, not the serving end. This will definitely need to be looked at. Any way we can get some logs posted from these configurations? Ideally with network_encoder_debug=true in each installs sage.properties (the linux server, as well as the windows encoding server).

[BobPhoenix]

Hopefully mechling-burgh can get those for you. I no longer have a setup that I can do that. At least for another week or two potentially. Would have to setup a server for a Windows network encoding server and I don't have a tuner currently available. But I will attempt to get a log if it is necessary.

[mechling-burgh]

Okay here are the logs I hope they help. One is Version 7 (PC) encoder to sage version 9 Linux Server. The other is version 9 encoder (PC) to the same Sage Linux server. On the v9 to v9 I tried to watch the channel and got no signal. Then I went to the Channel setup and previewed the channel where it it would work. I have attached a zip file with the logs.

[Fuzzy]

Originally Posted by mechling-burgh

Okay here are the logs I hope they help. One is Version 7 (PC) encoder to sage version 9 Linux Server. The other is version 9 encoder (PC) to the same Sage Linux server. On the v9 to v9 I tried to watch the channel and got no signal. Then I went to the Channel setup and previewed the channel where it it would work. I have attached a zip file with the logs.

That's very helpful, I may have found the issue (discussion here:https://github.com/google/sagetv/issues/159) - but I can't whip up the fix right now. If someone else can't get to it before me, I'll try to get a fix submitted later in the week. Would you be able to test out the fix if myself or someone else gets you a test sage.jar file for your encoding server?

[KarylFStein]

Originally Posted by Fuzzy

That's very helpful, I may have found the issue (discussion here:https://github.com/google/sagetv/issues/159) - but I can't whip up the fix right now. If someone else can't get to it before me, I'll try to get a fix submitted later in the week. Would you be able to test out the fix if myself or someone else gets you a test sage.jar file for your encoding server?

The fix idea you gave doesn't compile, but this does (ripped from the BUFFER section):

long bufferSize = Long.parseLong(toker.nextToken());

I don't have network tuners set up yet, (been hoping for a 64-bit Windows version), but can supply a JAR if someone wants it for testing.

[mechling-burgh]

ya I can set it up I saved the directories as V9 and V7 so I can switch between them for testing.

[Fuzzy]

Originally Posted by KarylFStein

The fix idea you gave doesn't compile, but this does (ripped from the BUFFER section):

long bufferSize = Long.parseLong(toker.nextToken());

I don't have network tuners set up yet, (been hoping for a 64-bit Windows version), but can supply a JAR if someone wants it for testing.

and see, now that's why i didn't submit it directly on the website without testing.. ;-)... yeah, it would need to be converted to long. I fixed it in the issue tracker so no-one else will be made aware of my now publicized bafoonery.