BRIEF §14.7: the server falls back to managed formats when no node is
available and says so in the job log. An MP4 job waits for render nodes at
least the node timeout, then as long as an online node can encode its codec
at its size; after that the server's engine takes it and writes each output
it cannot encode as MJPEG in AVI at the same size and frame rate, with a job
log line. A job the server started resumes there. Selective acceptance is
asynchronous for that; when node availability cannot be read the job keeps
waiting.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012iLMBNwBE2GnphAsu4cjaC
Accepts that throws now claims the job so it fails with its reason; claim
and finish errors are logged and the worker carries on. Other kinds keep
their atomic claim next to selective ones, and a lost race retries at once.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012iLMBNwBE2GnphAsu4cjaC
- JobEngine: ISelectiveJobHandler lets a host decline jobs of a kind it runs;
declined jobs stay queued for other claimers without holding up the rest.
JobContext.EnqueueFollowUpAsync queues follow-up work on the same engine.
- Server renders the jobs whose every output a managed encoder produces
(ManagedRenderJobHandler); MP4 jobs stay for render nodes. Program.cs
registers ProcessingModule next to ArchiveModule. Server renders ignore a
client's export folder.
- Light analysis is queued after imports and after scans that indexed new
sequences, so the advisor's Auto values exist without user action.
- Analysis jobs log a failing sequence and go on; the job then fails and a
retry analyses only the failed ones. The advised frame rate follows the
user's fit-to duration.
- ProcessingJobs.RenderEach splits a batch into one job per preset for
servers; render nodes say which batch presets they did not render, fetch
each content once and stop on a changed certificate.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012iLMBNwBE2GnphAsu4cjaC
An engine with no handlers (or a filter it could not serve) claimed every
job, so a host without a render handler would fail render-node work.
With several workers, jobs carry node ids such as pc#1, but crash
recovery only matched the bare node id and left them running forever.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012iLMBNwBE2GnphAsu4cjaC
JobEngine claims queued jobs atomically, persists progress at most every
checkpoint interval, stops a handler when its job is cancelled or paused
elsewhere and requeues jobs a crash left running.
Also installs the SQLite import resolver under a lock so a concurrent
first caller cannot reach a P/Invoke before the resolver is in place.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012iLMBNwBE2GnphAsu4cjaC