InfiniTV4 with OpenDCT

[tomdomm]

Attempted to update from SagDCT to OpenDCT. Tuner appears to configure OK. All 4 channels seen in tuner config in SageTV 7.1.9.256. SageTV plays back previously recorded shows. Basic channels are view able in older Hauppauge tuners. HD/extended channels of course are not available without the M-card in InfiniTV4. But nothing gets through the InfiniTV4 now- SageDCT or OpenDCT. The cable company is sending signal as TVs see normal channels.
What am I missing?

[EnterNoEscape]

Are you trying to use the ClearQAM or DCT functionality? It sounds like you were trying to use OpenDCT with an InfiniTV 4 without CableCARD installed (ClearQAM) and that should work ok. SageDCT doesn't support ClearQAM as far as I have determined. Can you attach a you log file? It should give me a better idea of what's going on.

If you're using the Windows version, the logs will be under C:\ProgramData\OpenDCT\logs. You'll want to include wrapper.log and opendct.log. In Linux it will be under /var/log/opendct.

Update: In case you're using OpenDCT for ClearQAM, I recommend using the version I just posted. If it's locked up for the reason mentioned in the post, you can get it back by either rebooting the computer or going to the webpage for the tuner, navigating to the Log page, and entering the command "reboot" into the text box, then clicking Send. It will take a minute or two, before you can access the tuner after executing that command.

[tomdomm]

Tried both with M-card in and removed from InfiniTV4. Prefer DCT if that means extended HD digital channels. Noticed that OpenDCT uses 192.168.200.2 for local address, always used 127.0.0.1 under SageDCT-make a difference?

[KryptoNyte]

What cable company?

[HelenWeathers]

Originally Posted by tomdomm

.....Noticed that OpenDCT uses 192.168.200.2 for local address, always used 127.0.0.1 under SageDCT-make a difference?

If you're using OpenDCT service on the same machine as your SageTV OpenDCT should use 127.0.0.1 as well.

[EnterNoEscape]

Originally Posted by tomdomm

Tried both with M-card in and removed from InfiniTV4. Prefer DCT if that means extended HD digital channels. Noticed that OpenDCT uses 192.168.200.2 for local address, always used 127.0.0.1 under SageDCT-make a difference?

I recommend you leave the M-Card inserted. You'll get a lot more channels.

The 127.0.0.1 address is used for SageTV to communicate with OpenDCT if they are found to be on the same computer. It's ok to see that inside of SageTV. If you're talking about the local address property, that needs to remain 192.168.200.2. That setting is an override in case OpenDCT is getting your local address wrong. In this case it is almost certainly the correct address.

Open up your internet browser and navigate to http://192.168.200.1. Click on One. Click on Tuner. Scroll to the bottom of the page. There should be a section called Streaming Setup. What does it say right now or does it not exist? Also while you're on the website, go to the System tab and get the firmware version.

The errors in the log are implying that the URL http://192.168.200.1/get_var?i=0&s=diag&v=Streaming_IP is returning an internal error (error 500) which might mean you have an firmware prior to Ceton adding the streaming settings to their webpage. If this is the case and you do not want to upgrade the firmware, you can still use OpenDCT, but you'll need to use it in UPnP mode. To do this, stop the OpenDCT service, then use the shortcut to OpenDCT Properties on the Start Menu to open up opendct.properties. Change the value of upnp.dct.http_tuning to false. Start the service back up and you'll be tuning using pure UPnP. It will take longer to tune into channels this way. If this works for you, you can try to speed up tuning by changing the value of upnp.dct.fast_tuning to false. Always stop the service before making changes to opendct.properties.

[tomdomm]

Cable Company is Cincinnati Bell / Fioptics without the fiber or other improvements.
M-card stay in - it is the extra channels I want.

