OpenDCT: An open source digital cable tuner.

[EnterNoEscape]

OpenDCT is now available to the public!

The latest stable installer can be found on GitHub.

The project source code and some useful installation and configuration information can be found on GitHub.

The minimum Java version is 1.7.

InfiniTV 4 users must be on the very last beta firmware from Ceton to be able to use OpenDCT.

On Windows, I recommend the 32-bit (x86) version unless you actually have 64-bit Java runtime installed. If you don't have 64-bit runtime installed and you install the 64-bit version of OpenDCT, you will not be able to start OpenDCT successfully. If you run into issues with Java Service Wrapper being unable to find your Java runtime, you will need to edit wrapper.conf under C:\Program Files [(x86)]\OpenDCT Authors\OpenDCT\jsw\conf\wrapper.conf to contain the complete path to your installed runtime. Most people should not need to do this.

On Linux, I recommend downloading the architecture of your distribution.

For the first run on any platform run OpenDCT on the console first. This is because it needs to detect your devices and populate the opendct.properties file. It will also immediately show if you have problems. On Linux there is a script called ./console-only and the configuration files can be found under /etc/opendct/conf. On versions 0.4.17-Beta and earlier configuration files are located under /opt/opendct/conf. On Windows, there is a shortcut called OpenDCT Run as Console and the configuration can be accessed by the shortcut OpenDCT Properties. Press Ctrl-C to stop the console after you see that it found your devices or just wait 30 seconds, then press Ctrl-C. It will shutdown cleanly. The next major release will replace manually editing the properties file with a web interface. After you have done this, take a look at the Configuration section on GitHub for details on how you can limit the devices that OpenDCT will initialize and how to configure SageTV to discover OpenDCT.

If you're having trouble getting started, many people have found this post by Daweeze very helpful.

The Windows installer will do upgrades so it is unnecessary to uninstall before installing a new version. It is however necessary to stop the service before upgrading. This post by KeithAbbott should help you out if you're interested in backing things up before upgrading. If you delete opendct.properties, make sure you make a note of what you have changed before you delete it.

Here are a few properties not on the GitHub page that might look interesting with their default values included if possible. This is not an exhaustive list, but it covers the basics.

• sagetv.device.global.required_devices_loaded_timeout_ms=30000

  This is the amount of time allowed in milliseconds to pass while waiting for the required number of devices before the program will exit with a failure. This timeout will only happen if sagetv.device.global.required_devices_loaded_count is higher than 0.

• sagetv.device.global.required_devices_loaded_count=0

  This is the number of devices that need to be detected and loaded before the required timeout. This must be the total number of devices OpenDCT normally detects and loads for standby support to work correctly. If this value is left at zero, OpenDCT will just return failures to SageTV when it asks for a device that has not been detected yet because it has no way to know if it should have that device or not. If you are not using standby changing this parameter will also help at startup because it will make OpenDCT hang onto any tuning requests from SageTV until all of the devices have been loaded.

• hdhr.enabled=false

  If set true, this will enable HDHomeRun native discovery and at the moment doesn't do anything because we detect all devices currently via UPnP even if that is not the method we will actually use for tuning.

• hdhr.locking=true

  If set true, this will enable HDHomeRun locking. This will only work if the HDHomeRun device is being tuned using its native protocol. The native protocol is used by default.

• sagetv.device.<unique_id>.always_force_external_unlock=false

  If set true, and locking is enabled, this will force the requested HDHomeRun device to become locked by OpenDCT. This will only work if the HDHomeRun device is being tuned using its native protocol. The native protocol is used by default.

• pm.enabled=true

  If set true, only on Windows, this will allow OpenDCT to gracefully handle the computer entering and exiting standby. There is provisioning for other operating systems, but no actual implementation.

• sagetv.device.<unique_id>.device_name=

  You can change the names of any discovered device. You must be careful to not rename a device to the same name as another device. This will result in the first discovered device loading and the second discovered device not loading.

• sagetv.device.parent.<unique_id>.consumer=opendct.consumer.FFmpegTransSageTVConsumerImpl

  This is the implementation to be used for streaming to SageTV. The currently valid values for this property are the default, opendct.consumer.RawSageTVConsumerImpl and opendct.consumer.MediaServerConsumerImpl (new in 0.5 and only uses media server). Parent entries cover an entire device. Right now this is for convenience, so you don't need to set this value for each tuner. It will probably change once we are using a web interface. opendct.consumer.FFmpegSageTVConsumerImpl has been deprecated as of 0.4.

