DCP-o-matic

The advanced tab is already pretty full, but I guess we could move these things in there. They shouldn't do any harm, though, no matter what they are set to. If they are left blank the default DCP-o-matic values should be used. Regarding the original problem, I seem to remember this happening before...

2.14.14 is up! Do let me know how you get on if you try it...

I think it's some weird artefact of a bug where - the user asks to crop to a width of 931 - that's an odd number so because of YUV subsampling we decide to crop to 930 - but we still scale to 931 so as we crop from 0 pixels upwards we go through scales of 1:1 and 1:very-close-to-1 which I think is c...

No problem!

Things should be better in 2.14.43 if anybody wants to try it.

It happens at least on `master` (v2.14.x) and `v2.15.x`. I would guess it's been there for a while.

Hi, thanks for the report - I see what you mean! That's a nasty one!

I made a bug report and I'll take a look as soon as I can.

Do you get any message when it crashes?

At the moment, the most likely first "version" of GPU encoding will be for nvidia, on Windows/Linux only (not macOS) and not free.

Yes, the one in the same folder as the main DCP-o-matic 2.app.

This should work again in 2.15.107.

It will not locate and start the player automatically (I would prefer this functionality, though).

Ah ... that's supposed to work

https://dcpomatic.com/mantis/view.php?id=1870