Getting Piano to actually work when everything else on your system is fine
I've been dealing with Piano for about four years now, mostly in studio environments where the software is supposed to just run and nobody wants to learn the internals. The frustrating thing is that half the time the issue isn't Piano itself but the environment around it. Before you dig into any configuration files, check your sample rate mismatch. That was the thing that ate my afternoon last Tuesday — I had Piano set to 48kHz but my interface was locked at 44.1kHz, and the only symptom was these tiny clicks every 30 seconds that looked completely random. Once I matched the rates, the whole problem went away. It doesn't even crash, which is why people miss it. Start with the basics, which means checking whether the application can see your audio hardware at all. Open Piano and go to the preferences menu under Edit or the app menu depending on your OS. Look for the Audio or I/O section. If your interface isn't showing up, it's almost always a driver issue, not a Piano issue. Update your ASIO drivers on Windows — the generic ones Microsoft ships will not cut it. On Mac, make sure your interface is selected in Audio MIDI Setup before you even launch the program. I've lost count of the times someone calls me because Piano won't open their project, and the real problem was that their interface had gone to sleep and macOS had dropped it from the active audio device list. The next layer is CPU load. Piano is fairly efficient, but it will choke if you have too many instances running simultaneously or if you're loading huge sample libraries without enough RAM allocated. Watch your CPU meter. If it's consistently above 80% while playing, you'll get dropouts and clicks. The workaround is usually to freeze tracks or consolidate instruments rather than trying to optimize individual settings. There's a myth that you should increase the buffer size — and yes, that helps, but it also increases latency to the point where recording becomes unusable. A buffer of 256 samples is usually the sweet spot for most work. Go higher only if you're just mixing and don't need to play anything back in real time.
Projects failing to save is another common headache, and it's rarely about the software. Check your permissions. On Windows, this shows up as access denied when you try to save to a network drive or a folder owned by another user account. On Mac, it's usually a sandbox issue where Piano doesn't have full disk access. Go to System Settings and grant it there. I hit this exact problem in March when I was working on a client's MacBook and couldn't figure out why my saves were silently failing. The project appeared to save fine — no error message, nothing — but the file on disk hadn't changed at all. Full disk access fixed it immediately. LATENCY issues often get blamed on Piano when the real culprit is USB power management. Modern laptops and some motherboards will throttle USB ports to save power, and that directly affects audio interface performance. On Windows, go into Device Manager, find your audio interface under Sound, video and game controllers, open Properties, and turn off Allow the computer to turn off this device to save power. On Mac, this is less of an issue unless you're running on battery. Plug in. Always. One thing nobody tells you about troubleshooting Piano: MIDI routing is often the hidden problem. If your keyboard plays notes but they trigger the wrong instrument or nothing at all, check the MIDI input assignment inside Piano first, not on your keyboard. I spent an entire evening chasing a phantom problem with a Behringer controller only to discover that Piano had its MIDI input set to the wrong port. The keyboard was fine the whole time. Check the I/O setup in Piano before you do anything else with your MIDI gear.
When nothing in this guide fixes your problem
There are scenarios where Piano simply won't run on your hardware, and no amount of tweaking will change that. Older Intel Macs with integrated graphics struggle with the UI rendering, especially when using multiple monitors. You'll notice frame drops in the piano roll and sluggish playback. The only real fix here is disabling hardware acceleration in preferences, which trades rendering smoothness for stability. It's not ideal, but it keeps the software usable. Another limitation worth knowing: Piano doesn't handle large numbers of automation points gracefully. If you've got a project with thousands of volume and pan moves across dozens of tracks, the timeline will lag during playback. This isn't a bug, it's an architectural constraint. The workaround is to bounce automation to audio where possible, or use the simplified timeline view when editing massive sessions. I keep a habit of consolidating automation after each session for this reason. It saves a lot of frustration later. If you've gone through all of this and Piano still won't start, try deleting the preferences file. On Windows it's usually in AppData\Roaming\Piano, and on Mac it's in Library/Application Support. A corrupted preferences file will cause silent crashes on launch with no error message, which is one of the most annoying failure modes in any DAW. I learned this the hard way when my Piano kept crashing every time I opened it after a minor update. Resetting preferences brought it back to life immediately.
Get the Full Details
There are also third-party plugin conflicts that can break Piano entirely. If you recently installed a new VST or AU plugin and Piano started acting strange, that's the first place to look. Move your plugins folder temporarily and see if stability returns. This takes a few minutes and rules out a whole category of problems before you go digging elsewhere. I don't have a download link to share here because I'm writing from experience, not promoting anything. If you need the software, go to the official Piano website and download the latest stable release. The beta versions often introduce the exact bugs this guide is trying to work around. Stay on stable until you have a specific reason to test something newer. One more practical tip: keep a backup copy of your Piano preferences and your last known good project template. When something breaks, restoring from a known state is faster than diagnosing what went wrong, and in a professional setting, time is money. I keep a folder called Piano_Backup that I snapshot once a month. It's saved me more than once when an update broke my entire setup.
Edge cases that don't make it into any manual
Using Piano with a USB-C to USB-A adapter on Windows can cause intermittent audio dropouts. The adapter introduces a slight resistance change that the interface interprets as a connection loss. It happens sporadically, which makes it nearly impossible to reproduce in a controlled way. The fix is either a direct USB-C connection or a powered USB hub. Don't skip this detail — it's the kind of thing that makes people think their software is broken when it's actually a $3 adapter. Another one I ran into recently: Piano's built-in reverb and effects will occasionally cause a CPU spike on the first playthrough of a project, then settle down. This is because the effects allocate resources lazily. If you're doing a quick mix pass and wonder why the first bar sounds worse than the rest, it's not your ears. It's the effects catching up. Let it play for 30 seconds and the performance normalizes. The bottom line is that Piano is generally stable, but the things that go wrong tend to be environmental rather than software-level. Driver conflicts, permission issues, and hardware mismatches dominate the problem space. Start there before assuming the application itself is the bottleneck. Most of the time it isn't.
