Offline Virtual Piano: Computer Keyboard, MIDI, and Audio Setup

An offline virtual piano should still behave like an instrument, not a web page saved for later. After installation, its normal playing path should keep key events, MIDI messages, sample reads, audio rendering, and preferences on the computer. It should also make failures visible: silence caused by a missing audio device is different from silence caused by an unselected MIDI input.

Type Piano is a native standalone piano with three input paths—computer keys, a MIDI controller, and an on-screen A0-C8 keyboard—feeding one performance state and one realtime audio engine. Its complete Community Edition is free. The following checks show how to configure that system and establish exactly what “offline” means.

What works offline, and what does not

Once an official package is installed, playing does not require an account or a cloud performance service. The packaged piano bank is read locally; notes are rendered locally; interface and device preferences are saved locally. Type Piano does not need to upload a performance before you can hear it.

That boundary is deliberately narrow:

Task	Type Piano boundary
Play with computer keys, MIDI, or the screen	Local desktop path
Render the four included instruments	Local audio engine and packaged resources
Save interface, sound, and device preferences	Local settings
Download a package, read online help, or visit the source repository	Requires whatever network access that external task normally needs
Record, sequence, host a plugin, show notation, or provide lessons	Not a Type Piano feature

This distinction matters when comparing an offline virtual piano with a browser piano. “Offline” here describes the installed performance path; it is not a claim that the operating system can install a missing audio or MIDI driver without network access.

Map the computer keyboard before adding hardware

The computer keyboard is the shortest diagnostic path because it removes the MIDI controller, cable, and driver from the chain. Type Piano maps 29 chromatic notes across two familiar rows:

• The lower run is Z S X D C V G B H N J M.
• The upper run continues with Q 2 W 3 E R 5 T 6 Y 7 U I 9 O 0 P.

At the default octave, Z is C4, Q is C5, I is C6, and P is E6. Changing the octave moves the mapping while the on-screen instrument remains the full 88-key A0-C8 reference. The displayed key hints are authoritative if a saved octave differs from the default.

A typing keyboard does not report how hard a key was struck, so Type Piano applies the velocity selected in the performance controls. Space is a momentary sustain control. The screen distinguishes physically held notes from notes retained by sustain instead of painting both states identically.

Run this first-sound check:

1. Open Type Piano, select Studio Grand, and leave the audio buffer at its stable default while testing.
2. Set one computer-keyboard velocity and play Z, X, and C. At the default octave, that is a C-major triad.
3. Hold Space, release the three note keys, and confirm that the display changes from held notes to sustained notes.
4. Release Space and confirm that the retained notes clear.
5. Move the octave once and repeat. If the visible notes move but no sound follows, investigate the audio path rather than the mapping.

This test also checks focus handling. When the application loses keyboard focus, it releases the computer-keyboard source rather than intentionally leaving those notes held.

Verify a MIDI keyboard without a DAW

Type Piano is MIDI desktop piano software, but it is not a DAW or plugin. A native system MIDI input sends note-on, note-off, note velocity, and sustain-pedal CC64 messages into the same performance model used by computer and pointer input.

Use an evidence-based setup sequence:

1. Connect and power the controller, then confirm that the operating system lists it as a MIDI input.
2. Open Type Piano or refresh its MIDI device list and select that input. A device missing from the operating-system list cannot be repaired by repeatedly selecting it in the application.
3. Play the same note softly and firmly. The sound and visible velocity response should change; this separates real MIDI velocity from the fixed velocity used by typing keys.
4. Press the sustain pedal, release a note, then lift the pedal. If the note stays retained, inspect whether the controller is still sending CC64 down.
5. At the default octave, hold MIDI C4, press and release Z, then release MIDI C4. The shared ownership model should keep the note active until the last input source releases it.

If the device disappears, check the cable, USB port, system MIDI list, and whether another application has exclusive ownership. Refresh or reconnect after changing the physical path. Type Piano exposes disconnected, connecting, connected, and attention states; an empty device list or a connection error is not counted as a successful silent session.

Tune the audio path instead of chasing a latency claim

Low-latency piano performance depends on more than application code. The output device, operating-system driver, sample rate, buffer, competing audio clients, and current system load all contribute. For that reason, Type Piano does not advertise one fixed latency number.

The available buffer choices are 256, 512, 1024, and 2048 frames, with 512 as the fresh-profile default. A smaller buffer can shorten one part of the path but leaves less time to finish each audio block; a larger buffer gives the system more margin at the cost of responsiveness. The engine follows the active device rate, so a frame count alone is not an end-to-end millisecond guarantee.

Use this repeatable audio check:

1. Select the intended output device and begin at 512 frames.
2. Play repeated notes, a sustained chord, and a short glissando while watching the audio and piano-bank status.
3. Switch among Studio Grand, Felt Room, Classic EP, and Glass Piano. This exercises both streamed samples and synthesized voices.
4. If the path is stable but feels slow, try 256 frames and repeat the same passage.
5. If sound breaks up, return to 512 or raise the buffer, then close competing audio clients before changing anything else.

Changing several variables at once hides the cause. Keep the patch, velocity, output device, and test phrase constant while comparing buffers. If both sampled instruments fail but the synthesized instruments play, check the piano-bank readiness rather than blaming MIDI.

Know where the piano sound comes from

Studio Grand and Felt Room use Salamander Grand Piano V3 recordings by Alexander Holm under CC BY 3.0. Type Piano packages a source-attested bank and preserves its attribution notice and legal text. Release checks pin the archive identity and verify the staged bank rather than inferring provenance from a filename.

The two acoustic presentations stream velocity, release, resonance, and pedal material through bounded voices; the application does not copy the entire library into process memory at launch. It also does not silently substitute an unrelated sound while claiming that the verified piano bank is ready.

The other instruments have different synthesis paths. Classic EP is velocity-responsive FM synthesis, and Glass Piano is additive synthesis. Comparing all four at the same velocity and master level avoids mistaking loudness for a different implementation.

Check the current Linux and Windows release boundary

Only files shown on the official Type Piano download page count as public releases. The current public channels are Linux x64 and Windows x64:

• Linux is published as AppImage, DEB, and RPM packages. Choose the format that matches the target system and verify the published checksum before installation.
• Windows is published as an x64 NSIS installer. It is currently unsigned and has no target-host acceptance report. Its checksum verifies the downloaded bytes; it does not prove installation, audio, MIDI, UI, or Windows security acceptance on a particular machine.
• macOS is not a current public channel. Building a file is not equivalent to publishing a signed, notarized, stapled, and natively accepted universal DMG.

That release language is intentionally precise. Package existence, checksum identity, code signing, and native runtime acceptance are separate pieces of evidence.

A practical acceptance checklist

Before relying on Type Piano away from a network connection, complete one local rehearsal:

1. Download the correct package from the official page and verify its checksum.
2. Disconnect from the network after installation.
3. Confirm a computer-keyboard chord, Space sustain, and octave movement.
4. If applicable, confirm MIDI enumeration, soft-versus-loud velocity, and CC64 pedal release.
5. Test the chosen audio output at a stable buffer with both a sampled patch and a synthesized patch.
6. Close and reopen the application to confirm that the intended settings persist.

For controls and troubleshooting detail, use the Type Piano performance guide. Release files and checksums stay on the download page, while issue reporting and public release evidence live in the official Type Piano repository.