<feed xmlns='http://www.w3.org/2005/Atom'>
<title>libdcp/src/dcp_time.cc, branch mac-tests</title>
<subtitle>DCP handling library</subtitle>
<id>https://git.carlh.net/cgit/libdcp/atom?h=mac-tests</id>
<link rel='self' href='https://git.carlh.net/cgit/libdcp/atom?h=mac-tests'/>
<link rel='alternate' type='text/html' href='https://git.carlh.net/cgit/libdcp/'/>
<updated>2021-03-15T00:36:51Z</updated>
<entry>
<title>Fix various bugs in subtitle/ccap verification.</title>
<updated>2021-03-15T00:36:51Z</updated>
<author>
<name>Carl Hetherington</name>
<email>cth@carlh.net</email>
</author>
<published>2021-03-15T00:36:51Z</published>
<link rel='alternate' type='text/html' href='https://git.carlh.net/cgit/libdcp/commit/?id=2c1faeb15715794525f48110c2b8a9df96b387c1'/>
<id>urn:sha1:2c1faeb15715794525f48110c2b8a9df96b387c1</id>
<content type='text'>
Check that subtitles don't overlap reel boundaries, and fix a few
tests that trip this check.

Fix confusion when calculating subtitle timings during verification
where the picture asset frame rate was being used rather than the
subtitle asset's edit rate.

Do the subtitle timing verification for Interop as well as SMPTE
subtitles.

Take &lt;StartTime&gt; tags into account when checking subtitles, even
though Bv2.1 says they should be set to 0.

Rename Time::as_editable_units to Time::as_editable_units_ceil
and add a _floor variant, then use that to round down when checking
reel boundary overlaps.
</content>
</entry>
<entry>
<title>Tidying.</title>
<updated>2021-01-24T03:15:26Z</updated>
<author>
<name>Carl Hetherington</name>
<email>cth@carlh.net</email>
</author>
<published>2021-01-24T03:15:26Z</published>
<link rel='alternate' type='text/html' href='https://git.carlh.net/cgit/libdcp/commit/?id=ceaf7bc52712cb60708ed5eb5c62c5e463dd8e89'/>
<id>urn:sha1:ceaf7bc52712cb60708ed5eb5c62c5e463dd8e89</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Use enum class for the things in types.h</title>
<updated>2021-01-21T00:57:06Z</updated>
<author>
<name>Carl Hetherington</name>
<email>cth@carlh.net</email>
</author>
<published>2021-01-21T00:57:06Z</published>
<link rel='alternate' type='text/html' href='https://git.carlh.net/cgit/libdcp/commit/?id=76e3325a16cdf6d7220a61e2b5cfdb9c804cc32c'/>
<id>urn:sha1:76e3325a16cdf6d7220a61e2b5cfdb9c804cc32c</id>
<content type='text'>
</content>
</entry>
<entry>
<title>s/DCPReadError/ReadError/g</title>
<updated>2020-04-14T18:16:44Z</updated>
<author>
<name>Carl Hetherington</name>
<email>cth@carlh.net</email>
</author>
<published>2020-04-14T18:16:44Z</published>
<link rel='alternate' type='text/html' href='https://git.carlh.net/cgit/libdcp/commit/?id=4d6c8aaf0167cde3bb63e9014604243bdc47b1a1'/>
<id>urn:sha1:4d6c8aaf0167cde3bb63e9014604243bdc47b1a1</id>
<content type='text'>
</content>
</entry>
<entry>
<title>rebase() would round up and so it was possible for ticks to go out of range.</title>
<updated>2018-05-02T21:16:03Z</updated>
<author>
<name>Carl Hetherington</name>
<email>cth@carlh.net</email>
</author>
<published>2018-05-02T21:16:03Z</published>
<link rel='alternate' type='text/html' href='https://git.carlh.net/cgit/libdcp/commit/?id=7b03aba8bc4e9df269430d79ce4ee2c6bd5f344c'/>
<id>urn:sha1:7b03aba8bc4e9df269430d79ce4ee2c6bd5f344c</id>
<content type='text'>
Now it still rounds up but then copes with overflow.
</content>
</entry>
<entry>
<title>db8af2f changed rebase() to round down when rebasing times, but</title>
<updated>2018-02-07T21:38:01Z</updated>
<author>
<name>Carl Hetherington</name>
<email>cth@carlh.net</email>
</author>
<published>2018-02-07T21:38:01Z</published>
<link rel='alternate' type='text/html' href='https://git.carlh.net/cgit/libdcp/commit/?id=f964e99d63f5f5999ae4f245e6b25ced014d8383'/>
<id>urn:sha1:f964e99d63f5f5999ae4f245e6b25ced014d8383</id>
<content type='text'>
did not say why.  This rounding down produces some unexpected results,
e.g. taking 41 at a TCR of 1000 to a TCR of 24 gives 0, which upsets
those who use DCP-o-matic and put in a SRT subtitle ending at ,041 ---
the sub time is rounded down to 0 for a SMPTE DCP.

This commit restores round-to-nearest behaviour.
</content>
</entry>
<entry>
<title>Fix ridiculous thinko in Time::operator{&lt;,&gt;}</title>
<updated>2016-08-22T15:06:29Z</updated>
<author>
<name>Carl Hetherington</name>
<email>cth@carlh.net</email>
</author>
<published>2016-08-22T15:06:29Z</published>
<link rel='alternate' type='text/html' href='https://git.carlh.net/cgit/libdcp/commit/?id=c178a9d89e489e37cd1db73c6b0d470616937966'/>
<id>urn:sha1:c178a9d89e489e37cd1db73c6b0d470616937966</id>
<content type='text'>
Before this x &lt; x and x &gt; x were true.
</content>
</entry>
<entry>
<title>Remove stringstream from Time.</title>
<updated>2016-08-11T14:26:30Z</updated>
<author>
<name>Carl Hetherington</name>
<email>cth@carlh.net</email>
</author>
<published>2016-08-11T14:26:30Z</published>
<link rel='alternate' type='text/html' href='https://git.carlh.net/cgit/libdcp/commit/?id=e5cd8c4b76c80f33c6e6733452cef43a06f7c701'/>
<id>urn:sha1:e5cd8c4b76c80f33c6e6733452cef43a06f7c701</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Use locked_sstream.  Replace once parse_stream with parse_memory.</title>
<updated>2016-07-22T08:20:58Z</updated>
<author>
<name>Carl Hetherington</name>
<email>cth@carlh.net</email>
</author>
<published>2016-07-22T08:20:58Z</published>
<link rel='alternate' type='text/html' href='https://git.carlh.net/cgit/libdcp/commit/?id=455475575bcfa30aa60a377235bfaf2fd7bc2da7'/>
<id>urn:sha1:455475575bcfa30aa60a377235bfaf2fd7bc2da7</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Tighten up time parsing, and also allow the previously</title>
<updated>2016-06-13T23:20:06Z</updated>
<author>
<name>Carl Hetherington</name>
<email>cth@carlh.net</email>
</author>
<published>2016-06-13T23:20:06Z</published>
<link rel='alternate' type='text/html' href='https://git.carlh.net/cgit/libdcp/commit/?id=8837fe70049bd5ed7ab583c06d6c9a620a01b351'/>
<id>urn:sha1:8837fe70049bd5ed7ab583c06d6c9a620a01b351</id>
<content type='text'>
unsupported Interop HH:MM:SS.sss format for times.
</content>
</entry>
</feed>
