PrimeNetEncoder - HDHomeRun Prime Network Encoder

[mgpaulus]

Originally Posted by mgpaulus

put your runEncoder.bat file into my PrimeEncoder directory and ran it. Same stinking Exception. I'm thinking we're gonna need to look at that .java file to see where the exception is being thrown and what object is Null.

Thanks for your help so far, but bedtime for bonzo.... Have to pick this up again another evening....

Well, got back to it tonight. Thought I'd try a couple of different things. So, I brought the PrimeNetEncoder directory over to my linux/mythtv box, and it worked fine there. Then I brought it over to my main windows box, and it worked there.

Decided to install JDK 1.7.0_79 and put in that JRE into \program files\java\jre, and walla, everything is now working.... Guess I had a wonky Java install of 1.7.0_67. Anyway, thanks for the patience.

[uberpixel]

Originally Posted by nyplayer

The tuners in Sage stay the same you just have to update the new properties file with tuner ids and tuner names from your old property file...copy over ffmpeg and use the new jar.

Hmm. Tried that. Didn't work. Still says there aren't any tuners that can encode the channel I'm trying to view.

Comparing the 100 and 101 versions of the properties files I noticed this... Wondering if it was intentional?

100
tuner0.port=7000
tuner1.port=7001
tuner2.port=7002
tuner0.transcoder.port=5000
tuner1.transcoder.port=5010
tuner2.transcoder.port=5020

101
tuner0.port=7000
tuner1.port=5001
tuner2.port=5002
tuner0.transcoder.port=5000
tuner1.transcoder.port=7001
tuner2.transcoder.port=7002

I tried it both ways with the 101 .jar and neither worked so I may have a different issue.

-uberpixel

[nyplayer]

That is the reason I only run batch files so that if there is a problem I do not have to shutdown Sage .... once i have it running I can then use the sageservice to load it.

Originally Posted by uberpixel

Hmm. Tried that. Didn't work. Still says there aren't any tuners that can encode the channel I'm trying to view.

Comparing the 100 and 101 versions of the properties files I noticed this... Wondering if it was intentional?

100
tuner0.port=7000
tuner1.port=7001
tuner2.port=7002
tuner0.transcoder.port=5000
tuner1.transcoder.port=5010
tuner2.transcoder.port=5020

101
tuner0.port=7000
tuner1.port=5001
tuner2.port=5002
tuner0.transcoder.port=5000
tuner1.transcoder.port=7001
tuner2.transcoder.port=7002

I tried it both ways with the 101 .jar and neither worked so I may have a different issue.

-uberpixel

It is wrong I fixed mine

I think there is a mistake in the properties. they should say enabled=True
tuner0.enabled=0
tuner1.enabled=0
tuner2.enabled=0

Original Properties

#
#Example Setings file for PrimeNetEncoder
#
tuners.count=3
tuner0.name=HDHomeRun Prime Tuner 0
tuner0.port=7000
tuner0.enabled=0
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=5001
tuner1.id=FFFFFFFF
tuner1.number=1
tuner1.enabled=0
tuner1.transcoder.port=7001
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=0
tuner2.id=FFFFFFFF
tuner2.number=2
tuner2.name=HDHomeRun Prime Tuner 2
tuner2.port=5002
tuner2.transcoder.port=7002
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

Corrected.

#
#Example Setings file for PrimeNetEncoder
#
tuners.count=3
tuner0.name=HDHomeRun Prime Tuner 1
tuner0.port=7000
tuner0.enabled=True
tuner0.id=131A192A
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 2
tuner1.port=7001
tuner1.id=131A192A
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=131A192A
tuner2.number=2
tuner2.name=HDHomeRun Prime Tuner 3
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=1000
discovery.port=8271

[jvl711]

Originally Posted by nyplayer

That is the reason I only run batch files so that if there is a problem I do not have to shutdown Sage .... once i have it running I can then use the sageservice to load it.




It is wrong I fixed mine

I think there is a mistake in the properties. they should say enabled=True
tuner0.enabled=0
tuner1.enabled=0
tuner2.enabled=0

Original Properties

#
#Example Setings file for PrimeNetEncoder
#
tuners.count=3
tuner0.name=HDHomeRun Prime Tuner 0
tuner0.port=7000
tuner0.enabled=0
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=5001
tuner1.id=FFFFFFFF
tuner1.number=1
tuner1.enabled=0
tuner1.transcoder.port=7001
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=0
tuner2.id=FFFFFFFF
tuner2.number=2
tuner2.name=HDHomeRun Prime Tuner 2
tuner2.port=5002
tuner2.transcoder.port=7002
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

Corrected.

