<feed xmlns='http://www.w3.org/2005/Atom'>
<title>dcpomatic/test/j2k_encode_threading_test.cc, branch mpeg2</title>
<subtitle>DCP-o-matic DCP tools</subtitle>
<id>https://git.carlh.net/cgit/dcpomatic/atom?h=mpeg2</id>
<link rel='self' href='https://git.carlh.net/cgit/dcpomatic/atom?h=mpeg2'/>
<link rel='alternate' type='text/html' href='https://git.carlh.net/cgit/dcpomatic/'/>
<updated>2024-04-21T21:18:23Z</updated>
<entry>
<title>Extract VideoEncoder as a parent of J2KEncoder.</title>
<updated>2024-04-21T21:18:23Z</updated>
<author>
<name>Carl Hetherington</name>
<email>cth@carlh.net</email>
</author>
<published>2024-03-19T16:10:27Z</published>
<link rel='alternate' type='text/html' href='https://git.carlh.net/cgit/dcpomatic/commit/?id=fa15dc1a375e13d2047a857e5aef202179eec0d4'/>
<id>urn:sha1:fa15dc1a375e13d2047a857e5aef202179eec0d4</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Rename Encoder -&gt; FilmEncoder, and subclasses.</title>
<updated>2024-04-21T21:18:19Z</updated>
<author>
<name>Carl Hetherington</name>
<email>cth@carlh.net</email>
</author>
<published>2024-03-19T15:29:13Z</published>
<link rel='alternate' type='text/html' href='https://git.carlh.net/cgit/dcpomatic/commit/?id=1fc8c0c6d045404732497ba70bd2eccfbe4cc6f6'/>
<id>urn:sha1:1fc8c0c6d045404732497ba70bd2eccfbe4cc6f6</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Rearrange encoder threading.</title>
<updated>2024-01-28T01:01:57Z</updated>
<author>
<name>Carl Hetherington</name>
<email>cth@carlh.net</email>
</author>
<published>2023-09-23T22:34:15Z</published>
<link rel='alternate' type='text/html' href='https://git.carlh.net/cgit/dcpomatic/commit/?id=f8d0dac871883c7cbfa6f31c182ca3e6d213aed1'/>
<id>urn:sha1:f8d0dac871883c7cbfa6f31c182ca3e6d213aed1</id>
<content type='text'>
Soon we'll add a new encoder type, and the existing structure was
already creaking a bit at the seams while handling local and remote
encodes.  Here we split out an encoder thread and introduce the concept
of a "sync" thread (which blocks while the encoding is happening).
Later we'll have another type which submits the encode request to a
GPU and receives the reply back later.
</content>
</entry>
</feed>
