dcpomatic/src/tools/dcpomatic_disk.cc, branch nvidiaDCP-o-matic DCP toolshttps://git.carlh.net/cgit/dcpomatic/atom?h=nvidia2022-04-22T21:50:01ZAnd another missed warnings.h2022-04-22T21:50:01ZCarl Hetheringtoncth@carlh.net2022-04-22T21:50:01Zurn:sha1:1d14e44952b8cd1430946437995ee0fa360d9bf7Use libdcp's warnings.h2022-04-22T21:27:15ZCarl Hetheringtoncth@carlh.net2022-04-22T21:27:15Zurn:sha1:3c29aa6531a4046a8db72dcac81189eb8893233cAdd some missing override labels.2022-04-09T11:58:27ZCarl Hetheringtoncth@carlh.net2022-04-09T11:58:27Zurn:sha1:b915348a8288d68e2ff114fb3dd89ad22e699969Add config location versioning (#2090).2021-09-27T09:32:49ZCarl Hetheringtoncth@carlh.net2021-09-25T22:09:04Zurn:sha1:ccacce39c39d16977ab6c1592fcb6e941b05ddffGive an error if a non-DCP folder is selected for DCP writing (#2024).2021-06-04T22:01:03ZCarl Hetheringtoncth@carlh.net2021-06-04T22:01:03Zurn:sha1:3c5a2f73afa9a3a5324b0345ffa9642ee474598dAdd some useful command-line options to dcpomatic2_disk.2021-05-28T09:24:54ZCarl Hetheringtoncth@carlh.net2021-05-28T09:24:54Zurn:sha1:04b34b7139407e3afa241939bc5416cf1bf06aefInsert a delay to make sure the QUIT message arrives (#2018).2021-05-26T21:06:52ZCarl Hetheringtoncth@carlh.net2021-05-26T21:06:52Zurn:sha1:f75c4440abe1a1cd9838301ac4e3a153178ceb94
I have no idea why this is necessary, but the nanomsg documentation
suggests it.
Open a dialogue if pinging the back-end fails on macOS.2021-05-10T21:35:53ZCarl Hetheringtoncth@carlh.net2021-05-10T13:12:23Zurn:sha1:1484f4e3642e3ddcb10515eb0f32b00370968da3
At least this means the user will get another go without losing
their setup. My only theory at this point is that sometimes the
backend takes a crazy amount of time to start up because of some
SIP / gatekeeper type nonsense (#1990).
Attempt ping from front- to back-end several times (#1990).2021-05-09T21:15:05ZCarl Hetheringtoncth@carlh.net2021-05-09T14:43:24Zurn:sha1:472959c1357f43e2eb33366c58bed0466474c2b7
On macOS it seems that the backend sometimes is not started very
quickly. Adding a long timeout to ping does not work, perhaps
because the backend is not listening.
Trying a few times seems to fix it.
With this fix I saw this log:
Sun May 9 23:02:51 2021: dcpomatic_disk_writer e63a485e23 started
Sun May 9 23:02:51 2021: Entering main loop
Sun May 9 23:02:51 2021: Writer receives command: P
from the backend and
Sun May 9 23:02:45 2021: Could not send ping to writer (attempt 1)
Sun May 9 23:02:47 2021: Could not send ping to writer (attempt 2)
Sun May 9 23:02:49 2021: Could not send ping to writer (attempt 3)
from the front-end, suggesting that the first 3 pings went to /dev/null
and the 4th was heard.
Add more logging to disk writer.2021-05-09T21:15:05ZCarl Hetheringtoncth@carlh.net2021-05-09T08:08:39Zurn:sha1:767238a8abebbb2a2f8d1e91806131754b9c67fd