Yep Comcast but if they ever Copy once every channel I just will move to WMC fully and then the upcoming HDHOMERUN DVR... Which I am currently testing. I am not using SageTV for my recordngs but others in my household are so I maintain it for them. I am using KODI on RPI with the PLEX Plugin to bring it all together in one interface .... PLEX Plugin in Kodi allows comskip to work. On my Server I Have SageTV, WMC, ServerWMC, and plex running.

PS on Comcast Portland the only ones they Copy Protect is NBATV HBO STARZ SHOWTIME ENCORE. Al others are copy freely.

I'm now running KeepAliveHD on my hard drive, and I have fully defragmented the drive using Raxco Perfectdisk v13. I'm still getting numerous "Halt Detected in Recording" errors, and they started at the same time that I removed SageDCT and switched to PrimeNetEncoder. It there anything in PrimeNetEncoder that could be causing this, or any parameters that can be adjusted to correct?

In PrimeNetEncoders.properties, I have ffmpeg.delay=2000. Could a different value here make a difference?

It seems like even though SageTV can see the tuners, when it's trying to access a tuner there is some kind of timeout that causes SageTV to think that the tuner is no longer accessible; and it appears that PrimeNetEncoder increases the likelihood of that happening.

This is what I have and I get no halts.

I have autologon to my server enabled.
windows 8.1 pro 64 bit

ffmpeg latest 64 bit

primencoder properties
ffmpeg.delay=1000

sage.properties
delay_to_wait_after_tuning=10000 on my prime tuners

allow ffmpeg.exe through firewall full access

Thanks nyplayer, you've been very helpful and I appreciate the insight.

I think I'm tracking pretty close other than that I didn't know about the "delay_to_wait_after_tuning=10000" parameter (mine was on the default 0 for each tuner). I also lowered by ffmpeg.delay to 1000 from 2000 (I've also tried 500 and still got halt errors, though).

I've modified the delay_to_wait_after_tuning parameter and I'll do some testing with that.

What is the unit for that number? Normally I'd guess it was milliseconds, but 10,000 milliseconds would be 10 seconds, and that seems awfully long. I'd have thought we might want the tuner to wait a second or two.

The 10000 I got from when I was using SageDCT it was the default.

I honestly don't think delay_to_wait_after_tuning has any impact on network encoders. Sage doesn't tell the encoders to tune, then wait then tell them to start recording. It simply tells them to START recording from a given channel to a given filename. Any after-tuning delay would be implemented in the network encoder itself, not controlled by sage.

I'm seeing the same "Halt Detected In Recording" errors with PrimeNetEncoder and HDHomeRun Prime as jgsouthard. Using the same values mentioned as nplayer a few posts ago, except I'm using W7 SP1 Pro 64bit.

It works great but every now an then I get the halt detected message. Sometimes it is just a single event, sometimes more (I've had it show as x21 times once).

I turned on verbose debug output and was watching the UI to try and catch it today. Caught a single event when it was doing an favorites record.

From the PrimeNetEncoder-tuner0.txt file. You can see about a minute and a half into the recording it halts and restarts:

From the sagetv_x.txt log file. No errors or problems detected before or after what I've snipped here. Shows the halt and restart at the same time.

Thanks for the update, CptKirk. There's something going on with PrimeNetEncoder that some of us are seeing, but not all (e.g. nyplayer).

I've tried everything suggested by nyplayer and others, and I'm still getting the halts on a regular basis. They are generally NOT right at the beginning of a recording, but more commonly (surprisingly consistently) about 1-5 minutes into the recording. If I have multiple recordings starting at once, the halts will occur on all tuners at about the same time (within a minute or two of each other).

This makes me think that the issue is most likely related to system activity or system load, but it also appears that PrimeNetEncoder is somehow more sensitive to it than SageDCT was. With SageDCT I was seeing halts like this maybe once every 2-3 days, and then only a signal quick incident (but I was seeing occasional pixelation or video blips that are totally gone now). So something changed with PrimeNetEncoder, possibly to generate Halts when SageDCT would keep going with pixelation.

Right now I'm recording to a separate partition on my primary (single) hard drive in the SageTV server (WD Black, SATA II), so I'm going to try recording onto a separate SATA III drive (also WD Black) to offload some of the system overhead and see if that helps.

As an experiment (but a long shot, I think), I'm also going to try inserting a remotely-powered signal booster into the incoming cable line at the demarc box. I'm going through about 14db of signal loss due to splitters between the incoming cable and my HDHomeRun Prime, leaving Signal Strength (as shown in HD Config) in the 84% range (Yellow). But Signal Quality and Symbol Quality are both consistently 100%, so I don't really think that's the problem.

But tweaking PrimeNetEncoder and/or SageTV properties hasn't helped at all....

See this thread I meant to post it here about scheduled tasks priority.

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

Checked the task manager and Java is running at normal priority.

The Sage server does an auto-login and then runs a batch file for PNE that is in the startup group. I'm not using scheduler.

That did the trick, thanks! Numerous recordings today with no "Halt Detected in Recording" errors, after increasing the priority of the Java PrimeNetEncoder process in Task Scheduler from 7 (Below Normal, default) to 4 (Normal).

I am still having trouble getting PrimeNetEncoder set up on my server.

I can add the tuners an do a channel scan, but am getting a number of "weird" channels (like OKC-118). My guess is there is a mapping problem or Sage is somehow not seeing the HDhomerun channel scan. Would really appreciate any help here.

Sage does't use the HDHR's channel scan. It goes off the channel list from the EPG provider.

Right, but when I do the channel scan in Sage, something is wrong. The HDHR channel scan finds 477 channels. When I do the channel scan in Sage, I get 201 channels--and they are not "real channels" (like OKC-118). I have a feeling I have a single wrong setting somewhere, but I have been the instructions line-by-line multiple times.

Anyone happen to be in Orange County, CA? Cox Cable transitions to all digital and requires a set top box in 4 weeks--and I really don't want to give up on Sage in 4 weeks.

Certainly not an expert at this stuff--but I have had Sage running 7-8 years and hope to have another 7+ years.

Thanks.

It's my understanding that you don't do a channel scan in Sage with this tuner. After following the installation instructions, you select the EPG for your region and go. Don't scan in Sage.

Thanks--but still no go.

I just tried adding the 7001 tuner without a channel scan. Sage adds 6 different tuners (all the same name) and it can't tune a channel. Sceenshot (showing 3 versions of the same tuner attached).

See this thread about duplicates.
http://forums.sagetv.com/forums/show...&postcount=176

You have to make sure to add ffmpeg.exe to your firewall.

Hey NP, after replacing those lines mentioned in the thread that you linked to, does the user still need to alter the encoding host IP address to match the Sage machine, or is that optional?

You can either use 127.0.0.1 or the host IP your preference. 127.0.0.1 only use if Primeencoder and SageTV Server are running on the same machine.

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?