1.3.0

Reports read the offload's own checks, one offload window with ticked live drives, the next card queues, Sony looks right, less CPU, SORT, buttons that stay put, and updates inside the app.

NEW 04

• New changelog page at engram.metawrks.com: every release, searchable, by area (Offload, Reports, Viewer & colour, Library, Transcode)

  OFFLOAD

• New option: Settings › Functionality › "Viewer as a Rec.709 monitor (gamma 2.4)", so the viewer matches your SDI monitor. Off by default

  VIEWER & COLOUR

• New Library › New Day (SHIFT+CMD+D): copies the latest DAY's folders as the next DAY, empty, with UNDO

  OFFLOAD

• New Library › Wrap Day Report: the whole DAY's report from the library, using the offload's own checks — nothing is scanned again

  OFFLOAD

IMPROVED 02

• An offload could never run without its <drive>/…/<CAM>/<MAG> folders now — if they are missing, it says so and copies nothing

  OFFLOAD

• Note blocks that explained the code are off the screen. Controls, values and real warnings stay

FIXED 101

• There was no way to update from inside the app, and Settings said "No update channel configured yet"

  Now: ENGRAM › Check for Updates… and Settings › System › UPDATES › CHECK FOR UPDATES. It also checks by itself at launch and every 4 hours (switch it off in the same place)

• A new version was never announced

  Now: a calm window shows the new version, its build, the date and the changes in a text block, with UPDATE, REMIND ME LATER (asks again tomorrow) and SKIP THIS VERSION (stays quiet until a newer one)

• An update could have landed mid-job

  Now: nothing installs, and the window doesn't pop up, while an offload, verify, report or transcode runs or cards are queued; it says what it's waiting for

  OFFLOAD

• An update had no way back

  Now: UPDATE checks the package and gets it ready; RESTART TO USE swaps it in when you choose, keeps the version you had, and puts the old one back by itself if the new one doesn't check out. ROLL BACK in Settings goes back one step in one press

  OFFLOAD

• About said "1.2" on every build

  Now: About and Settings show the real version and build: 1.3.0 (build 130)

• Sony S-Log3 clips showed ENGRAM's own S-Log3 curve, about a stop hot in the highlights

  Now: they show Sony's own LC-709TypeA LUT, taken from your Resolve LUT folder. Pick another Sony look (LC-709, Cine+709, SLog2-709, s709) in Settings › Functionality › SONY LOOK. ENGRAM's own curve is still in the LUT list, now named "ENGRAM generic, not Sony"

  VIEWER & COLOUR

• S-Cinetone clips (C CAM day 1) got an S-Log3 LUT on top and went half black

  Now: S-Cinetone, Rec.709, Cine and HG clips show as recorded, with no LUT. HLG reads as HLG. S-Log2 asks you to set it by hand

  VIEWER & COLOUR

• FX6 MXF clips fed the Sony LUT the wrong code values (crushed blacks, hot whites) and didn't match FX3/FX30 MP4s through the same LUT

  Now: the LUT gets the values the camera recorded; FX6 and FX3 now agree within half a code value. On the D002 demo clip the picture is within ΔE 0.44 (avg) of Sony's own LUT, from 2.21 before

  VIEWER & COLOUR

• S-Gamut3 clips (not .Cine) went through a .Cine LUT as-is

  Now: they're converted to S-Gamut3.Cine first (Sony's S-Gamut3 LUT is used instead when you have it)

  VIEWER & COLOUR

• False colour with the LUT on read the LUT's picture as log: +2 stops showed as +6

  Now: false colour always reads the camera's own image: +2 shows +2.0, −4 to +4 within 0.05 stop, LUT on or off

  VIEWER & COLOUR

• Posters, scrub frames and the viewer decoded about 2 code values dark

  Now: decoded exactly (old cached frames rebuild by themselves)

  VIEWER & COLOUR

• A paused frame was a lower-quality JPEG of the clip

  Now: it's the real full-quality frame, the same one playback shows

  VIEWER & COLOUR