• sagetv.device.parent.<unique_id>.http.producer=opendct.producer.HTTPProducerImpl (0.5 default: opendct.producer.NIOHTTPProducerImpl)

  This is the implementation to be used for receiving content from devices with HTTP capabilities. opendct.producer.NIOHTTPProducerImpl was added as of 0.5.

• sagetv.device.parent.<unique_id>.lineup=

  These lineups are automatically generated based on the available devices. This allows you to do things like use the lineup from you InfiniTV device that actually has a CableCARD to look up the frequency and program for any ClearQAM device. The lineup files are located under lineups in the configuration directory and are updated by default every 8 hours.

• sagetv.device.parent.<unique_id>.local_ip_override=

  This is the local interface IP address. It is not populated by default. If OpenDCT is detecting your local IP address that communicates with this remote device incorrectly, you can override it here.

• consumer.ffmpeg.upload_id_enabled=false
• consumer.raw.upload_id_enabled=false

  If set true, these will use the Media Server (upload id) feature of SageTV instead of writing directly to the file when recording.

• sagetv.use_automatic_loopback=true

  If set true, OpenDCT will detect if it is running on the same computer as SageTV and use the loopback interface when sending PROPERTIES.

• upnp.dct.fast_tuning=false (no longer available in 0.5)

  If set true, this will enable the tuner to always be in PLAY mode with RTSP configured. When the command STOP is received, the channel is tuned to 0 or if the device is ClearQAM, it will tune to the frequency 0. This improves tuning time by as much as 500ms.

• upnp.dct.http_tuning=true (no longer available in 0.5)

  If set true, this uses the same "tricks" as fast_tuning, but this uses the forms on the web interface to tune into channels instead of the UPnP interface. This method is even faster. This method is also the only way to tune when using an InfiniTV device in ClearQAM mode (no CableCARD). Even if the value is false, it will be overridden just for ClearQAM. This is only used on InfiniTV devices. It has no effect on tuning the HDHomeRun Prime.

• upnp.dct.hdhr_tuning=true (no longer available in 0.5)

  If set true, this will use the HDHomeRun native protocols for tuning. This is the fastest possible way to tune the HDHomeRun Prime. This is the only method used to tune the Prime when it is in ClearQAM mode. Even if the value is false, it will be overridden just for ClearQAM. This setting has no effect on InfiniTV devices.

• upnp.qam.automap_reference_lookup=true (replaced the the global option channels.qam.automap_reference_lookup=true in 0.5)

  If set true, ClearQAM devices will check all available lineups for frequency and program information if they don't already have it and then update their own lineup with the discovered information when a channel is requested.

• upnp.qam.automap_tuning_lookup=false (replaced the the global option channels.qam.automap_tuning_lookup=true in 0.5)

  If set true, ClearQAM devices after not being able to find the frequency and program for the requested channel on any lineup, it will select a currently not in use tuner that also has a CableCARD installed to tune the channel and get the frequency and program that way. If all tuners are in use, it will fail.

New Features in 0.4

• Tuner Pooling.

  This new feature enables OpenDCT to intelligently select a tuner based on merit and lock status in that order. It does two passes over the tuners. The first one tries to find the highest merit tuner that is not currently in use by SageTV; it checks each one in order to see if it's locked. If they are all either in use or locked, it then it goes through a shorter list of tuners not in use by SageTV, but locked and checks if it's allowed to unlock any of them forcefully. If it's not allowed on any of them, then it gives up. These locked checks are surprisingly fast. Since the InfiniTV devices do not have a locked indication like the HDHomeRun Prime devices, enabling pooling with only InfiniTV devices will just remap them based on merit.

  To enable the pooling feature change the property pool.enabled from false to true.

  Because of this new feature, the force unlock feature is now set per capture device. To enable forced unlocking, change the value of sagetv.device.<unique_id>.always_force_external_unlock to true for each device that you want this feature enabled on. The global setting no longer has any effect.

  Merit is set by changing the value of sagetv.device.<unique_id>.encoder_merit. Higher numbers mean higher priority. This is also the merit that will be sent on discovery.

  Pools are automatically assigned based on capture device type the first time you run OpenDCT. You can change the pools by changing the value of sagetv.device.<unique_id>.encoder_pool to another name for all of the capture devices that you want to put into a different pool. The name is case sensitive. Also be sure to not have any extra spaces. I highly do not recommend putting capture devices that cannot tune the same channels into the same pool. It will create a problem per paragraph two in the issue created for this feature.

