SageTV Community  

Go Back   SageTV Community > Hardware Support > Hardware Support

Notices

Hardware Support Discussions related to using various hardware setups with SageTV products. Anything relating to capture cards, remotes, infrared receivers/transmitters, system compatibility or other hardware related problems or suggestions should be posted here.

Reply
 
Thread Tools Search this Thread Display Modes
  #681  
Old 08-11-2017, 03:08 PM
jvl711's Avatar
jvl711 jvl711 is offline
Sage Expert
 
Join Date: Jan 2004
Posts: 606
Quote:
Originally Posted by phelme View Post
it's definitely not show specific, happens to every one on KTVU.

guess I could take this opportunity to check out OpenDCT and see if it has the same issue in my area.

I haven't used SageDCT in years, glad to hear it's still working.

Edit: Hmm, did notice something when looking again at the audio streams via VLC and MPC-HC of KTVU, raw, from the HDHomeRun Prime. The "main" audio stream is curiously marked as "mono" for shows now. I wonder if PrimeNetEncoder sees that and skips it hoping to find a multichannel one instead and lands on the secondary program.

Code:
Video: MPEG2 Video 1280x720 59.94fps [V: mpeg2 main, yuv420p, 1280x720]
Audio: Dolby AC3 48000Hz mono 192kbps [A: English [eng] (ac3, 48000 Hz, mono, 192 kb/s)]
Audio: Dolby AC3 48000Hz stereo 192kbps [A: Spanish [spa] (ac3, 48000 Hz, stereo, 192 kb/s)]
That is interesting. ffmpeg is doing all of the heavy lifting on identify and converting streams. PrimeNetEncoder is just a middleman between HDHomeRun ffmpeg and SagTV. It is supposed to pass the streams as they are without modification. I wonder if for some reason it is having an issue identifying the mono first stream.

Did you check a recording that was done with PrimeNetEncoder after the fact to see what streams are in the file?
Reply With Quote
  #682  
Old 08-11-2017, 11:13 PM
phelme's Avatar
phelme phelme is offline
Sage Icon
 
Join Date: Dec 2006
Posts: 1,048
Received this from KTVU this afternoon to a query about their mono broadcast:

Thanks for the email. You are correct. We have an issue with an audio device that will be repaired soon.

So that answers that. 😀

Now the question is, what is the reason PrimeNetEncoder is having issues with that mono stream?
Reply With Quote
  #683  
Old 08-12-2017, 11:19 PM
phelme's Avatar
phelme phelme is offline
Sage Icon
 
Join Date: Dec 2006
Posts: 1,048
Quote:
Originally Posted by jvl711 View Post
That is interesting. ffmpeg is doing all of the heavy lifting on identify and converting streams. PrimeNetEncoder is just a middleman between HDHomeRun ffmpeg and SagTV. It is supposed to pass the streams as they are without modification. I wonder if for some reason it is having an issue identifying the mono first stream.

Did you check a recording that was done with PrimeNetEncoder after the fact to see what streams are in the file?
Yep I have, on a few recordings. There is always only the one secondary stream. They are marked usually as Spanish and in stereo, but are English and often have the descriptive commentary. But I imagine that has something to do with their temporary audio equipment and how they have it configured.

Curious though, if there are multiple streams usually, why doesn't ffmpeg encode them all?
Reply With Quote
  #684  
Old 08-13-2017, 03:10 AM
bisongde bisongde is offline
Sage User
 
Join Date: Mar 2016
Location: New York
Posts: 12
Hey guys,

Can I get a fresh set of eyes on this? Been at it 17 hours straight trying to get everything to work. A little background: we have two HDHomeRun "Tech" units (commercial). Essentially each one is two HDHomeRun Prime CC units in a single chassis. Server is running on Ubuntu 16.04.

HDHomeRun app and VLC can tune and play all channels in the lineup without issue. With the same lineup and EPG Sage isn't able to tune or render anything. It was briefly able to shortly after initial setup but hasn't done anything in quite some time. Clients have been configured on both Windows and Linux clients without improvement.

Here's the output of one of the tuner's PNE files that seems to indicate the specific issue PNE is having, if anyone can make sense of it I'd be very grateful:

