PrimeNetEncoder - HDHomeRun Prime Network Encoder

[nyplayer]

Originally Posted by civerson4

Thanks for the help trouble shooting--really appreciate it.

I swapped the sage properties info from nyplayer's link and that solved my duplicates issue. I can add each of the 3 tuners (and only see 3 tuners), but still no signal within Sage when I tune a channel.

I have sage in service mode (shutting it down before making any property file changes).

The Prime Encoder works with the HDHR software.

Windows firewall is turned off--but I added ffmpeg.exe as an exception anyway.

Any other ideas?

Can you post the PrimeEncoder tuner logs ... also look in the logs and make sure the tuners have the correct IP's.
Also how are you running it batch job or runnable in sagetv?

[civerson4]

File attached. I think the issue may be PrimeNet thinks I am running in console mode, but (I think) I have Sage set to run PrimeNet as a runnable class within Sage.

The logs don't show much. Maybe a remaining issue in my properties file?

The log file for Primenet says the following (the last line repeats forever and the file is 4000kb):

07/05/2015 11:07:04 - Running PrimeNetEncoder in Console Mode
07/05/2015 11:07:04 - Starting tunner threads
07/05/2015 11:07:04 - Starting Debug Console
07/05/2015 11:07:04 - Unexpected error reading from the console. The handle is invalid
07/05/2015 11:07:04 - Unexpected error reading from the console. The handle is invalid
07/05/2015 11:07:04 - Unexpected error reading from the console. The handle is invalid


I am really not a computer programmer, so I really appreciate the help and patience.

[nyplayer]

Originally Posted by civerson4

File attached. I think the issue may be PrimeNet thinks I am running in console mode, but (I think) I have Sage set to run PrimeNet as a runnable class within Sage.

The logs don't show much. Maybe a remaining issue in my properties file?

The log file for Primenet says the following (the last line repeats forever and the file is 4000kb):

07/05/2015 11:07:04 - Running PrimeNetEncoder in Console Mode
07/05/2015 11:07:04 - Starting tunner threads
07/05/2015 11:07:04 - Starting Debug Console
07/05/2015 11:07:04 - Unexpected error reading from the console. The handle is invalid
07/05/2015 11:07:04 - Unexpected error reading from the console. The handle is invalid
07/05/2015 11:07:04 - Unexpected error reading from the console. The handle is invalid


I am really not a computer programmer, so I really appreciate the help and patience.

You sure yo do not have a console Instance running? Also did you copy over properties and ffmpeg to your sage folder?... If I were you I would check that and reboot. Your properties files are perfect.

[civerson4]

Yes, ffmpeg and PrimeEncoder are both in the SageTV directory. I think I posted an old logs by mistake--from the PrimeNet directory, not Sage. The new log for PrimeNet (from the SageTV directory) is attached. Do these help?

Re-booted, still no go.

[nyplayer]

Originally Posted by civerson4

Yes, ffmpeg and PrimeEncoder are both in the SageTV directory. I think I posted an old logs by mistake--from the PrimeNet directory, not Sage. The new log for PrimeNet (from the SageTV directory) is attached. Do these help?

Re-booted, still no go.

Did you accidently change this In the prime properties it is not correct.

"C:Program FilesSilicondustHDHomeRunhdhomerun_config.exe"

it should look like this.
HDHomeRunConfig.path=C\:\\Program Files\\Silicondust\\HDHomeRun\\hdhomerun_config.exe


Yours looks like this.
HDHomeRunConfig.path=C:\Program Files\Silicondust\HDHomeRun\hdhomerun_config.exe

[civerson4]

THANK YOU!

I wouldn't say I accidentally changed it, I purposely changed it like an idiot as the syntax looked funny to me. Lesson learned. I also sent you a PM.

[Fuzzy]

Originally Posted by civerson4

THANK YOU!

I wouldn't say I accidentally changed it, I purposely changed it like an idiot as the syntax looked funny to me. Lesson learned. I also sent you a PM.

Yeah, in the properties files, \ is an escape character to be able to handle special characters. So, when you want the string to actually include a backslash, you have to enter it as \\.

[CptKirk]

jgsouthard, are you still running with no 'halt detected' now?

I've been on normal (4) 100% of the time and I'm still getting them. Just had a few over the weekend.

[uberpixel]

Anyone else experience occasional dropping of the Prime tuners?

Once they drop I have to either restart sage or the entire server to get them back.

Other missing recordings due to tuner conflict there's no warning that they've dropped out.

I'm running PrimeNetEncoder as a batch at startup. This seems to have fixed any of the halts I had been having.

I'm away on vacation and just noticed via the web UI that I'm missing a bunch of recordings.

I could have scheduled nightly restarts but that seems like a poor workaround.

Any thoughts?

-uberpixel

[nyplayer]

Originally Posted by uberpixel

Anyone else experience occasional dropping of the Prime tuners?

Once they drop I have to either restart sage or the entire server to get them back.