• Early Port Assignment.

  When this is enabled, OpenDCT will immediately (< 500ms from startup) open any ports assigned in opendct.properties. For most people this will just be port 9000. Set the property sagetv.early_port_assignment to true to enable this feature.

  If you are using this feature, just like standby, you must set sagetv.device.global.required_devices_loaded_count to match the total number of capture devices OpenDCT should expect to be detected and loaded. If you do not set this property and SageTV makes a tuning request before anything has been detected, OpenDCT will not know that it should hang onto that request and the request will just return ERROR to SageTV.

• HDHomeRun Prime Channel Auto-Enabling.

  This is enabled by default. It can be disabled by setting channels.prime.enable_all_channels to false.

  The process of importing these channels already happens one minute after startup and every 8 hours by default in OpenDCT. The change is that now unless the channel actually indicates that it required DRM to tune, OpenDCT assumes it's tunable. What this translates into directly is you can now do a channel scan within SageTV and import your last channel scan from your HDHomeRun Prime.

• UPnP Ignore Interface by IP or Interface Name

  You can now specify a comma separated list of local IP addresses or interfaces to prevent UPnP from using them.

  You can provide a comma separated list of interfaces on the property upnp.service.configuration.ignore_interfaces_csv. You will need to reference the log to figure out what interfaces you want to list here. The ones being used are listed very early in opendct.log. This difficulty is the reason why the IP address option is available too.

  You can provide a comma separated list of IP addresses on the property upnp.service.configuration.ignore_local_ip_csv.

• Exclusive Server Address.

  If you set the property sagetv.device.<unique_id>.exclusive_server_address to the IP address of the server intended to use it, when PROPERTIES are requested if the request did not come from this IP address, the capture device is not returned. This should help some people clean up tuner discovery, since you can now effectively make specific tuners only visible to a specific server.

• Transcoding.

  Set the software transcoding profile by changing sagetv.device.<unique_id>.transcode_profile to one of the available profiles are stored under C:\ProgramData\OpenDCT\config\transcode on Windows and /etc/opendct/conf/transcode on Linux. See profile_example.properties for help on how you can create your own. Do not include the .properties extension when setting the profile.

New Features in 0.5

CCExtractor Options:

• consumer.ffmpeg.ccextractor_all_streams=true

  This enables extracting of both CC1 and CC2. If this is off, it will output only CC1. You will likely want to leave this set to true.

• consumer.ffmpeg.ccextractor_custom_options=

  This can be any combination of valid CCExtractor options with the exception of -12, -1, -2, -in=, -out= and -o. Some people might want to change how roll-up captions are written for example. These options are sanitized to prevent execution of other programs, so you will not be able to do that from this option.

• consumer.ffmpeg.ccextractor_enabled=false

  This enables CCExtractor when set to true.

Dynamic Consumer Options:

• Channel Range Notation

  Channel ranges are defined by a number then a hyphen followed by another number (8-10). Multiple ranges are separated by a comma (13-15,8-10). ATSC channels are defined by a number (frequency channel) then a hyphen followed by a the channel number then a hyphen followed by the sub-channel number (50-8-1). The use of two hyphens automatically makes it literally a channel instead of a range.

  Ex. 8-10,50-8-1,13-16 will match the following channels: 8, 9, 10, 50-8-1, 13, 14, 15, 16

• consumer.dynamic.channels.ffmpeg=

  These are the channels that will always be assigned to the transcoding FFmpeg consumer.

• consumer.dynamic.channels.raw=

  These are the channels that will always be assigned to the raw consumer.

• consumer.dynamic.default=opendct.consumer.FFmpegTransSageTVConsumerImpl

  This is the consumer always used if the channel currently tuned doesn't match the channels under consumer.dynamic.channels.ffmpeg or consumer.dynamic.channels.raw.

Generic HTTP Capture Device:

