18 Jun
2014
18 Jun
'14
1:22 p.m.
I think currently DCP-o-matic only maps into DCI channel numbers. These are fixed for
Interop and current (pre-final) SMPTE packages.
The servers then apply either manual (Interop) or automatic (future SMPTE) mappings from
16 DCI channels to 16/8*2 AES channels.
What DCP-o-matic currently allows is to map INPUT channels to DCI channels. It't then
up to the server to route where e.g. 7 and 8 go.
This is necessary, because e.g. for 7.1 mixes, DCI channels 11 and 12 are used.
DCP-o-matic needs to be able to map e.g. 7+8 input to 11 and 12 in the DCP output.
With full SMPTE DCPs, per CPL channel mappings will be possible based on channel labels
like L,C,R. They are still working on it.
- Carsten
Am 18.06.2014 um 15:08 schrieb Manuel AC:
I never understood if the channels can actually be
mapped in the dcp,
or only in the server for projection.
Dcpomatic is telling in the mxf which channel is C, L, R etc.? or just
putting them in the right order and hoping that every theater use the
same order.
Is one of those retrofit/oldschool things that scares me. Because
obviously, should be marked.
Thanks!
Manuel AC
On Wed, Jun 18, 2014 at 8:36 AM, Carl Hetherington <cth(a)carlh.net> wrote:
Hi Carsten
It will put 3, 5, or 7 into the resulting MXF. I guess that's
wrong...
Best
Carl
On Wed, 18 Jun 2014, Carsten Kurz wrote:
_______________________________________________
DCPomatic mailing list
DCPomatic(a)carlh.net
http://main.carlh.net/cgi-bin/mailman/listinfo/dcpomatic DCP properties in DCP-o-matic allows to set odd
numbers of audio channels
- how does it encode if I set it to 3,5,7? I see it updates the channel
matrix accodingly, but what will be the resulting audio.mxf?
- Carsten
_______________________________________________
DCPomatic mailing list
DCPomatic(a)carlh.net
http://main.carlh.net/cgi-bin/mailman/listinfo/dcpomatic
_______________________________________________
DCPomatic mailing list
DCPomatic(a)carlh.net
http://main.carlh.net/cgi-bin/mailman/listinfo/dcpomatic