Code:
08/13/2017 01:29:02 - Setting local IP address to: 127.0.1.1
08/13/2017 01:29:02 - Starting encoder thread: FFFFFFFF-2
08/13/2017 02:09:15 - Setting local IP address to: 10.0.0.112
08/13/2017 02:09:15 - Starting encoder thread: 10.0.0.201-2
08/13/2017 02:17:56 - Setting local IP address to: 10.0.0.112
08/13/2017 02:17:56 - Starting encoder thread: 10.0.0.201-2
08/13/2017 02:27:50 - Setting local IP address to: 10.0.0.112
08/13/2017 02:27:50 - Starting encoder thread: 10.0.0.201-2
08/13/2017 04:23:35 - Setting local IP address to: 10.0.0.112
08/13/2017 04:23:35 - Starting encoder thread: 10.0.0.201-3
08/13/2017 04:24:40 - Get property request recieved
08/13/2017 04:24:40 - Sending: 
31
mmc/encoders/31035317/100/0/brightness=-1
mmc/encoders/31035317/100/0/broadcast_standard=
mmc/encoders/31035317/100/0/contrast=-1
mmc/encoders/31035317/100/0/device_name=PrimeNetEncoder 201-3
mmc/encoders/31035317/100/0/encode_digital_tv_as_program_stream=false
mmc/encoders/31035317/100/0/hue=-1
mmc/encoders/31035317/100/0/saturation=-1
mmc/encoders/31035317/100/0/sharpness=-1
mmc/encoders/31035317/100/0/tuning_mode=Cable
mmc/encoders/31035317/100/0/tuning_plugin=
mmc/encoders/31035317/100/0/tuning_plugin_port=0
mmc/encoders/31035317/100/0/video_crossbar_index=0
mmc/encoders/31035317/100/0/video_crossbar_type=100
mmc/encoders/31035317/audio_capture_device_name=
mmc/encoders/31035317/capture_config=2000
mmc/encoders/31035317/default_device_quality=Great
mmc/encoders/31035317/delay_to_wait_after_tuning=0
mmc/encoders/31035317/device_class=
mmc/encoders/31035317/encoder_host=10.0.0.112:7003
mmc/encoders/31035317/encoder_merit=0
mmc/encoders/31035317/encoding_host=10.0.0.112:7003
mmc/encoders/31035317/fast_network_encoder_switch=false
mmc/encoders/31035317/forced_video_storage_path_prefix=
mmc/encoders/31035317/last_cross_index=0
mmc/encoders/31035317/last_cross_type=100
mmc/encoders/31035317/live_audio_input=
mmc/encoders/31035317/multicast_host=
mmc/encoders/31035317/never_stop_encoding=false
mmc/encoders/31035317/video_capture_device_name=PrimeNetEncoder 201-3
mmc/encoders/31035317/video_capture_device_num=0
mmc/encoders/31035317/video_encoding_params=Great

08/13/2017 04:27:57 - Unknown Command: BUFFER PrimeNetEncoder 201-3 Digital TV Tuner|1054650385|2|83886080|/var/media/tv/PrimeNetEncoder2013onUS4GRABBER7003DigitalTVTuner-0.mpgbuf|Great
08/13/2017 04:27:57 - -------------------------------------------------------------------------------
08/13/2017 04:27:57 - Stopping Recording: 10.0.0.201 3
08/13/2017 04:27:57 - -------------------------------------------------------------------------------
08/13/2017 04:51:28 - Setting local IP address to: 10.0.0.112
08/13/2017 04:51:28 - Starting encoder thread: 10.0.0.201-3
08/13/2017 04:52:07 - -------------------------------------------------------------------------------
08/13/2017 04:52:07 - Stopping Recording: 10.0.0.201 3
08/13/2017 04:52:07 - -------------------------------------------------------------------------------
Reply With Quote
  #685  
Old 08-13-2017, 11:05 AM
Fuzzy's Avatar
Fuzzy Fuzzy is offline
SageTVaholic
 
Join Date: Sep 2005
Location: Jurupa Valley, CA
Posts: 9,957
Quote:
Originally Posted by bisongde View Post
Hey guys,

Can I get a fresh set of eyes on this? Been at it 17 hours straight trying to get everything to work. A little background: we have two HDHomeRun "Tech" units (commercial). Essentially each one is two HDHomeRun Prime CC units in a single chassis. Server is running on Ubuntu 16.04.

HDHomeRun app and VLC can tune and play all channels in the lineup without issue. With the same lineup and EPG Sage isn't able to tune or render anything. It was briefly able to shortly after initial setup but hasn't done anything in quite some time. Clients have been configured on both Windows and Linux clients without improvement.