• Creating Capture Devices for Editing

  Create names for them under the property generic.http.device_names_csv in opendct.properties separated by commas. Start the OpenDCT service, let it run for a few seconds, then stop it. You should now see entries in opendct.properties that have the property sagetv.device.<unique_id>.device_name matching the name of the devices you requested. The names can really be anything, just don't use commas in the names for what should be obvious reasons.

  Ex. generic.http.device_names_csv=Encoder 1,Encoder 2

• sagetv.device.<unique_id>.channel_padding=

  This is the minimum length to be passed for the %c% variable. Values shorter than this length will have zeros (0) appended to the left of the channel to make up the difference. (Ex. 8 becomes 008 if this is set to 3.)

• sagetv.device.<unique_id>.custom_channels=

  This is an optional semicolon delimited list of channels you want to appear in SageTV for this device. This is a shortcut around creating an actual OpenDCT lineup. If there are any values in the field, they will override the lineup assigned to this capture device on a channel scan. This provides an easy way to add channels if you are not actually going to use guide data.

• sagetv.device.<unique_id>.pretuning_executable=

  This is an optional executable that if defined, will always be run before actually tuning the channel. You can add the channel as an argument by using the variable %c%. Don't forget to escape backslashes (\ needs to be \\).

• sagetv.device.<unique_id>.stopping_executable=

  This is an optional executable that if defined, will always be run when the capture device is told to stop. You can add the last tuned channel as an argument by using the variable %c%. Don't forget to escape backslashes (\ needs to be \\).

• sagetv.device.<unique_id>.streaming_url=

  This is a URL that points directly to an audio/video stream. If you provide %c% in the URL, it will be replaced with the channel requested by SageTV. HLS and m3u8 playlists are not supported at this time.

• sagetv.device.<unique_id>.streaming_url2=

  This is an alternative URL that points directly to an audio/video stream. If you provide %c% in the URL, it will be replaced with the channel requested by SageTV. This stream will only be used if a channel matches one of the ranges in streaming_url2_channels. HLS and m3u8 playlists are not supported at this time.

• sagetv.device.<unique_id>.streaming_url2_channels=

  This is the channel ranges that will use the alternative URL. This uses the same formatting as the dynamic consumer channel ranges.

• sagetv.device.<unique_id>.tuning_delay_ms=0

  This is the amount of time in milliseconds to wait after the program associated with tuning_executable has returned.

• sagetv.device.<unique_id>.tuning_executable=

  This is an optional executable that if defined will be used to change the channel being streamed. Insert %c% where the channel needs to be provided to the executable. If %c% isn't provided, but this property is defined, the channel number will be appended as a final parameter. Don't forget to escape backslashes (\ needs to be \\).

  Ex. sagetv.device.<unique_id>.tuning_executable=/full/path/tune 0 %c%

  Ex. sagetv.device.<unique_id>.tuning_executable=C:\\Full\\Path\\tune.exe 0 %c%

  Ex. sagetv.device.<unique_id>.tuning_executable=cmd /c C:\\Full\\Path\\tune.cmd 0 %c%

[nyplayer]

Great job easy to setup ... I set it on my test machine channel changes are quick. Setup was Simple.... no artifacts.


One thing that I do not like about it is if I have the tuners setup for Sagetv and I am watching using another program and PC ... This particular network encoder just gives a no signal and hangs it will not go to the next tuner. The primenetencoder unlocks that tuner and takes control of it ... Which I prefer because if I have a tuner assigned to SageTV I want Sagetv to take control of it.

The way it is now it will lead to missed recordings.

Maybe you can add a user option to unlock and take control of the tuners if it needs to.

[EnterNoEscape]

That interesting. When I was testing HDHomeRun tuner locking features, it looked like if a different IP address tried to unlock the tuner than the IP address that originally locked it, it would not be allowed to unlock the tuner. Since I don't use my Prime to the fullest, I wasn't aware that other programs used to view streams from it directly also locked the tuner. I'll see what I can do.

[nyplayer]

Originally Posted by EnterNoEscape

That interesting. When I was testing HDHomeRun tuner locking features, it looked like if a different IP address tried to unlock the tuner than the IP address that originally locked it, it would not be allowed to unlock the tuner. Since I don't use my Prime to the fullest, I wasn't aware that other programs used to view streams from it directly also locked the tuner. I'll see what I can do.

