FM-1: a bank with a performance plan

Design the palette before filling the memory

An eight-slot bank can feel spacious if each sound has a distinct function. It can feel cramped when every slot contains a long version of the same texture. Start with a performance plan written in ordinary language: a dry pulse, a low body, an unstable accent, a breath, a scrape, a sustained colour, a transition and a silence with character. These are roles, not mandatory instrument types.

Record or gather material you have permission to use, then audition it at a comfortable matched level. Choose sounds that remain different when the room is noisy and the arrangement is busy. A delicate high-frequency detail may be wonderful alone yet disappear beside a dense FM voice. Keep it if you can give it space; otherwise shorten the collection rather than forcing every interesting recording into this particular set.

Separate the things that need saving

FM1 Open V14 documents eight sample slots sharing roughly 19.55 seconds for new sample storage. Project files do not include sample audio. Its independent DX7 voice library is backed up in four groups, A through D. These are separate parts of a recoverable performance, so a project export alone is not the complete set.

The same documentation describes NORMAL and PLAY track roles. PLAY can retain a timbre and held notes across project changes, but its timbre edits are not saved with projects; they need their own export or an appropriate voice-library save. That distinction makes a useful sustained bridge possible, but also makes an unsaved rehearsal change easy to lose.

Make a folder for one version of the set. Put project exports, sample-bank backup, voice exports and a brief routing note inside it. Include the installed firmware identity. Use a new folder for the next substantial revision. The point is not elaborate administration: it is being able to return to a particular musical state after a successful experiment.

Spend seconds where they matter

Trim a sound according to its role. A dry strike needs a clear beginning and enough decay to retain its character. A noisy transition might need a longer arc. A sustained texture may be better generated by the synth than stored as several seconds of almost unchanged audio. Listen to the seam whenever you shorten a sound; memory saved by an ugly edit is not free.

Avoid automatically normalising every file to the same peak. Peak equality does not guarantee equal perceived loudness, and an intentionally quiet texture can lose its place in the arrangement if pushed forward. Instead, compare the sounds in a short test pattern at the levels you expect to use. Keep some headroom for combinations. Mark one sound as the level reference and revisit it when the rest of the bank changes.

Give filenames a useful order and a musical purpose. Write a tiny map showing what each slot does and which project depends on it. Changing a sample bank can alter the meaning of an existing pattern even when the notes stay the same. Treat that as a deliberate composition technique only when you have preserved the previous bank and know which version you are hearing.

Rehearse the project boundary

Choose one sound to carry across a transition. Hold a simple note or interval and move to the next project using the documented track-role behaviour. Listen for whether the bridge actually belongs to both sections. A sustained sound is not automatically a good transition; its register, harmony and brightness can make the incoming rhythm feel either inevitable or awkward.

Now practise the opposite transition: release the bridge completely, leave a measured gap, then enter the new material. Compare the two recordings. Silence often explains a structural change more clearly than a long effect tail. Keep whichever version serves the piece, not whichever demonstrates more firmware features.

Finally, perform the whole sequence from a fresh start using your saved files and written map. Check that samples, voices and routing match the rehearsal. Do not infer recovery from seeing filenames in a folder: verify the process on copies before a performance. Firmware switching and project-format compatibility are separate questions. A carefully designed bank becomes an instrument only when its sound, controls and saved state agree.