OpenDCT: An open source digital cable tuner.

[sflamm]

I have the following setup:

SageTV 9 Server <-----> SageTV 9 Server Network Encoder
(main Server) <-----> (network encoder - slave)

The SageTV 9 Network Encoder is running OpenDCT and connecting to a BM3000-HDMI using USB-UIRT to tune.

The problem is that when configuring the SageTV 9 Server to use the BM3000-HDMI as a network encoder there is no way to tune! Tuner selection of USB-UIRT is NOT ALLOWED since the USB-UIRT is NOT Local. See attached image.

Is there a way to enhance the OpenDCT/USB-UIRT integration to allow for remote channel changes?

Thanks in advance.

[sflamm]

Managed to trick SageTV into using a USB-UIRT with the Network Encoder by temporarily installing it locally... (see attached image).

But even though the command is sent to change channel and received remotely it does NOT do anything on the remote Network Encoder:

23:52:34.899 [RawSageTVConsumerImpl-146:STB-1] INFO RawSageTVConsumerImpl - Raw consumer thread is now stopping.
23:52:34.900 [RawSageTVConsumerImpl-146:STB-1] DEBUG RawSageTVConsumerImpl - Bytes available to be read = 0
23:52:34.900 [RawSageTVConsumerImpl-146:STB-1] DEBUG RawSageTVConsumerImpl - Space available for writing in bytes = 2097151
23:52:34.900 [RawSageTVConsumerImpl-146:STB-1] INFO RawSageTVConsumerImpl - Raw consumer thread has stopped.
23:52:34.900 [SageTVRequestHandler-141:STB-1] DEBUG GenericHttpCaptureDevice - Capture device is now re-unlocked.
23:52:34.901 [SageTVRequestHandler-141:STB-1] DEBUG SageTVRequestHandler - Replied: 'OK'
23:52:34.901 [StoppingThread-147] DEBUG GenericHttpCaptureDevice - Stopping executable will be run in 15000 milliseconds.
23:53:50.441 [SageTVRequestHandler-149:Unknown] DEBUG SageTVRequestHandler - SageTV sent: 'BUFFER STB-1 HDMI|1253860965|4|83886080|\\nas\public\RecordedTV\STB1on1000259000HDMI-0.mpgbuf|Great-H.264'
23:53:50.441 [SageTVRequestHandler-149:STB-1] DEBUG GenericHttpCaptureDevice - Capture device is now re-locked.
23:53:50.441 [SageTVRequestHandler-149:STB-1] DEBUG SageTVRequestHandler - Starting buffered network encoder via upload ID '1253860965' to file name '\\nas\public\RecordedTV\STB1on1000259000HDMI-0.mpgbuf'.
23:53:50.441 [SageTVRequestHandler-149:STB-1] DEBUG BasicCaptureDevice - Consumer is was not in progress.
23:53:50.443 [SageTVRequestHandler-149:STB-1] INFO GenericHttpCaptureDevice - Starting the encoding for the channel '4' from the device 'STB-1' to the file '\\nas\public\RecordedTV\STB1on1000259000HDMI-0.mpgbuf'...
23:53:50.443 [SageTVRequestHandler-149:STB-1] INFO GenericHttpCaptureDevice - Configuring and starting the new SageTV producer...
23:53:50.444 [SageTVRequestHandler-149:STB-1] INFO NIOHTTPProducerImpl - Connecting to source using the URL 'http://10.0.0.40/0.ts'
23:53:50.464 [SageTVRequestHandler-149:STB-1] DEBUG NIOHttpDownloader - HTTP response: 'HTTP/1.1 200 OK', 'Content-type: application/octet-stream', 'Cache-Control: no-cache', 'Server: Box',
23:53:50.464 [SageTVRequestHandler-149:STB-1] INFO GenericHttpCaptureDevice - Configuring and starting the new SageTV consumer...
23:53:50.464 [NIOHTTPProducerImpl-150:STB-1] INFO NIOHTTPProducerImpl - Producer thread is running.
23:53:50.464 [NIOHTTPProducerImpl-150:STB-1] DEBUG NIOHTTPProducerImpl - Thread priority is 9.
23:53:50.470 [SageTVRequestHandler-149:STB-1] DEBUG BasicCaptureDevice - Consumer is was not in progress.
23:53:50.471 [SageTVRequestHandler-149:STB-1] DEBUG SageTVRequestHandler - Replied: 'OK'
23:53:50.471 [RawSageTVConsumerImpl-151:STB-1] DEBUG RawSageTVConsumerImpl - Thread priority is 8.
23:53:50.471 [RawSageTVConsumerImpl-151:STB-1] INFO RawSageTVConsumerImpl - Raw consumer thread is now running.
23:53:50.471 [RawSageTVConsumerImpl-151:STB-1] INFO RawSageTVConsumerImpl - Waiting for PES start byte...
23:53:50.545 [RawSageTVConsumerImpl-151:STB-1] DEBUG VideoUtil - PAT packet found at index 1504.
23:53:50.545 [RawSageTVConsumerImpl-151:STB-1] INFO RawSageTVConsumerImpl - Raw consumer is now streaming...
23:54:08.274 [SageTVRequestHandler-149:Unknown] DEBUG SageTVRequestHandler - SageTV sent: 'STOP STB-1 HDMI'
23:54:08.274 [SageTVRequestHandler-149:STB-1] DEBUG GenericHttpCaptureDevice - Stopping encoding...
23:54:08.275 [SageTVRequestHandler-149:STB-1] DEBUG HTTPCaptureDeviceServices - Stopping producer thread...
23:54:08.275 [SageTVRequestHandler-149:STB-1] DEBUG HTTPCaptureDeviceServices - Waiting for producer thread to stop...
23:54:08.275 [NIOHTTPProducerImpl-150:STB-1] DEBUG NIOHTTPProducerImpl - The socket has been closed.
23:54:08.275 [NIOHTTPProducerImpl-150:STB-1] INFO NIOHTTPProducerImpl - Producer thread has stopped.
23:54:08.275 [SageTVRequestHandler-149:STB-1] DEBUG BasicCaptureDevice - Stopping consumer thread...
23:54:08.275 [SageTVRequestHandler-149:STB-1] DEBUG BasicCaptureDevice - Waiting for consumer thread to stop...

