<feed xmlns='http://www.w3.org/2005/Atom'>
<title>dcpomatic/src/lib/grok_j2k_encoder_thread.cc, branch v2.17.9</title>
<subtitle>DCP-o-matic DCP tools</subtitle>
<id>https://git.carlh.net/cgit/dcpomatic/atom?h=v2.17.9</id>
<link rel='self' href='https://git.carlh.net/cgit/dcpomatic/atom?h=v2.17.9'/>
<link rel='alternate' type='text/html' href='https://git.carlh.net/cgit/dcpomatic/'/>
<updated>2023-11-29T20:20:30Z</updated>
<entry>
<title>Clean up grok's presence in the config file and make sure it's optional.</title>
<updated>2023-11-29T20:20:30Z</updated>
<author>
<name>Carl Hetherington</name>
<email>cth@carlh.net</email>
</author>
<published>2023-10-06T20:42:44Z</published>
<link rel='alternate' type='text/html' href='https://git.carlh.net/cgit/dcpomatic/commit/?id=0dc71b05952a258e5deb9fcc9b099357caa928f1'/>
<id>urn:sha1:0dc71b05952a258e5deb9fcc9b099357caa928f1</id>
<content type='text'>
It should be allowed to not have any grok stuff in the config file,
and we should generally call it grok rather than GPU in case
other non-grok GPU stuff arrives in the future.
</content>
</entry>
<entry>
<title>Log failure to schedule a frame with grok.</title>
<updated>2023-11-29T20:19:56Z</updated>
<author>
<name>Carl Hetherington</name>
<email>cth@carlh.net</email>
</author>
<published>2023-10-04T13:36:55Z</published>
<link rel='alternate' type='text/html' href='https://git.carlh.net/cgit/dcpomatic/commit/?id=8f103d361702749ca9ac4847cd78811cdd5e7261'/>
<id>urn:sha1:8f103d361702749ca9ac4847cd78811cdd5e7261</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Forward-declare grk_plugin stuff.</title>
<updated>2023-11-29T20:19:56Z</updated>
<author>
<name>Carl Hetherington</name>
<email>cth@carlh.net</email>
</author>
<published>2023-09-26T11:32:00Z</published>
<link rel='alternate' type='text/html' href='https://git.carlh.net/cgit/dcpomatic/commit/?id=dc41cc6d32d04a50f4952f729b45538f5e2b84f7'/>
<id>urn:sha1:dc41cc6d32d04a50f4952f729b45538f5e2b84f7</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Rearrange encoder threading.</title>
<updated>2023-11-29T20:19:55Z</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=d51c2864b48adf1b3b76d218c549445cc1005d9b'/>
<id>urn:sha1:d51c2864b48adf1b3b76d218c549445cc1005d9b</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>
