SageTV Community

SageTV Community (http://forums.sagetv.com/forums/index.php)
-   Hardware Support (http://forums.sagetv.com/forums/forumdisplay.php?f=9)
-   -   PrimeNetEncoder - HDHomeRun Prime Network Encoder (http://forums.sagetv.com/forums/showthread.php?t=62055)

jarredduq 04-28-2015 09:18 PM

Quote:

Originally Posted by Deacon Crusher (Post 571744)
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.


Find out if Andy will allow you to post the updated files. Just got my HDHomeRun tuner today. However, I would like to keep my Ceton tuner, if it could be made to work correctly with the updated files from Andy.

Monedeath 04-29-2015 10:12 AM

Quote:

Originally Posted by jarredduq (Post 571759)
Find out if Andy will allow you to post the updated files. Just got my HDHomeRun tuner today. However, I would like to keep my Ceton tuner, if it could be made to work correctly with the updated files from Andy.

Looks like Andy posted the updated files on his website.

jarredduq 04-29-2015 08:06 PM

Quote:

Originally Posted by Monedeath (Post 571778)
Looks like Andy posted the updated files on his website.

Applied update. Now I've got 7 tuners at my disposal. It's great to see this community coming alive again and the open source version hasn't even been released yet!

Ender 04-29-2015 11:13 PM

1 Attachment(s)
I ave been tinkering with this for a while, and seem to have messed it up. I cannot get sage to tune a channel with this. I get an error (-10) no encoders can tune the selected station.

I looked at my tuner logs, and it appears that it is looking for an encoder on my sage server, rather than the HDHR. I have changed all the requisite properties files to my knowledge, and am running it from within sage, not from the command line. I have also turned off the windows firewall.

Attached are my properties files, and a few logs.

Any guidance would be greatly appreciated.

nyplayer 04-29-2015 11:27 PM

Quote:

Originally Posted by Ender (Post 571823)
I ave been tinkering with this for a while, and seem to have messed it up. I cannot get sage to tune a channel with this. I get an error (-10) no encoders can tune the selected station.

I looked at my tuner logs, and it appears that it is looking for an encoder on my sage server, rather than the HDHR. I have changed all the requisite properties files to my knowledge, and am running it from within sage, not from the command line. I have also turned off the windows firewall.

Attached are my properties files, and a few logs.

Any guidance would be greatly appreciated.

The Properties are wrong in the download they have to be corrected see this post. Follow that corrected properties just change 131A192A to your ID.

http://forums.sagetv.com/forums/show...6&postcount=63

nyplayer 04-29-2015 11:33 PM

jvl711,

You need to correct the property file in your download causing confusion. Thank You.

Ender 04-30-2015 12:23 AM

Quote:

Originally Posted by nyplayer (Post 571824)
The Properties are wrong in the download they have to be corrected see this post. Follow that corrected properties just change 131A192A to your ID.

http://forums.sagetv.com/forums/show...6&postcount=63

It was worth a try, unfortunately the issue still remains...

nyplayer 04-30-2015 07:07 AM

Quote:

Originally Posted by Ender (Post 571827)
It was worth a try, unfortunately the issue still remains...

re-post your properties files. It works you obviously have something wrong either firewall or properties.

nyplayer 04-30-2015 07:36 AM

1 Attachment(s)
Corrected properties file just change FFFFFFFF to your tuner. The one in the download is wrong.

Ender 04-30-2015 08:27 PM

Nyplayer,

Thank You for your help, I was able to get SageDCT 2.73 to work, the Prime encoder was intriguing, alas I was chasing down a rabbit hole, and could not see an end so I took a tangent.

jarredduq 05-14-2015 11:00 PM

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 05-14-2015 11:41 PM

Quote:

Originally Posted by jarredduq (Post 572232)
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.

jarredduq 05-15-2015 03:57 PM

Quote:

Originally Posted by nyplayer (Post 572233)
Sounds like you might have 2 tuners with the same names ... or same ports.

I'm going to be replacing my Ceton tuner with a 2nd HDHomeRun, so hopefully that will eliminate the conflicts.

I've prepped my properties files to account for the 2nd HDHomeRun and will be turning it up later today.

jarredduq 05-15-2015 04:02 PM

Music Choice Channel on Comcast
 
Has anybody had issues with the music channels? When I tune to one of the music channels, I just get a black screen. I'm able to tune them on my computer through VLC and also the silicondust app on my Android phone.

I'm thinking it may be something going on with FFMPEG.

This also affects the Ceton tuner I have running through SageDCT. If I switch SageDCT to raw, then the music channel will tune correctly.

However, I'm not happy with SageDCT and the pixelating/drop-outs I get on the recordings and will be replacing the Ceton with another HDHomerun.

For now I'm just remapping the music channels to use my HDPVR through the cable box.

uberpixel 05-15-2015 09:07 PM

My "PrimeNetEncoder.txt" file just hit 58GB... :eek:

Any idea why?

I assume I can just delete and it will recreate as needed.

-uberpixel

nyplayer 05-15-2015 10:05 PM

Quote:

Originally Posted by uberpixel (Post 572251)
My "PrimeNetEncoder.txt" file just hit 58GB... :eek:

Any idea why?

I assume I can just delete and it will recreate as needed.

-uberpixel

Mine is very very small I suggest you look at it because it should only log to it when you restart the program.

Code:

04/15/2015 19:50:11 - Running PrimeNetEncoder in Console Mode
04/15/2015 19:50:11 - PrimeNetEncoder Version: 1.0.1
04/15/2015 19:50:11 - Starting tunner threads


uberpixel 05-16-2015 10:27 AM

Quote:

Originally Posted by nyplayer (Post 572252)
Mine is very very small I suggest you look at it because it should only log to it when you restart the program.

Code:

04/15/2015 19:50:11 - Running PrimeNetEncoder in Console Mode
04/15/2015 19:50:11 - PrimeNetEncoder Version: 1.0.1
04/15/2015 19:50:11 - Starting tunner threads


As it turns out, I had a bad stick of ram that was causing some serious instability for my server. I ran Memtest last night to confirm. I suspect that was the reason why PrimeNetEncoder was freaking out. The file was actually so large that I couldn't open it, but from the preview pane I saw entries in the log referring to running out of memory...

Since putting in a good set of ram and deleting the log, I have only the same three entries you've noted.

I suspect that the remaining gremlins I was chasing (capture device failure and recording hiccups) with this tuner option were probably related to this ram issue. I've got my fingers crossed!

-uberpixel

mechling-burgh 05-21-2015 06:13 AM

Well I finally solved my halts in recordings I believe. The problem seems to be that i have several green drives and that spin down when not in use. I set the windows power setting to not spin down the drives after a set time period about two weeks ago and that seemed to solve my problems. I haven't had any halts since then. So if anyone is still getting halts even after setting the delay time in the latest version try turning off spin down drives under windows power settings. I prefer saving power but I like to have the full shows also.

jarredduq 05-21-2015 12:14 PM

It's working good for me as well compared with the results I was getting with SageDCT. However, for some reason my music channels do not work. I get "no signal" when tuning to them. There are no errors in the logs, etc.

As mentioned in a previous post, it is probably something going on with FFMPEG. The music channels are at a lower bitrate than a typical channel. Not sure if there is anything that can be done.

nyplayer 05-21-2015 12:51 PM

One thing I did do also to eliminate all problems etc... is to make my windows 7 SageTV server act more like a file server by doing some registry tweaks. Windows 7 is limited as far as acting like a file server without any tweaks. The changes I made are in red... Also improves Plex KODI file sharing.

Code:

Tuning Workstation for Server-like Loads

NT Workstation and NT Server have vastly different performance characteristics due to the internal tuning that the NT operating system, which is identical on both, performs. Most tuning parameters are inaccessible, but a few are located in the Registry. If you are running Server and you double-click on the Server entry of the Services tab in the Control Panel's Network applet, you will get a dialog that lets you determine what type of application you want the machine to be tuned for. Choices let you select between "Minimize Memory Used", "Balance", "Maximize Usage for File Sharing", and "Maximize Usage for Network Applications". This dialog box is not presented on Workstation installations. The various selections actually change the values of two Registry values:

HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\LargeSystemCache

and

HKLM\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters\Size

This table (which was derived from sessions with Regmon) presents the settings you should select on a Workstation to achieve the same effect you would get using the dialog box were your system a Server.

Tuning Target              LargeSystemCache        Size
Minimize Memory Used            0                  1
Balance                            0                  2
File Sharing                    1                  3
Network Applications            0                  3

Also if you see the error below in event viewer those settings will take care of that.

Source: srv
Event ID: 2017 or 2019
Level: Error
The server was unable to allocate from the system nonpaged pool because the server reached the configured limit for nonpaged pool allocations.

waynedunham 05-24-2015 07:54 PM

Quote:

Originally Posted by mechling-burgh (Post 572380)
Well I finally solved my halts in recordings I believe. The problem seems to be that i have several green drives and that spin down when not in use. I set the windows power setting to not spin down the drives after a set time period about two weeks ago and that seemed to solve my problems. I haven't had any halts since then. So if anyone is still getting halts even after setting the delay time in the latest version try turning off spin down drives under windows power settings. I prefer saving power but I like to have the full shows also.

That is why I go with WD Blacks.

KryptoNyte 05-25-2015 05:57 AM

Quote:

Originally Posted by mechling-burgh (Post 572380)
Well I finally solved my halts in recordings I believe. The problem seems to be that i have several green drives and that spin down when not in use. I set the windows power setting to not spin down the drives after a set time period about two weeks ago and that seemed to solve my problems. I haven't had any halts since then. So if anyone is still getting halts even after setting the delay time in the latest version try turning off spin down drives under windows power settings. I prefer saving power but I like to have the full shows also.

There is also a head parking feature that can be disabled on the green drives. When head parking is enabled, it has been rumored that it shortens the life of the drive.

nkd 06-05-2015 08:02 PM

Only one tuner is being used
 
Hello experts .. I am at my wits end so i am hoping that some one can help
I installed PrimeNewEncoder yesterday and all went well but today i noticed that only one of my tuners is being used. I have reinstalled everything but same results. I am using the encoder on the same machine as my headless sage server.

My config
1. 2 nics, one for LAN and another connected to HDHR
2. Firewall off to remove any related issues

HELP!!!

Sage died yesterday during the NBA game and fortunately we were home, but I need to get this going for Sunday's game; need to record 3 programs in parallel.

I have been using SageDCT for some time but that failed 2 days ago

Logs as below

----------------------------------------------------
06/05/2015 18:36:27 - Setting local IP address to: 169.254.65.17
06/05/2015 18:36:27 - Setting local IP address to: 169.254.65.17
06/05/2015 18:36:27 - Starting encoder thread: 13195F9B-0
06/05/2015 18:36:39 - Unknown Command: BUFFER HDHomeRun Prime Tuner 0 Digital TV Tuner|2|83886080|D:\RecordedTV\HDHomeRunPrimeTuner0on1270017000DigitalTVTuner-0.mpgbuf|Great
06/05/2015 18:36:39 - -------------------------------------------------------------------------------
06/05/2015 18:36:39 - Stopping Recording: 13195F9B 0
06/05/2015 18:36:39 - -------------------------------------------------------------------------------
06/05/2015 18:38:00 - -------------------------------------------------------------------------------
06/05/2015 18:38:00 - Switching Channel for Tuner: 13195F9B 0
06/05/2015 18:38:00 - -------------------------------------------------------------------------------
06/05/2015 18:38:00 - Local IP: 169.254.65.17
06/05/2015 18:38:00 - Listening Port: 7000
06/05/2015 18:38:00 - ffmpeg Transcode Port: 5000
06/05/2015 18:38:00 - Starting transcoder: D:\RecordedTV\MLBBaseball-SanFranciscoGiantsatPhiladelphiaPhillies-14716188-1.ts
06/05/2015 18:38:00 - Passing stream to file unaltered
06/05/2015 18:38:01 - Switch channel: 720
06/05/2015 18:38:01 - Send stream to transcoder: 5000
06/05/2015 18:42:34 - -------------------------------------------------------------------------------
06/05/2015 18:42:34 - Stopping Recording: 13195F9B 0
06/05/2015 18:42:34 - -------------------------------------------------------------------------------
06/05/2015 18:42:34 - Stopping the stream:
06/05/2015 18:42:34 - Recording stopped
06/05/2015 18:44:25 - Setting local IP address to: 169.254.65.17
06/05/2015 18:44:25 - Setting local IP address to: 169.254.65.17
06/05/2015 18:44:25 - Starting encoder thread: 13195F9B-0
06/05/2015 18:47:37 - -------------------------------------------------------------------------------
06/05/2015 18:47:37 - Switching Channel for Tuner: 13195F9B 0
06/05/2015 18:47:37 - -------------------------------------------------------------------------------
06/05/2015 18:47:37 - Local IP: 169.254.65.17
06/05/2015 18:47:37 - Listening Port: 7000
06/05/2015 18:47:37 - ffmpeg Transcode Port: 5000
06/05/2015 18:47:37 - Starting transcoder: D:\RecordedTV\MLBBaseball-SanFranciscoGiantsatPhiladelphiaPhillies-14716188-2.ts
06/05/2015 18:47:37 - Passing stream to file unaltered
06/05/2015 18:47:38 - Switch channel: 720
06/05/2015 18:47:38 - Send stream to transcoder: 5000

---------------------------------------------------------

06/05/2015 18:36:27 - Setting local IP address to: 169.254.65.17
06/05/2015 18:36:27 - Setting local IP address to: 169.254.65.17
06/05/2015 18:36:27 - Starting encoder thread: 13195F9B-1
06/05/2015 18:44:25 - Setting local IP address to: 169.254.65.17
06/05/2015 18:44:25 - Setting local IP address to: 169.254.65.17
06/05/2015 18:44:25 - Starting encoder thread: 13195F9B-1

-----------------------------------------------------------

06/05/2015 18:36:27 - Setting local IP address to: 169.254.65.17
06/05/2015 18:36:27 - Setting local IP address to: 169.254.65.17
06/05/2015 18:36:27 - Starting encoder thread: 13195F9B-2
06/05/2015 18:44:25 - Setting local IP address to: 169.254.65.17
06/05/2015 18:44:25 - Setting local IP address to: 169.254.65.17
06/05/2015 18:44:25 - Starting encoder thread: 13195F9B-2

KryptoNyte 06-05-2015 08:10 PM

Because there is a time frame involved, the first question is; do you have a complete system image from a short time ago, when the system was still running properly?

When you say that you reinstalled, did you also reinstall SageTV from scratch?

nyplayer 06-05-2015 08:14 PM

Post your primencoder properties file and your sagetv.properties file.

PS are you trying to get SAGEDCT to work too or the PrimeEncoder only one can run at a time.

nkd 06-05-2015 08:28 PM

1 Attachment(s)
Frankly i moved to PrinmeNetEncoder as SageDCT failed. In my setup I have SageDCT service disabled

nkd 06-05-2015 08:29 PM

thanks for your help

nyplayer 06-05-2015 08:34 PM

Quote:

Originally Posted by nkd (Post 572908)
Frankly i moved to PrinmeNetEncoder as SageDCT failed. In my setup I have SageDCT service disabled

Your tuner ports for the other 2 tuners were wrong they are corrected below. They are wrong in the DOC I have asked for this to be corrected. Just make corrections to the prime encoder properties file... and restart,

Code:

#
#Example Setings file for PrimeNetEncoder
#
tuners.count=3
tuner0.name=HDHomeRun Prime Tuner 0
tuner0.port=7000
tuner0.enabled=True
tuner0.id=13195F9B
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=13195F9B
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=13195F9B
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


nkd 06-05-2015 09:10 PM

that's it ... thank you !!

To answer KryptoNyte, i do have a image but i wanted to ask the forum first before i go the restore route tomorrow. In general Sage has been rock solid

thank you again

nyplayer 06-05-2015 09:11 PM

Quote:

Originally Posted by nkd (Post 572911)
that's it ... thank you !!

To answer KryptoNyte, i do have a image but i wanted to ask the forum first before i go the restore route tomorrow. In general Sage has been rock solid

thank you again

You are welcomed.

KryptoNyte 06-05-2015 09:40 PM

Quote:

Originally Posted by nkd (Post 572911)

To answer KryptoNyte, i do have a image but i wanted to ask the forum first before i go the restore route tomorrow. In general Sage has been rock solid

1) Were you ever able to figure out what caused the problem with SageDCT?

2) Do you see any difference in quality between running SageDCT and PrimeNetEncoder?

nyplayer 06-05-2015 09:51 PM

Quote:

Originally Posted by KryptoNyte (Post 572914)
1) Were you ever able to figure out what caused the problem with SageDCT?