Here's the output of one of the tuner's PNE files that seems to indicate the specific issue PNE is having, if anyone can make sense of it I'd be very grateful:

Code:
08/13/2017 01:29:02 - Setting local IP address to: 127.0.1.1
08/13/2017 01:29:02 - Starting encoder thread: FFFFFFFF-2
08/13/2017 02:09:15 - Setting local IP address to: 10.0.0.112
08/13/2017 02:09:15 - Starting encoder thread: 10.0.0.201-2
08/13/2017 02:17:56 - Setting local IP address to: 10.0.0.112
08/13/2017 02:17:56 - Starting encoder thread: 10.0.0.201-2
08/13/2017 02:27:50 - Setting local IP address to: 10.0.0.112
08/13/2017 02:27:50 - Starting encoder thread: 10.0.0.201-2
08/13/2017 04:23:35 - Setting local IP address to: 10.0.0.112
08/13/2017 04:23:35 - Starting encoder thread: 10.0.0.201-3
08/13/2017 04:24:40 - Get property request recieved
08/13/2017 04:24:40 - Sending: 
31
mmc/encoders/31035317/100/0/brightness=-1
mmc/encoders/31035317/100/0/broadcast_standard=
mmc/encoders/31035317/100/0/contrast=-1
mmc/encoders/31035317/100/0/device_name=PrimeNetEncoder 201-3
mmc/encoders/31035317/100/0/encode_digital_tv_as_program_stream=false
mmc/encoders/31035317/100/0/hue=-1
mmc/encoders/31035317/100/0/saturation=-1
mmc/encoders/31035317/100/0/sharpness=-1
mmc/encoders/31035317/100/0/tuning_mode=Cable
mmc/encoders/31035317/100/0/tuning_plugin=
mmc/encoders/31035317/100/0/tuning_plugin_port=0
mmc/encoders/31035317/100/0/video_crossbar_index=0
mmc/encoders/31035317/100/0/video_crossbar_type=100
mmc/encoders/31035317/audio_capture_device_name=
mmc/encoders/31035317/capture_config=2000
mmc/encoders/31035317/default_device_quality=Great
mmc/encoders/31035317/delay_to_wait_after_tuning=0
mmc/encoders/31035317/device_class=
mmc/encoders/31035317/encoder_host=10.0.0.112:7003
mmc/encoders/31035317/encoder_merit=0
mmc/encoders/31035317/encoding_host=10.0.0.112:7003
mmc/encoders/31035317/fast_network_encoder_switch=false
mmc/encoders/31035317/forced_video_storage_path_prefix=
mmc/encoders/31035317/last_cross_index=0
mmc/encoders/31035317/last_cross_type=100
mmc/encoders/31035317/live_audio_input=
mmc/encoders/31035317/multicast_host=
mmc/encoders/31035317/never_stop_encoding=false
mmc/encoders/31035317/video_capture_device_name=PrimeNetEncoder 201-3
mmc/encoders/31035317/video_capture_device_num=0
mmc/encoders/31035317/video_encoding_params=Great

08/13/2017 04:27:57 - Unknown Command: BUFFER PrimeNetEncoder 201-3 Digital TV Tuner|1054650385|2|83886080|/var/media/tv/PrimeNetEncoder2013onUS4GRABBER7003DigitalTVTuner-0.mpgbuf|Great
08/13/2017 04:27:57 - -------------------------------------------------------------------------------
08/13/2017 04:27:57 - Stopping Recording: 10.0.0.201 3
08/13/2017 04:27:57 - -------------------------------------------------------------------------------
08/13/2017 04:51:28 - Setting local IP address to: 10.0.0.112
08/13/2017 04:51:28 - Starting encoder thread: 10.0.0.201-3
08/13/2017 04:52:07 - -------------------------------------------------------------------------------
08/13/2017 04:52:07 - Stopping Recording: 10.0.0.201 3
08/13/2017 04:52:07 - -------------------------------------------------------------------------------
"BUFFER" is the command sage uses when previewing the channels in the lineup, but it is not used for normal recording.. as such, I don't think PNE ever supported the buffer command. You'd need to configure it and go out to the guide and try to watch something there for sage to issue the proper START command to get it to start recordings, then check the log for that to see what is going on.
__________________
Buy Fuzzy a beer! (Fuzzy likes beer)

