Network encoder

[guho]

Originally Posted by EnterNoEscape

Those are super clear. Thank you.

When I did my self-install I initially had channel changing problems. They were fixed once I made sure both R5000-HD boards are well grounded to STB ground.

[EnterNoEscape]

Originally Posted by guho

When I did my self-install I initially had channel changing problems. They were fixed once I made sure both R5000-HD boards are well grounded to STB ground.

Thanks for the advice. It's nice to be talking with someone using the R5000-HD for a cable STB.

[guho]

Originally Posted by EnterNoEscape

Thanks for the advice. It's nice to be talking with someone using the R5000-HD for a cable STB.

Did you get your R5000-HD installed and working?

[EnterNoEscape]

Originally Posted by guho

Did you get your R5000-HD installed and working?

Partly. I got side-tracked and haven't come back around to it. I'll get there again. I've just got so much going on right now.

[EnterNoEscape]

My aspirations ended when one of the caps that wasn't looking too healthy before I even modded the box went poof. I could replace it, but it's hard to make out if anything about it is special. I have doubts that any old replacement capacitor of similar capacity will do. I could rent one of the HD boxes and mod it, I should be able to get H.264 to decode in that case. I just don't know if I feel like paying for something that I only need for HBO.

[pdermody]

Neat, how generic is the code with regards to R5000 support? Guess I should download the code and have a look, albeit the current setup works fine for me (dish network receiver). Mainly I am curious about future alternative support if needed (or if I get the bug to add a second receiver to the mix as I don't think I can even request keys anymore...)

-pd

[guho]

Originally Posted by pdermody

Neat, how generic is the code with regards to R5000 support? Guess I should download the code and have a look, albeit the current setup works fine for me (dish network receiver). Mainly I am curious about future alternative support if needed (or if I get the bug to add a second receiver to the mix as I don't think I can even request keys anymore...)

-pd

I only have incorporated the IR codes of the Moto DCT cable but you could add dish IR codes to suit your needs.

[btrcp2000]

are any of you successfully using v9 with r5000? About to set mine up again via dish, wondering if there is anything different this time around. May even need to beg someone for the nextcom exe.

[guho]

Originally Posted by btrcp2000

are any of you successfully using v9 with r5000? About to set mine up again via dish, wondering if there is anything different this time around. May even need to beg someone for the nextcom exe.

Should work fine. I do not use the nextcom exe anymore as I use my own R5000-HD network encoder, with the latest SageTV9 in service mode on Windows 8.1 x64.

[gandalf]

So what network encoders are known to work with an R5000 amd SageTV V9?
I cannot get the Nextcom version to work - it was fine on V7 but it only establishes a brief connection from V9 then drops it.

[pendragonsound]

Originally Posted by gandalf

So what network encoders are known to work with an R5000 amd SageTV V9? I cannot get the Nextcom version to work - it was fine on V7 but it only establishes a brief connection from V9 then drops it.

I have four R5000s working fine with V9 on Vista 32-bit, running Nextcom version 3.0c. But I'll be moving to Linux soon, once I complete a Network Encoder for it.

[gandalf]

Interesting - thanks for the update.

I am running Nextcom 3.1d, which seems to be the latest version before they closed down. I am also running Windows 8.1 64 bit.

Not sure if either of those differences could be the cause of my problems - hopefully someone has a working R5000 on a similar system, has had similar problems to me, and has fixed them to get a working system.

[pdermody]

Originally Posted by gandalf

Interesting - thanks for the update.

I am running Nextcom 3.1d, which seems to be the latest version before they closed down. I am also running Windows 8.1 64 bit.

Not sure if either of those differences could be the cause of my problems - hopefully someone has a working R5000 on a similar system, has had similar problems to me, and has fixed them to get a working system.

I'm running 3.1d on both a win7 box and win10 box with sage9 on each without issue. I did run into a problem with the 10 box but I think it was plugin related that was solved by trashing the upgraded sagetv (6->7->9) and starting clean with a fresh install and restored wiz.bin file.

-pd

[btrcp2000]

I am attempting to move my sage setup which includes 2 r5000hd dish vip211 boxes. Neither the 3.1d version now the 3.0c version will accept my nextcomwireless key.

is there another network encoder out there I can get ahold of that will work with this equipment?

[btrcp2000]

Bumping this thread for anyone using Dish r5000 boxes with Linux/Unraid. I solved my issue with the license key long ago, but have since concluded that the nextcomwireless software cannot be used as a networked encoder on a windows VM as it doesn't seem to understand the way the recording path is described in unraid. I have a whole other thread going, but suffice to say that it seems to want to treat var/media/tv or mnt/user/sagemedia/tv as a UNC path. Since it can't find it, it refuses to write the file.

Anybody have this working?