Other missing recordings due to tuner conflict there's no warning that they've dropped out.

I'm running PrimeNetEncoder as a batch at startup. This seems to have fixed any of the halts I had been having.

I'm away on vacation and just noticed via the web UI that I'm missing a bunch of recordings.

I could have scheduled nightly restarts but that seems like a poor workaround.





Any thoughts?

-uberpixel

I have never seen that .... can you post your batch job. Also are you running at normal priority.

This is my batch Job. It have it in my PrimeEncoder folder.

CD /d "%~dp0"
c:
:loop
"C:\Program Files (x86)\Java\jre7\bin\java.exe" -jar PrimeNetEncoder.jar
goto loop

[uberpixel]

Originally Posted by nyplayer

I have never seen that .... can you post your batch job. Also are you running at normal priority.

This is my batch Job. It have it in my PrimeEncoder folder.

CD /d "%~dp0"
c:
:loop
"C:\Program Files (x86)\Java\jre7\bin\java.exe" -jar PrimeNetEncoder.jar
goto loop

I'll post my batch job when I'm back from vacation but it's possible I copied yours.

Where is the "normal priority" set?

-uberpixel

[nyplayer]

Originally Posted by uberpixel

I'll post my batch job when I'm back from vacation but it's possible I copied yours.

Where is the "normal priority" set?

-uberpixel

See this thread
http://forums.sagetv.com/forums/show...2&postcount=55

I would check the cable that connects the Prime maybe even replace it with a good cable ... I have never seen tuners lost like that when using the Prime or Sagedct for that matter.

[KryptoNyte]

I lose one of the Primes on occasion, and nothing but a reboot of the unit gets it going again (SageDCT). I'm starting to wonder if there are a handful of duds out there.

I am now in the habit of rebooting each tuner with a batch file at least once a week.

[nyplayer]

Originally Posted by KryptoNyte

I lose one of the Primes on occasion, and nothing but a reboot of the unit gets it going again (SageDCT). I'm starting to wonder if there are a handful of duds out there.

I am now in the habit of rebooting each tuner with a batch file at least once a week.

If you think you have a dud why not turn on Hd Homerun diagnostics and open a trouble ticket their support is great... that way you will know for sure. I always say address the problem do not mask it.

[KryptoNyte]

Originally Posted by nyplayer

If you think you have a dud why not turn on Hd Homerun diagnostics and open a trouble ticket their support is great... that way you will know for sure. I always say address the problem do not mask it.

When I had already tried that months ago, they were unable to find a problem, or a solution to the offending tuner. Any other ideas?

[civerson4]

I picked up a 2nd HDHR Prime (thanks again for everyone's help getting the first one working).

There is a note in the instructions about just changing the tuner count properties in the PrimeNetEncoder properties file and then creating new entries in both that file and the Sage properties file for the new tuners.

I assume I also should change the transcoder.port (continue 5000, 5010, 5020...) and the tunerX.port (7000, 7001, 7002....)

What about the discovery.port or anything else?

[nyplayer]

Originally Posted by civerson4

I picked up a 2nd HDHR Prime (thanks again for everyone's help getting the first one working).

There is a note in the instructions about just changing the tuner count properties in the PrimeNetEncoder properties file and then creating new entries in both that file and the Sage properties file for the new tuners.

I assume I also should change the transcoder.port (continue 5000, 5010, 5020...) and the tunerX.port (7000, 7001, 7002....)

What about the discovery.port or anything else?

No change to discovery ports. You just have to add the to the sage properties the new tuners and the primeencoder properties. Remember you have to increment the tuner numbers also in sage.properties.

[civerson4]

I am having trouble modifying the Sage Properties file to add the additional HDHR Prime tuners. I modify Sage Properties per the attached (6 tuner file), but as soon as I restart the Sage Service, it reverts back to the original Sage Properties (also attached). I literally watch the file size change from 344 kb to 338 kb in windows as the Sage Service completes loading.

I am completely shutting down Sage and stopping Sage Service before opening the files in Notepad (Win 7). I've modified the properties file in the past and have never had this problem. Any idea what I am doing wrong?

The only modifications I am making are add the mmc/encoders/1012343954 section for the 3 new tuners.

Also attached is my the PrimeNetEncoder properties file for 6 tuners (in case that may help track down the issue).

Thanks in advance for any guidance.

[civerson4]

Originally Posted by nyplayer

Remember you have to increment the tuner numbers also in sage.properties.

Nevermind. I just re-read this post and this was the step I forgot. Doh!

[KryptoNyte]

I just remotely logged into this Sage Server this morning, and using the HDHomeRun Config (GUI) was able to verify that one of the two Prime tuners simply wasn't present. It took a complete power cycle of the Prime to get it back up. When I requested a look at the logs that Silicon Dust was pulling from the tuners, they refused. These logs area apparently only available to them.

This is a weekly occurrence. Does anyone have any ideas on how to troubleshoot this issue, that results in halted recordings?