PrimeNetEncoder - HDHomeRun Prime Network Encoder

[jvl711]

Hi,

First I would like to thank all of the forum members that beta tested for me. Their feedback was very helpful in ensuring that my first release was as stable as possible. I need to give special thanks to nyplayer. He went above and beyond in his testing efforts and helped me work through many of the issues.

Overview

PrimeNetEncoder is a network encoder for HDHomeRunPrime. It is designed to run on both windows and linux and to have minimal requirements. The encoder uses the hdhomerun_config application and ffmpeg to capture the stream. Since ffmpeg is only capturing the stream and writing to a file PrimeNetEncoder has very low overhead.

PrimeNetEncoder can be configured to handle any number of HDHomeRunPrime tuners. If you are going to use more than one HDHomeRun Prime you will need to modify the tuners.count property, and create new entries for the tunners in the PrimeNetEncoder.properties file, and create new tuner entries in the sage.properties. Forum members have tested and confirmed that PrimeNetEncoder can also work with other HDHomeRun tuners. Please check the forums for notes on compatibility.

PrimeNetEncoder also offers the option to transcode to h.264 in realtime. This does requires a reasonable amount of CPU resources to accomplish. Transcoding is configurable at the tunner level. There are settings available for quality and performance.

Guides
Note: Installation instructions are included in the download.
There is a very good guide to setting up the PrimeNetEncoder on Linux by SageWizdom http://forums.sagetv.com/forums/showthread.php?t=62737
Below this post is a guide on setting up Non Prime DLNA OTA tuners by nyplayer
Known Issues

1. Please read the install guide for specific issues.

Upgrading

See any specific upgrade notes for the version. To upgrade from a previous version you should replace the PrimeNetEncoder.jar with the new one. You should run the program once so that it can add the new properties to the PrimeNetEncoder.properties file.

Changelog

Version 2.0.0 - Download

• Added quit command. This will attempt to exit gracefully if the tuners are not currently recording.
• Added an local address override to the properties file. This is to workaround some issues with certain Linux distros, and possibly machines with multiple IP addresses
• Change property mediaserver.transfer default value from true to false. Some machines seem to be struggling with transferring to sage using this method.

Version 1.2.5 (RC1) - Download

1. Increased UDP receive buffer size to 262140
2. Added properties for ffmpeg.outputbuffersize, ffmpeg.inputbuffersize and mediaserver.outputbuffersize
3. Set default size for input/output buffers to 32768
4. Added signal quality output to the STATUS command
5. Set a short timeout on UDP read to try and reduce latency
6. Added a PrimeNetEncoder.bat file with recommended settings to pass to java

Version 1.2.4 (Beta) - Download

1. Fixed mediaserver.transfer = false.
2. Added the ability for the OutputWatcher to reset the tuner if data is not produced in a timely fashion
3. Enhanced the exception handling in the TunerOutput thread. This was causing issues with keeping the UDP port open
4. Set thread priority to TunerOutput to MAX. Set thread priority to Watcher to MIN
5. Cleaned up some of the code that was double buffering streams. This might have been causing performance issues
6. Added timeout to the UDP connections

Note: PrimeNetEncoder.properties was removed from the download. Users will need to run the application once to generate a default properties file. Documentation was updated to reflect this.

Version 1.2.2 (Beta) - Download

1. Added media server transfer
2. Using STDIN/STDOUT to transfer data between ffmpeg and PrimeNetEncoder
3. PrimeNetEncoder is handling Stream from HDHomeRun instead of ffmpeg
4. Added ffmpeg setting analyzeduration and probesize
5. Added tuner locking (Note: I do a force unlock when ever I start a new recording)
6. Modified discovery logic to only respond to discovery requests if there is not an active connection with SageTV server

Note: If you are upgrading from a previous version I recommend that you remove the current tuner entries from Sage.properties file and allow SageTV to use network encoder discovery to add the tuners. This ensures that the right properties are added to SageTV. If you are using Windows Firewall please review the install guide for addition ports that need to be opened.

Version 1.0.1 (Beta) - Download

