OpenDCT: An open source digital cable tuner.

[EnterNoEscape]

Originally Posted by bnh

same behaviour with the 3.11beta.

Yes, dct_infinitv.properties does contain channels. it looks complete for what i have access to.

Ceton Infinitv Firmware Version: 1.1.7.2
Diagnostic tool says both driver and firmware are up to date.

Based on the new information in the logs, your issue isn't even close to what I was thinking. The logs suggest that I have some improvement to make on matching the local interfaces. For now I would recommend changing the property sagetv.device.parent.<unique_id>.local_ip_override= to match the local IP address that accesses your tuner. I suspect it will be 192.168.200.2.

Actually, to test the auto-detection, try stopping the service, then remove that line, then start it back up to see if it gets a different IP address.

[mechling-burgh]

Here are the log files. I did remove the extra tuners and the load java class in the properties file. Right now I have the computer on always awake till I get a chance to do some more testing after these changes. I hope these help.

[EnterNoEscape]

Originally Posted by mechling-burgh

Here are the log files. I did remove the extra tuners and the load java class in the properties file. Right now I have the computer on always awake till I get a chance to do some more testing after these changes. I hope these help.

I think you need to change the log file extension to .txt or the forums will reject the file.

[mechling-burgh]

sorry try again

[EnterNoEscape]

From what I can see it is going into standby very cleanly and coming out exactly how I would expect it to. I can see you were able to record/watch something right after coming out of standby, and even watched something long enough to have it SWITCH too. I have never used SageTV with standby enabled (this feature is there because Bill needs it), so I can't tell you anything more than OpenDCT looks like it's working correctly. Sorry I can't be of more help on why it's not waking up, perhaps someone has seen this before and can offer a suggestion.

[mechling-burgh]

I haven't had a chance to try this since the changes and I'm not sure about the one recording because my daughter started to watch something at that time. I will try and schedule some recordings for tonight after bed. Then will report back, once it's up and running it's been rock solid.

[troll5501]

Is there any way to install OpenDCT (manually or otherwise) on Windows XP? I would like to try it out but the installer says "This product requires at least Windows Vista / Server 2008" and then exits. I don't know if the app really requires a higher version of Windows or if it's just the way the installer was built.

I know XP is old and I will soon migrate to Windows 7, but was hoping to avoid all of that effort just to give OpenDCT a test drive. Thanks!

[EnterNoEscape]

Originally Posted by troll5501

Is there any way to install OpenDCT (manually or otherwise) on Windows XP? I would like to try it out but the installer says "This product requires at least Windows Vista / Server 2008" and then exits. I don't know if the app really requires a higher version of Windows or if it's just the way the installer was built.

I know XP is old and I will soon migrate to Windows 7, but was hoping to avoid all of that effort just to give OpenDCT a test drive. Thanks!

The Windows version restriction is because we are not supporting operating systems older than Vista. This is partly because they may have unexpected issues that we will not be fixing. You can certainly install the software anyway if you modify the msi file to not check for the Windows version. On the LaunchCondition table drop the condition Installed OR (VersionNT >= 600) I use Orca to do this kind of fiddling. If you can't find Orca, SuperOrca works just as well.

[Telecore]

Originally Posted by EnterNoEscape

If SageTV actually pulled in the tuner properties from OpenDCT, you will see in the log an entry that looks like [SageTVDiscovery-xx] INFO SageTVDiscovery - Sent discovery response datagram to SageTV server '/x.x.x.x:8270'.

What I would do is stop the SageTV service, check that network_encoder_discovery is still set to true in Sage.properties, then start the SageTV service again. That should be enough to get the tuners to show up as capture devices available to be added.

Sorry, my update was unclear - I was able to add all 6 OpenDCT tuners as video sources into SageTV (V9), however, when I tuned the channels, nothing showed up. Because this was a Ceton card that was previously untested, I went ahead an removed OpenDCT and installed SageDCT to ensure the hardware was not bad. SageDCT did work in both FFMPEG and DUMP modes. When I get some more time, I will try OpenDCT again.