[EnterNoEscape]

Originally Posted by sflamm

I have the following setup:



The SageTV 9 Network Encoder is running OpenDCT and connecting to a BM3000-HDMI using USB-UIRT to tune.

The problem is that when configuring the SageTV 9 Server to use the BM3000-HDMI as a network encoder there is no way to tune! Tuner selection of USB-UIRT is NOT ALLOWED since the USB-UIRT is NOT Local. See attached image.

Is there a way to enhance the OpenDCT/USB-UIRT integration to allow for remote channel changes?

Thanks in advance.

There isn't any way to do that without adding support for SageTV tuning plugins directly to OpenDCT which I do not have any intentions of doing because it would be really awkward to configure them and it would be a fair amount of effort for something that's rarely needed.

[sflamm]

How is this different from a previous configuration that worked:

1. SageTV Server as network encoder
2. HDPVR local to Network Encoder (attached to STB)
3. firewire tuning local to Network Encoder (attached to STB)

The command to start the video source went to the Network Encoder which in turn:

a) started the video source
b) tuned the channel with the tuning plugin

Why can't this continue to happen - with the remote SageTV Network coder streaming the source (essentially a proxy)? The source does not need to come directly from OpenDCT.

[EnterNoEscape]

Originally Posted by sflamm

How is this different from a previous configuration that worked:

1. SageTV Server as network encoder
2. HDPVR local to Network Encoder (attached to STB)
3. firewire tuning local to Network Encoder (attached to STB)