• 33-point LUTs lost detail between their points in the viewer

  Now: they're applied on a finer grid

  VIEWER & COLOUR

• Transcodes with a Sony S-Log3 LUT on FX6 MXF had the same wrong code values

  Now: they get the camera's values too

  VIEWER & COLOUR

• Pressing START (or plugging in the next card) while a card copied did nothing

  Now: the card QUEUES. When the copying card is certified, the next one starts by itself. If it isn't certified, the queue stops and tells you which card; START NEXT or CLEAR on the queue bar. A card that needs you (a red × drive, a duplicate) stays open in the offload window

  OFFLOAD

• After-copy options were buried in Settings

  Now: the offload window has an AFTER row: EJECT CARD · REPORT · TRANSCODE, ticked right there

  OFFLOAD

• Nothing told you a card was done with

  Now: a lime SAFE TO PULL bar and a notification ("SAFE TO PULL — A005 · 3/3 DRIVES VERIFIED") once every drive verified and the card re-read clean

  OFFLOAD

• A card going in only showed a small bar (and only if you had turned it on)

  Now: it opens the offload window, filled in with the card. It never starts by itself unless you turn on "Then start by itself after 5 seconds" (off by default); STARTING IN 5 shows in the window, STOP holds it

  OFFLOAD

• Routes had no camera letter

  Now: new CAM LETTER token: A005 lands in "A CAM" by itself

• SAFE TO PULL showed after RUN ON 1 when one of your usual 2 drives was offline ("1/1 DRIVES VERIFIED" while the card was only on one drive)

  Now: SAFE TO PULL only shows when the card is on every drive you usually use; the count matches the result line (1/2 stays amber, no SAFE TO PULL)

  OFFLOAD

• A queued card went into whatever bin was selected when it started, not the bin you queued it into

  Now: the bin is locked in when you press QUEUE and shows on the card's chip (B001 → A CAM). If that bin was deleted, moved to another show or the project changed, the queue stops with NEEDS YOU instead of copying

  OFFLOAD