unRAID Server: i7-6700, 32GB RAM, Dual 128GB SSD cache and 13TB pool, with SageTVv9, openDCT, Logitech Media Server and Plex Media Server each in Dockers.
Sources: HRHR Prime with Charter CableCard. HDHR-US for OTA.
Primary Client: HD-300 through XBoxOne in Living Room, Samsung HLT-6189S
Other Clients: Mi Box in Master Bedroom, HD-200 in kids room
Reply With Quote
  #686  
Old 08-13-2017, 01:18 PM
bisongde bisongde is offline
Sage User
 
Join Date: Mar 2016
Location: New York
Posts: 12
Quote:
Originally Posted by Fuzzy View Post
"BUFFER" is the command sage uses when previewing the channels in the lineup, but it is not used for normal recording.. as such, I don't think PNE ever supported the buffer command. You'd need to configure it and go out to the guide and try to watch something there for sage to issue the proper START command to get it to start recordings, then check the log for that to see what is going on.
The TECH units are discovered by Sage off the bat. I don't know if this is true of consumer Primes as well.

I think initially we built using a 9.0.x .deb and we got signal and were even able to record. Then we realized that the OSS EPG plugin has been abandoned and the feature rolled into Sage proper, so we had to upgrade to the newest client and server (9.1.6 I think?). The tuners are still discovered by Sage immediately despite being network devices that operate off of RDP streams.

I came to PNE in the thought that maybe like the Cetons and SageDCT, Sage will see the tuners but not be able to use the RDP stream they produce.

If you configure the tuners themselves without PNE mediating, you get some of those config lines you see here:


Code:
mmc/encoders/31035317/100/0/encode_digital_tv_as_program_stream=false
mmc/encoders/31035317/100/0/hue=-1
mmc/encoders/31035317/100/0/saturation=-1
mmc/encoders/31035317/100/0/sharpness=-1
mmc/encoders/31035317/100/0/tuning_mode=Cable
mmc/encoders/31035317/100/0/tuning_plugin=
mmc/encoders/31035317/100/0/tuning_plugin_port=0
mmc/encoders/31035317/100/0/video_crossbar_index=0
mmc/encoders/31035317/100/0/video_crossbar_type=100
mmc/encoders/31035317/audio_capture_device_name=
mmc/encoders/31035317/capture_config=2000
mmc/encoders/31035317/default_device_quality=Great
mmc/encoders/31035317/delay_to_wait_after_tuning=0
Which makes me wonder if something is just not configured as it should be by default? Happy to post my entire Sage.properties file if someone could help me puzzle through it.
Reply With Quote
  #687  
Old 08-13-2017, 05:58 PM
Tiki's Avatar
Tiki Tiki is offline
Sage Icon
 
Join Date: Feb 2005
Location: Southwest Florida, USA
Posts: 1,925
Sage does not have native support for any cable card tuners. However, the Prime can also act like a clear QAM tuner (if your cable co broadcasts any clear QAM channels still), and Sage flies support those natively.