PrimenetEncoder Does see below.. If you can make it a user option as some users prefer not to force unlock tuner.

12/15/2015 08:32:37 - Start commmand received: START PrimeNetEncoder 13147C7B-0 Digital TV Tuner|459979109|735|2900394314216|C:\Users\epere\Videos\SageTV\SportsCenter-221589-1.ts|Great
12/15/2015 08:32:37 - -------------------------------------------------------------------------------
12/15/2015 08:32:37 - Switching Channel for Tuner: 13147C7B 0
12/15/2015 08:32:37 - -------------------------------------------------------------------------------
12/15/2015 08:32:37 - Channel: 735
12/15/2015 08:32:37 - File: SportsCenter-221589-1.ts
12/15/2015 08:32:37 - UploadID: 459979109
12/15/2015 08:32:37 - Quality: Great
12/15/2015 08:32:37 - Local IP: 192.168.0.100
12/15/2015 08:32:37 - Listening Port: 7000
12/15/2015 08:32:37 - Stream listening Port: 5000
12/15/2015 08:32:37 - Checking to see if the tuner is locked.
12/15/2015 08:32:37 - Tuner is locked.  Force unlocking the tuner.
12/15/2015 08:32:37 - Switch channel: 735
12/15/2015 08:32:37 - 	Using Lockkey: 1954438578
12/15/2015 08:32:37 - 	Command output: null
12/15/2015 08:32:37 - Send stream to UDP port: 5000
12/15/2015 08:32:37 - 	Using Lockkey: 1954438578

[Fuzzy]

Originally Posted by nyplayer

PrimenetEncoder Does see below.. If you can make it a user option as some users prefer not to force unlock tuner.

12/15/2015 08:32:37 - Start commmand received: START PrimeNetEncoder 13147C7B-0 Digital TV Tuner|459979109|735|2900394314216|C:\Users\epere\Videos\SageTV\SportsCenter-221589-1.ts|Great
12/15/2015 08:32:37 - -------------------------------------------------------------------------------
12/15/2015 08:32:37 - Switching Channel for Tuner: 13147C7B 0
12/15/2015 08:32:37 - -------------------------------------------------------------------------------
12/15/2015 08:32:37 - Channel: 735
12/15/2015 08:32:37 - File: SportsCenter-221589-1.ts
12/15/2015 08:32:37 - UploadID: 459979109
12/15/2015 08:32:37 - Quality: Great
12/15/2015 08:32:37 - Local IP: 192.168.0.100
12/15/2015 08:32:37 - Listening Port: 7000
12/15/2015 08:32:37 - Stream listening Port: 5000
12/15/2015 08:32:37 - Checking to see if the tuner is locked.
12/15/2015 08:32:37 - Tuner is locked.  Force unlocking the tuner.
12/15/2015 08:32:37 - Switch channel: 735
12/15/2015 08:32:37 - 	Using Lockkey: 1954438578
12/15/2015 08:32:37 - 	Command output: null
12/15/2015 08:32:37 - Send stream to UDP port: 5000
12/15/2015 08:32:37 - 	Using Lockkey: 1954438578

Probably the most 'robust' method here, would take a bit more work. Each tuner would have a 'if_locked_failover_to' property that, if it finds the tuner is locked, will cascade the request to the listed tuner. This, combined with a 'force_unlock' property FOR EACH TUNER. This would allow the highest merit tuner to have the next highest set as it's failover-to, and so on, and only the lowest merit tuner have the force unlock feature enabled. This will enable nearly anything to be recorded, regardless of what tuner it was scheduled on or what tuner was locked for live viewing elsewhere, and still, ultimately, if everything is in use, the recording will take precedence.

[nyplayer]

Originally Posted by Fuzzy

Probably the most 'robust' method here, would take a bit more work. Each tuner would have a 'if_locked_failover_to' property that, if it finds the tuner is locked, will cascade the request to the listed tuner. This, combined with a 'force_unlock' property FOR EACH TUNER. This would allow the highest merit tuner to have the next highest set as it's failover-to, and so on, and only the lowest merit tuner have the force unlock feature enabled. This will enable nearly anything to be recorded, regardless of what tuner it was scheduled on or what tuner was locked for live viewing elsewhere, and still, ultimately, if everything is in use, the recording will take precedence.

That sounds like sound reasoning.

