Hi Carl.
I was testdriving your freshly released v1.10 of DCP-O-Matic this afternoon.
After encoding the Big Buck Bunny trailer, I got an error regarding openssl (see attached screenshot).
Not just did this error occur, but it halted the process, so no metafiles were ever created.
Only the two MXF files were created.
I closed the program, an re-opened it, then encoded the Sintel short with almost the same parameters and got the same error.
I've zipped and attached the 'log' and 'metadata.xml' files from the bbb trailer encode to this mail.
FYI, I had another OpenSSL version installed, but after uninstalling that, I ran another bbb encode with the same error.
UPDATE (while writing this mail): I just tried running openssl.exe from the commandline and got this:
c:\Program Files\DCP-o-matic\bin>openssl.exe
WARNING: can't open config file: C:\programs\OpenSSL-Win64\bin\openssl.cfg
That's the path of my old OpenSSL installation.
I looked for openssl.cfg in this folder: c:\Program Files\DCP-o-matic\bin\
but no such file exists there.
Seems like the openssl.cfg is missing from the package.
UPDATE II: I just did the same test encoding the bbb trailer with the 1.11 version. Same error: Sun Oct 13 16:29:57 2013: Transcode job failed (error in C:\Program Files\DCP-o-matic\bin\openssl.exe genrsa -out ca.key 2048
However, when running the command manually in commandline, openssl actually generates the ca.key file (with the 'missing cfg file' error, but the key file is generated!).