To use CC tuners like the Prime with Sage (or really any other special type of capture device that Sage doesn't know about), you need an external piece of software called a Network Encoder. The network encoder acts like a gateway and communicates to a sage in a standard way. There are at least three network encoders that people have written for CC tuners and posted on these forums: Prime Net Encoder, SageDCT, and OpenDCT.

All of these seem to work, but they are not all exactly the same. OpenDCT seems to be the best supported one right now and it has the most extra features, but it is also a little more complicated because there are a lot of configuration opens that can be adjusted and they are all done via configuration files. The author, EnterNoEscape, is very active on these forums and has been contributing a lot to the Sage Open Source development.
__________________
Server: Ryzen 2400G with integrated graphics, ASRock X470 Taichi Motherboard, HDMI output to Vizio 1080p LCD, Win10-64Bit (Professional), 16GB RAM
Capture Devices (7 tuners): Colossus (x1), HDHR Prime (x2)
,USBUIRT (multi-zone)
Source:
Comcast/Xfinity X1 Cable
Primary Client: Server Other Clients: (1) HD200, (1) HD300
Retired Equipment: MediaMVP, PVR150 (x2), PVR150MCE,
HDHR, HVR-2250, HD-PVR
Reply With Quote
  #688  
Old 08-13-2017, 05:59 PM
bisongde bisongde is offline
Sage User
 
Join Date: Mar 2016
Location: New York
Posts: 12
Getting closer

Okay, so I decompiled PrimeNetEncoder.jar because I got the following message on one of the tuners:

Code:
08/13/2017 04:37:23 - Start commmand received: START PrimeNetEncoder 204-3 Digital TV Tuner|311243780|74|3005226886162|/SAGE/RECORDINGS/30for30-TheUPart2-1508966-0.ts|Great
08/13/2017 04:37:23 - -------------------------------------------------------------------------------
08/13/2017 04:37:23 - Switching Channel for Tuner: 10.0.0.204 12
08/13/2017 04:37:23 - -------------------------------------------------------------------------------
08/13/2017 04:37:23 - Channel: 74
08/13/2017 04:37:23 - File: 30for30-TheUPart2-1508966-0.ts
08/13/2017 04:37:23 - UploadID: 311243780
08/13/2017 04:37:23 - Quality: Great
08/13/2017 04:37:23 - Local IP: 10.0.0.112
08/13/2017 04:37:23 - Listening Port: 7012
08/13/2017 04:37:23 - Stream listening Port: 5012
08/13/2017 04:37:23 - Checking to see if the tuner is locked.
08/13/2017 04:37:23 - Tuner is locked.  Force unlocking the tuner.
08/13/2017 04:37:23 - Switch channel: 74
08/13/2017 04:37:23 - 	Using Lockkey: 1543394950
08/13/2017 04:37:23 - 	Command output: ERROR: unknown getset variable
08/13/2017 04:37:23 - Send stream to UDP port: 5012
08/13/2017 04:37:23 - 	Using Lockkey: 1543394950
08/13/2017 04:37:23 - 	Command output: ERROR: unknown getset variable
08/13/2017 04:37:23 - Transcoding stream to SageTV as h.264
08/13/2017 04:37:23 - Starting TunerOutput thread for ffmpeg CIFS output to SageTV
08/13/2017 04:37:23 - Tuner output thread HDHomeRun(UDP) -> PrimeNetEncoder(STDIN) -> ffmpeg(STDOUT) -> PrimeNetEncoder -> File(CIFS/SMB)
08/13/2017 04:37:23 - Sleeping to allow ffmpeg to fully launch: 500
08/13/2017 04:37:23 - TunerBridge thread started udpPort: 5012
08/13/2017 04:37:23 - Tuner bridge has transfered: 0
08/13/2017 04:37:23 - TunerOutput thread exited
08/13/2017 04:37:23 - TunerBridge thread exited
08/13/2017 04:37:23 - Tuner bridge has transfered: 0
08/13/2017 04:37:23 - Tuner bridge has transfered: 0
08/13/2017 04:37:23 - Tuner bridge has transfered: 0
08/13/2017 04:37:24 - Tuner bridge has transfered: 0
08/13/2017 04:37:24 - Tuner bridge has transfered: 0
08/13/2017 04:37:24 - Tuner bridge has transfered: 0
08/13/2017 04:37:24 - Tuner bridge has transfered: 0
08/13/2017 04:37:25 - Tuner bridge has transfered: 0
08/13/2017 04:37:25 - Tuner bridge has transfered: 0
08/13/2017 04:37:25 - Tuner bridge has transfered: 0
08/13/2017 04:37:25 - Tuner bridge has transfered: 0
08/13/2017 04:37:26 - Tuner bridge has transfered: 0
08/13/2017 04:37:26 - Tuner bridge has transfered: 0
08/13/2017 04:37:26 - Tuner bridge has transfered: 0
08/13/2017 04:37:26 - Tuner bridge has transfered: 0
08/13/2017 04:37:27 - Tuner bridge has transfered: 0
08/13/2017 04:37:27 - Tuner bridge has transfered: 0
08/13/2017 04:37:27 - Tuner bridge has transfered: 0
08/13/2017 04:37:27 - Tuner bridge has transfered: 0
08/13/2017 04:37:28 - Tuner bridge has transfered: 0
08/13/2017 04:37:28 - No data transfered in 6000ms.  Reseting tuner channel and stream.
08/13/2017 04:37:28 - Switch channel: 74
08/13/2017 04:37:28 - 	Using Lockkey: 1543394950
08/13/2017 04:37:28 - 	Command output: ERROR: unknown getset variable
08/13/2017 04:37:28 - Send stream to UDP port: 5012
08/13/2017 04:37:28 - 	Using Lockkey: 1543394950
08/13/2017 04:37:28 - 	Command output: ERROR: unknown getset variable
08/13/2017 04:37:28 - Tuner bridge has transfered: 0
08/13/2017 04:37:28 - Tuner bridge has transfered: 0
08/13/2017 04:37:28 - Tuner bridge has transfered: 0
08/13/2017 04:37:29 - Tuner bridge has transfered: 0
08/13/2017 04:37:29 - Tuner bridge has transfered: 0
08/13/2017 04:37:29 - Tuner bridge has transfered: 0
08/13/2017 04:37:29 - Tuner bridge has transfered: 0
08/13/2017 04:37:30 - Tuner bridge has transfered: 0
08/13/2017 04:37:30 - Tuner bridge has transfered: 0
08/13/2017 04:37:30 - Tuner bridge has transfered: 0
08/13/2017 04:37:30 - Tuner bridge has transfered: 0
08/13/2017 04:37:31 - Tuner bridge has transfered: 0
08/13/2017 04:37:31 - Tuner bridge has transfered: 0
08/13/2017 04:37:31 - Tuner bridge has transfered: 0
08/13/2017 04:37:31 - Tuner bridge has transfered: 0
08/13/2017 04:37:32 - Tuner bridge has transfered: 0
08/13/2017 04:37:32 - Tuner bridge has transfered: 0
08/13/2017 04:37:32 - Tuner bridge has transfered: 0
08/13/2017 04:37:32 - Tuner bridge has transfered: 0
08/13/2017 04:37:33 - Tuner bridge has transfered: 0
08/13/2017 04:37:33 - No data transfered in 6000ms.  Reseting tuner channel and stream.
08/13/2017 04:37:33 - Switch channel: 74
08/13/2017 04:37:33 - 	Using Lockkey: 1543394950
08/13/2017 04:37:33 - 	Command output: ERROR: unknown getset variable
08/13/2017 04:37:33 - Send stream to UDP port: 5012
08/13/2017 04:37:33 - 	Using Lockkey: 1543394950
08/13/2017 04:37:33 - 	Command output: ERROR: unknown getset variable
08/13/2017 04:37:33 - Tuner bridge has transfered: 0
08/13/2017 04:37:33 - Tuner bridge has transfered: 0
08/13/2017 04:37:34 - Tuner bridge has transfered: 0
08/13/2017 04:37:34 - Tuner bridge has transfered: 0
08/13/2017 04:37:34 - Tuner bridge has transfered: 0
08/13/2017 04:37:34 - Tuner bridge has transfered: 0
08/13/2017 04:37:35 - Tuner bridge has transfered: 0
08/13/2017 04:37:35 - WARNING: Tuner has not produced data in (12000ms)
So it seems like either I've misconfigured my PrimeNetEncoder.properties file or the syntax for set /tuner<n>/lockkey is off in tuner.class, more likely the former. hdhomerun_config is definitely compatible with this tuner, I've run the commands on it manually with no issues.

Here's my properties file, jvl711, what am I screwing up here that's making it complain about the getset value? Is it the tuner numbers? Why am I getting an error for the BUFFER command?

Code:
bindingaddress.override=
ffmpeg.delay=500
ffmpeg.probesize=5000000
ffmpeg.analyzeduration=5000000
ffmpeg.path=/opt/sagetv/server/ffmpeg
HDHomeRunConfig.path=/usr/bin/hdhomerun_config
tuners.count=12
discovery.port=8271
discovery.enabled=true
mediaserver.transfer=false
ffmpeg.outputbuffersize=32768
ffmpeg.inputbuffersize=32768
mediaserver.outputbuffersize=32768
tuner0.name=PrimeNetEncoder 201-1
tuner0.id=10.0.0.201
tuner0.number=1
tuner0.port=7001
tuner0.transcoder.port=5001
tuner0.enabled=true
tuner0.transcode.enabled=enabled
tuner0.transcode.deinterlace=true
tuner0.transcode.bitrate=4000
tuner0.transcode.scaling=
tuner0.transcode.preset=veryfast
tuner0.transcode.codec=libx264
tuner1.name=PrimeNetEncoder 201-2
tuner1.id=10.0.0.201
tuner1.number=2
tuner1.port=7002
tuner1.transcoder.port=5002
tuner1.enabled=true
tuner1.transcode.enabled=enabled
tuner1.transcode.deinterlace=true
tuner1.transcode.bitrate=4000
tuner1.transcode.scaling=
tuner1.transcode.preset=veryfast
tuner1.transcode.codec=libx264
tuner2.name=PrimeNetEncoder 201-3
tuner2.id=10.0.0.201
tuner2.number=3
tuner2.port=7003
tuner2.transcoder.port=5003
tuner2.enabled=true
tuner2.transcode.enabled=true
tuner2.transcode.deinterlace=true
tuner2.transcode.bitrate=4000
tuner2.transcode.scaling=
tuner2.transcode.preset=veryfast
tuner2.transcode.codec=libx264
tuner3.name=PrimeNetEncoder 202-1
tuner3.id=10.0.0.202
tuner3.number=4
tuner3.port=7004
tuner3.transcoder.port=5004
tuner3.enabled=true
tuner3.transcode.enabled=true
tuner3.transcode.deinterlace=true
tuner3.transcode.bitrate=4000
tuner3.transcode.scaling=
tuner3.transcode.preset=veryfast
tuner3.transcode.codec=libx264
tuner4.name=PrimeNetEncoder 202-2
tuner4.id=10.0.0.202
tuner4.number=5
tuner4.port=7005
tuner4.transcoder.port=5005
tuner4.enabled=true
tuner4.transcode.enabled=true
tuner4.transcode.deinterlace=true
tuner4.transcode.bitrate=4000
tuner4.transcode.scaling=
tuner4.transcode.preset=veryfast
tuner4.transcode.codec=libx264
tuner5.name=PrimeNetEncoder 202-3
tuner5.id=10.0.0.202
tuner5.number=6
tuner5.port=7006
tuner5.transcoder.port=5006
tuner5.enabled=true
tuner5.transcode.enabled=true
tuner5.transcode.deinterlace=true
tuner5.transcode.bitrate=4000
tuner5.transcode.scaling=
tuner5.transcode.preset=veryfast
tuner5.transcode.codec=libx264
tuner6.name=PrimeNetEncoder 203-1
tuner6.id=10.0.0.203
tuner6.number=7
tuner6.port=7007
tuner6.transcoder.port=5007
tuner6.enabled=true
tuner6.transcode.enabled=true
tuner6.transcode.deinterlace=true
tuner6.transcode.bitrate=4000
tuner6.transcode.scaling=
tuner6.transcode.preset=veryfast
tuner6.transcode.codec=libx264
tuner7.name=PrimeNetEncoder 203-2
tuner7.id=10.0.0.203
tuner7.number=8
tuner7.port=7008
tuner7.transcoder.port=5008
tuner7.enabled=true
tuner7.transcode.enabled=true
tuner7.transcode.deinterlace=true
tuner7.transcode.bitrate=4000
tuner7.transcode.scaling=
tuner7.transcode.preset=veryfast
tuner7.transcode.codec=libx264
tuner8.name=PrimeNetEncoder 203-3
tuner8.id=10.0.0.203
tuner8.number=9
tuner8.port=7009
tuner8.transcoder.port=5009
tuner8.enabled=true
tuner8.transcode.enabled=true
tuner8.transcode.deinterlace=true
tuner8.transcode.bitrate=4000
tuner8.transcode.scaling=
tuner8.transcode.preset=veryfast
tuner8.transcode.codec=libx264
tuner9.name=PrimeNetEncoder 204-1
tuner9.id=10.0.0.204
tuner9.number=10
tuner9.port=7010
tuner9.transcoder.port=5010
tuner9.enabled=true
tuner9.transcode.enabled=true
tuner9.transcode.deinterlace=true
tuner9.transcode.bitrate=4000
tuner9.transcode.scaling=
tuner9.transcode.preset=veryfast
tuner9.transcode.codec=libx264
tuner10.name=PrimeNetEncoder 204-2
tuner10.id=10.0.0.204
tuner10.number=11
tuner10.port=7011
tuner10.transcoder.port=5011
tuner10.enabled=true
tuner10.transcode.enabled=true
tuner10.transcode.deinterlace=true
tuner10.transcode.bitrate=4000
tuner10.transcode.scaling=
tuner10.transcode.preset=veryfast
tuner10.transcode.codec=libx264
tuner11.name=PrimeNetEncoder 204-3
tuner11.id=10.0.0.204
tuner11.number=12
tuner11.port=7012
tuner11.transcoder.port=5012
tuner11.enabled=true
tuner11.transcode.enabled=true
tuner11.transcode.deinterlace=true
tuner11.transcode.bitrate=4000
tuner11.transcode.scaling=
tuner11.transcode.preset=veryfast
tuner11.transcode.codec=libx264
Reply With Quote
  #689  
Old 08-13-2017, 06:05 PM
bisongde bisongde is offline
Sage User
 
Join Date: Mar 2016
Location: New York
Posts: 12
Quote:
Originally Posted by Tiki View Post
Sage does not have native support for any cable card tuners. However, the Prime can also act like a clear QAM tuner (if your cable co broadcasts any clear QAM channels still), and Sage flies support those natively.

To use CC tuners like the Prime with Sage (or really any other special type of capture device that Sage doesn't know about), you need an external piece of software called a Network Encoder. The network encoder acts like a gateway and communicates to a sage in a standard way. There are at least three network encoders that people have written for CC tuners and posted on these forums: Prime Net Encoder, SageDCT, and OpenDCT.

All of these seem to work, but they are not all exactly the same. OpenDCT seems to be the best supported one right now and it has the most extra features, but it is also a little more complicated because there are a lot of configuration opens that can be adjusted and they are all done via configuration files. The author, EnterNoEscape, is very active on these forums and has been contributing a lot to the Sage Open Source development.
Cool. I'll check OpenDCT out as well...just asked a pretty long question with lots of code and realized that TunerNumber is relative to the individual device, not absolute. So each one is 0, 1, 2 even if it's your 7th tuner overall. Going to give that a swing and see how it goes.

Does OpenDCT offer integration with ffmpeg and transcoding to h.264?
Reply With Quote
  #690  
Old 08-13-2017, 07:15 PM
KarylFStein KarylFStein is offline
Sage Fanatic
 
Join Date: Apr 2006
Location: Westland, Michigan, USA
Posts: 999
Quote:
Originally Posted by bisongde View Post
Does OpenDCT offer integration with ffmpeg and transcoding to h.264?
Yes.
__________________
Home Network: https://karylstein.com/technology.html
Reply With Quote
  #691  
Old 10-12-2020, 03:48 PM
phelme's Avatar
phelme phelme is offline
Sage Icon
 
Join Date: Dec 2006
Posts: 1,048
I know this thread is stale but does anyone know if PrimeNetEncoder has ever supported ATSC sub-channel/program tuning? I'm trying to use this with the new Silicondust Connect Quattro (ATSC 3.0 tuner) and I keep getting errors like this

10/12/2020 14:24:22 - Switch channel: 33-65-2
10/12/2020 14:24:22 - Using Lockkey: 1650899869
10/12/2020 14:24:22 - Command output: ERROR: invalid virtual channel

I've looked at the docs for hdhomerun_config and it seems to imply that you first need to select the channel and then the program with a separate command i.e.

Code:
hdhomerun_config.exe FFFFFFFF set /tuner0/channel 33
hdhomerun_config.exe FFFFFFFF set /tuner0/program 4
does PNE do that?

I may have to set up OpenDCT instead if I can't get this to work.

thanks.

Last edited by phelme; 10-12-2020 at 03:57 PM.
Reply With Quote
  #692  
Old 10-18-2020, 10:47 AM
mgpaulus mgpaulus is offline
Sage Advanced User
 
Join Date: Mar 2011
Location: Colorado Springs, CO
Posts: 174
I would take the plunge and move over to OpenDCT if I were you. I haven't even thought of Prime Net Encoder since OpenDCT has come along. OpenDCT still has active support, many folks are using it, and you can get most any question answered in the OpenDCT thread.
Reply With Quote
Reply


Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
 
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Interest in HDHomeRun Prime Network Encoder jvl711 Hardware Support 175 04-13-2015 01:11 PM
Prime Encoder Script checkbin SageTV Linux 14 03-22-2015 07:50 AM
SageTV as a network encoder / recording on network encoder works, not from server perfessor101 SageTV Software 0 06-21-2014 05:59 AM
Ubuntu + HDHomerunPrime + Prime Encoder matt91 SageTV Linux 2 03-23-2014 03:46 PM
HDHomerun Prime? cenwesi Hardware Support 26 04-19-2011 05:40 PM


All times are GMT -6. The time now is 03:56 PM.


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