[EnterNoEscape]

Originally Posted by Fuzzy

Probably the most 'robust' method here, would take a bit more work. Each tuner would have a 'if_locked_failover_to' property that, if it finds the tuner is locked, will cascade the request to the listed tuner. This, combined with a 'force_unlock' property FOR EACH TUNER. This would allow the highest merit tuner to have the next highest set as it's failover-to, and so on, and only the lowest merit tuner have the force unlock feature enabled. This will enable nearly anything to be recorded, regardless of what tuner it was scheduled on or what tuner was locked for live viewing elsewhere, and still, ultimately, if everything is in use, the recording will take precedence.

That seems like a bit much. We would be pretty much doing the job of the scheduler on the network encoder. I'm certain it can be done, but it won't happen until next year.

Originally Posted by mechling-burgh

Does this collect the data like SageDCT by recording the stream directly to the drive or does it run it through ffmpeg to clear the errors that comcast seems to introduce?

You have the option to remux via FFmpeg or get the raw stream. FFmpeg is the default.

[mechling-burgh]

Okay to be thick where are the OpenDCT logs I can't find them. I also realized I forgot to remove the Prime Encoder java loader which I will do once I get my kids off the sage. I was just going through the sage.properties and noticed that the DCT has the locale look up (127.0.0.1) and it also picked up the test computer (192.168.2.60). Should the network_encoder_discovery be set to false after the first install? I will also remove the extra tuners when I fix the java loader.

[nyplayer]

Originally Posted by mechling-burgh

Okay to be thick where are the OpenDCT logs I can't find them. I also realized I forgot to remove the Prime Encoder java loader which I will do once I get my kids off the sage. I was just going through the sage.properties and noticed that the DCT has the locale look up (127.0.0.1) and it also picked up the test computer (192.168.2.60). Should the network_encoder_discovery be set to false after the first install? I will also remove the extra tuners when I fix the java loader.

if using windows 7 and later the logs are in c:\programdata. Setup the tuners with with 127.0.0.1 make sure you have the 3.11 Beta just released. There is a property to Ignore tuners I have not used it yet.

[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.

[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!

[mechling-burgh]

Not sure what is causing this but every time the computer restarts opendct crashes. I have attached the logs I have tried have the sage services start has a delay thinking the opendct did not have time to start up fully, but that did not help any idea on your end.

[EnterNoEscape]

You'll want to use the latest beta (0.4.18) to completely resolve this issue. The problem you're seeing is that all of the capture devices aren't being detected within the 30 second threshold. 0.3.16 isn't as aggressive at locating all of the devices, so it can take over a minute under the right conditions for anything come in. I can see that when it launches the second time it finds everything immediately.

[mechling-burgh]

Great I will try that tonight, I figured it was something I was missing.

[Cooper]

First off great work on this as I moved from SageDCT a month or so ago and has worked pretty well. We have started noticing when watching live TV and when pausing on and off once the show that is on is finished sage will pop back to the guide instead of just playing through to the next show that is on but continues to record and you have to select in the guide to continue watching.

I don't remembering this happening in the past and wanted to check if this is a know problem? I have not changed any of the default properties and using the most current Beta. I'm currently using 2 Homerun Primes and Homerun Extend.

Thanks

[EnterNoEscape]

Originally Posted by Cooper

First off great work on this as I moved from SageDCT a month or so ago and has worked pretty well. We have started noticing when watching live TV and when pausing on and off once the show that is on is finished sage will pop back to the guide instead of just playing through to the next show that is on but continues to record and you have to select in the guide to continue watching.

I don't remembering this happening in the past and wanted to check if this is a know problem? I have not changed any of the default properties and using the most current Beta. I'm currently using 2 Homerun Primes and Homerun Extend.

Thanks

That's odd. That's one of the things I test constantly. There will be a move to the transcoding consumer when I move on to 0.5 because I have improved so much and it doesn't make sense to keep them synced up when they effectively do the same thing when remuxing. Try changing all of the values for sagetv.device.<unique_id>.consumer to opendct.consumer.FFmpegTransSageTVConsumerImpl and see if the situation improves. The difference is that it performs SWITCH more accurately on the key frames.

The reason why you would have never seen this in SageDCT is because it didn't support SWITCH which is why you get that brief interruption between recordings when watching live.