dcpomatic2_kdm_cli.exe bug

[Jan Rogowski]

I think there's been a bug introduced sometime between 2.12.13 and 2.13.102 (I'm running 64 bit)

The following command...

dcpomatic2_kdm_cli.exe --certificate "Y:\my\license.pem" -f now -d "2 weeks" -o "Y:\my\kdm.xml" "Y:\my\dom\path"

...yields a KDM as expected with 2.12.13. But with 2.13.012 I get this:


-

[Jan Rogowski]

I can confirm that by switching between the two versions I can create an encrypted DCP (2.13.012) and the accompanying KDM (2.12.13), although I do have to do a text replace in metadata.xml to roll the DOM version back to 36.


I have also encountered another minor bug. It appears dcpomatic2_kdm_cli.exe doesn't like longer paths. If I use a big old isdcf naming convention for a DOM project directory, eg...

X:\myDomProjects\StarDogAndTurb_TSR-2D-24_F_EN-XX_UK-NR_20_2K_NULL_20190115_NUL_IOP_OV

Then try to write the kdm in a subDir of that it will fail. If I reduce the size of the dir name it will succeed.

[carl]

What happens when it fails with a long path? Do you get an error?

What sort of filesystem is drive X: ?

[Jan Rogowski]

The process executes without error but no kdm file appears.

It's a Linux server, XFS I think. Samba share to windows 7 64 workstation.

[Jan Rogowski]

Possibly just clipping the path?

[carl]

Could you just try it onto a local drive?

[carl]

The "entry point not found" should be fixed in .103

[Jan Rogowski]

Thanks Carl, I'll try this out in the morning and let you know.

[carl]

Great. Actually it will be .104 now. It should let you do

Code: Select all

dcpomatic2_create --threed --left-eye left_content --right-eye right_content

Let me know how you get on!

[Jan Rogowski]

Hi Carl,

The 3D option works a treat! Thank you.

I am no longer getting the entry point error but I am still encountering issues generating a kdm with .104 though. I'm currently creating the dom project and encoding with .104 and switching back to 2.12.13 for kdm creation. I will try and flesh that out a bit and report back.

Jan.