[EnterNoEscape]

I'm going to guess the issues you had were caused by the local IP address not being detected correctly. I have a new release that I've been testing that looks like it will do an even better job at this.

[troll5501]

Originally Posted by EnterNoEscape

The Windows version restriction is because we are not supporting operating systems older than Vista. This is partly because they may have unexpected issues that we will not be fixing. You can certainly install the software anyway if you modify the msi file to not check for the Windows version. On the LaunchCondition table drop the condition Installed OR (VersionNT >= 600) I use Orca to do this kind of fiddling. If you can't find Orca, SuperOrca works just as well.

Thank you very much! I modified the msi with Orca, installed OpenDCT, and it's up and running on XP!

[bnh]

Originally Posted by EnterNoEscape

Based on the new information in the logs, your issue isn't even close to what I was thinking. The logs suggest that I have some improvement to make on matching the local interfaces. For now I would recommend changing the property sagetv.device.parent.<unique_id>.local_ip_override= to match the local IP address that accesses your tuner. I suspect it will be 192.168.200.2.

Actually, to test the auto-detection, try stopping the service, then remove that line, then start it back up to see if it gets a different IP address.

I removed the line and restarted. nothing changed in the properties file until i stopped OpenDCT again. But then it simply added the same line/address as was there before. I then changed it to 192.168.200.2 as you suggested, but still get No Signal.

Sounds like you're working another build. i will test that when it becomes available.

[ThePaladinTech]

So does openDCT work on a virtual machine? PrimeNetEncoder does not due to it requiring the use of hdhomerun config to configure the channels. SageDCT doesn't have this limitiation... hoping openDCT doesn't

[troll5501]

