Failure Loading video capture device - OpenDCT

[brandypuff]

Lately i have been having issues with my Homerun EXTEND with OTA channels.
The Extend is working properly, but when i schedule two channels recordings for the same time, i get "failure loading video capture devices" . I've attached the OpenDCT logs.

However, despite these messages, the shows usually record ok. I am also getting the conflict warning icon sometimes but can't figure out why.

[EnterNoEscape]

I'm not clear on what you're seeing in those logs that looks problematic. They look completely normal to me other than SageTV isn't talking to OpenDCT.

[brandypuff]

I just installed the latest version of Java and OpenDCT will no longer start.
c:\java -version
java version "1.8.0_201"
Java(TM) SE Runtime Environment (build 1.8.0_201-b09)
Java HotSpot(TM) Client VM (build 25.201-b09, mixed mode, sharing)

INFO | jvm 5 | 2019/02/07 08:24:20.505 | Error: opening registry key 'Software\JavaSoft\Java Runtime Environment'
INFO | jvm 5 | 2019/02/07 08:24:20.506 | Error: could not find java.dll
INFO | jvm 5 | 2019/02/07 08:24:20.506 | Error: Could not find Java SE Runtime Environment.
ERROR | wrapper | 2019/02/07 08:24:20.506 | JVM exited while loading the application.
FATAL | wrapper | 2019/02/07 08:24:20.615 | There were 5 failed launches in a row, each lasting less than 300


I've tried everything, uninstalling v8, installing v7 uninstalling everything and reinstalling v8 and still can;t get opendct working again!
iT'S A MESS!

Please help! Cannot record shows now. Why did updating Java break this?
Thanks.

[brandypuff]

C:\Users\James>"C:\WINDOWS\system32\java.exe" -Dopendct_log_root=c:/ProgramData/OpenDCT/logs -Dconfig_dir=c:/ProgramData/OpenDCT/config -Ddaemon_mode=true -XX:ErrorFile=c:/ProgramData/OpenDCT/logs/hs_err_pid%p.log -verbose:gc -XX:+UseG1GC -Xms128m -Xmx768m -Djava.library.path="./lib;../lib" -classpath "./lib/wrapper.jar;../lib/opendct-0.5.29.jar;../lib/cling-core-2.1.1.jar;../lib/log4j-api-2.5.jar;../lib/log4j-core-2.5.jar;../lib/jna-4.2.1.jar;../lib/jna-platform-4.2.1.jar;../lib/nanohttpd-2.3.0.jar;../lib/nanohttpd-nanolets-2.3.0.jar;../lib/gson-2.8.0.jar;../lib/javacpp-1.1.jar;../lib/ffmpeg-2.8.1-1.1.jar;../lib/ffmpeg-2.8.1-1.1-windows-x86_64.jar;../lib/seamless-util-1.1.1.jar;../lib/seamless-http-1.1.1.jar;../lib/seamless-xml-1.1.1.jar" -Dwrapper.key="Qh53OJM2K8YLieeL" -Dwrapper.port=32001 -Dwrapper.jvm.port.min=31000 -Dwrapper.jvm.port.max=31999 -Dwrapper.pid=8316 -Dwrapper.version="3.2.3" -Dwrapper.native_library="wrapper" -Dwrapper.service="TRUE" -Dwrapper.cpu.timeout="10" -Dwrapper.jvmid=5 org.tanukisoftware.wrapper.WrapperSimpleApp opendct.Main
Error: opening registry key 'Software\JavaSoft\Java Runtime Environment'
Error: could not find java.dll
Error: Could not find Java SE Runtime Environment.

C:\Users\James>java -version
java version "1.8.0_201"
Java(TM) SE Runtime Environment (build 1.8.0_201-b09)
Java HotSpot(TM) Client VM (build 25.201-b09, mixed mode, sharing)

[brandypuff]

after a couple hours of screwing around with JAVA, i modified the OpenDCT wrapper.conf file to point to JAVA directly via JAVA_HOME and now OpenDC starts.

# Specify a specific java binary:
set.JAVA_HOME=C:\Program Files (x86)\Java\jre1.8.0_201
wrapper.java.command=%JAVA_HOME%/bin/java

[brandypuff]

Ever since an OPendct and java upgrade my prime tuners have not been recording anything and the wife is screaming at me to fix it. Seems like support in these groups have dwindled to almost non existent. I've uploaded the wrapper.log file. Not sure i i need to scrap my whole system and reinstall everything for scratch? What version of java is supported by OpenDCT?

* merged all similar topics into one *

[Tiki]

Originally Posted by brandypuff

Ever since an OPendct and java upgrade my prime tuners have not been recording anything and the wife is screaming at me to fix it. Seems like support in these groups have dwindled to almost non existent. I've uploaded the wrapper.log file. Not sure i i need to scrap my whole system and reinstall everything for scratch? What version of java is supported by OpenDCT?

* merged all similar topics into one *

I don’t think OpenDCT is very sensitive to the java version. You should be fine with 1.8. However, I have seen posts that indicate that it can get confused if you have both 32 bit (x86) and 64 bit (x64) versions of Java installed.

[wnjj]

Originally Posted by Tiki

I don’t think OpenDCT is very sensitive to the java version. You should be fine with 1.8. However, I have seen posts that indicate that it can get confused if you have both 32 bit (x86) and 64 bit (x64) versions of Java installed.

Agreed. It looks like you’re calling out 64-bit java from system32 plus the registry keys it’s complaining about don’t show WOW6432node yet you installed and pointed at the x86 version. There’s also c:\java, c:\windows\system32 and c:\program files (x86) for paths.

Which bitness are you trying to use?

[brandypuff]

It all started with me upgrading to:
java version "1.8.0_201"
Java(TM) SE Runtime Environment (build 1.8.0_201-b09)
Java HotSpot(TM) Client VM (build 25.201-b09, mixed mode)

to fix an issue with plugins not installing OK. I had a couple versions of JAVA previously installed but i don;t know what bitness they were. Once i installed the latest java update, OpenDCT couldn't find a a registry key so i hardcoded the path to Java in wrapper.config. It started OK but then later, nothing would record so i uninstalled OpenDCT x64 and installed the X86 version and then it started working OK. JAVA can be a real headache. I thought Java mixed mode woult support both x86 and x64 programs.

Also, i noticed that my two Prime EXTEND OTA tuners are Not going through OpenDCT in Sage but are directly connected,ie, it doesn't list them as "HDHomeRun Digital TV Tuner on 10562c06-01 on 127.0.0.1:9000". I wonder if that is why i am seeing flakyness in OTA tuning?

[EnterNoEscape]

Originally Posted by brandypuff

Also, i noticed that my two Prime EXTEND OTA tuners are Not going through OpenDCT in Sage but are directly connected,ie, it doesn't list them as "HDHomeRun Digital TV Tuner on 10562c06-01 on 127.0.0.1:9000". I wonder if that is why i am seeing flakyness in OTA tuning?

There's a chance that that's what is happening considering the logs you posted didn't show any tuning activity from SageTV.