I am a new user of DCP-o-Matic, but an experienced IT professional who has many years experience supporting and administering systems in post-production environments.
I have three spare Macs in my house that are running macOS 12 Monterey (or newer, if supported), and I installed the latest version of the DCP-o-Matic server app on them (2.18.44). DCP-o-Matic 2.18.44 is running on my control Mac: a MacBook Pro M1. This Mac is also being used to render.
All the Intel Macs acting as DCP encoders are accepting jobs from the M1 without any problem. However, I notice that when I pull up the Tools > Encoding Servers... list, it's usually missing one or more nodes that are definitely running and available on the LAN. If I wait a bit and re-check the list, it is sometimes complete.
Is this a known bug?
PS: the three spare Macs are as follows: a 2013 Mac Pro (12-core/24-thread) @ 2.7GHz, a 2018 Mac mini Core i7 (6-core/12-thread) @ 3.2GHz, and an M1 Mac mini (8 cores). The oldest Mac Pro is at least twice as fast as the other two.
Bug: the list of encoding servers is usually incomplete
-
theirongiant
- Posts: 9
- Joined: Mon Jul 06, 2026 1:03 am
-
theirongiant
- Posts: 9
- Joined: Mon Jul 06, 2026 1:03 am
Re: Bug: the list of encoding servers is usually incomplete
I just noticed that there is a Github repository for DCP-o-Matic, so I will be filing an issue there.
-
Carsten
- Posts: 3114
- Joined: Tue Apr 15, 2014 9:11 pm
- Location: Germany