Getting quite a few of the following errors along with hiccups/stutters in the playback at the same time. It seems to get more frequent as the load (# of concurrent recordings) increases. Do I need to tune any properties?

21:19:20.810 [FFmpegSageTVConsumerImpl-66:DCT-HDHomeRun Prime Tuner 13191941-0] DEBUG ffmpeg - [mpegts @ 043502e0] Continuity check failed for pid 4245 expected 3 got 11
21:19:20.810 [FFmpegSageTVConsumerImpl-66:DCT-HDHomeRun Prime Tuner 13191941-0] DEBUG ffmpeg - [mpegts @ 043502e0] Continuity check failed for pid 4246 expected 7 got 2
21:19:20.810 [FFmpegSageTVConsumerImpl-66:DCT-HDHomeRun Prime Tuner 13191941-0] DEBUG ffmpeg - [mpegts @ 043502e0] Continuity check failed for pid 4247 expected 6 got 13
21:19:20.826 [FFmpegSageTVConsumerImpl-66:DCT-HDHomeRun Prime Tuner 13191941-0] WARN  ffmpeg - [mpegts @ 043502e0] PES packet size mismatch
21:19:20.841 [FFmpegSageTVConsumerImpl-66:DCT-HDHomeRun Prime Tuner 13191941-0] WARN  ffmpeg - [mpegts @ 043502e0] PES packet size mismatch
21:19:20.920 [FFmpegSageTVConsumerImpl-66:DCT-HDHomeRun Prime Tuner 13191941-0] DEBUG ffmpeg - [mpegts @ 043502e0] Continuity check failed for pid 0 expected 11 got 7
21:19:20.920 [FFmpegSageTVConsumerImpl-66:DCT-HDHomeRun Prime Tuner 13191941-0] DEBUG ffmpeg - [mpegts @ 043502e0] Continuity check failed for pid 68 expected 5 got 1
21:19:31.670 [FFmpegSageTVConsumerImpl-66:DCT-HDHomeRun Prime Tuner 13191941-0] DEBUG ffmpeg - [mpegts @ 043502e0] Continuity check failed for pid 4245 expected 4 got 15
21:19:31.670 [FFmpegSageTVConsumerImpl-66:DCT-HDHomeRun Prime Tuner 13191941-0] DEBUG ffmpeg - [mpegts @ 043502e0] Continuity check failed for pid 0 expected 14 got 13
21:19:31.670 [FFmpegSageTVConsumerImpl-66:DCT-HDHomeRun Prime Tuner 13191941-0] DEBUG ffmpeg - [mpegts @ 043502e0] Continuity check failed for pid 68 expected 8 got 7
21:19:31.670 [FFmpegSageTVConsumerImpl-66:DCT-HDHomeRun Prime Tuner 13191941-0] DEBUG ffmpeg - [mpegts @ 043502e0] Continuity check failed for pid 4247 expected 11 got 4
21:19:31.670 [FFmpegSageTVConsumerImpl-66:DCT-HDHomeRun Prime Tuner 13191941-0] DEBUG ffmpeg - [mpegts @ 043502e0] Continuity check failed for pid 4246 expected 1 got 9
21:19:31.701 [FFmpegSageTVConsumerImpl-66:DCT-HDHomeRun Prime Tuner 13191941-0] WARN  ffmpeg - [mpegts @ 043502e0] PES packet size mismatch
21:19:31.717 [FFmpegSageTVConsumerImpl-66:DCT-HDHomeRun Prime Tuner 13191941-0] WARN  ffmpeg - [mpegts @ 043502e0] PES packet size mismatch
21:19:45.514 [FFmpegSageTVConsumerImpl-66:DCT-HDHomeRun Prime Tuner 13191941-0] DEBUG ffmpeg - [mpegts @ 043502e0] Continuity check failed for pid 4245 expected 7 got 15
21:19:45.514 [FFmpegSageTVConsumerImpl-66:DCT-HDHomeRun Prime Tuner 13191941-0] DEBUG ffmpeg - [mpegts @ 043502e0] Continuity check failed for pid 4247 expected 2 got 8
21:19:45.514 [FFmpegSageTVConsumerImpl-66:DCT-HDHomeRun Prime Tuner 13191941-0] DEBUG ffmpeg - [mpegts @ 043502e0] Continuity check failed for pid 4246 expected 1 got 15
21:19:45.592 [FFmpegSageTVConsumerImpl-66:DCT-HDHomeRun Prime Tuner 13191941-0] DEBUG ffmpeg - [mpegts @ 043502e0] Continuity check failed for pid 0 expected 15 got 13
21:19:45.592 [FFmpegSageTVConsumerImpl-66:DCT-HDHomeRun Prime Tuner 13191941-0] DEBUG ffmpeg - [mpegts @ 043502e0] Continuity check failed for pid 68 expected 9 got 7
21:19:45.639 [FFmpegSageTVConsumerImpl-66:DCT-HDHomeRun Prime Tuner 13191941-0] WARN  ffmpeg - [mpegts @ 043502e0] PES packet size mismatch
21:19:45.639 [FFmpegSageTVConsumerImpl-66:DCT-HDHomeRun Prime Tuner 13191941-0] WARN  ffmpeg - [mpegts @ 043502e0] PES packet size mismatch

[EnterNoEscape]

Originally Posted by ThePaladinTech

So does openDCT work on a virtual machine? PrimeNetEncoder does not due to it requiring the use of hdhomerun config to configure the channels. SageDCT doesn't have this limitiation... hoping openDCT doesn't

I have been doing all of the development with the exception of a few suspend tests on a VM, so yes, it should be working OK on virtual machines. Just keep in mind that the virtual network adapters need to be able to keep up with/not mangle the UDP traffic. This is a problem people commonly run into when using PXE in a VM environment and I will not be surprised if someone reports it when using OpenDCT in a VM.

Originally Posted by troll5501

Getting quite a few of the following errors along with hiccups/stutters in the playback at the same time. It seems to get more frequent as the load (# of concurrent recordings) increases. Do I need to tune any properties?

Try turning upload id off. Stop the service, then change this property to false consumer.ffmpeg.upload_id_enabled=. Have you seen any errors in the log that look like Expected frame number xx, received frame number xx? If you're seeing those, your computer isn't keeping up with the UDP traffic.

[EnterNoEscape]

Version 0.3.12-beta has been released.

There have been some improvements on local interface detection. I tested this on several IP/subnet configurations and they were all detected correctly even when there were many interfaces to choose from. Hopefully this will be the last time we need to visit this issue.

If you had problems with No Signal, please stop OpenDCT, then remove all occurrences of the property sagetv.device.parent.<unique_id>.local_ip_override= from opendct.properties, then start the service again. It will re-populate that field and this time it should be the correct IP address.

[jvl711]

Originally Posted by ThePaladinTech

So does openDCT work on a virtual machine? PrimeNetEncoder does not due to it requiring the use of hdhomerun config to configure the channels. SageDCT doesn't have this limitiation... hoping openDCT doesn't

FYI... PrimeNetEncoder does work on Virtual Machines. You just need to install the HDHomeRun software on the virtual machine. My development machine is virtual.

[EnterNoEscape]

I was wondering about that. I couldn't see a reason why installing the software would be a restriction. I actually used a VM to test some of the HDHomeRun commands before implementing them in OpenDCT.

[bnh]

Originally Posted by EnterNoEscape

Version 0.3.12-beta has been released.

There have been some improvements on local interface detection. I tested this on several IP/subnet configurations and they were all detected correctly even when there were many interfaces to choose from. Hopefully this will be the last time we need to visit this issue.

If you had problems with No Signal, please stop OpenDCT, then remove all occurrences of the property sagetv.device.parent.<unique_id>.local_ip_override= from opendct.properties, then start the service again. It will re-populate that field and this time it should be the correct IP address.

On first startup, the local_ip_override was populated with 192.168.200.2, and not the local NIC address which i was getting before.

However, still No Signal.

[troll5501]

Originally Posted by EnterNoEscape

Try turning upload id off. Stop the service, then change this property to false consumer.ffmpeg.upload_id_enabled=. Have you seen any errors in the log that look like Expected frame number xx, received frame number xx? If you're seeing those, your computer isn't keeping up with the UDP traffic.

Thanks, I'll give this a try. I did not get any of the "frame number" errors.

I also experienced two other issues when using OpenDCT (using default config) that I do not see when using natively supported tuners in SageTV:

1) Several times when tuning to a channel, there was some hiccup right away and it had to stop and restart the stream, leading to a *-0.ts and a *-1.ts file. I kept the live TV active and suddenly the CPU usage increased significantly for sagetv.exe and in the SageTV debug log I saw that it was trying to delete the *-0.ts file but failed and it would keep looping trying to delete the file every few seconds until I restarted SageTV. Not sure why it was trying to delete part of an active recording. When SageTV restarted it would successfully delete the files on first attempt. This happened at least 3 times so far in my testing:

Tue 12/22 0:07:10.085 [ProgressiveDeleter@abc331] Starting progressive delete for:\\myserver\sagedata\MyRecording-36532303-0.ts
Tue 12/22 0:07:11.607 [ProgressiveDeleter@abc331] Progressive deletion failed for:\\myserver\sagedata\MyRecording-36532303-0.ts reinserting it into the queue...

2) If I start all 3 Prime tuners recording shows, watch one of them for a bit, then go into the Guide or Recording Schedule and cancel one of the other 2 recordings, sagetv.exe immediately goes to 100% CPU and becomes essentially unresponsive. I've reproduced this issue several times on-demand and each time I had to kill the sagetv.exe process. This also does not happen when using natively supported tuners.

Not sure if these are OpenDCT or SageTV issues.