
A darktable tethering jobcode is an input to a naming pattern, not an independent guarantee that every destination folder will contain that text. The Session module supplies the jobcode, while Import preferences define the base directory, filmroll pattern and filename pattern. Check where the JOBCODE variable is actually used.
Trace the three naming parts
The official Session manual defines a session as tethered exposures placed in one filmroll. It points to Preferences > Import > Session options for using the jobcode in the creation of that filmroll.
The Import preferences documentation separates the naming pattern into a parent directory, a session-specific filmroll component and an individual filename component. The documented variable is $(JOBCODE). A custom filmroll pattern containing only the date can omit the jobcode even when the Session field was filled correctly.
Write down the intended destination structure before changing the camera session. The approved-asset handoff guide helps identify deliverables later, but approval labels are separate from the folder-generation rules used at capture.
Check one hypothetical two-client day
Imagine a studio photographing two authorized product ranges on the same day. The session identifiers are CedarFront and CedarDetail. The proposed goal is a separate filmroll folder for each range inside one known base directory.
Inspect the current filmroll pattern. A pattern using a date plus $(JOBCODE) expresses that distinction; a date-only pattern does not. Keep the filename pattern distinct in your notes, since changing a filename does not by itself establish a separate filmroll directory.
Before the actual shoot, use a small test session and a safe destination:
- Confirm the base directory is the intended location and is accessible.
- Record the exact filmroll pattern and whether it includes $(JOBCODE).
- Set a recognizable test jobcode in the Session module.
- Capture a harmless test exposure using the supported tethering setup.
- Locate the resulting file and compare its parent directory and filename with the written expectation.
This is a proposed rehearsal, not a reported camera test. It does not certify that a particular camera is compatible with tethering.
Do not repair a path problem by moving the only capture
If the test lands in an unexpected directory, preserve it and inspect the active naming preferences before the next capture. Do not repeatedly shoot into uncertain destinations and manually shuffle the only files afterward. Distinguish an unavailable drive from a pattern that simply omitted a variable.
The recorded batch-filename guide describes another repeated-path problem, but its action overrides are not darktable session controls. Use the actual three-part pattern here rather than borrowing a similarly named export setting.
Accept both storage and session identity
For the two-client example, verify that one test from each intended session appears under its expected filmroll and that neither requires a guess based solely on thumbnail appearance. Keep source captures separate from later editable masters and flat deliveries.
Record the confirmed pattern alongside the session brief. The result passes when the jobcode reaches the intended path component, captured files are accessible there, and the selected naming convention supports the real handoff without relying on an assumed folder rule.
Related tasks
- How Do I Keep the Approved AI Image or Video from Getting Lost Among Revisions?
- Why Does My Photoshop Batch Action Save Files Under the Same Name?
- What Is the Difference Between an Editable Artwork Master and a Flat PNG?
Sources and scope
- darktable user manual: session: Session jobcode participates in filmroll creation through Import naming patterns; the pattern has base, session and filename components.
- darktable user manual: import preferences: Session naming consists of base directory, filmroll and filename patterns. JOBCODE is available as an input variable.
Based on the current online darktable manual reviewed October 31, 2026. Match controls to the installed release. Examples and acceptance checks are proposed, not measured application or print tests.
Prepared by Imagild Editorial, the company editorial team responsible for these guides. AI assisted research and drafting. This is documentation-based guidance with proposed examples, not a claim of hands-on testing or an independent product review. Report a correction.
Cover: AI-generated conceptual editorial illustration; not a real application screenshot, observed output or before-and-after test.