OpenDCT: An open source digital cable tuner.

[ptaylor]

Thank you - That worked!

[Fuzzy]

Originally Posted by EnterNoEscape

You're probably doing nothing wrong. I think the container is scripted to force MediaServerConsumerImpl on you. It might be easier to change sagetv.device.<unique_id>.consumer=opendct.consumer.DynamicConsumerImpl to opendct.consumer.FFmpegTransSageTVConsumerImpl for each capture device.

I know that the docker scripts don't manipulate those values.

Alternatively, I believe you can set the dynamic consumer to use FFMPEG for channels 1-9999, or perhaps just for the channels that exhibit issues.

consumer.dynamic.channels.ffmpeg=1-9999

[EnterNoEscape]

Originally Posted by Fuzzy

Alternatively, I believe you can set the dynamic consumer to use FFMPEG for channels 1-9999, or perhaps just for the channels that exhibit issues.

consumer.dynamic.channels.ffmpeg=1-9999

You can do that, but if you decide later to use ATSC, that approach is no longer as simple. Also, the newest version of OpenDCT (0.5.28) uses the media server by default (and I don't intend to change that in the future), so the scripted changes are no longer needed for the container.

[Fuzzy]

Originally Posted by EnterNoEscape

You can do that, but if you decide later to use ATSC, that approach is no longer as simple. Also, the newest version of OpenDCT (0.5.28) uses the media server by default (and I don't intend to change that in the future), so the scripted changes are no longer needed for the container.

Okay, cool.. I'll try to push out a change to the template later this week that removes that bit of the script. I've been pretty absent from all things sage for the last couple months, so haven't even looked at things for a bit.

[EnterNoEscape]

Originally Posted by Fuzzy

Okay, cool.. I'll try to push out a change to the template later this week that removes that bit of the script. I've been pretty absent from all things sage for the last couple months, so haven't even looked at things for a bit.

I noticed I wasn't seeing you posting anything. You're usually so active I was actually a little concerned. Also by media server I mean it's using FFmpeg and streaming to the media server. It's not using the media server remuxer since it has some problems that may or may not bite some people.

[ranger]

I am setting up a 2nd SageTV server for testing and am having problems setting up the tuners. My original SageTV server has OpenDCT version 0.5.24 installed and working just great. The second SageTV server is on the same subnet and SageTV detects the tuners on my SageTV server running OpenDCT and sets them up, but when I try to actually tune and watch a channel, it doesn't work; just displays the "No Signal" message. Kind of stumped. Tried disabling the Windows Firewall on the OpenDCT machine to test and that didn't help. The channel scan performed in the new SageTV server seemed to work fine. It detected all the channels it should have.

Looked through the configuration file and found one line that seemed relevant but it appears to be correct (to me).

sagetv.use_automatic_loopback=false

the sage log was fairly clean, but I'm no expert on reading it. Anything you can point me at to troubleshoot would be appreciated.

Removed log clip and uploaded log in next post

[ranger]

Added this log file instead and removed log clip from previous post

[EnterNoEscape]

Originally Posted by ranger

I am setting up a 2nd SageTV server for testing and am having problems setting up the tuners. My original SageTV server has OpenDCT version 0.5.24 installed and working just great. The second SageTV server is on the same subnet and SageTV detects the tuners on my SageTV server running OpenDCT and sets them up, but when I try to actually tune and watch a channel, it doesn't work; just displays the "No Signal" message. Kind of stumped. Tried disabling the Windows Firewall on the OpenDCT machine to test and that didn't help. The channel scan performed in the new SageTV server seemed to work fine. It detected all the channels it should have.

Looked through the configuration file and found one line that seemed relevant but it appears to be correct (to me).

sagetv.use_automatic_loopback=false

the sage log was fairly clean, but I'm no expert on reading it. Anything you can point me at to troubleshoot would be appreciated.

Removed log clip and uploaded log in next post

The OpenDCT logs would confirm this, but I suspect your second server doesn't have the IP address 172.16.20.190 which is the IP address you are communicating with OpenDCT on. The reason you can't record anything is because the remote instance of OpenDCT cannot directly access your filesystem. This is especially true since you're not using UNC paths (but I'm not going to recommend that approach). What you want to do instead is enable the use of the SageTV media server (upload ID). Change the properties on your remote instance of OpenDCT in opendct.properties to the following values:

consumer.ffmpeg.upload_id_enabled=true
consumer.raw.upload_id_enabled=true

Be sure OpenDCT is stopped before changing those values or they will not take effect. If you have a local instance of OpenDCT installed and you're not seeing it, check the right side of the screen when you're adding a new capture device. You might notice a scrollbar. If you do try scrolling down.

[sflamm]

Not familiar with the SageTV Media server you are referring to:

What you want to do instead is enable the use of the SageTV media server (upload ID

For us uninitiated to it can you explain what/how this works? (I use UNC paths)

Thanks in advance.

[Fuzzy]

Originally Posted by sflamm

Not familiar with the SageTV Media server you are referring to:



For us uninitiated to it can you explain what/how this works? (I use UNC paths)

Thanks in advance.

In this context, using the 'uploadid' or 'media server' method causes openDCT to stream the content to the sagetv server asking for it, and lets the server write that stream to disk. This is in contrast to the default method that network encoders use, which is to have the encoder itself write the file directly. Using the upload ID allows the encoders to work without having direct access to the recording folder, and avoids potential permission issues.

[EnterNoEscape]

Upload ID is also the default for new OpenDCT installs, but if you have an old installation and you did not enable it, it will remain disabled.

[ranger]

Thanks. I took the opportunity to upgrade to 0.5.28 and set the values as shown. One quirk though, the parameter "consumer.raw.upload_id_enabled=" wasn't in the properties file so I just added it.

consumer.ffmpeg.upload_id_enabled=true
consumer.raw.upload_id_enabled=true

One other question comes to mind. I now have 2 SageTV servers using the same instance of OpenDCT. Any problems or caveats?

[sflamm]

The file being written directly to the UNC file path is more efficient performances -wise.

Also - for software clients the UNC will be required to see the common recording folder.

Why/when would it be better to use the Media Server approach ?

[EnterNoEscape]

Originally Posted by ranger

Thanks. I took the opportunity to upgrade to 0.5.28 and set the values as shown. One quirk though, the parameter "consumer.raw.upload_id_enabled=" wasn't in the properties file so I just added it.

I take it that you deleted opendct.properties when you upgraded. That's not necessarily a problem, but that's also why you didn't see that property. If you were using the raw consumer for anything that property would have appeared in the properties set to true. The default opendct.properties file has it already in there and set to true, but you only get that file on the first install or possibly after a reinstall if you also removed opendct.properties after you uninstalled. If you delete it, similar to SageTV, it re-builds the file with defaults. This is how it has always worked since the first version of OpenDCT.

Originally Posted by sflamm

The file being written directly to the UNC file path is more efficient performances -wise.

Also - for software clients the UNC will be required to see the common recording folder.

Why/when would it be better to use the Media Server approach ?

That's only true if the UNC path is a different server from your SageTV setup. If the UNC path is your SageTV box, it's more efficient to use the drives directly and use the media server. Also the media server is a lot more convenient in that you only need to make sure SageTV can correctly access your recording drives as opposed to making sure OpenDCT can access them too.

If you're using Comskip, the UNC path requirement is no longer needed since it currently uses SageTV API calls to get the contents of the EDL files. SageTV already uses the media server to playback your files on the software client regardless of if the UNC path is accessible.

There is one other reason to care. Sometime this year I will be committing some new code that will enable you to record shows with overlapping padding. It has been made compatible with older network encoders that don't use the media server, but that mode is not very efficient since it has to take what the network encoder wrote and copy it live for however many overlaps you have at the time. If you're using the media server, instead of writing to one file directly, SageTV can internally split the stream up and not need to read any files to make the needed copies. The new code will be optional and turned off by default since it is a very significant change, so you don't need to worry about anything suddenly not working the next time you upgrade.

[NetworkGuy]

Originally Posted by sflamm

Why/when would it be better to use the Media Server approach ?

Originally Posted by EnterNoEscape

There is one other reason to care. Sometime this year I will be committing some new code that will enable you to record shows with overlapping padding. It has been made compatible with older network encoders that don't use the media server, but that mode is not very efficient since it has to take what the network encoder wrote and copy it live for however many overlaps you have at the time. If you're using the media server, instead of writing to one file directly, SageTV can internally split the stream up and not need to read any files to make the needed copies. The new code will be optional and turned off by default since it is a very significant change, so you don't need to worry about anything suddenly not working the next time you upgrade.

Sorry, I am missing something. What do you guys mean when you talk about the media server approach? And as opposed to what?

[EnterNoEscape]

Originally Posted by NetworkGuy

Sorry, I am missing something. What do you guys mean when you talk about the media server approach? And as opposed to what?

Writing directly to the file.

[NetworkGuy]

Originally Posted by EnterNoEscape

Writing directly to the file.

Got it.

When upload_id is set to false, OpenDCT writes to the file instead of the SageTV media server.

I just just checked and mine is set to false. I am guessing that is because I originally installed OpenDCT about a year ago and the updates do not change the setting of the flag.

[EnterNoEscape]

Originally Posted by NetworkGuy

Got it.

When upload_id is set to false, OpenDCT writes to the file instead of the SageTV media server.

I just just checked and mine is set to false. I am guessing that is because I originally installed OpenDCT about a year ago and the updates do not change the setting of the flag.

Correct. There's no need to fiddle with it right now. If there becomes a higher need to fiddle with the setting I would change it as a result of the next configuration upgrade, but I generally don't force new defaults unless there's a good reason.

[sflamm]

If the UNC path is your SageTV box, it's more efficient to use the drives directly and use the media server.

I believe the MSFT RMI is smarter than that... if it is determines from the UNC path that the network location is localhost it simply uses local I/O (correct me if I'm wrong). In that case having OpenDCT use the UNC and therefore writing directly would be faster than handing the stream off to the SageTV server and then writing it locally from the server process.

SageTV already uses the media server to playback your files on the software client regardless of if the UNC path is accessible.

If this a change in SageTV 9? I thought previously the software clients were given the file location of media (recording path, video, photos, music ..) from the server as set on the server... if you set your media path to use an UNC then the location the software client would read from was the UNC.

Are none of these using the UNC path anymore?

What happens if you use a central phoenix meta data store?

If you're using the media server, instead of writing to one file directly, SageTV can internally split

Nice approach.

Comskip, the UNC path requirement is no longer needed since it currently uses SageTV API calls to get the contents of the EDL files

Speaking of Comskip... the native UI doesnt seem to understand the EDL files being written... is there a way to turn it on natively without adding a plugin?

[EnterNoEscape]

Originally Posted by sflamm

I believe the MSFT RMI is smarter than that... if it is determines from the UNC path that the network location is localhost it simply uses local I/O (correct me if I'm wrong). In that case having OpenDCT use the UNC and therefore writing directly would be faster than handing the stream off to the SageTV server and then writing it locally from the server process.

The traffic is likely being routed through the loopback interface, but it's still using SMB protocol to read/write the data. If you run something like WireShark you will see that it isn't really all that clever. You can even see a network traffic difference in Resource Monitor.

Originally Posted by sflamm

If this a change in SageTV 9? I thought previously the software clients were given the file location of media (recording path, video, photos, music ..) from the server as set on the server... if you set your media path to use an UNC then the location the software client would read from was the UNC.

This is not new. Most of us didn't really know how the media server worked until SageTV went open source. It looks like it might have been using the media server since whenever network encoder protocol v3 started to be used which looks like it was definitely prior to v9.

Originally Posted by sflamm

Are none of these using the UNC path anymore?

What happens if you use a central phoenix meta data store?

All FanArt related things as far as I know still need to be UNC if you want to use a common store. Comskip is the only one I know that was changed.

Originally Posted by sflamm

Speaking of Comskip... the native UI doesnt seem to understand the EDL files being written... is there a way to turn it on natively without adding a plugin?

Comskip is in no way a part of the default installation. You always need to install a plugin to get Comskip support.