2) Do you see any difference in quality between running SageDCT and PrimeNetEncoder?

Since i have a lot of experience with both SAGEDCT and PrimeEncoder. I will give you reasons why I switched to Prime Encoder.

1. SAGEDCT was not being updated with PrimeEncoder it is a matter of dropping in the most recent ffmpeg.exe.

2. PrimeEncoder uses the HdHomerun software for channel change. This means that I can also use it with the new OTA tuners (which I do). Sage remuxes the TS OTA files to mpg Incorrectly. I could not even extract closed captions ... no problem doing this when using PrimEncoder files.
See this thread.
http://forums.sagetv.com/forums/showthread.php?t=61971


3. If you have a Powerful PC you can transcode to h264 on the fly.


$. I was getting breakups with SageDCT.

I would recommend it for anyone that uses a Prime.

nkd 06-06-2015 12:18 AM

From my end, i don't have a working SageDCT solution so at this point i can not comment. I have not had a lot of issues with SageDCT in the past; some failures related to SageDCT loosing the connection with the tuners once in a while and frequent video tearing. So i was thinking of moving to PrimeNewEncoder sometime over the summer. But the recent SageDCT failure accelerated that move.

Greg2dot0 06-07-2015 04:10 AM

PrimetNetEncoder Properties errors
 
