No sound even though the piano is connected? Or does the sound come noticeably after the key press? Both usually have a simple, harmless cause.
Start with a player action in the browser
Browsers may only start audio after a deliberate interaction. Tap "Play through only" or the selected practice start button. If the system suspends the audio context later, another interaction may be needed — Klavissimo does not promise that one unlock lasts for the rest of the session.
Check volume and output
Check Volume under ⚙ → Sound → Piano in the player: at 0 %, the app’s piano sound is muted. Also check the system volume and whether headphones, speakers or AirPlay are connected as the output. The iPhone/iPad app is configured so play-through should remain audible with the silent switch on; if it still stays silent, use the visible restart in the next step.
Use "Restart audio"
If the player measures no sound at the shared audio output or start-up fails, it shows "Audio couldn't be started." or "The play-through stayed silent — no sound came through." Tap "Start audio again". The action rebuilds the audio path; it only reports after a new start has been attempted.
Bluetooth headphones add latency
Headphones or speakers connected over Bluetooth transmit sound with a noticeable, physically caused delay — that can't be configured away. For exact timing while practising, only a cable helps: wired headphones or speakers on the device.
Sounds load in shortly after
Right after starting a piece, the first few notes can briefly sound simpler while Klavissimo loads the actual sounds in the background — piano samples, or SoundFonts for ensemble voices. It settles by itself once loading finishes.
Good to know:
Bluetooth latency isn't a Klavissimo problem, it's physics: every Bluetooth connection takes time to transmit. It affects every music app equally.
Your data:
If the problem is reproducible, open "Instrument check" and then "Technical state →". "Copy state" only puts the report on your clipboard; nothing is sent automatically.