Skip to main content
How can we help?
Table of Contents
< All Topics
● Knowledge Base · Panels

Import/Export & Burn-In Standard / Ultra

Two related panels for moving metadata in and out of basehead through plain text files, plus burning database edits back into the source files.

Import / Export Text File F7

Edit metadata in a spreadsheet (Excel, Google Sheets) and round-trip it through basehead, or import text-file dumps from other software you’re migrating away from.

Import/Export Text File panel

Importing

  • Reads .tsv, .csv, and .txt files — tab, comma, or semicolon delimited.
  • Auto-matches columns to fields with manual re-routing in the bottom section.
  • Uncheck any field on the left to skip it during import.
  • Imports text-file dumps from the major rival sound-management programs, so migration is a single round trip.
To re-link files back into basehead, the import needs [folder] + [filename] (PC) or [path] (macOS). The Relink using [filenames] only option helps when you’ve imported a text file with paths that don’t exist on this machine — e.g., something pulled off the BOOM Library site or shared from another rig.

Exporting

  • Exports .tsv, .csv, or .txt — tab, comma, or semicolon delimited.
  • Choose between current search results or the entire database.
  • Three field-set options to control what gets exported.
  • Include Mandatory Fields ensures the export will round-trip cleanly back into basehead after editing.
Use .tsv when possible — it’s less prone to delimiter conflicts than CSV.

Burn-In Metadata F6

Burns database values back into the metadata of the actual source files.

You only need this in two cases:
  1. Right after importing a text file with the F7 panel.
  2. When you’ve enabled Disable File Writing on the UCS / Chunks Options page (so edits live in the database only) and now want the files updated to match.
Burn-In panel

Features

  • Three options for which records to burn — all selected, changed only, or all with files attached.
  • Multiple chunk choices to pick which metadata gets updated.
  • Use with Changed Records Only enabled to sync only DB-side edits back to the files.

To find what’s out of sync, use Database › Show UnBurnt Records.

FAQ

How do I import a database from a rival program?

From the rival app, choose Dump Search Query as Text File (or equivalent). Make sure the dump includes [FilePath] and [RecID] — both should be there by default. Open the dump in basehead’s Import panel and it should auto-detect the format.

How do I import from Netmix?

Export the text file from Netmix with [Path] and [FileID] included. Import the file into basehead and it’ll auto-map the fields against files in the current database.