Sage 9 on Ubuntu 16.04 w/OpenDCT

[EnterNoEscape]

Originally Posted by chairmanmao

I could've sworn I had opendct not running when I ran console-only...but maybe not.

So I redid everything, starting with deleting all the tuners from Sage.properties.

I made absolutely positively sure that opendct wasn't running. Nor was sage. And then ran console-only.

It appeared to run fine...but the same old same old: same "unusual" tuners listed in Sage, same too long channel scan, and no video.

I'm beginning to think I'm trapped in hell, where even when you follow the instructions nothing works

Other thoughts? Is there an alternative to opendct that runs on Linux? I'm about ready to throw in the towel on this experiment, 'cause nothing seems to work. Or provide any information on why it isn't working, either

Perhaps there's an order of operations problem here. Try this:

1) Stop the OpenDCT service.
2) Stop the SageTV service.
3) Start the OpenDCT service.
4) Wait a minute.
5) Start the SageTV service.

If SageTV is in fact able to talk to OpenDCT, you will see in opendct.log lines that actually say that it sent PROPERTIES (it will be in caps) to the SageTV server. One other thought I have is that if you have enabled ufw, to stop and disable it for now in case the firewall is causing some problems.

[chairmanmao]

Well, those are easier next steps than what I had in mind

I'll give it a shot.

[Fuzzy]

Also, are you scrolling down in the list of tuners in sage? I know it sounds simple, but sage DOES have native HDHomeRun capability built-in, so it WILL discover the HDHomeRun devices on your network (which is what you are seeing in your screenshot). They are not removed from the list when the OpenDCT handled devices are added, so you likely need to scroll down past the edge of the single screen to see the OpenDCT entries.

[chairmanmao]

SUCCESS!!!


Fuzzy, have a beer, on me. Or a glass of wine, whichever is your preference!

It turns out the "problem" was simply that I didn't scroll down the list of available tuners in Sage to find the ones being offered by OpenDCT. I happen to have two Primes, which collectively offer 6 tuners. Which just happens to fill up one entire screen within Sage's UI.

Since I could see "all" of the available tuners on that one page, it never occurred to me to notice that the scroll bar indicated there were other entries available further down.

I imagine this won't be a common problem. But it might be worthwhile to mention it in the OpenDCT docs (I don't recall seeing it there). Simply knowing that you have to skip past the Sage-identified tuners to the OpenDCT tuners would be very helpful. And if that's already in the docs, even more my bad than things already are.

Anyway, now I'm off to check recording capability, playback, etc.

Thanx, everyone, for your advice and assistance.

- Mark

[Wrx4me]

OMG Glad you figured it out, I was looking through my setup this evening to see if there was anything else I could find to help out.