OpenDCT and R5000

[checkbin]

I recently upgraded to SageTV 9 on Kubuntu Linux. In the process I switched from Prime Encoder to OpenDCT. I'm also using Netxcomm's R5000HD, which worked very well using a second Windows server to host the R5000 and an NFS mount for SageTV to see it. Since upgrading, I'm having lots of stability problems and it seems wiz.bin keeps getting messed up. Does anyone know if these issues could be cause by incompabilities between the R5000 and OpenDCT, or perhaps between the R5000 and SageTC 9? Any suggestions or thoughts would be greatly appreciated. Thank you. Happy Holidays to the Sage community.

[EnterNoEscape]

OpenDCT doesn't interact with other network encoders, but could possibly interfere if it supports the same devices as another network encoder. This is not the case in your situation.

I don't think forced_video_storage_path is a problem since I would assume that's managed by SageTV. OpenDCT just writes out to whatever file SageTV tells it to use.

I have some ideas of what might be going on, but I would need to see logs. If you can post logs of things failing from both SageTV and OpenDCT, that would help sort this out a lot better. The most recent OpenDCT log will be at /var/log/opendct/opendct.log.

[checkbin]

Here attached is the opendct.log with both opendct and R5000 enabled.

[checkbin]

Attached is the sagetv log as well. Timeframe is slightly earlier but the error messages all through the log were the same as these.

[EnterNoEscape]

There should be a lot more logging in sagetv_0.txt, can you please make sure debug_logging is set to true in Sage.properties?

Edit: Also are you running the latest version of SageTV v9? Your stack trace doesn't line up with the current commits.

[Fuzzy]

The R5000HD network encoder is pretty autonomous, so i can't really see much in the way of potential conflicts. It sort of just does what it does on it's own, actually with very little interaction with sagetv.