I installed this last night in a crisis because the latest HDHR Firmware broke SageDCT last night.

There are a couple of lines that I had to change beyond the tuner.id=

For tuner1 and tuner2, I had to update the ports and transcoder ports in order to get those tuners working. I assume that this is correct:

OOB Config
tuner1.port=5001
tuner1.transcoder.port=7001

tuner2.port=5002
tuner2.transcoder.port=7002

Modified Config
tuner1.port=7001
tuner1.transcoder.port=5010

tuner2.port=7002
tuner2.transcoder.port=5020

nyplayer 06-07-2015 06:50 AM

Quote:

Originally Posted by Greg2dot0 (Post 572929)
I installed this last night in a crisis because the latest HDHR Firmware broke SageDCT last night.

There are a couple of lines that I had to change beyond the tuner.id=

For tuner1 and tuner2, I had to update the ports and transcoder ports in order to get those tuners working. I assume that this is correct:

OOB Config
tuner1.port=5001
tuner1.transcoder.port=7001

tuner2.port=5002
tuner2.transcoder.port=7002

Modified Config
tuner1.port=7001
tuner1.transcoder.port=5010

tuner2.port=7002
tuner2.transcoder.port=5020



Yes see my post.
http://forums.sagetv.com/forums/show...&postcount=108

