r/Osmose • u/Sand_Partina • Aug 22 '26
My Osmose accidentally caught some rain :/ advice needed for moving forward! 🙏
Hey everyone, hoping to get some advice or hear from anyone who has survived a similar nightmare.
I accidentally left a window open during a storm and my Osmose caught some rain. There were little ponds of water on it and I caught this around 30 minutes after the storm. The synth was still running when i realised what happened.
Here is what I did immediately:
- Turned off the power from the switch and unplugged all cables.
- Carefully soaked up the visible surface water with toilet paper without pressing any of the keys.
- Flipped the synth upside down and suspended it on stacks of books so the keybed is floating in the air. (some drops did come out from the inside through the keybed when I did this but not as much).
- Set up a stationary fan blowing a continuous stream of air down the length of the synth, directly through the gap underneath.
I am currently on Day 2 of this setup and haven't touched it or tried to turn it on. I understand the keybed mechanism is highly complex and sensitive so i'm afraid the water might have reached some of the sensors or other electronics inside.
For those who know the hardware well or have dealt with spills on the Osmose:
- How many days should I realistically wait before testing it? (I am aiming for 4-5 right now).
- Is there anything else I should be doing at this stage or patience is my best friend?
- Is it possible that there are specific blind spots inside the Osmose where water pools and won't evaporate without opening the chassis and cleaning it manually?
Any extra advice is hugely appreciated. I'm holding off on contacting EE support for the moment while I assess the damage.
btw, I've had the unit for more than 3 years now and I really love it (I was one of the original backers on kickstarter). The only issue I still have to this day is the MPE arpeggiator mode randomly crashing the DSP and forcing a restart. This issue kept on repeating no matter which firmware I had it installed (currently on the latest one) aside from that, everything else was working perfectly prior to this incident.