1. Better error handling when binding port is already in use
2. Added setting for delay to wait for ffmpeg to fully start
3. Added scaling property to the transcoding to allow resizing video
4. Adding setting for changing codec used for transcoding

Version 1.0.0 - Download

1. Initial Release

[nyplayer]

Imortant*************************

The properties Included in the Doc are wrong they will be corrected once the Coder gets a chance. The correct ports are below. I have attatched the corrected properties file PrimeNetEncoder.zip

#
#Example Setings file for PrimeNetEncoder
#
tuners.count=3
tuner0.name=HDHomeRun Prime Tuner 0
tuner0.port=7000
tuner0.enabled=True
tuner0.id=FFFFFFFF
tuner0.number=0
tuner0.transcoder.port=5000
tuner0.transcode.enabled=False
tuner0.transcode.deinterlace=True
tuner0.transcode.bitrate=4000
# Example for h.264 safe scaling to 720p: trunc(oh*a/2)*2:720
# A setting of blank will do no scaling
tuner0.transcode.scaling=
tuner0.transcode.preset=ultrafast
# Codec is an experimental setting for testing hardware encoding
# There are development builds of ffmpeg that incude those features
tuner0.transcode.codec=libx264
tuner1.name=HDHomeRun Prime Tuner 1
tuner1.port=7001
tuner1.id=FFFFFFFF
tuner1.number=1
tuner1.enabled=True
tuner1.transcoder.port=5010
tuner1.transcode.enabled=False
tuner1.transcode.deinterlace=True
tuner1.transcode.bitrate=4000
tuner1.transcode.scaling=
tuner1.transcode.preset=ultrafast
tuner1.transcode.codec=libx264
tuner2.enabled=True
tuner2.id=FFFFFFFF
tuner2.number=2
tuner2.name=HDHomeRun Prime Tuner 2
tuner2.port=7002
tuner2.transcoder.port=5020
tuner2.transcode.enabled=False
tuner2.transcode.deinterlace=True
tuner2.transcode.bitrate=4000
tuner2.transcode.scaling=
tuner2.transcode.preset=ultrafast
tuner2.transcode.codec=libx264
HDHomeRunConfig.path=C\:\\Program Files\\Silicondust\\HDHomeRun\\hdhomerun_config.exe
ffmpeg.path=ffmpeg.exe
# This setting is in miliseconds.  
# Increasing setting may result in less halts in starting recording
ffmpeg.delay=500
discovery.port=8271

Attached is the doc on setup of Non Prime DLNA OTA tuners..... HDHR4-2US and HDTC-2US

[uberpixel]

Looking forward to giving this a try this weekend. I'm hoping this will resolve my random pixelation and sound pops.

Couple of questions. Why would I want to transcode to H264? And why would I want to use this for the non-prime HDHR?

Also, does this replace SageDCT and does it need to be removed from my installation? Which version of Silicondust Firmware does this work with? I've been reluctant to update not knowing if it would break SageDCT.

-uberpixel

[Fuzzy]

Originally Posted by uberpixel

Couple of questions. Why would I want to transcode to H264? And why would I want to use this for the non-prime HDHR?

The answer to the first answers the second. Space saving, and better playback on devices (many of which no longer support MPEG-2).

[nyplayer]

Originally Posted by uberpixel

Looking forward to giving this a try this weekend. I'm hoping this will resolve my random pixelation and sound pops.

Couple of questions. Why would I want to transcode to H264? And why would I want to use this for the non-prime HDHR?

Also, does this replace SageDCT and does it need to be removed from my installation? Which version of Silicondust Firmware does this work with? I've been reluctant to update not knowing if it would break SageDCT.

-uberpixel

I am on the latest firmware as Silicondust has done so many changes that if you are not on the latest beta you should be for EX. Hd Homerun View for Kodi and android.. Fuzzy answered your other questions. I completely removed SAGEDCT and am quite happy I did. As far as none Prime tuners Sage remuxes the mpg and it messes it up that you cannot even extract CC. Also you can esaily update to the latest FFMPG simply by dropping the FFMPEG exe in the folder.

I get no pixelation what so ever since I switched to this encoder.

PS if you are reluctant then stay where you are as some people fear change.

[jvl711]

