<feed xmlns='http://www.w3.org/2005/Atom'>
<title>dcpomatic/src/lib/atmos_decoder.cc, branch encrypt-atmos</title>
<subtitle>DCP-o-matic DCP tools</subtitle>
<id>https://git.carlh.net/cgit/dcpomatic/atom?h=encrypt-atmos</id>
<link rel='self' href='https://git.carlh.net/cgit/dcpomatic/atom?h=encrypt-atmos'/>
<link rel='alternate' type='text/html' href='https://git.carlh.net/cgit/dcpomatic/'/>
<updated>2020-06-19T11:42:24Z</updated>
<entry>
<title>Make Atmos content work more like other content.  Now its MXFs</title>
<updated>2020-06-19T11:42:24Z</updated>
<author>
<name>Carl Hetherington</name>
<email>cth@carlh.net</email>
</author>
<published>2020-06-19T11:30:02Z</published>
<link rel='alternate' type='text/html' href='https://git.carlh.net/cgit/dcpomatic/commit/?id=a0c931b6bfb05b56996a75bbfcf378cd44ef18e1'/>
<id>urn:sha1:a0c931b6bfb05b56996a75bbfcf378cd44ef18e1</id>
<content type='text'>
are re-written, meaning that they can be encrypted.

This commit is mostly just for the backend.  We also need a fair
few checks/restrictions in the UI:

- any present atmos content dictates the project frame rate
- no mixed edit rates of atmos content
- probably some other things I haven't thought of
</content>
</entry>
</feed>