The command to start the video source went to the Network Encoder which in turn:

a) started the video source
b) tuned the channel with the tuning plugin

Why can't this continue to happen - with the remote SageTV Network coder streaming the source (essentially a proxy)? The source does not need to come directly from OpenDCT.

I don't think SageTV will let you hop around like that. It will just go straight to the network encoder. I'm not sure what that would look like if you accessed a network encoder through a network encoder, but it might be hard for SageTV to decipher what's going on.

[sflamm]

The start of the video source is supposed to be sent to the remote SageTV Server acting as a Network Encoder (enable_encoding_server = true). The remote SageTV Server is the one that tunes and gets the local video source (local to the remote SageTV Server) and returns the video stream.

This works perfectly with other sources e.g. HDPVR with USB-UIRT

The problem here is the SageTV Server is not getting the video stream from the remote SageTV Server acting as a Network Encoder. Instead it is getting video directly from OpenDCT (it should not). This is NOT following the design of the SageTV Network Encoder (which has previously always worked).

Try what I am saying - works perfectly for other video sources local to the remote SageTV Network Encoder. The issue is you are retrieving the video source directly from OpenDCT and not from the Network Encoder which is the remote SageTV Server with the property enable_encoding_server = true

[sflamm]

See attached image of video sources:

1. Both sources are discovered from the remote SageTV Server with the property enable_encoding_server=true

2. The HDPVR entry is correct - Hauppague HD PVR Capture Device #2 on HDSTB:6969 points to the remote SageTV Server acting as a Network Encoder (HDSTB has IP: 10.0.0.25)

The request to start the video source is directed to the HDSTB:6969 and it a) invokes the tuner assigned (USB-UIRT in this case) and b) start the video source (HDPVR in this case)

There are can/be multiple... there is also Hauppague HD PVR Capture Device #1 on HDSTB:6969

[two remote HDPVRs]

3. The STB-2 entry is NOT correct. It says the video source is STB-2 on 10.0.0.25:9000 (same as "STB-2 on HDSTB:9000") - which points directly to the OpenDCT server running on HDSTB (ip:10.0.0.25).

That should be advertised similarly to the HDPVR as a source on HDSTB.. it should be something like: STB-2 Capture Device #1 on HDSTB:6969

[sflamm]

On the remote SageTV Server acting as a Network Encoder (enable_encoding_server=true) there is a video source:

STB-2 on 10.0.0.25:9000 HDMI
Tuner Control: USB-UIRT Transceiver PaceRNG150-1

On the SageTV Server using the SageTV Network Encoder there SHOULD BE A SOURCE:

STB-2 on 10.0.0.25:6969 HDMI

The same way there is a video source on the SageTV Server for the remote HDPVR:

Hauppague HD PVR Capture Device #1 on HDSTB:6969

The video source local to the remote SageTV Server acting as Network Encoder is:

Hauppague HD PVR Capture Device #1
Tuner Control: USB-UIRT Transceiver PaceRNG150-1

[EnterNoEscape]

You will not see it on port 6969. The reason is that the SageTV instance acting as a network encoder will not re-advertise devices that are already loaded as network encoders from it's own perspective. It would likely end up being a endless loop between the two servers. What you are trying to do is not going to work.

[sflamm]

Shouldn't be a loop at all...

The named video source from the Network Encoder represents a video stream.
The video stream is obtained by whatever means from the Network Encoder. The Network Encoder is the only one who knows how the stream is obtained. It can obtain it from OpenDCT or wherever. And tune it using whatever plugin is available. The Network Encoder gets the video stream and simply proxies it back. Nothing more.

The command to the Network encoder is (same as always): start stream / channel, stop stream

This works today for local sources to the remote Network Encoder.

Why would the origin of the video stream be exposed? And how is that possibly a loop?

[sflamm]

1. Providing Network Encoders: enable_encoding_server=true
2. Discovery of Network Encoders: network_encoder_discovery=true

