Ahh... Now I see. I am not sure why I did that. I might change that later. I was probably just playing with different techniques.

I thought you did it that way because you were using the upload id method to create the recording.

The UploadID method is optional, turned on or off with the mediaserver.transfer=true line in the .properties file. We're discussing the behavior when it is set to false.

In version 3 of the SageTV network encoder protocol the start recording command sends the uploadID and the FileName. You can either write directly to the file (CIFS or local), or you can upload the file utilizing the uploadID passed to the Sage MediaServer.

Now that I think of it I do not think Sage cares how you get the file to it. I suppose you could use any methodology that would allow it to read it back at the same time you are writing to it.

Correct, there's no real difference as far as sage is concerned. The advantage of the MediaServer method is that it keeps everything in basic TCP/UDP messaging, so things like CIFS/SMB security don't matter. It allows the SageTVService process to be the only thing writing and reading the files. When the encoder is running on the same system, however, it's just a bit more steps going through the networking, especially when it's already going through ffmpeg, which could write the files itself.

I updated to RC1 last night, used the java switches from your batch file and did a little testing. Everything seems to be running much better, I haven't noticed any picture/sound corruptions since the update, whereas they were pretty frequent before.


Thanks for the hard work on this.

I installed 1.2.5 and so far so good... I will post if i have issues.

So i finally got my cable card properly paired with Comcast and now instead of HBO saying i am not subscribed, it says it can not show it (it being the HomeRunPrime VIEW application) and that i can use Windows Media Center to see it.

I got the channels all mapped through to sage and yes, the dreaded No Signal.

Any ideas on how to handle the situation? or am i relegated to recording all HBO shows on the Xfinity DVR? (which i realize is not the end of the world + the is the HBOGo app)

Thanks in advance for your thoughts!

HBO is probably DRM protected you can do a scan on your Prime web page and it will show you which channels are DRM those you cannot use SageTV. So you might as well disable those channels in SageTV.

Comcast puts DRM protection on premium channels like HBO and Sage can't tune those. In order to access premium content using the Prime, you need a supported client. I believe that's currently limited to Windows Media Center, Playstation 3, and the Android app. Only WMC allows you to record DRM protected channels - at least until Silicon Dust gets their DVR experiment fully operational.

issues - help
 

I cannot get the HDHomerun to function --- it was a path issue with ffmpeg and primenet encoder...

1.2.5
 

Running 1.2.5 for a few days on Ubuntu 14.04... working great. Noticing less artifacts than with 1.2.4.

Only thing I am noticing is that the java process running PrimeNetEncoder is pegged at 100% all the time regardless of what's happening. Not really an issue for me because I'm running a couple of Xeon's with 8 cores each :) but I thought I'd mention it because I'm not sure why that'd be happening.

jvl711,

Just want to let you know that this release has been outstanding.. Not even one halt no artifacts ... No one has been able to steal the tuners when SageTV is recording .. my compliments. I no longer have to worry about watching on any other device using other software and Interrupting a sage recording.

Thank You

I am using PrimeNetEncoder embedded in SageTV, and was having halts with version 1.0.1. So, I thought I'd upgrade to v1.2.5. Dropped in the new jar file and added a few parms to the PrimeNetEncoder.properties. All of a sudden it started puking. So, I thought, maybe I should go console.
Tried to set up the batch job to start up via TaskScheduler at startup. Thought I had everything set up, but I could never get it to run. I would click the Run button, or right click the job and hit Run, but it never started. And yes, I did have the "allow job to be started on demand" clicked.

So, then I decided to run the console from the command line, and did a status. It was complaining about couldn't find 'c\:\\Program Files\\SiliconDust\\HDHomeRun\\hdomerun_config.exe'.
Turns out that jvl11 must have changed the input scheme for the string, and we don't have to escape the special characters any more. So, removed the double backslashes. Now the console can do a status.
So, I re-enabled the embedded PrimeNetEncoder, and ran 3 recordings on it. Seems to be doing great so far.

I am still puzzled/confused as to why TaskScheduler wouldn't start my batch job tho. No messages that I could find in the Event Viewer, so I'm not sure how to debug that little jewel.
Running on Windows 7 32-bit. I have a 64-bit setup with 16GB of ram waiting for me to take the time to port over to the new OS. Want to do that since I run SageTV and Plex on this box, and 4GB seems to be a bit tight. And I'm on a Phenom II X4 B93, and planning on upgrading to a Phenon II X6 1055T.

Anyway, some info for others who might run into a similar issue.

Can someone briefly (is that possible?) summarize the changes needed in the sagetv.properties files, when moving forward from 1.0.1 to 1.2.5?

I remember doing quite a bit of editing to the sagetv.properties file when installing 1.0.1. Some of this may have been from moving from SageDCT to PrimeNetEncoder.

And of course now it's difficult to keep track of what needs to stay, be added, or be removed :bang:

I would not even use the 1.0.1 properties ... if you run the 1.2.5 jar it will create a sample properties and all you have to do is populate your tuner ID.

He was asking about the sage.properties file, not the PrimeNetEncoder.properties file. If you keep port numbers the same, you would not need to make any changes in the sage.properties file when upgrading.

I've been on the 1.2.5 build since it was released and it has been working great.

Got up this morning and noticed I had the little red i on the UI for 'halt detected in recording'.

The PrimeNetEncoder box was showing an exception:

Attached the PrimeNetEncoder log file for this tuner.

The 10:30-11:00 recording was ok. The 11:00-11:30 is when the java exception happened.

Is there any possibility that either the HDHomeRun software was removed/modified, or the HDHomeRun itself might have malfunctioned??? It looks like when it was checking for the lock it was either unable to call the hdhomerun_config app, or the hdhomerun_config app was unable to talk to the device.

How were you able to recover from this? Did you have to restart the PrimeNetEncoder? Did you have to reset the HDHomeRun?

I just moved over to v1.2.5, and from internal to external PrimeNetEncoder. Thought I had everything working ok, but today I started noticing this in my tuner1.log:

10/15/2015 21:27:09 - Tuner bridge has transfered: 6102448
10/15/2015 21:27:09 - Tuner bridge has transfered: 6285372
10/15/2015 21:27:09 - Tuner has produced data in (5750ms)
10/15/2015 22:57:02 - Start commmand received: START HDHomeRun Prime Tuner 1 Digital TV Tuner|1710799592|767|2889942844912|e:\Videos\HouseHuntersInternational-S08E60-SouthYarraIstheNewBlack-23039305-0.ts|Great
10/15/2015 22:57:02 - -------------------------------------------------------------------------------
10/15/2015 22:57:02 - Switching Channel for Tuner: 131B4C09 1
10/15/2015 22:57:02 - -------------------------------------------------------------------------------
10/15/2015 22:57:02 - Channel: 767
10/15/2015 22:57:02 - File: HouseHuntersInternational-S08E60-SouthYarraIstheNewBlack-23039305-0.ts
10/15/2015 22:57:02 - UploadID: 1710799592
10/15/2015 22:57:02 - Quality: Great
10/15/2015 22:57:02 - Local IP: 192.168.0.10
10/15/2015 22:57:02 - Listening Port: 7001
10/15/2015 22:57:02 - Stream listening Port: 5010
10/15/2015 22:57:02 - Checking to see if the tuner is locked.
10/15/2015 22:57:02 - Tuner is locked. Force unlocking the tuner.
10/15/2015 22:57:02 - Switch channel: 767
10/15/2015 22:57:02 - Using Lockkey: 1976438938
10/15/2015 22:57:02 - Command output: null
10/15/2015 22:57:02 - Send stream to UDP port: 5010
10/15/2015 22:57:02 - Using Lockkey: 1976438938
10/15/2015 22:57:02 - Command output: null
10/15/2015 22:57:02 - Passing stream to SageTV unaltered (ffmpeg stream copy)
10/15/2015 22:57:02 - Starting TunerOutput thread for stdin to ffmpeg then stdout to SageTV MediaServer
10/15/2015 22:57:02 - Tuner output thread constructed for UploadID: 1710799592
10/15/2015 22:57:02 - Tuner output thread HDHomeRun(UDP) -> PrimeNetEncoder(SDIN) -> ffmpeg(STDOUT) -> SageTV Media Server(TCP)
10/15/2015 22:57:02 - Sleeping to allow ffmpeg to fully launch: 1000
10/15/2015 22:57:02 - Tuner bridge has transfered: 0
10/15/2015 22:57:02 - TunerBridge thread started udpPort: 5010
10/15/2015 22:57:03 - Sending write open command
10/15/2015 22:57:03 - Unhandled Exception in tuner bridge: Address already in use: Cannot bind
10/15/2015 22:57:03 - TunerBridge thread exited
10/15/2015 22:57:03 - Tuner bridge has transfered: 0
10/15/2015 22:57:03 - Tuner bridge has transfered: 0
10/15/2015 22:57:03 - Tuner bridge has transfered: 0
10/15/2015 22:57:03 - Tuner bridge has transfered: 0
10/15/2015 22:57:04 - Tuner bridge has transfered: 0
10/15/2015 22:57:04 - Tuner bridge has transfered: 0
10/15/2015 22:57:04 - Tuner bridge has transfered: 0
10/15/2015 22:57:04 - Tuner bridge has transfered: 0
10/15/2015 22:57:05 - Tuner bridge has transfered: 0
10/15/2015 22:57:05 - Tuner bridge has transfered: 0


Not sure what that exception means? What do I need to look for to see if it's still/already running?

After those errors it picked up and recorded everything on that tuner with no problems, nothing was reset or restarted. I wasn't around to do anything to the system, it was during the middle of the day.