Originally Posted by uberpixel

Looking forward to giving this a try this weekend. I'm hoping this will resolve my random pixelation and sound pops.

Couple of questions. Why would I want to transcode to H264? And why would I want to use this for the non-prime HDHR?

Also, does this replace SageDCT and does it need to be removed from my installation? Which version of Silicondust Firmware does this work with? I've been reluctant to update not knowing if it would break SageDCT.

-uberpixel

You do not need to remove SageDCT. I would suggest you stop the SageDCT service while you are testing my application though. The machine I developed this on had SageDCT installed on it while I was developing and testing this.

Josh

[uberpixel]

Well, after trying to set this up I can report that it is not idiot proof...

I'm not an IT guy (Mechanical Engineer) so it's possible that I missed some implied steps in the install process (which I thought I followed correctly) but I'm having problems nonetheless.

The odd behaviour starts after I add the new tuner. At first it shows 1 "Digital Tuner" but when I select it, it pauses and then another "Digital Tuner" option shows up (see attached screenshot). If I select either - the wizard moves on to the next step. Then when I get back to the source summary page, it lists 3 identical versions of the same Prime tuner (see attached screenshot).

If I go back and remove the new source and add it again, it shows 4 "Digital Tuner" options to select...

If I try to tune a channel with the new source it says no signal.

I have not removed the legacy SageDCT tuners from my source list but I have disable the service.

I'm running the latest stable firmware from HDHomerun 20141210. I know you said latest Beta but I was hedging my bets in case this didn't work so I could go back to a previously stable SageDCT solution. Java 8. More system info in my signature.

Any ideas where I may have screwed up? I can post my properties files if that would help.

-uberpixel

[nyplayer]

Originally Posted by uberpixel

Well, after trying to set this up I can report that it is not idiot proof...

I'm not an IT guy (Mechanical Engineer) so it's possible that I missed some implied steps in the install process (which I thought I followed correctly) but I'm having problems nonetheless.

The odd behaviour starts after I add the new tuner. At first it shows 1 "Digital Tuner" but when I select it, it pauses and then another "Digital Tuner" option shows up (see attached screenshot). If I select either - the wizard moves on to the next step. Then when I get back to the source summary page, it lists 3 identical versions of the same Prime tuner (see attached screenshot).

If I go back and remove the new source and add it again, it shows 4 "Digital Tuner" options to select...

If I try to tune a channel with the new source it says no signal.

I have not removed the legacy SageDCT tuners from my source list but I have disable the service.

I'm running the latest stable firmware from HDHomerun 20141210. I know you said latest Beta but I was hedging my bets in case this didn't work so I could go back to a previously stable SageDCT solution. Java 8. More system info in my signature.

Any ideas where I may have screwed up? I can post my properties files if that would help.

-uberpixel

By any chance are you using Diamond or Gemstone? I am asking this because I saw this when using Diamond but not the default STV. If you stop and restart the SageTVService you will see that it is a mirage. I had the same problem when using the firewire Network tuner.

[uberpixel]

Gemstone...

I'll try the install again with the default STV and see what happens.

Not sure why that would cause the "No Signal" result but I'll give it a whirl.

-uberpixel

Originally Posted by nyplayer

By any chance are you using Diamond or Gemstone? I am asking this because I saw this when using Diamond but not the default STV. If you stop and restart the SageTVService you will see that it is a mirage. I had the same problem when using the firewire Network tuner.

[nyplayer]

Originally Posted by uberpixel

Gemstone...

I'll try the install again with the default STV and see what happens.

Not sure why that would cause the "No Signal" result but I'll give it a whirl.

-uberpixel

That would not cause the no signal just the duplicate showings of tuners the no signal is usually a firewall issue. Make sure ffmpeg is defined in the firewall I gave full access to the ffmpeg in the PrimeNetEncoderv1.0.0 folder. As I added tuners I did not want to keep opening ports.

[uberpixel]

Same result with the default SageTV 7 STV.

Still getting multiple instances of the same tuner on the same port.

Showing 3 all on port 7000 for example. Then no signal when I try to tune.

-uberpixel

[nyplayer]

Originally Posted by uberpixel