Maybe you should post in the SAGEDCT thread what problems you had and how the firmware broke SAGEDCT. Might help other users.

KryptoNyte 06-07-2015 07:17 AM

Is the HDHR firmware upgrade ever forcibly applied, or does it always prompt a user?

nyplayer 06-07-2015 07:24 AM

Quote:

Originally Posted by KryptoNyte (Post 572931)
Is the HDHR firmware upgrade ever forcibly applied, or does it always prompt a user?

Everything is optional there is a prompt if an upgrade is available that is strictly up to you ... but with the new changes etc... and the new soon to be released DVR software it is prudent to upgrade if you plan on using the new DVR etc...

Also it would be nice if it was posted exactly what was happening in SAGEDCT.... with the new firmware I am sure Andy can fix it.

Greg2dot0 06-07-2015 07:51 AM

Quote:

Originally Posted by nyplayer (Post 572930)
Yes see my post.
http://forums.sagetv.com/forums/show...&postcount=108

Maybe you should post in the SAGEDCT thread what problems you had and how the firmware broke SAGEDCT. Might help other users.

Yeah, I did see that the same thing was already reported, but will add a "me 2". I thought I had scoured this thread before posting this, but obviously in the panic of all the sudden no tuners, I must have missed that post.

nyplayer 06-07-2015 07:54 AM

Quote:

Originally Posted by Greg2dot0 (Post 572933)
Yeah, I did see that the same thing was already reported, but will add a "me 2". I thought I had scoured this thread before posting this, but obviously in the panic of all the sudden no tuners, I must have missed that post.

Yeah the Programmer to this great piece of code ... is busy at the moment and stated he will get back soon... I am sure he will the update the docs.

phelme 06-07-2015 02:15 PM

Quote:

Originally Posted by nyplayer (Post 572915)
3. If you have a Powerful PC you can transcode to h264 on the fly.

I'm curious if anyone is actually using this feature regularly and if so, what their system is. I tried it for a while on my AMD A10-A6800K based server and the 3 tuners from the Prime if all recording give the quad core quite a workout. :)

I've since turned the transcoding off and went back to running SJQ at night to do Handbrake conversions.


All times are GMT -6. The time now is 03:25 AM.

Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2023, vBulletin Solutions Inc.
Copyright 2003-2005 SageTV, LLC. All rights reserved.