OpenDCT: An open source digital cable tuner.

[nyplayer]

Originally Posted by EnterNoEscape

Something I had observed was that WMC will automatically switch to a channel if you input the max number of digits for any channel in the guide. For example, if you don't have any guide data set (which I believe is what you did), and you input a channel number preceded by enough zeros to make it 7 digits total, the channel will tune right in without the need to press enter. I wonder if using padding would help your situation at all. The property to set this would be:

sagetv.device.<device_id>.channel_padding=7

Now that I am on Schedules direct I use the same guide data for both using epg123 for WMC... so I do have guide data for both ... but you are correct some shows only have 2 digits. I will test with padding.... let you know

That appears to have fixed my problem.

[jhkoenig]

So I'm embarking on the voyage from SageDCT to OpenDCT with great anticipation. Sadly, the install is failing at "Start OpenDCT in console mode" with a string of DOS errors "Unable to create the Java virtual machine".

SageTV has been running fine. Java claims to be version 1.6.0_10 and the updater says it is current.

So what have I fat-fingered? The instructions are clear, so I'm overlooking something truly basic. THANKS!

[jhkoenig]

Originally Posted by jhkoenig

So I'm embarking on the voyage from SageDCT to OpenDCT with great anticipation. Sadly, the install is failing at "Start OpenDCT in console mode" with a string of DOS errors "Unable to create the Java virtual machine".

SageTV has been running fine. Java claims to be version 1.6.0_10 and the updater says it is current.

So what have I fat-fingered? The instructions are clear, so I'm overlooking something truly basic. THANKS!

Forgot to the log file. Here it is.

[JustFred]

See post #1 in this thread.

"The minimum Java version is 1.7."

[jhkoenig]

Thanks! Of all the things I've lost with advancing age, the thing I miss most is my mind. I upgraded to 1.7 and the installer has been running happily for several minutes.

Appreciate the help!

[NetworkGuy]

Memory is the second thing to go.

You never remember what the first was.

[EnterNoEscape]

• Fixed non-legacy channel scanning.
• Fixed Generic Pipe producer stall being detected when there isn't a stall.
• Fixed some Generic Pipe logging.
• Changed Generic Pipe to required the use of %c% to specify the requested channel for sagetv.device.<unique_id>.streaming_executable

That last one is important. I ran into a few situations where it was a real problem to have the channel tacked on as the final parameter. From here on out, you must provide %c% if you want the channel to be provided at all. e.g.

sagetv.device.<unique_id>.streaming_executable=/path/to/executable --tune=%c%

[tmiranda]

Just want to say that after sorting out one small issue OpenDCT has been rock solid for me. Thanks!

[EnterNoEscape]

Originally Posted by tmiranda

Just want to say that after sorting out one small issue OpenDCT has been rock solid for me. Thanks!

You're welcome! It's always nice to hear things are working well.

[jhkoenig]

Add me to your growing list of fans, EnterNoEscape! My migration from SageDCT to OpenDCT went far better than I could possible imagine! Great work!

My only open issue is the occasional 1-2 second freeze that happens every 2-10 minutes. Something is not bolted down quite right, but I'm basking in the success before I take up troubleshooting. There will be time for that, but right now I'm just SO HAPPY with your code!!!!!

[tmiranda]

Originally Posted by EnterNoEscape

You're welcome! It's always nice to hear things are working well.

Now if it only could have recorded the Giants winning yesterday... You do need to do something about that.

[videolog]

Originally Posted by EnterNoEscape

You might want to verify that your hard drive is ok. I'm seeing mostly the circular buffer completely filling up, then deferring to the queue buffer, then dropping data. It does write out several MB before this happens, but it could be a specific location on the disk causing issues.

Okay, I installed a new Hard Drive, one rated for 24/7 running. Ended up with the attached. Interesting the first time it froze up it corrected itself after about a minute. The second time I had to shutdown Open DCT, then restart it. I noted that it also did not want to shutdown, took a few tries like it was hung up.

Again, Thanks for the great program and all your help.

[EnterNoEscape]

Originally Posted by videolog

Okay, I installed a new Hard Drive, one rated for 24/7 running. Ended up with the attached. Interesting the first time it froze up it corrected itself after about a minute. The second time I had to shutdown Open DCT, then restart it. I noted that it also did not want to shutdown, took a few tries like it was hung up.

Again, Thanks for the great program and all your help.

I didn't actually mean go buy a new hard drive (although new doesn't mean good). Anyway, it looks like everything is ok until tuner 6 starts recording, then things start to get really backed up again. I would be checking things like CPU usage and Resource Monitor to be sure the write queue length for your recording drive is staying at or below 1. Also if you're using Comskip or any other live/post processing programs, turn them off temporarily.

