Nexus and Windows

dt nexus is mac only its ai crop, sequencer, fusion, and lighting control features depend on macos frameworks to connect to capture one so what if your institution is "windows only"? in practice, "windows only" can mean three different things, and the path forward is different in each case mac friendly institutions some institutions already run a mixed fleet, or are willing to support a mac when there is a reason to it may be that you were not previously aware that a particular building, group, or department has macs already there is little to discuss in this case — the capture station mac is procured and brought online alongside the rest of the system existing it processes for imaging, credentialing, and asset tracking apply unchanged mac skeptical or mac resistant institutions these are institutions whose it departments will approve a mac under certain conditions but whose default posture is to push back the most productive framing in this conversation is that the mac running dt nexus is not a general purpose computer on the network — it is a component of a capture station that also includes lights, a camera, color and resolution targets, and bench such it departments may grant exceptions for embedded computers that are part of a larger instrument (microscopes, mri consoles, a/v editing suites, conservation imaging rigs), and the capture station belongs in the same category on request, dt can supply a letter on company letterhead stating that mac is the only supported platform for our software and is an integrated part of our hardware solution; this is usually what a formal exception process needs in writing it also helps to explain that the mac also does not necessarily have to live on the institution's internal network for the workflow to function several patterns work well in practice sync the capture folder over the institution's public or guest wifi network using dropbox, google drive, or a similar service so the mac never touches the private network; pool work locally at the capture station and move it to a networked pc workstation in batches using an external usb c ssd, which is now fast enough to add only a few minutes per session and which doubles as a first line backup of the capture until the job is closed out; or ask it to provision a single smb share reachable from the mac without making the mac a full directory joined member of the fleet in each pattern the mac is a single, well defined endpoint with a known software stack, which is generally easier for it to approve than a general purpose mac on the network while dt does not provide generalized ongoing it consulting services, we are glad to join calls or email threads to help communicate how we've seen this work at other institutions and answer technical questions where we are able mac excluded institutions a small number of institutions exclude macs categorically — typically driven by federal contracting requirements, classified environment rules, or a directive that the entire endpoint fleet be a single managed image in this case please know that dt's hardware — cameras, lights, copy benches, profiling targets — is widely deployed alongside windows capture and processing pipelines, with strong customer satisfaction what is unavailable in this case is specifically the dt nexus software layer such as ai crop, the sequencer, and the integrated lighting workflow conventional capture one workflows, manual cropping, legacy autocrop tool (which works quite well for less challenging content like white paper on a black background) and standard color management pipelines remain fully supported on windows