Both SageDCT and OpenDCT use the same InfiniTV4 card, having both on same system would cause conflict? So I've been uninstalling / reinstalling, activating/ deactivating services. Should I be removing the mmc/encoders entries from sage.properties? How do I get to a clean sage.properties file lacking old Centon tuner entries? Or is that not worth the effort?

If I read 'EnterNoEscape' correctly, I leave the 192.168.200.1 address in the OpenDCT setup properties but should /can change the address in Sage.properties. Till I remove SageDCT completely. Although if my card does not have streaming I lose the purpose of switching - faster tuning.
Cenon inifiTV Firmware=1.1.8.2
Centon Hardware = 6210
Driver Package = 13.6.3.1088

So my plan is to:
Stop SageTV service
Stop SageDCT services
Backup sage.properties & wiz.bin
Check OpenDCT properties verify 192.168.200.2 still there- no changes
Run OpenDCT as Console
OpenDCT Start Services
Change Sage.properties network_encoder_discovery to true
Not removing mmc/encoder SageDCT listing?
start sagetv
remove any InfiniTV tuners from setup
setup OpenCelon tuners
Go to http://192.168.200.1 in browser
check above parameters

Thank You ALL for Helping in my time of need

[tomdomm]

uninstalled SageDCT
Installed OpenDCT
Configured SageTV tuners
Ceton Infini Website tuners do NOT show Streaming Setup at bottom of screen.
System Firmware shows 1.1.8.2
All four tuners show WMDRM as RED
Tuning Adapter - TR Status as Disabled
Log files attached it might help some smarter than me to troubleshoot..

My interpretation I have an OLD Ceton tuner card and from a comment above it is not updatable to latest updates. If So: Is the Ceton InfiniTV6 PCIe card the one to go to for multiple tuners and transitioning to SageTV V9 eventually.
OR can I get this beast working?
To late to stay with SageDCT as it now loads nonfunctioning. so moving forward...CentonWEbLOG.txt

OpenDCT_Logs_1_24.zip

[EnterNoEscape]

I'm reasonably sure I have confused you. In Sage.properties, 127.0.0.1:9000 is fine if OpenDCT is running on the same computer as SageTV. The tuners in SageTV likely look something like DCT-Ceton InfiniTV PCIe (00-80-4f-2f) Tuner 1 on 127.0.0.1:9000. That's ok. They will also by default use the same port.

The InfiniTV 4 is supported, don't worry about upgrading or anything like that. It's just that I think you're the first one that I've seen with a firmware that doesn't have the current cgi scripts.

Stopping SageDCT and disabling the service is a perfectly fine way to temporarily disable it. That's what I did before I made a complete transition.

You should be able to update to the latest beta firmware unless Ceton has stopped advertising them completely. Open Ceton Diagnostics, select the tuner from the dropdown, go to the Update tab, make sure Include beta updates is selected. It should tell you that there is an update.

You do not need to update if you're ok with tuning performance being a little slower. To do this, stop the OpenDCT service, then use the shortcut to OpenDCT Properties on the Start Menu to open up opendct.properties. Change the value of upnp.dct.http_tuning to false. Start the service back up and you'll be tuning using pure UPnP protocols. It will take longer to tune into channels this way. If this works for you, you can try to speed up tuning by changing the value of upnp.dct.fast_tuning to false. Always stop the service before making changes to opendct.properties.

[tomdomm]

Updated Ceton Infini to 13.6.3.1088
went to web tuner page and turned on streaming
ran OpenDCT Console
turned on service
reinstalled tuners into SageTV
attempting to view live TV from menu - system crashes
Sage logs attached

[tomdomm]

Don't see log files attached trying again
Also noticed when running OpenDCT Console that saw an ERROR Msg: SageTVSocketServer unable to open Socket Port 9000 Java.Net.BondException Address already in use

[EnterNoEscape]

Don't open the console while the service is running. They are both trying to run the exact same program; that's why the console is failing. For our purposes don't open the console at all and make sure you have closed it. If you're not completely sure what state everything is in, reboot the computer. The OpenDCT service will already be running after you reboot. If SageTV crashes again, send me the log file from SageTV. It will probably be under C:\Program Files (x86)\SageTV\SageTV\sagetv_0.txt.

