Import a native .tff, name and colour the channels, set the HPF and the gate and comp switches, and export a copy the offline editor opens. The preview names every field load·in writes and every field the desk keeps.
.tff is the project file the offline 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.
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.
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.
An offline editor 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.
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 need an internet connection. Native files are free for every desk; Live adds the smart translations.