[KryptoNyte]

Originally Posted by tmiranda

Now if it only could have recorded the Giants winning yesterday... You do need to do something about that.

Yeah ... that's too bad. That was a cold game from the 40 yard line, about 43 rows up.

FYI, my Sage recorded the winner perfectly.

[wayner]

I am trying OpenDCT for the first time to be able to access IP cameras in SageTV. This is on SageTV V9 for Win. OpenDCT did discover my HDHR OTA devices but I have them set to ignore for now.

One question regarding services - what is the order of stopping and starting the SageTV service and OpenDCT service? Which should be started first? And I assume that both should be stopped when editing opendct.proeprties, correct? And I can just stop and start the SageTV OpenDCT in the Windows services panel rather than using the installed shortcuts, can I not?

I am trying to set up the opendct service for two IP cams. I can view these cameras in Google Chrome with the given URL 192.168.1.31/mjpeg.cgi.

I don't see the devices as SageTV sources. Should I not see two new sources with the names that I gave them when I go to "Add New Source?? Why wouldn't they show up? Do I need a streaming executable? If so what would I use for such a setup.

Here is my config file for one of these tuners.

sagetv.device.1433103548.channel_padding=0
sagetv.device.1433103548.consumer=opendct.consumer.DynamicConsumerImpl
sagetv.device.1433103548.custom_channels=1000
sagetv.device.1433103548.device_name=Bedroom
sagetv.device.1433103548.encoder_listen_port=9001
sagetv.device.1433103548.encoder_merit=0
sagetv.device.1433103548.encoder_pool=generic_http
sagetv.device.1433103548.fast_network_encoder_switch=true
sagetv.device.1433103548.http_password=user
sagetv.device.1433103548.http_username=password
sagetv.device.1433103548.last_channel=-1
sagetv.device.1433103548.pretuning_executable=
sagetv.device.1433103548.stopping_executable=
sagetv.device.1433103548.stopping_executable_delay_ms=15000
sagetv.device.1433103548.streaming_url=http\://192.168.1.31/mjpeg.cgi
sagetv.device.1433103548.streaming_url2=
sagetv.device.1433103548.streaming_url2_channels=
sagetv.device.1433103548.transcode_profile=
sagetv.device.1433103548.tuning_delay_ms=0
sagetv.device.1433103548.tuning_executable=

And here are the log lines related to this tuner

18:30:09.296 [GenericHttpLoader-40] DEBUG DeviceLoaderImpl - Advertising new capture device 'Bedroom'.
18:30:09.296 [GenericHttpLoader-40] DEBUG SageTVManager - The requested capture device 'Bedroom' did not exist. Triggering re-discovery.
18:30:09.296 [GenericHttpLoader-40] DEBUG DynamicConsumerImpl - Using default consumer 'opendct.consumer.FFmpegTransSageTVConsumerImpl' for channel ''
18:30:09.299 [GenericHttpLoader-40] INFO  SageTVManager - The capture device 'Bedroom' is ready.

[Fuzzy]

The OpenDCT service needs to be up and running when SageTV starts (at least once) for Sage to detect the new tuners, and grab the associated properties from them. After that, they can be started in any order, or simultaneously. They can also be restarted individually. Editing opendct.properties, for instance, only needs opendct stopped, sagetv does not access the file, so it doesn't need to be stopped to edit it.

[wayner]

Ok, thanks Fuzzy. Obviously it did work at least once since it did grab the properties and found my HDHR tuners. Any reason what I did wrong and why it isn't working for me?

[Fuzzy]

Was opecdct running BEFORE you started sagetv, AFTER you added the camera settings to opendct.properties? Also, did you try scrolling down on the list of tuners in the Add New Source page?

[wayner]

I scrolled down and there are definitely no other tuners if you scroll down. I am not sure if OpenDCT was running before I started SageTV or not. Is there a way to start over by nuking the opendct.properties file or something like that?

[EnterNoEscape]

Originally Posted by wayner

I scrolled down and there are definitely no other tuners if you scroll down. I am not sure if OpenDCT was running before I started SageTV or not. Is there a way to start over by nuking the opendct.properties file or something like that?

Any time you are adding a new capture device, make sure both SageTV and OpenDCT are stopped. Make your changes, then start the OpenDCT service again. After that, start the SageTV service. You should now see the new capture device. The key here is that OpenDCT needs to be running before the SageTV service because the SageTV service only broadcasts for network encoder discovery at startup. There's no reason to nuke anything.