[tomdomm]

reset all setting to default in OpenDCT.Properties
upnp.dct.http_tuning: true
upnp.dct.fast.tuning: true
...local_ip_override=192.168.200.1
reran console setup - error msg cleared
reinstalled tuners in sagetv
noticed IP address still points to 127.0.0.1 even thou changed in OpenDCT properties
attempt to watch live tv still crashes sagetv

[tomdomm]

No txt files only a log file so zipped it so could upload.
noticed that IP did not change in Sage Tuner setup from 127.0.0.1 to 192.168.200.1
only have a little time left to fight this, so when I return to the battle tonight I an tempted to stop all services; ceton, opendct, sage
uninstall opendct
reboot
restart ceton
reinstall opendct stable version
delete all mmc.encoder listing in sage.properties
run opendct console
start dct service
attempt to reconfigure tuners in sagetv

as you have a better idea of what is suppose to happen, this removes all setting, resets all setting to default, removes confusing setting (to me anyway) in sage.properties
on the last point- I may be able to come up with a sage.properties file from before all this from backup, would that be better. it would have the SageDCT entries now defunct, but was a working version
open to ideas

[EnterNoEscape]

Before you redo everything I have another suggestion. Try changing the value of consumer.ffmpeg.upload_id_enabled to false in opendct.properties. SageTV might not have enough free memory to use upload id and that might be why it's crashing. Make sure you stop the OpenDCT service before making this change.

If that doesn't work you, it might not be a bad idea to remove all of the mmc.encoder entries relating to SageDCT and OpenDCT and let the OpenDCT entries re-populate. I want to emphasis that 127.0.0.1 is ok to see in SageTV. The error you appear to be getting when trying to tune into live TV is a little odd and very unexpected. It basically is telling me some native code has crashed the JVM.

Check this post out on how to enable debug logging in SageTV. It might give us a better idea of why the native code is failing.

[tomdomm]

Reinstalled OpenDCT as planned.
Did not enable debug as the post referenced older versions of SageTV.
When installing tuners into SageTV the Celon tuners found no tune able channels. The older Haupaugage tuners at least scanned before finding 0 channels.
Is there a way to test if there is an output from OpenDCT & Celon InfiniTV tuners?

[EnterNoEscape]

I would not use the channel scanning in SageTV with OpenDCT unless you have an HDHomeRun Prime and even then there is a problem on the SageTV side of things with it only asking for 159 channels. The InfiniTV channel scanning only works if you enable an experimental feature. I do not recommend using it unless we have everything else working.

It's clear you are not having a very good experience. I assure you that OpenDCT was designed to be hassle free, but it feels like we are going to keep going in circles.

1. Stop the SageTV service.
2. Stop the OpenDCT service.
3. Open the file "C:\ProgramData\OpenDCT\config\opendct.properties" in notepad.
4. Change the line consumer.ffmpeg.upload_id_enabled=true to consumer.ffmpeg.upload_id_enabled=false.
5. Save the file.
6. Start the OpenDCT service.
7. Start the SageTV service.
8. Open SageTV.
9. If you haven't already, add the tuners that start with DCT- from within the UI in SageTV.
10. You will need to enable the channels you are subscribed to from your cable company. Detection will not find anything. OpenDCT will not lock up the UI if you're not subscribed to the channel. As a test, I would try to tune into a local channel since most people get all of the local channels.

[tomdomm]

Get a NO Signal error message in the video playback screen.
did set the debug flag files attached.

[EnterNoEscape]

That at least means we likely attempted to tune a channel in OpenDCT. I'll need to log file from C:\ProgramData\OpenDCT\logs\opendct.log. You will need to rename it to .txt or put it in a zip file to attach it.

[tomdomm]

files from test debug text edited down for uploading- removed show listing