The Keyboard Played the Song. The Recording Contained No Sound.
Share
The producer presses play in a Nairobi studio. The notes are there on the screen, neatly lined up, and the keyboard sounded perfectly normal while the musician was playing. But the exported file is silent.
Someone suggests buying a better USB cable. Someone else says the keyboard needs a more expensive interface. Before spending anything, there is a more useful question: did the computer record sound, or did it record instructions?
MIDI and audio can travel through equipment that looks almost identical from the outside, but they are not the same thing. MIDI carries performance information, such as which note was played, when it started, and how strongly the key was struck. Audio carries the sound itself. A MIDI recording is closer to a set of instructions for a musician than a recording of the performance.
That distinction explains why a keyboard can control a software piano without sending its own piano sound into the computer. The software instrument generates the sound. Change that instrument and the same recorded notes can become a different piano, an organ, or a synthesiser. This is useful, not a fault. You can correct a note or change the arrangement without asking the player to repeat the whole take.
Recording the keyboard's own sound is a different job. If the instrument supports USB audio, its documentation should say so explicitly. A USB socket alone does not establish that capability. Other instruments require their audio outputs to feed suitable audio-interface inputs. The connection, input type, and recording settings must match the particular instrument and interface.
This matters when a client chooses a particular keyboard voice for a song. Recording only MIDI may preserve the performance but not capture that exact sound. The session might play correctly while the keyboard is connected, then go quiet when it is removed. A software instrument might also be missing or disabled when the project opens elsewhere.
Start by deciding what needs to survive the session. If you want editable notes and freedom to choose the sound later, MIDI is useful. If you need the sound the musician approved today, capture audio. Sometimes recording both gives you the most flexibility, provided your equipment and software support the routing.
Here is a quick self-audit: open yesterday's keyboard track and identify what is actually stored. Is it a waveform or a sequence of notes? If it is MIDI, identify the device or software instrument producing the sound. Then export a short test and listen to the exported file outside the recording application. Do not wait until the musician has left to discover that the finished file depends on equipment no longer in the room.
When you send a session to another producer, explain which tracks are MIDI and which are audio. Where appropriate, include rendered audio copies of the approved sounds as well as the editable project. That avoids a technically intact project arriving with the wrong piano sound, or none at all.
At Zamar Audio Solutions, the starting point is the sound you need to capture, not the socket that happens to fit. Our studio equipment collection is the next step for matching that recording path to suitable gear. A correct signal chain preserves the performance first and saves the expensive guessing for nobody.