StretchwiseMoving from TuneLab or Entropy Piano Tuner
Stretchwise reads the files other tuning apps save, so you don't start each piano from nothing. It builds its own stretch curve from each piano's inharmonicity, so the most useful thing to bring over is your measurements. Another app's finished curve isn't imported.
Where to import
Tap the piano bar at the top of the tuning screen. In the list of pianos, expand Import & backup and tap Import a tuning file…, then choose the file from Files, iCloud Drive or another storage app. Stretchwise names each new piano after the piano name inside the file, or after the file name if there isn't one. It selects the new piano when the import finishes.
From TuneLab
Tuning files (.tun)
Imported:
- The inharmonicity readings, which Stretchwise uses to build the piano's stretch curve.
- Your custom per-note offsets, as per-note corrections you can change later under Tuning target.
- The file's pitch offset, as the piano's reference pitch.
- The stretch setting: 8:4/4:1 becomes Average, 8:4/4:2 becomes Expanded, and 4:2/2:1 becomes Clean. Any other setting becomes Average, and the import message says so.
Not imported: TuneLab's own stretch offsets, because Stretchwise calculates its own curve, and the template and interval settings. A .tun file doesn't contain pitches, so play each note once to record its pitch. A note you measure in Stretchwise uses its new inharmonicity reading in place of the imported one.
Temperament files (.tem)
Select the piano first: a temperament is applied to the piano that's selected, and no new piano is created. The file needs all twelve notes, C to B. If it matches one of Stretchwise's built-in temperaments within 0.1 cent, that temperament is used. Otherwise it's saved as a custom temperament named after the file.
From Entropy Piano Tuner
Entropy files (.ept) bring the piano's name, its concert pitch, and the recorded frequency and measured inharmonicity of each recorded key. Keys with no recording are left for you to measure. Entropy's calculated and tuned frequencies aren't read.
Entropy CSV exports also work. Keys with a recorded frequency of 0 Hz count as not measured.
From anything else: a table of notes
If your app or spreadsheet can save a table of notes, export it as CSV (comma, semicolon or tab separated) and import that. Each row needs:
- A note name, such as A4, Bb0 or C♯5, or a key number from 1 to 88.
- A pitch, as a frequency in Hz or as cents from equal temperament.
- Optionally, an inharmonicity value and a correction in cents.
Headings such as Note, Key, Hz, Frequency, Cents, Offset and Inharmonicity are recognised in any capitalisation. Files without headings work if the note comes first. Stretchwise skips rows more than 100 cents from their note. It also accepts inharmonicity shown ×1000, as TuneLab displays it, and converts it.
Not supported
Verituner, CyberTuner and PianoMeter files can't be imported. Their formats aren't published, so Stretchwise can't read them reliably. If one of these apps can export a table of notes, try importing that table.
After an import
The message tells you how many notes came in and whether anything was changed on the way, such as a stretch setting. It also lists up to three skipped lines with the reason, for example "more than 100 cents from the note". If nothing usable is found, nothing is imported.
To keep a copy of everything, use Back up all pianos… in the same section. Importing a backup on another device adds its pianos and replaces a piano only with a newer copy.
Before you rely on it
On the recordings we have tested, Stretchwise's curve comes within 0.9 to 1.7 cents rms of TuneLab's. That hasn't yet been confirmed on real pianos in the field. Check a few notes you know well the first time you tune a piano you've imported. If an import doesn't look right, email support@tempore.net. Please send the file only if you're happy to share it.