These are completely separate features.

As detailed in Appendix G of the SageTV manual.

To date - it has always been possible to do these independently.

#1 takes any source that is configure locally (by whatever means) and publishes it as a network encoder

#2 allows discovery of sources that are NOT configured locally


Use of #1 by #2 never entails a loop - as the source is ONLY referred to by name.


This is the whole point of SageTV Server acting as a Network Encoder - locate it locally to a source to allow the Network Encoder to tune and stream the local source. Because it is local whatever means are available to tune and capture can be used without the remote consumer being aware at all.

[sflamm]

In lieu of this - is it possible for someone to provide a mechanism to remotely invoke a tuning plugin that is installed in SageTV?

With that we could make it easy to combine OpenDCT with tuning plugins...

tuningPluginName Channel=channel#

For .ir the Tuning Plugin can be configured to use different .ir files for each zone (as it is done today in USB-UIRT).

This would be simply a REST invocation of the tuningPlugin by Name passing the channel...

[Fuzzy]

Why are you using a SageTV Network Encoder to talk to a Network Encoder? Just connect directly to openDCT.

[Tiki]

Originally Posted by Fuzzy

Why are you using a SageTV Network Encoder to talk to a Network Encoder? Just connect directly to openDCT.

I'm going to guess that his real issue is that he wants multi-zone USBUIRT support in Linux/unraid.

I'm guessing that he is running his primary Sage server in Linux and then wants to use a second instance of Sage on Windows as a network encoder so it can do the multi-zone USBUIRT. This would work if he was using encoders that were local to that second Sage instance (like HDPVR or Colossus).

[sflamm]

Correct - my primary server needs to be different from the secondary (configured as a Network Encoder).

As a general configuration having a Network Encoder with local resources and tuning is VERY helpful... and really the point of a Network Encoder.

Why is it a problem to have a Network Encoder that uses Network Encoders? The Client of the Network Encoder doesnt see how the video sources of the Network Encoder are configured.

[sflamm]

It would be incredibly useful if there was a plugin to SageTV that allowed the Tuning Plugins to be called remotely through a REST API.

By having that in combination with OpenDCT almost all scenarios can be address for sources/tuning.

[Monedeath]

Originally Posted by EnterNoEscape

That's correct, it's the total.

Well, pulled the trigger on it this weekend while chasing everything else. Seems to be working very well, much less painful than SageDCT was to work with.

Also liked it when I fired up SageTV on the planed replacement server and found the OpenDCT tuners advertising on the network. Not sure that's an intended default, but I'm not complaining, saves me from trying to figure out how to turn it on.

Originally Posted by EnterNoEscape

The reason that it's difficult has nothing to do with frequency. It has to do with the fact that network encoders do not communicate errors or messages directly to SageTV. The only way you get network encoder "messages" in SageTV is if the network encoder isn't responding or recording what they have been told to record. The route that I would likely take is sagex which I really don't want to do because it would make a helpful feature require stored passwords and it would add more steps to using OpenDCT. Maybe when I implement network encoder protocol v4 I'll add messaging.

Well, one thing that does seem to exist in the current SageTV Protocol that would be a nice include on OpenDCT is this:

When SageTV directly communicates with the HDHomeRun encoders, it can get signal strength data from it. However, once OpenDCT is included in the loop, signal strength reverts to 100%.

And in that respect, if you just gave us the option of having Signal Strength data passed to SageTV, then my previous "wish list" item can instead be addressed as a plug-in on SageTV by having it check and record signal strengths on a given tuner whenever it records a program.

Of course, Sage just gives a raw % indicator from what I've seen via the UI. I imagine there is a more useful number you could get to on the network tuners, but that's deep wish list stuff.

[sflamm]

I've created a working powershell script that can tune the USB-UIRT channels remotely:

Param([string]$TunerNumber, [string]$ChannelNumber)