Same result with the default SageTV 7 STV.

Still getting multiple instances of the same tuner on the same port.

Showing 3 all on port 7000 for example. Then no signal when I try to tune.

-uberpixel

You cannot do a preview it will not work. Is there a way for you to test without the firewall? turn off firewall go to the guide and view a channel. For now ignore the duplicate tuners you are seeing just set 1 up. for tuner 0 tuner 1 tuner 2. It will not affect anything as far as recording etc... If you simply disable Gemstone you will still see the duplicate tuners ... I have no answer for this but it is only a visual problem not a working problem.

Ps I am also using HDHomerun Prime + (Comcast)

[Deacon Crusher]

So, I have a Ceton infinitv 6 which I love, but suddenly I'm having very strange behavior, mostly with recordings from it.

Please take a look at a couple posts in this thread

http://forums.sagetv.com/forums/showthread.php?t=62071

and if someone could please tell me if I switch to the hdhomerun prime that I have and use this software package if I'm likely to resolve this problem.

I'll likely get a second cable card and leave the silicon dust in and just set those tuners as below my atsc and the prime tuners in priority as being down a net of 3 tuners would be a drag.

Thanks

[jvl711]

Originally Posted by Deacon Crusher

So, I have a Ceton infinitv 6 which I love, but suddenly I'm having very strange behavior, mostly with recordings from it.

Please take a look at a couple posts in this thread

http://forums.sagetv.com/forums/showthread.php?t=62071

and if someone could please tell me if I switch to the hdhomerun prime that I have and use this software package if I'm likely to resolve this problem.

I'll likely get a second cable card and leave the silicon dust in and just set those tuners as below my atsc and the prime tuners in priority as being down a net of 3 tuners would be a drag.

Thanks

I do not think I have seen the specific issues you are describing, but it is possible that my solution may clean up the files a little better than SageDCT. Since the files are sent through a newer version of ffmpeg minor issues in the file seem to be corrected. I think it may be worth a try.

Josh

[nyplayer]

Any chance of getting the tuner locking in the next release? This will also help with certain tuner interrupts.

[jvl711]

Originally Posted by nyplayer

Any chance of getting the tuner locking in the next release? This will also help with certain tuner interrupts.

Yes. I just need to find a good stopping point on what I am working on. I am starting another project to add Vera (formally MiCasaVerde) as a plugin into sage.

[uberpixel]

Originally Posted by jvl711

Yes. I just need to find a good stopping point on what I am working on. I am starting another project to add Vera (formally MiCasaVerde) as a plugin into sage.

Great news about Vera! I've been wondering if someone would give that a try!

Let me know if you need an idiot to help you idiot-proof for you.

-uberpixel

[Deacon Crusher]

Originally Posted by jvl711

Yes. I just need to find a good stopping point on what I am working on. I am starting another project to add Vera (formally MiCasaVerde) as a plugin into sage.

Also a micasaverde user here so happy to help test this also when you get it running.

literally about to work on using your prime tuner/encoder software this minute.

Hopefully it goes smoothly.

thanks

[jarredduq]

I started getting the error below on one of my tuners. Every time sage tries to record from this tuner it shows as a failed recording. What address is it referring to?

05/09/2015 14:30:18 - Setting local IP address to: 192.168.1.2
05/09/2015 14:30:18 - Setting local IP address to: 192.168.1.2
05/09/2015 14:30:18 - Starting encoder thread: 131EDFC5-0
05/09/2015 14:30:18 - Error binding (131EDFC5 0): Address already in use: JVM_Bind

[nyplayer]

Originally Posted by jarredduq

I started getting the error below on one of my tuners. Every time sage tries to record from this tuner it shows as a failed recording. What address is it referring to?

05/09/2015 14:30:18 - Setting local IP address to: 192.168.1.2
05/09/2015 14:30:18 - Setting local IP address to: 192.168.1.2
05/09/2015 14:30:18 - Starting encoder thread: 131EDFC5-0
05/09/2015 14:30:18 - Error binding (131EDFC5 0): Address already in use: JVM_Bind

Sounds like you might have 2 tuners with the same names ... or same ports.