Ceton Infinitv4, Windows 10

[Pctravel]

here you go.  For the ceton log are you looking for the complete diagnostic log??

[mvallevand]

Ok I don't know why your setup is trying to open port 9001 could you send me the zipped opendct.properties file too.

Do you run SageTV too?

Martin

[Pctravel]

No I don't run Sage. So appreciate the help.

[mvallevand]

If 9091 is in use, did you confirm that you haven't got the server running when you are also trying to run the command line version? This looks like a start without a stop.

14:34:33.019 [ChannelManager-53] INFO InfiniTVChannels - Connecting to InfiniTV DCT using the URL 'http://192.168.200.1:80/view_channel_map.cgi?page=0'
14:36:48.591 [WrapperSimpleAppMain] INFO Main - Starting OpenDCT 0.5.29...

You might also have to stop the service to unzip and copy the custom jar file into c:\Program Files\OpenDCT Authors\OpenDCT\lib

Martin

[Pctravel]

Sorry I'm not sure on the next trouble shooting. I restarted, made sure the sage service was not running. Copied another version the unzipped opendct jar file and tried again. The status window shows the tuner is streaming but doesn't display. If I did the start without a stop you mention how can I correct this?  I reviewed the listenting ports in task manager and I do see port 9091.  If I change the channel in Nextpvr I also see the status streaming change but still doesn't display in nextpvr play window.  The ports are showing duplicates? Is that normal?

I do have Nextpvr V4 and V5 installed but have changed the port for v5 to 8867 if that matters? Nextpvr device setup did see all the tuners and I scanned all the channels to the first tuner only.

The OpenDCT path also copied to my Program files (x86) folder and I installed the x86 version. should I try the 64 bit? Would that make any difference? I created a restore point before I installed so I could start fresh again.

[mvallevand]

I don't see duplicates I see ipv4 and ipv6. You don't need to run the batch file just let the service run. I would need to see the new opendct log with the NextPVR logs.

Also what is the date of your jar file? Perhaps there is another forum issue on that post.

Martin

[Pctravel]

here are the Nextpvr logs and all the logs for Opendct

Opendct-0.5.29 date of file 3-2-20

I only have the 32 bit Java installed

[mvallevand]

Ok this must be close they are communicating but I am not seeing the custom jar information.

Code:

21:57:55.767 [SageTVRequestHandler-75:Unknown] DEBUG SageTVRequestHandler - SageTV sent: 'START DCT-Ceton InfiniTV PCIe (00-80-9f-48) Tuner 1|7820|18|12345678|stdout|Great'
21:57:55.767 [SageTVRequestHandler-75:DCT-Ceton InfiniTV PCIe (00-80-9f-48) Tuner 1] DEBUG InfiniTVCaptureDevice - Capture device is now re-locked.
21:57:55.767 [SageTVRequestHandler-75:DCT-Ceton InfiniTV PCIe (00-80-9f-48) Tuner 1] DEBUG SageTVRequestHandler - Starting network encoder via upload ID '7820' to file name 'stdout'.
21:57:55.767 [SageTVRequestHandler-75:DCT-Ceton InfiniTV PCIe (00-80-9f-48) Tuner 1] DEBUG RTPCaptureDeviceServices - Producer was not running.

What is the date of the jar file?

Martin

[Pctravel]

sorry, 3-2-20 is the date of the file.

Does it matter the opendct version installed was x86 and my windows is 64 bit?

[mvallevand]

No this should be 32 bit. I suggest you stop the service and change

consumer.ffmpeg.upload_id_enabled=false

to true and restart the service and see if that helps.

Martin