dcpomatic/src/tools/dcpomatic_disk.cc, branch cleanups DCP-o-matic DCP tools https://git.carlh.net/cgit/dcpomatic/atom?h=cleanups 2021-09-27T09:32:49Z Add config location versioning (#2090). 2021-09-27T09:32:49Z Carl Hetherington cth@carlh.net 2021-09-25T22:09:04Z urn:sha1:ccacce39c39d16977ab6c1592fcb6e941b05ddff Give an error if a non-DCP folder is selected for DCP writing (#2024). 2021-06-04T22:01:03Z Carl Hetherington cth@carlh.net 2021-06-04T22:01:03Z urn:sha1:3c5a2f73afa9a3a5324b0345ffa9642ee474598d Add some useful command-line options to dcpomatic2_disk. 2021-05-28T09:24:54Z Carl Hetherington cth@carlh.net 2021-05-28T09:24:54Z urn:sha1:04b34b7139407e3afa241939bc5416cf1bf06aef Insert a delay to make sure the QUIT message arrives (#2018). 2021-05-26T21:06:52Z Carl Hetherington cth@carlh.net 2021-05-26T21:06:52Z urn: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:53Z Carl Hetherington cth@carlh.net 2021-05-10T13:12:23Z urn: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:05Z Carl Hetherington cth@carlh.net 2021-05-09T14:43:24Z urn: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:05Z Carl Hetherington cth@carlh.net 2021-05-09T08:08:39Z urn:sha1:767238a8abebbb2a2f8d1e91806131754b9c67fd Wait a while for unmounts to go through in case we have to authenticate the user. 2021-04-22T13:42:11Z Carl Hetherington cth@carlh.net 2021-04-21T23:40:19Z urn:sha1:704c71ae870d8bfb7811567406f111e2f1efdc03 Re-scan drives just before writing the DCP (#1969). 2021-04-21T21:14:18Z Carl Hetherington cth@carlh.net 2021-04-21T21:14:18Z urn:sha1:f68217c17dddafdf9453e3bfdc6d7acb9430736e In case the drive you chose has disappeared, or something about it has changed since it was found. More disk build fixes. 2021-04-03T22:40:56Z Carl Hetherington cth@carlh.net 2021-04-03T22:40:56Z urn:sha1:8e1b0dfe3103867a749ff51156e3ed6547f298a0