OpenDCT: An open source digital cable tuner.

[nyplayer]

I noticed that in SageTV Docker Java 11 ... opendct consumer defaults to ...

consumer.dynamic.default=opendct.consumer.MediaServerConsumerImpl

Which cause EXOPLAYER to fail on my MPEPG2 recordings I tried to change it to

consumer.dynamic.default=opendct.consumer.FFmpegTransSageTVConsumerImpl


But as soon as I restart the Docker it reverts to

consumer.dynamic.default=opendct.consumer.MediaServerConsumerImpl ...... on my windows install the default is consumer.dynamic.default=opendct.consumer.FFmpegTransSageTVConsumerImpl


Why can't I change this ? I am forced to use IJKPLAYER which the de-interlacer is terrible.

EDit...

Finally got around it ...I changed every instance of consumer=opendct.consumer.DynamicConsumerImpl to opendct.consumer.FFmpegTransSageTVConsumerImpl

[Zogg]

Is there a logical or practical limit to how many generic pipe tuners you can define with one instance of OpenDCT?

I have 2 Prime tuners and have 5 generic pipes defined (reserving one tuner for other use), and now want to add my HDHR Connect Quatro with 4 OTA tuners.

I wouldn't think there would be an issue with 9 tuners defined like this, but just checking, since in theory there could be 9 instances of ffmpeg running at once under one OpenDCT instance.

[nyplayer]

Originally Posted by Zogg

Is there a logical or practical limit to how many generic pipe tuners you can define with one instance of OpenDCT?

I have 2 Prime tuners and have 5 generic pipes defined (reserving one tuner for other use), and now want to add my HDHR Connect Quatro with 4 OTA tuners.

I wouldn't think there would be an issue with 9 tuners defined like this, but just checking, since in theory there could be 9 instances of ffmpeg running at once under one OpenDCT instance.

I have 20 Generic pipes for Pluto OTA Cable and TVE with Channels DVR backend.


generic.pipe.device_names_csv=tve01,tve02,tve03,tve04,tve05,tve06,tve07,tve08,tve09,tve10,tve11,tve12,tve13,tve14,tve15,tve16,tve17,tve18,tve19,tve20

[Zogg]

Originally Posted by nyplayer

I have 20 Generic pipes for Pluto OTA Cable and TVE with Channels DVR backend.


generic.pipe.device_names_csv=tve01,tve02,tve03,tve04,tve05,tve06,tve07,tve08,tve09,tve10,tve11,tve12,tve13,tve14,tve15,tve16,tve17,tve18,tve19,tve20

Asked and answered

[nyplayer]

What are the ODDs of having a new release of OPENDCT with FFMPEG 4/5 ? FFMPEG 4/5 can do ASTC 3.0.

[hufnagel]

So i'm having a problem setting up a new system for mom. I need to switch to an HDHR3-CC due to Optimum finally getting around to doing their dirty deed. I've failed to get the original system working right, so I built a new from scratch one, and am still having the same problem.
the HDHR viewer app can tune just fine, but SageTV keeps coming up with 'no signal' for all channels.

I've attached my opendct log file. it looks like the it keeps reporting that the tuner is already locked, but there's no other system attempting to use it. I bet it's something simple/stupid I overlooked, but i'm at a loss.

eta: adding my sagetv log, as well as the opendct config file, and dct_homerun.properties.
the sagetv log is a "clean" start up, attempted watch, shut down file also.

eta2: you can ignore any of the tuners listed that are NOT DCT-HDHomeRun Prime Tuner 1327AAA4-*.
the others are the legacy QAM tuners that are still working until 4/25 it appears, and they're being used by the old system. Obviously the new one sees them, but i'm not touching them.

eta3: a tedious line by line comparison between this new setup and my own personal one that uses the same HDHR3-CC hardware came up with no differences other than: device names, the older QAM units, an openDCT version difference (mine: 0.5,29. new: 0.5.32), and the new setup missing a single line: "consumer.ffmpeg.transcode_limit=6". I don't see that being a smoking gun though.

eta4: ok I have no idea why, but it just started working a couple hours ago. if anyone can give any insight I'd appreciate it. I hate having things that didn't work, then suddenly work, without any explaination.

[brandypuff]

I've been having a lot of problems recording shows with my OTA 2 tuner HDHomeRunExtend. The tuners are OK because i can record shows fine using the tuner and the JellyFin PVR software that accesses the tuners directly. I have a HDHomerun Prime Cable tuner that is working fine but the Extend just won't record shows reliably anymore. The signal strength is 100% so that's not an issue. I can watch live shows ok also using the HDHomerun app.

Any help would be appreciated. It worked fine for years.



10:24:52.797 [SageTVRequestHandler-109:HDHomeRun HDTC-2US Tuner 10562C06-0] ERROR SageTVRequestHandler - SageTV sent: 'START HDHomeRun HDTC-2US Tuner 10562C06-0 Digital TV Tuner|320711217|29-38-4|3307668585516|G:\Record2\PaintLikeAProWithPaintZoom-5137795-0.ts|Great', Replied: 'ERROR Device Start Failed'
10:24:52.797 [SageTVRequestHandler-109:HDHomeRun HDTC-2US Tuner 10562C06-0] ERROR SageTVRequestHandler - Encoder device is unable to start.
10:24:56.022 [SageTVTuningMonitor-60] DEBUG HDHomeRunControl - key: '/tuner0/vstatus' value: 'null' lockKey: '0' sendLength: 26 address: 192.168.0.220

[trk2]

Is JellyFin installed on the same computer as your Sage server? Or did you verify using the HDHomern app on the Sage server? I would start with making sure there is no weird network issue between the Extend and the Sage server. Also, is 192.168.0.220 the ip address of the extend?

[nyplayer]

bump ... Do not want to lose this thread.

[AlphaCrew]

I know right, this thread is solid gold!