#
#Example Setings file for PrimeNetEncoder
#
tuners.count=3
tuner0.name=HDHomeRun Prime Tuner 1
tuner0.port=7000
tuner0.enabled=True
tuner0.id=131A192A
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 2
tuner1.port=7001
tuner1.id=131A192A
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=131A192A
tuner2.number=2
tuner2.name=HDHomeRun Prime Tuner 3
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=1000
discovery.port=8271

Oppps

I updated the download. Should hopefully be correct now. Glad I marked that one as beta.

[Fuzzy]

Originally Posted by jvl711

Oppps

I updated the download. Should hopefully be correct now. Glad I marked that one as beta.

Perhaps the best thing, going forward, is to have upgraders only replace the .jar, and not the .properties file. Then, when the program launches, it reads in the existing file. Any new fields added that do not exist in the file can be written to it either blank or with the default value of the new property filled in.

This would provide seemless upgrades.

[uberpixel]

Originally Posted by jvl711

Oppps

I updated the download. Should hopefully be correct now. Glad I marked that one as beta.

I think you still have the ports wrong in the latest upload. See post #62 above.

I have it working after setting the enabled property to true.

-uberpixel

[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 uberpixel

I think you still have the ports wrong in the latest upload. See post #62 above.

I have it working after setting the enabled property to true.

-uberpixel

Hmm. Still having halts.

Also noticed that the tuners disappear after a restart.

Maybe I'll try running it outside of Sage.

-uberpixel

[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

[Deacon Crusher]

while adding prime encoder to sage I'm getting multiple digital tuner entries for each tuner???

Edit

That problem went away, but my network encoders are saying functioning FALSE? no love so far.

Edit again

your prime properties file has port 5000 but the port in the mmc lines you have us insert into sage are 7000 are they supposed to be different or the same?

ANOTHER EDIT>
Also, here's my problem I assume from prime logs

04/26/2015 09:07:27 - Setting local IP address to: 192.168.167.13
04/26/2015 09:07:27 - Setting local IP address to: 192.168.167.13
04/26/2015 09:07:27 - Starting encoder thread: 13106B9B-0
04/26/2015 09:07:27 - Error binding (13106B9B 0): Address already in use: JVM_Bind

but I don't get quite how to fix. I'm running everything on one machine (sage server.)

Edit again

mostly fixed. tuners showing working, now starting to test.

Thanks

[Deacon Crusher]

okay, after user error, documentation clarification and some fiddling I'm really happy with this setup.

Seems to be working very reliably and no more recording/playback problems, through first 24 hours or so. If I can get through a full week then will be thrilled.

Thanks very much to jvl711 for this solution. Your timing was incredible and so glad I bought a Prime when it came out even if just to sit around on the shelf until now.

I'm also testing the the sagedct 2.7.02 which I'd never needed before. Curious to see if I can get that to "solve" my problems also.

Thanks

[nyplayer]

Originally Posted by Deacon Crusher

okay, after user error, documentation clarification and some fiddling I'm really happy with this setup.

Seems to be working very reliably and no more recording/playback problems, through first 24 hours or so. If I can get through a full week then will be thrilled.

Thanks very much to jvl711 for this solution. Your timing was incredible and so glad I bought a Prime when it came out even if just to sit around on the shelf until now.

I'm also testing the the sagedct 2.7.02 which I'd never needed before. Curious to see if I can get that to "solve" my problems also.

Thanks

You do know that SAGEDCT is using a outdated FFMPEG it did cause problems on my system.

[Deacon Crusher]

Sort of new that it had an embedded ffmpeg, but wasn't clear if folks thought that was the issue or not. Thanks for info.

[jarredduq]

Originally Posted by nyplayer

You do know that SAGEDCT is using a outdated FFMPEG it did cause problems on my system.

Can you update the FFMPEG that SageDCT is using?

[nyplayer]

Originally Posted by jarredduq

Can you update the FFMPEG that SageDCT is using?

You will have to ask Andy that. This Prime Encoder you simply drop in the latest FFMPEG.

[Deacon Crusher]

FYI

I did start that conversation with Andy Sunday evening and Monday day he got me a test build of a drop-in replacement of a couple files that work with his 2702 release that update ffmpeg.

I got 2702 and the replacement files installed very late last night and did a quick test and seemed to work, so now in place today and turned off a couple channels in my prime tuner so they'd record using my ceton today and we'll see how it goes.

Separately and more on target for this thread, this solution of jvl711's is the bomb. Was recording 5 shows simultaneously for a fair chunk of Monday night using 2 and even all 3 of the prime tuners (including a 3 plus hour recording of a depressing Giants game) at different times and it worked like a charm. Never hiccuped as far as I could tell.

So, big thumps up to the Prime Network Encoder.

Originally Posted by nyplayer

You will have to ask Andy that. This Prime Encoder you simply drop in the latest FFMPEG.