• The library file was rewritten whole, about once a second, while a card copied (61 MB each time on today's job)

  Now: only a small catalog (≈2 MB) is written, at most every few seconds during a copy; each clip's metadata is added as one small line instead. Your old library file is kept next to it as a backup the first time

  OFFLOAD

• Opening or closing a folder in the library rewrote the whole library

  Now: it saves only which folders are open

  LIBRARY

• Clip metadata landing during an offload redrew the library once per clip

  Now: it lands in batches, about once a second

  OFFLOAD

• Scrub previews, posters and the viewer decoded on the CPU, up to 4–6 cores per clip

  Now: Sony XAVC-I, XAVC-L and XAVC HS (H.264 / H.265) decode on the GPU, with the exact same picture (checked byte for byte). ProRes stays on the CPU, because the GPU decoder is 2–3 code values off

  VIEWER & COLOUR

• One scrub-preview builder could take 4–6 cores and 1.2 GB

  Now: it uses 2 at most, runs at the lowest priority, and reads only keyframes on long-GOP clips

  VIEWER & COLOUR

• After each card, scrub previews for the whole drive were built while the next card copied

  Now: they wait until the copy is done, and stop if a new card starts

  OFFLOAD

• Each drive's copy was checked one drive after the other

  Now: all drives are checked at the same time, on separate cores

  OFFLOAD

• Clip metadata was read one clip at a time

  Now: several at once across the cores; fewer while a card copies, so the copy keeps its speed

  OFFLOAD

• The CPU meter showed the app only, not ffmpeg or the copy engine

  Now: it shows the app plus everything it started, and the GPU next to it (click it for the app's own share)

  OFFLOAD

• Scopes kept redrawing on a paused frame

  Now: they rest until the picture changes

  VIEWER & COLOUR

• Picking a source opened one window, then a scan window, then the offload window

  Now: it is ONE window: card list → scanning → setup, all in the same window. Nothing asks for a destination after the card

  OFFLOAD

• You had to pick the card again even when you were already looking at it

  Now: a card you're browsing in the grid (or the one card plugged in) opens the offload window straight on it. SOURCE in the window swaps the card

  OFFLOAD

• Drives showed OFFLINE only, and a dead drive could still be ticked

  Now: every drive is a tile with a tick box and a status: READY (and how many more cards of this size fit), or a red × OFFLINE / READ-ONLY / SOURCE / FULL. A red × drive can't be ticked

  OFFLOAD

• START could make folders before finding a drive it couldn't write

  Now: every ticked drive is checked again at START, before any folder is made; a red × drive holds START and RUN ON N copies to the rest

  OFFLOAD

• × on a drive was final

  Now: × is instant and UNDO puts it back (place, tick, route)

  OFFLOAD

• The drive list was the same for every project

  Now: each project remembers its own drives; a new project starts with the drives you have

  OFFLOAD

• The finished result could show inside the offload window

  Now: the window never shows a result or DONE; the copy's progress and verdict are in TASKS and on the library strip

  OFFLOAD

• There was no way to copy a day's folders

  Now: right-click › Duplicate Structure or CMD+D: DAY 003 → DAY 004 with every OCF / CAM folder, empty (no rolls, no clips, nothing marked verified), placed below the last day and ready to rename. UNDO in the note at the bottom. It only makes the folders on your drives when you tick "Also Make On Drives" (off by default)

  OFFLOAD

• GRID/VIEWER/LIST/DATA slid sideways and shrank when you opened VIEWER (a BACK chip appeared in front of them)

  Now: the four buttons sit in the exact same spot and size on every page; GRID, Esc and CMD+1 still go back

  VIEWER & COLOUR

• The GRID/VIEWER/LIST/DATA bar sometimes dropped to icons only on one page

  Now: it always shows its words, every button the same width

  VIEWER & COLOUR

• Switching LIBRARY/TRANSCODE/TASKS made the whole top band drop and fade in

  Now: the page crossfades in place; nothing in the band moves

  LIBRARY

• Buttons came in different heights (18, 20, 22, 26, 28, 30)

  Now: every boxed button in a top band is one height, the same as LIBRARY/TRANSCODE/TASKS; window and footer buttons share one height of their own; both follow UI Scale

  LIBRARY

• The gear and the CPU meter were taller than the chips beside them and ignored UI Scale

  Now: same box as the chips

• The selected tab turned bold and nudged its neighbours

  Now: selection shows by colour only; nothing reflows

  VIEWER & COLOUR

• TASKS' CARDS/TIMELINE were two loose icons on the right

  Now: one boxed switch at the left, where LIBRARY's view switch sits

  OFFLOAD

• INFO disappeared in DATA, and TASKS' chips jumped when CLEARED appeared

  Now: both are always there, dimmed when they can't be used

• Going to TRANSCODE pushed the project name sideways

  Now: the project name never moves

  TRANSCODE

• Going LIBRARY

  Now: TASKS → LIBRARY landed on GRID → it comes back to the same clip in VIEWER

  VIEWER & COLOUR

• OFFLOAD window tabs (LIBRARY & METADATA / BACKUP & VERIFY, rename scope, existing files) were a different size

  Now: same box as the other tabs

  OFFLOAD

• There was no way to put clips in order

  Now: SORT button in the LIBRARY band: Name, Record time, Backup time, Size, Duration, Camera, Reel / Mag, Format / codec, Frame rate; ascending or descending. One order for GRID, LIST and the VIEWER strip, remembered between launches. LIST's NAME / TYPE / SIZE headers use the same order. Clips missing a value go last. Sorting never re-reads the clips

  VIEWER & COLOUR

• Backup time had nowhere to come from

  Now: each clip now records when it landed verified

  REPORTS

• Exporting a report re-read and re-checked every clip that was already verified on the offload

  Now: the report reads what the offload already recorded; 0 clips are read from the drives for a verified bin

  OFFLOAD

• There was no way to force a full re-read when you actually want one

  Now: RE-SCAN MEDIA in the REPORT window, off by default, for that one report only

  REPORTS

• Picking a source sometimes showed the last card's finished/report window instead of the new card

  Now: every offload button closes the finished job first; the window always opens on the new card's setup (the result stays in TASKS)

  OFFLOAD

• After a report, View › Offload and GO TO OFFLOAD reopened the report, and CMD+R ran it again

  Now: they open OFFLOAD; CMD+R after a finished report opens its setup

  OFFLOAD

• RETRY / RUN AGAIN could fail on files the first run already copied, or copy the whole card when you had picked some files

  Now: it re-checks what is already there (Skip Identical) and copies the same files you picked

  OFFLOAD

• The bin's Offload buttons stayed live while a card was copying

  Now: they grey out until the copy ends

  OFFLOAD

• Sources vanished from the list while a drive was spinning up or busy

  Now: the drive stays listed and says BUSY, and comes back to normal on its own

  OFFLOAD

• A clip still being written (size changed after the scan) could pass

  Now: that clip FAILS and is named: "SOURCE CHANGED DURING OFFLOAD"

  OFFLOAD

• NOT CERTIFIED didn't say which file

  Now: it names the file, the reason and the fix

  REPORTS

• The REPORT tab could walk a whole drive

  Now: it reports on the library selection; a whole drive only when you pick it yourself

  OFFLOAD

• Camera thumbnails, XML/JSON sidecars and system files counted as "files backed up"

  Now: the total counts media; the rest are their own rows (still copied and in the ASC-MHL)

  REPORTS

• The grid opened full of JPGs and thumbnails

  Now: motion clips first; stills behind one chip

  LIBRARY

• The long drive list sat across the grid

  Now: hidden behind one drive toggle, remembered

  OFFLOAD

• Sony cards: blank metadata on a clip whose XML landed after it, odd frame rates, a 4294967295 "serial", reel letters other than C/L missed

  Now: probed again once the XML lands, exact rates, serial left blank, any camera letter

  OFFLOAD

• With RENAME on, the dailies transcode after an offload looked for the card's original names and found nothing

  Now: it opens the renamed copies that actually landed on the drive

  OFFLOAD

• A START that was refused left empty <bin>/<MAG> folders on every drive

  Now: the empty folders that START made are taken back; a folder that was already there, or holds a file, is never touched

  OFFLOAD

• RUN ON N stayed armed after a refused START

  Now: a refused START asks again

  OFFLOAD

• If the engine itself failed to launch, RETRY could register the copy into a bin that had been removed

  Now: the mag bin and its folders stay for RETRY

  OFFLOAD

• A card pulled after you opened it still let START make the mag bin and folders, then jumped to an empty bin

  Now: START says "Source is offline" and stays put; nothing is made

  OFFLOAD

• If a job refused to start after START, the window closed onto an empty bin and the drive folders stayed armed for the next run

  Now: the card stays open in the window, the bin and your answers go back, and nothing is left armed

  OFFLOAD

• The dailies transcode after an offload could read a drive you skipped with RUN ON N, or look at the drive root

  Now: it reads the copy that job just wrote and verified, in <drive>/…/<CAM>/<MAG>

  OFFLOAD

• CMD+N on an open card kept that card's resume answer

  Now: the new card replaces it the same way the top OFFLOAD button does

  OFFLOAD

• CMD+R with no card did nothing

  Now: it asks for the card, same as the top OFFLOAD button

  OFFLOAD

• Clicking a bin with no drives listed added that bin's drive, right-click didn't

  Now: neither adds a drive; you add drives in the window with ADD DESTINATION

  OFFLOAD

• A drive that dropped without warning (the OWC RAID) could still count as plugged in for a few seconds

  Now: START, RETRY and COPY TO MISSING check every drive fresh before writing; no stray folder on the Mac's disk

  OFFLOAD

• A destination folder on the Mac's own disk read as a different drive every card

  Now: it counts as the same drive, so no false "drive missing"

  OFFLOAD

• The library's "Offload Into This Bin" and the OFFLOAD button up top behaved differently

  Now: both ask for the card, open the same window, land on every drive in the same folders and use the same START check; the only difference is which bin it goes into

  OFFLOAD

• With no drive listed, the library door asked for a destination the top button didn't

  Now: both open the window and you add drives there with ADD DESTINATION

  OFFLOAD

• The top OFFLOAD button reopened the last card without asking

  Now: it asks for the card, starting on the last one, so one press re-picks it

  OFFLOAD

• CMD+R while a card was open skipped the drive check and could copy loose to each drive root

  Now: CMD+R does exactly what START does, red line and all

  OFFLOAD

• A RETRY that was refused (card not back in yet) hid the result and left the next RUN copying loose to drive roots

  Now: a refused RETRY keeps the result on screen and leaves nothing behind

  OFFLOAD

• RUN ON N left the skipped drive unticked on every card after

  Now: the drive is ticked again for the next card, and warns if it is still missing

  OFFLOAD

• The finished-job banner could say "3/3 drives " when the job was then marked NOT CERTIFIED

  Now: the banner waits for the final verdict

  OFFLOAD

• Checking drives on every redraw could stutter the window while a shuttle spun up

  Now: drive status is remembered and refreshed when a drive comes or goes

  OFFLOAD

• Right-click "Offload Into This Bin" cut your drives down to one

  Now: every drive you listed stays; the bin only picks the folder on each drive

  OFFLOAD

• New Offload (CMD+N) wiped your drive list

  Now: it clears the card and slate only; your drives stay

  OFFLOAD

• Clicking a bin on another shuttle swapped out your first drive

  Now: clicking a bin never changes your drives

  OFFLOAD

• Nothing warned when fewer drives were going than last card

  Now: START shows a red line ("2 drives missing: …") with ADD BACK or RUN ON 1 DRIVE, one press each

  OFFLOAD

• An unplugged drive could vanish from the list

  Now: it stays listed and says OFFLINE

  OFFLOAD

• "Verified" read the same for 1 drive as for 3

  Now: the result, the library strip and the notification say "I004 · 3/3 drives 008 · 006 · 003", amber when short

  OFFLOAD

• No way to see which mags were on fewer drives

  Now: each mag shows its copy count (3×, amber when short); right-click a DAY or CAM › Copies… lists the short ones with COPY TO MISSING

  OFFLOAD

• A card staged while the last one was still copying renamed the last card's record (C009 saved as I004)

  Now: each record keeps its own bin name; a new card can't be staged mid-copy

  OFFLOAD

• COPIES counted a stopped or part-copied card as a full copy

  Now: a drive counts only when the whole card verified on it

  OFFLOAD

• RETRY / RUN AGAIN dropped the card loose at each drive root and skipped the drive check

  Now: it re-runs into the same <drive>/…/<CAM>/<MAG> folders and asks the same drive question START does

  OFFLOAD

• A failed drive still read "3/3 drives ×"

  Now: the count is drives that verified, and the bad one is named ("2/3 drives × 008 · 003 — 006 FAILED")

  OFFLOAD

• Taking a drive off with × kept warning "1 drive missing" on every card

  Now: × forgets that drive

  OFFLOAD

• COPY TO MISSING failed on a half-filled folder and could start a transcode

  Now: it re-checks files already there (Skip Identical) and never chains a transcode

  OFFLOAD

• RUN ON N could skip an offline drive and then do nothing when another warning was open

  Now: it is greyed until that warning is cleared, and skips nothing

  OFFLOAD

• A leftover /Volumes folder from a dropped drive counted as the drive

  Now: only a real mounted drive counts; the leftover reads OFFLINE

  OFFLOAD