Request for supporting Ceton devices on Linux

[mvallevand]

Right but I asked you to stop testing this way for a few reasons,

- this is the test comand to make sure the API connection and opendct work and you tested it many times
- it doesn't create the return response to the server which is the part that is broken
- using /dev/null was not so we can see a file but so we can see the python file working.after you removed the comments.
- this method will not work with NextPVR

If you do want to test for yourself, with a filename run with a real filename like you originally were doing. It likely won't play right away but if it is growing you should be able to use ffplay after a minute or so.

[run088]

as far as /dev/null the python code does work as expected

[mvallevand]

Something else is going on. I don't know what opendct1.sh, is you shouldn't be starting even using bash on the command line and passing /dev/null as the filename doesn't make too much sense. Regardless this is not the test I want.

Martin

[run088]

here you go

# 136,139,150,152 removed
raw
timeout 15

codes ran shown in term.log (copy and paste of the running screen during test)

[mvallevand]

The term log looks fine with no timeout now. And what happens when you put the comments back and try with NextPVR?

Martin

[run088]

failed in the browser in nextpvr with nothing hitting the opendct log

[mvallevand]

After uncommenting what does this show

bash -c "/var/opt/nextpvr/scripts/opendct.sh 1110 \"DCT-Ceton InfiniTV PCIe (00-80-84-b9) Tuner 4\" 7822\" > /dev/null

If that fails try this.

bash -c "/var/opt/nextpvr/scripts/opendct.sh 1110 \"DCT-Ceton InfiniTV PCIe (00-80-84-b9) Tuner 4\" 7822"> /dev/null

Martin

[run088]

jrun@impact4solutions:/var/opt/nextpvr/scripts$ bash -c "/var/opt/nextpvr/scripts/opendct.sh 1110\"DCT-Ceton-InfiniTV PCIe (00-80-84-b9) Tuner 4\" 7822\" > /dev/null
>

jrun@impact4solutions:/var/opt/nextpvr/scripts$ bash -c "/var/opt/nextpvr/scripts/opendct.sh 1110 \"DCT-Ceton-InfiniTV PCIe (00-80-84-b9) Tuner 4\" 7822"> /dev/null
/var/opt/nextpvr/scripts/opendct.sh: line 1: $'\r': command not found
START DCT-Ceton-InfiniTV PCIe (00-80-84-b9) Tuner 4|7822|1110|12345678|stdout|Great
listening
ERROR Invalid Input

Exit
GET_SIZE DCT-Ceton-InfiniTV PCIe (00-80-84-b9) Tuner 4
timed out
Exit
STOP DCT-Ceton-InfiniTV PCIe (00-80-84-b9) Tuner 4
OK

Exit



(with the "|" added. without it creates null with a space after the name)

[mvallevand]

That first one is the error I expected, so the extras file is bad.

The second might be a bad copy/paste try this

Code:

bash -c "/var/opt/nextpvr/scripts/opendct.sh 1110 \"DCT-Ceton InfiniTV PCIe (00-80-84-b9) Tuner 4\" 7822" > /dev/null

The start stop command are not valid for this test and don't worry about piping anything yet.

[run088]

seems like its running.


jrun@impact4solutions:~$ bash -c "/var/opt/nextpvr/scripts/opendct.sh 1110 \"DCT-Ceton InfiniTV PCIe (00-80-84-b9) Tuner 4\" 7822" > /dev/null
/var/opt/nextpvr/scripts/opendct.sh: line 1: $'\r': command not found
START DCT-Ceton InfiniTV PCIe (00-80-84-b9) Tuner 4|7822|1110|12345678|stdout|Great
listening
waiting
OK


====================================================


OpenDCT 0.5.32

Loaded Capture Devices:

DCT-Ceton InfiniTV PCIe (00-80-84-b9) Tuner 1: Idle
DCT-Ceton InfiniTV PCIe (00-80-84-b9) Tuner 2: Idle
DCT-Ceton InfiniTV PCIe (00-80-84-b9) Tuner 3: Idle
DCT-Ceton InfiniTV PCIe (00-80-84-b9) Tuner 4: Recording to stdout
DCT-Ceton InfiniTV PCIe (00-80-84-b9) Tuner 5: Idle
DCT-Ceton InfiniTV PCIe (00-80-84-b9) Tuner 6: Idle



ceton web page shows it running as well