Home/Consoles/Yamaha TF
YAMAHA TF1 / TF3 / TF5 / TF-RACK · .TFF · NEW

Your TF project, named and switched from your phone.

Import a native .tff, name and colour the channels, set the HPF and the gate and comp switches, and export a copy the TF Editor opens. The preview names every field load·in writes and every field the desk keeps.

Open load·in See what it won't touch
01 — The format

One project file for four consoles

.tff is the project file the TF Editor and the TF consoles save. TF1, TF3, TF5 and TF-Rack share it, and load·in reads the file's own model tag to say which one it came from. Every export patches the project you imported; a from-scratch export starts from a TF3 factory project and says so in the preview.

File Format
.tff
TF Editor's native project file
Input Channels
40
In the file, on every model
Channel names
8
Characters a TF shows; longer names are cut and the preview says which
02 — What load·in reads

The channel identity and the switches

Import a .tff and load·in pulls channel names, colours, icons, stereo links, HPF on/frequency, the first EQ band's frequency and gain, the gate and comp switches and the fader into the project. Everything else in the file is preserved exactly as the desk saved it.

03 — What load·in writes

Names, colours, links and switches

✓Channel names you edit in the app, cut to the eight characters a TF shows (accents fold to plain letters, and the preview names every cut)
✓Colours and icons where the TF has a matching one; otherwise the channel keeps what the file had
✓Stereo links for pairs you link in the app
✓HPF on and frequency, gate on/off, comp on/off, fader level
—Never written: EQ, LPF, gate and comp values, mix sends, mute, pan, digital gain, 48V, polarity and input patch. The desk keeps its own, and the export says so in its own sentence.
04 — What load·in leaves alone

Your project stays your project

load·in patches only the fields above inside the project you imported. A channel above the file's range is folded down with the move named in the preview, never dropped in silence, and a name the file already carries is left byte for byte when you did not change it.

05 — What load·in won't claim

The honest edges

—No physical TF console has loaded an exported file yet. Every export has been opened in TF Editor V4.5.0, and that is the whole proof so far.
—A stereo link is written; pan is not. The TF Editor pans a pair it links hard left and right, and load·in leaves the pans as the file had them. Check the pair's pan at the desk.
—Only TF3 projects have been captured so far. TF1, TF5 and TF-Rack ride the same container and the same writer; their own files are welcome.
06 — Before the show

Verify it before it's the desk's problem

TF Editor V4.5.0 opened every load·in export without a format or load error, including a no-edit round trip that came back byte for byte. That is editor acceptance. It is not console acceptance, and until a TF console has loaded one of these files the app marks every TF export "verify on your console before show use."

Other Yamaha workflows: CL/QL · DM3 · DM7 · RIVAGE PM · the full list is on the console support page.

Native files for audio consoles. The TF included.

Import your TF project. Name it. Switch it. Export a copy the editor opens.

Try load·in free →

No signup required for local planning. TF console-file import and export require Pro and an internet connection.