Request for supporting Ceton devices on Linux

[mvallevand]

I think the delay might work with raw mode but not sure, certainly the file was not big enough for ffmpeg in NextPVR to be able to transcode, it might also work ok with direct play but it is hard to say.

Only one tuner is supported because it is hard coded to listen on one socket. The next version will do open a socket per tuner.

For the tuning issue i'd have to see the opendct logs, and I'd have to ask the people that use this with Ceton's. I don't have one myself so like I said this was all theory. Confirm the channel number is 747 in Myth and also see if it takes longer to tune we can boost the timeout in the script.

The next instructions will automate everything we learned so far into one command.

Martin

[dapharsyde]

For the tuning issue i'd have to see the opendct logs, and I'd have to ask the people that use this with Ceton's.  I don't have one myself so like I said this was all theory.  Confirm the channel number is 747 in Myth and also see if it takes longer to tune we can boost the timeout in the script.

Confirmed the channel number is correct.  I changed opendct.py to sock.settimeout(60) instead, and by running the script by itself, a video file is created, but only after a short delay.

I ran: python3 /var/opt/nextpvr/scripts/opendct.py "START" "DCT-Ceton InfiniTV Ethernet (00-80-8d-8a) Tuner 2" 747 /tmp/foodtv.ts

After about 18 seconds, the python script completed with the "OK" message, and the /tmp/foodtv.ts file was created with 0 bytes.

After about another 14 seconds, (32s total), the file began to grow in size.

While attempting to play this channel from the Guide on the web interface, the player times out after 30s before playing the video - is there a way to extend this timeout?

Edit:  I found a few other channels this happens with also - tuning seems to take a long time, and the video never works through the web player.  I can look into the opendct logs - do you know where are they located?  Or do I need to enable debugging for logs to be created?

[mvallevand]

I have reached out to the SageTV community regarding the timeout question.

Sub would have to address the web server question. I don't test using the browser since transcoding adds extra unnecessary variables. Direct play via vlc or ffplay to me makes more sense ie.

ffplay "http://localhost:8866/live?channel=747"

Logs should be in /var/log/opendct

Martin

[dapharsyde]

Logs should be in /var/log/opendct

Thanks for the pointer.  While testing some more I've come to realize that there is some inconsistent behavior when tuning into channels.

Here is a opendct.log that shows success tuning to 745 (copy free), success tuning to 747 (copy free), then failure tuning back to 745 (copy never)

of particular note is these line entries:

Code:

Line 143: 12:40:56.806 [SageTVRequestHandler-48:DCT-Ceton InfiniTV Ethernet (00-80-8d-8a) Tuner 6] INFO  InfiniTVCaptureDevice - Starting the encoding for the channel '745' from the device 'DCT-Ceton InfiniTV Ethernet (00-80-8d-8a) Tuner 6' to the file 'stdout' via the upload id '8888'...
Line 200: 12:40:59.067 [SageTVRequestHandler-48:DCT-Ceton InfiniTV Ethernet (00-80-8d-8a) Tuner 6] DEBUG InfiniTVStatus - The returned value was trimmed to 'Copy Control Information: "Copy Free" (00)'

Line 276: 12:41:19.428 [SageTVRequestHandler-48:DCT-Ceton InfiniTV Ethernet (00-80-8d-8a) Tuner 6] INFO  InfiniTVCaptureDevice - Starting the encoding for the channel '747' from the device 'DCT-Ceton InfiniTV Ethernet (00-80-8d-8a) Tuner 6' to the file 'stdout' via the upload id '8888'...
Line 374: 12:41:23.396 [SageTVTuningMonitor-50] DEBUG InfiniTVStatus - The returned value was trimmed to 'Copy Control Information: "Copy Free" (00)'

Line 417: 12:41:59.921 [SageTVRequestHandler-48:DCT-Ceton InfiniTV Ethernet (00-80-8d-8a) Tuner 6] INFO  InfiniTVCaptureDevice - Starting the encoding for the channel '745' from the device 'DCT-Ceton InfiniTV Ethernet (00-80-8d-8a) Tuner 6' to the file 'stdout' via the upload id '8888'...
Line 449: 12:42:02.659 [SageTVRequestHandler-48:DCT-Ceton InfiniTV Ethernet (00-80-8d-8a) Tuner 6] DEBUG InfiniTVStatus - The returned value was trimmed to 'Copy Control Information: "Copy Never" (0x03)'

It is strange that the same channel is going between copy free and copy never.  I guess I need to troubleshoot this with the SageTV team also?  If that's the case, can you point me to them?

[mvallevand]

You might want to check the Ceton log too I believe I found it is at http://cetonip/Services/Log.html

There is a blog-like thread for OpenDCT here https://forums.sagetv.com/forums/showthread.php?t=62774 That is one reason I quickly got you into a new thread, I don't find 135 page threads helpful

I did post some questions there this morning but have yet to get a response.

Martin

[dapharsyde]

I don't find 135 page threads helpful

I totally agree

I posted there anyways, just waiting for the moderator to approve my post since my account is new.  Hopefully I hear back from them.

Thanks for walking me through everything up to this point!

[mvallevand]

I might be not understanding certain command in the SageTV protocol that I don't see with my HDHR  I am looking to see if you get a WRITEOPEN request.

In opendct.py

add  the following

Code:

            if received[0]=='WRITE':
...
add these  3 lines
            elif received[0]=='WRITEOPEN':               
                data = 'OK\r\n'
                connMediaServer.send(data.encode())
before
            else:

Martin

[dapharsyde]

I might be not understanding certain command in the SageTV protocol that I don't see with my HDHR  I am looking to see if you get a WRITEOPEN request.

In opendct.py

add  the following

Code:

            if received[0]=='WRITE':
...
add these  3 lines
            elif received[0]=='WRITEOPEN':               
                data = 'OK\r\n'
                connMediaServer.send(data.encode())
before
            else:

Martin

Hi again - sorry for the slow response.

For the most part, I'm still concerned that I have inconsistent results tuning to certain channels, with CCI flipping between Copy Free and Copy Never.  This seems to be a problem that can only be addressed over on the Sage forums, where it's been relatively quiet.

In the meantime I can continue to test your new changes like above, but I'm unclear what it is meant to improve.  Once I make this change, what should I test, and what logs should I upload for you to review?

[mvallevand]

I looked at the opendct log you posted on the SageTV forum and that is a protocol command that was failing that I probably need to support but I don't have a device that uses it. Once it is implmented I want to go back to the forum with other comment

SageTV is dying certainly but then again so is Ceton so I think this should work once we get it going.

Martin

[dapharsyde]

I looked at the opendct log you posted on the SageTV forum and that is a protocol command that was failing that I probably need to support but I don't have a device that uses it. Once it is implmented I want to go back to the forum with other comment

SageTV is dying certainly but then again so is Ceton so I think this should work once we get it going.

Martin

Got it.  So what should I test, and are there logs that you want to see?