Soundcolour Studio & Ingest

A gentle front-end for the ingest system. Staff can log a new asset, generate an SCID stub and hand it to the Mac-based automation running at Leongatha or Narracan.

Acid Studio test box

Ingest console

Use this form when a new recording, video, stills batch or document arrives. It doesn’t move the files; it generates a clean ingest summary that can be pasted into the spreadsheet, ticketing system or notes.

If left blank, today’s date will be used when generating the SCID stub.

This does not upload or move files. It simply generates clean text ready to paste into the ingest spreadsheet or automation input.

Output

SCID ingest summary

Fill in the form and click “Generate SCID ingest stub”. A summary will appear here.
Staff instructions
  1. 1. Confirm that files are on the correct ingest drive / folder.
  2. 2. Fill in the form and generate the stub.
  3. 3. Paste the block into the shared ingest spreadsheet and/or ticket.
  4. 4. Tag which Mac (Leongatha or Narracan) will run the ingest.

How this connects to the automation

This website pack is deliberately simple. The heavy lifting is done by Python / shell scripts on the Macs that watch the ingest folders and talk to SCID, ISRC and backup systems.

Step 1

Capture & backup

Files are recorded on the appropriate device (Logic, Resolve, camera, phones) and parked on the T7 / Cloud Pod / local drive as agreed.

Step 2

Ingest stub

A staff member logs the incoming asset here and pastes the resulting text into the shared ingest sheet. That keeps humans and automations in sync.

Step 3

Mac-based scripts

On the studio Macs, launchd / cron jobs read the sheet, move or copy the files into the correct Soundcolour_Collect structure and assign SCIDs.

Step 4

Archive & publish

Once checked, assets are promoted to Soundcolour_Studio and long-term archive, then wired into artist pages, EPKs and distribution plans.