The ports could be anything that is open, and it doesn't matter, especially with discovery being used, as the ports should match in the sage.properties.

If you're going to implement copy protection detection, you might want to do it as a background task that happens when a tuner is not being requested. That is how I'm implementing it in my network encoder. I'm also spreading the load out across all available tuners on the same device to speed things up a bit. A while back I ran a perl script that listed the CCI status of all of my channels and it had to wait a few seconds on each channel just to get that status. While it was waiting to get the status, the channel was definitely already streaming. Adding this check could delay the perceived tuning time.

Alternatively, there are a couple web pages on the HDHR interface that will return the channel list, including whether they are protected or not. Just have to trigger the HDHR to initiate it's own scan, then when done, pull down and parse the inputs. unfortunately, the scan compulsively uses all three tuners, even IF they are locked (at least it did when I tested it like 6 months ago).

That's a cool feature. You don't get things like that with the InfiniTV. Naturally :), I still like my idea since you can notice a tuner is needed for something else and just stop using it in the scan.

Well, I haven't tested recently, but I had reported the issue to SiliconDust a while ago. They really should only use tuners that don't have a lock for their scan. If that got fixed (don't know if it did or not), then it would be real easy to start a scan whenever, and it'll just take as long as it takes, but it will be done automatically by the tuner itself.

They do matter in the firewall if you reverse the ports from what is on the documentation then you also have to open them correctly in the firewall. The firewall settings in the DOC no longer apply.

Yeah, I don't often think about firewalls - because I see no reason why they are ever turned on on a private network - other than to complicate things.

Depends on how much you trust the other people using your private network. ;)

One accidently infected system (with the "right" kind of infection) could become rather troublesome if there are no additional protections within the private network itself.

Firewall is off.

1. Killed SageTV service.
2. Killed PrimeNetEncoder task.
3. Deleted PrimeNetEncoder.properties.
4. Started PrimeNetEncoder task to generated default .properties file.
5. Killed PrimeNetEncoder task.
6. Edit PrimeNetEncoder.properties file for HDHomerun Prime.
7. Deleted all PrimeNetEncoder references from Sage.properties.
8. Started PrimeNetEncoder task.
9. Started SageTV service.
10. Added PrimeNetEncoder tuner in SageTV.
11. Tune channel using PrimeNetEncoder tuner.

Same errors as previously reported occur.

Running on Windows 10 Pro x86.
PrimeNetEncoder v1.0.1 worked perfectly on this same system.

Looks like I'm going back to v1.0.1.

I looked at your previous logs and it shows. 1.2.2 I thought you wre running 1.2.4. Are you running 1.2.2 or 1.2.4. Maybe there are 2 Instances running?

10/02/2015 15:09:21 - Running PrimeNetEncoder in Console Mode
10/02/2015 15:09:21 - PrimeNetEncoder Version: 1.2.2
10/02/2015 15:09:22 - Starting tunner threads
10/02/2015 15:09:22 - Starting Debug Console

Mr. JVL. now that you are using the UploadID method of pushing data to the server, have you looked into implementing the BUFFER commands? This is likely simpler with the UploadID, as you don't have to worry about writing to the file itself, just have to reset your offset when the buffer is full. Would be even easier if you set your STDIN buffer to be the same size, or a even dividend of the BUFFER commands size parameter.

Do you know if the buffer value refers to a certain number of bytes to buffer or a certain amount of time probably in milliseconds since it's a long variable?

HELP - can't get PrimeNetEncoder working
 

I have read through what feels like everything... When i run the Jar file I get the following in the .txt log file:

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

I can't seem to get past this. My remaining thought is that i am running Java 8 and maybe that is the issue?

My PrimeNetEncoder folder is in my main SAGE folder on the server... i am running 64-bit Windows 7. FFMpeg is 64-bit and is placed in the PrimeNetEncoder folder (just the single file)

attached are my files if anyone can please take a look. I have not even gotten to the point where i start sage... i am just trying to get the .txt file from growing exponentially with this error first!

Never seen that error before ... for that matter I do not use Java 8 on my SageTV Server. This looks like a question for JVL.

Try dropping in a 32-bit ffmpeg.exe

Tried the 32-bit ffmpeg.exe... dropped into the the PNE folder. I moved everything to C:\PrimeNetEncoder and ran there and still the same issue.

i was wondering if there are issues with 32-bit java on a 64-bit machine?

I can't run the command "java –jar PrimeNetEncoder.jar" withour getting an error... I can only run it as "PrimeNetEncoder.jar" and it runs...

UPDATE: The error i get is "Error: Could not find or load main class jar?"

UPDATE: wanted to add that the tuner is working with the HDHomeRun VIEW program... all channels appear and are tunable

I run 32 Bit Java on my 64 bit system with 64 bit FFMPEG and have no problems. Of Course I am running Java 7. My batch file below.... maybe you can substitute your java 8 path and see if it works. Make sure to put the batch file in C:\PrimeNetEncoder

Plenty of people are using this in 32-bit java on a 64-bit machine. It, instead, may be an issue if you run PNE with a 64-bit java - never tried, I've never bother to install a 64-bit java. If you use a batch file like nyplayer just posted, making sure it's pointing to a 32-bit java.exe, then that should eliminate that potential problem.

I am having this very issue.

Any luck?

So why not try the batch file above???? Most of these issues are self imposed.... if setup correctly it works. Like Fuzzy said use the recommended Java 7 for sage... do not try and complicate matters.