22 Oct
2015
22 Oct
'15
8:52 a.m.
On Wed, 21 Oct 2015 19:27:41 +0100
Jim Dummett via DCPomatic <dcpomatic(a)carlh.net> wrote:
Hi Carl.
It might make more sense if you did use --container-ratio as well; if
you don't specify it dcpomatic_create will set container_ratio =
content_ratio. I'm not quite sure why it does that ... sounds like
there is some tidying up needed.
[snip]
It looks like that is left over from before
DCP-o-matic did better
guessing of ratio from the input size. It can probably be made
optional. Are you using a 1.x version
Yes, I'm on v1.83.0. --content-ratio does have an effect, just not the
effect I expected! It dictates the container (scope, flat etc). The
--container-ratio argument isn't compulsory and I didn't try it. By the way, cine-matic.com is an interesting concept.
But as you say,
the problem is the volume of data that has to go up to, and down again
from the cloud. I'm kind of working on something similar - a web app
that controls DCP creation, but my approach has been that the web app in
the cloud only acts as command-and-control - the actual DCP-encoding
happens on worker machines down here in the "real world", with big
drives attached. So the video data never needs to go via the cloud.
I'm afraid your cine-matic job won't run at the moment; the backend
script is now out of date with the API of the cloud servers that I was
using and I haven't got around to fixing it.
Your creation app sounds interesting... what makes you want a web app
rather than a local app? Just so you can initiate DCP creation from
anywhere?
Cheers,
Carl