$ChannelNumberArray = $ChannelNumber.ToCharArray()

$TuningCommand = "http://10.0.0.25:8080/sagex/api/?c=TransmitCommandUsingInfraredTuningPlugin"
$TuningPlugin = "&1=USB-UIRT Transceiver"
$TuningPluginPort = "&2=0"
$BaseRemoteName = "PaceRNG150"
$RemoteName = "&3=" + $BaseRemoteName + "-" + $TunerNumber
$RepeatFactor = "&5=2"

$Username = "sage"
$Password = "frey"

$Headers = @{ Authorization = "Basic {0}" -f [Convert]::ToBase64String([Text.Encoding]::ASCII.GetBytes(("{0}:{1}" -f $Username,$Password))) }

$Output = "output.txt"


foreach ($digit in $ChannelNumberArray) {

#Write-Output ********

$CommandName = "&4=$digit"
$Uri = $TuningCommand +  $TuningPlugin + $TuningPluginPort + $RemoteName + $CommandName + $RepeatFactor

Write-Output uri:$Uri

Invoke-RestMethod -Uri $Uri -Headers $Headers -Outfile $Output

This can be used with OpenDCT for the tuning executable (adjust parameter names accordingly)

sagetv.device.sagetv.device.<unique_id>.tuning_executable=/path/to/tuning/script --device=0 --tune=%c%

[EnterNoEscape]

Originally Posted by Monedeath

Well, one thing that does seem to exist in the current SageTV Protocol that would be a nice include on OpenDCT is this:

When SageTV directly communicates with the HDHomeRun encoders, it can get signal strength data from it. However, once OpenDCT is included in the loop, signal strength reverts to 100%.

And in that respect, if you just gave us the option of having Signal Strength data passed to SageTV, then my previous "wish list" item can instead be addressed as a plug-in on SageTV by having it check and record signal strengths on a given tuner whenever it records a program.

Of course, Sage just gives a raw % indicator from what I've seen via the UI. I imagine there is a more useful number you could get to on the network tuners, but that's deep wish list stuff.

The network encoder doesn't provide that information. When using a network encoder, SageTV automatically just shows 100%. That kind of addition is really low on my list of things to do, but it could be added to the 4.0 protocol I will be implementing at some point in time. I always kind of wondered why it didn't ask the network encoder instead of just showing 100%.

[EnterNoEscape]

Originally Posted by sflamm

I've created a working powershell script that can tune the USB-UIRT channels remotely:

Param([string]$TunerNumber, [string]$ChannelNumber)


$ChannelNumberArray = $ChannelNumber.ToCharArray()

$TuningCommand = "http://10.0.0.25:8080/sagex/api/?c=TransmitCommandUsingInfraredTuningPlugin"
$TuningPlugin = "&1=USB-UIRT Transceiver"
$TuningPluginPort = "&2=0"
$BaseRemoteName = "PaceRNG150"
$RemoteName = "&3=" + $BaseRemoteName + "-" + $TunerNumber
$RepeatFactor = "&5=2"

$Username = "sage"
$Password = "frey"

$Headers = @{ Authorization = "Basic {0}" -f [Convert]::ToBase64String([Text.Encoding]::ASCII.GetBytes(("{0}:{1}" -f $Username,$Password))) }

$Output = "output.txt"


foreach ($digit in $ChannelNumberArray) {

#Write-Output ********

$CommandName = "&4=$digit"
$Uri = $TuningCommand +  $TuningPlugin + $TuningPluginPort + $RemoteName + $CommandName + $RepeatFactor

Write-Output uri:$Uri

Invoke-RestMethod -Uri $Uri -Headers $Headers -Outfile $Output

This can be used with OpenDCT for the tuning executable (adjust parameter names accordingly)

sagetv.device.sagetv.device.<unique_id>.tuning_executable=/path/to/tuning/script --device=0 --tune=%c%

Nice work there. Thanks for sharing.