OpenDCT: An open source digital cable tuner.

[KryptoNyte]

Okay, just checking. I had an issue with both of my Primes disappearing from the network intermittently. The firmware upgrade fixed one of them but not the other (which I ended up replacing inside of warranty, on my dime).

[EnterNoEscape]

You could also try the latest beta firmware if this becomes a frequent problem.

20160516atest1:
https://www.silicondust.com/forum/viewtopic.php?t=20613


Edit: I never thought about a DHCP failure and how it would effect the HDHomeRun. I wonder if this is the cause of some of the mysterious HDHomeRun disappearances that other forum members have reported.

[EnterNoEscape]

Originally Posted by nateziemann

I've been running SageDCT w/ a Prime and Sage 7.1.9 for a long time successfully. Lately more and more channels just won't tune within sage but tune fine using HDHomeRun apps on FireTVs just fine. It seems random...and pisses off the fam missing recordings.

So I'm considering moving to OpenDCT with Sage 7.1.9. Should I jump on the latest Beta 0.5.x on git or latest stable 0.4.x

I'd go with the latest stable if you don't have any interest in any of the newer features like CCExtractor or Generic HTTP capture device support. The only reason to go with the beta releases is for new features that are still in testing.

[matt91]

Originally Posted by EnterNoEscape

You could also try the latest beta firmware if this becomes a frequent problem.

20160516atest1:
https://www.silicondust.com/forum/viewtopic.php?t=20613

Does this do anything else other than upgrade the firmware? Looks like it's part of the HDHR DVR package.

[EnterNoEscape]

Originally Posted by matt91

Does this do anything else other than upgrade the firmware? Looks like it's part of the HDHR DVR package.

It will upgrade the HDHomeRun software on whatever computer you install it on, but it doesn't put you in an position whereby you might be forced into installing the DVR software somewhere.

[KryptoNyte]

Originally Posted by matt91

I woke up this morning to a bunch of missed recordings. In looking into it a little bit, it looks like my HDHR Prime wasn't getting an IP address and therefore Sage couldn't connect to it.

How long have you been running the Prime? Is this the only time this has ever happened?

[matt91]

Originally Posted by KryptoNyte

How long have you been running the Prime? Is this the only time this has ever happened?

a few years. It may have happened before, but it's the first time that I realized what had happened. I do recall doing a power cycle on the unit a couple of times; that may or may not have been the same issue.

[matt91]

Originally Posted by EnterNoEscape

It will upgrade the HDHomeRun software on whatever computer you install it on, but it doesn't put you in an position whereby you might be forced into installing the DVR software somewhere.

dad@poweredge:~/temp$ ./hdhomerun_record_linux
Usage: hdhomerun_record <command> [<options>]
Commands:
  start       Start the hdhomerun_record daemon
  stop        Stop the hdhomerun_record daemon
  status      Running status of the hdhomerun_record daemon
  foreground  Run hdhomerun_record as a foreground process
  version     Display version information
Options:
  --conf <file>     Load config from specified file
dad@poweredge:~/temp$

am i missing the option to upgrade?

thanks
Matt

[EnterNoEscape]

Originally Posted by matt91

dad@poweredge:~/temp$ ./hdhomerun_record_linux
Usage: hdhomerun_record <command> [<options>]
Commands:
  start       Start the hdhomerun_record daemon
  stop        Stop the hdhomerun_record daemon
  status      Running status of the hdhomerun_record daemon
  foreground  Run hdhomerun_record as a foreground process
  version     Display version information
Options:
  --conf <file>     Load config from specified file
dad@poweredge:~/temp$

am i missing the option to upgrade?

thanks
Matt

I forgot you were using Linux. You should be able to apply the upgrade via hdhomerun_config.

./hdhomerun_config discover
./hdhomerun_config <device_id> upgrade <firmware_filename>.bin

[matt91]

Originally Posted by EnterNoEscape

I forgot you were using Linux. You should be able to apply the upgrade via hdhomerun_config.

./hdhomerun_config discover
./hdhomerun_config <device_id> upgrade <firmware_filename>.bin

but there doesn't seem to be a bin file to be had.

[KryptoNyte]

Originally Posted by matt91

a few years. It may have happened before, but it's the first time that I realized what had happened. I do recall doing a power cycle on the unit a couple of times; that may or may not have been the same issue.

This sounds like a rare event. At one point, when my Prime's were unstable, I was taking shots in the dark and hooked them up to an uninterruptible power supply. It could have been something as simple as a power issue (even a power supply starting to fail I suppose), or some other LAN issue, cable/switch/router, or even a kid knocking the wall wart out.

[nyplayer]

All of a sudden I am getting no signal on my test machines.

[EnterNoEscape]

Originally Posted by nyplayer

All of a sudden I am getting no signal on my test machines.

I think I see what happened. Some of the code that's meant to keep things from getting unresponsive is allowing a second tuning request from SageTV to prevent the consumer from ever starting. This appears to be a timing issue and I don't think this will be a simple fix.

[nyplayer]

Originally Posted by EnterNoEscape

I think I see what happened. Some of the code that's meant to keep things from getting unresponsive is allowing a second tuning request from SageTV to prevent the consumer from ever starting. This appears to be a timing issue and I don't think this will be a simple fix.

What is weird is at least my Production machine is working the only difference is that on my Production machine I have to always force unlock.

[EnterNoEscape]

Originally Posted by nyplayer

What is weird is at least my Production machine is working the only difference is that on my Production machine I have to always force unlock.

Presumably, your production hardware is going to be a little better performance-wise than your testing hardware. Actually I think I spotted something even more relevant to nothing working: the log entry FFmpeg loaded in {}ms, is missing. The lack of that entry essentially means the library never loaded which would cause anything that requires FFmpeg to not be able to load.

Try starting OpenDCT and just let it sit there for a little while to see if that entry eventually appears in the log.

[nyplayer]

Originally Posted by EnterNoEscape

Presumably, your production hardware is going to be a little better performance-wise than your testing hardware. Actually I think I spotted something even more relevant to nothing working: the log entry FFmpeg loaded in {}ms, is missing. The lack of that entry essentially means the library never loaded which would cause anything that requires FFmpeg to not be able to load.

Try starting OpenDCT and just let it sit there for a little while to see if that entry eventually appears in the log.

I did what you said... still no go.

[EnterNoEscape]

Originally Posted by nyplayer

I did what you said... still no go.

That's truly strange. I'll post a version for you to try that will log every step of the initialization. In the mean time, have you tried reinstalling?

[nyplayer]

Originally Posted by EnterNoEscape

That's truly strange. I'll post a version for you to try that will log every step of the initialization. In the mean time, have you tried reinstalling?

Yes even tried the Stable Version.... am now back to the Beta. It could be something that was added in Windows 10 security.

[EnterNoEscape]

Originally Posted by nyplayer

Yes even tried the Stable Version.... am now back to the Beta. It could be something that was added in Windows 10 security.

Download the 32-bit and 64-bit versions of FFmpeg from here and run .\bin\ffmpeg.exe from the command line to see if you get any errors.

It looks like some people started having issues on Windows 10 with FFmpeg depending on how it was built starting in March 2016.

[nyplayer]

Originally Posted by EnterNoEscape

Download the 32-bit and 64-bit versions of FFmpeg from here and run .\bin\ffmpeg.exe from the command line to see if you get any errors.

It looks like some people started having issues on Windows 10 with FFmpeg depending on how it was built starting in March 2016.

No errors they both ran ok.