SageTV HDHomerun Prime + SageDCT

[gabrielcab]

I think i'll need a simple idiot proof guide as no matter what I settings I change on my firewall I cannot get signal. I even tried disabling the firewall with no luck either.

[gabrielcab]

Hello,

I'm having problems configuring my HDHomerun with SageDCT. What firewall change I need to make to make this work? I'm getting a "no signal" message on sagetv live tv. Do I need to install a codec to view live tv?

[nyplayer]

Check out this thread.

http://forums.sagetv.com/forums/show...postcount=1360

[gabrielcab]

Originally Posted by nyplayer

Check out this thread.

http://forums.sagetv.com/forums/show...postcount=1360

TYVM.

When I generate the property file on SageDCT, should I choose to create the property txt using the "localhost 127.0.0.1" or the current IP of the HDHomerRun Prime?

[nyplayer]

localhost if SAGEDCT is running on the Sage Server this has nothing to do with the HD Homerun IP.

[cupp]

I might be doing this wrong but I changed the host to the ip of the computer using sage.

from

mmc/encoders/123456970/encoding_host=127.0.0.1\:6970

to

mmc/encoders/123456970/encoding_host=192.168.1.132\:6970


this worked for me.

[nyplayer]

Originally Posted by cupp

I might be doing this wrong but I changed the host to the ip of the computer using sage.

from

mmc/encoders/123456970/encoding_host=127.0.0.1\:6970

to

mmc/encoders/123456970/encoding_host=192.168.1.132\:6970


this worked for me.

If SAGEDCT is on the Sage Server why would you change it from the 127.0.0.1 what happens if your IP changes for some reason? Also using 127.0.0.1 is more efficient.

[cupp]

I just could not get it to work with local host, no matter what I did. I came across someone else who changed theirs to get it to work.

I made the computer and hdhr prime both static ip's to prevent them from changing.

On my next update I can try it again. Any ideas other than the firewall why it would not communicate?

[gabrielcab]

Originally Posted by nyplayer

Check out this thread.

http://forums.sagetv.com/forums/show...postcount=1360

Thanks again nyplayer,

Finally have SageTV running, my problem was that I needed to install the FFdshow and AC3 codecs. Now its time for me to cry again for selling all my HD300

[james_k_p]

I think I'm going to drop by charter this Sat and finally get a cable card and tuning adapter (which I see other places I will need) and open my Prime that I've had for a year sitting in the box. lol

Is there any reason that sagedct would have an issue with 2 other hdhomeruns that I already use within Sagetv? I have the original white one with 2 tuners, and a blue one that has one cable tuner I believe. I forget the model names. But with the NFL season coming up as I record many of the games, I'm leary to screw up my whole setup by trying to get this to work. Thanks.

[james_k_p]

Well, I picked up my tuner adapter and card last friday, couldn't get charter phone support to activate it. They rolled a truck which came out yesterday (wednesday) and they checked signals/changed a splitter, then called Tier 2 support that they have access to, and the guy on the other end knew actually what needed to be done and what numbers he needed.

I ran SageDCT following the instructions here and got it working.

The only issue I have is that I cannot manipulate the channel names like I can on the regular blue/purple hdhomerun that I have on basic cable. The reason I've done that in the past is my antenna hdhomerun has its channel IDs read in sagetv straight from the antenna and air waves and not the hdhomerun setup app's labels. So for the direct basic cable one, I'd change the channel name from antenna version WWLDT which is the same channel on cable, but I rename is to simply WWL, so it comes up as a different channel in the program guide, so I can dictate whether i want something to record OTA or cable.

Well with the prime, I'm not sure where it's reading that info from. It's definitely not reading it from the hdhomerun prime's setup app. I guess it's reading the line up from the cable card.

So now my prime's tuners for WWLDT are lumped together with the WWLDT from OTA. I hate this. If I remap the OTA's in any way, and I've tried a dozen different ways, the program guide doesn't pick it up. UG!

If anyone has any ideas or can shed any lights of something I may not know about this or a way to control which tuner a recording will occur on, I'd be most grateful.

I usually like to record most of my football games OTA for best and uncompressed signal. So I prefer to have it isolated. For now, I just disabled the locals, including the WWLDT, on the prime tuners so I only have the OTA WWLDT.

[eopian]

Originally Posted by james_k_p

So now my prime's tuners for WWLDT are lumped together with the WWLDT from OTA. I hate this. If I remap the OTA's in any way, and I've tried a dozen different ways, the program guide doesn't pick it up. UG!

If anyone has any ideas or can shed any lights of something I may not know about this or a way to control which tuner a recording will occur on, I'd be most grateful.

I know this is two years later, but I have my OTA tuners set with the highest priority, so locals are always recorded on the antenna first; if those two tuners are busy, then on cable. You can then control which show has priority with manual recordings taking highest priority, then favorites are ordered in the favorites menu.

To set tuner priority http://davidvielmetter.com/sagetv/ho...ity-in-sagetv/

[sdsean]

Not sure if anyone out there is listening or not. . . but I thought I'd give it a shot. . .

I setup SageDCT, mainly b/c TimeWarner is now forcing everything (even locals) through encryption in one form or the other, and I use them just to get local channels.

Anyway, I have the setup running just fine, but some channels I get a "No Signal" on them.

I then used the "Test" tab in SageDCT config tool, to send start/stop commands for that channel number, and sure enough when I do that, I get a valid recording / file.

I think there is something getting mismatched in the channel numbers or something as that's the only thing that seems to explain why it would claim "no signal" on certain channels. ..

thoughts?

[sdsean]

Nevermind, I found the issue, indeed it is a channel mapping issue.
The guide data I'm getting for some of the locals seems to be picking up "physical channel" numbers like 78-1034-8, which SageDCT does not handle since it needs to be a number.

And so I just re-mapped the physical channel to match what is in the HDHomeRun setup and voila.