Support

Help & FAQ.

Quick answers to the questions we hear most often. If yours isn't here, email ose@outhentic.eu - we read everything.

Permissions & the microphone

OSE only asks for a permission when a feature needs it, and everything is processed on your device - nothing you record or play is ever uploaded or shared, and there's no account or tracking. The microphone is used only to detect pitch in the Tuner and to record the audio you choose to capture; deny it and the rest of the app still works. For the full list - Bluetooth, media/storage, notifications and the legacy location-for-Bluetooth-scan gate (Android 11 and below only) - and the exact purpose of each, see the Privacy Policy.

Troubleshooting checklist

When something isn't working, walk this list top-to-bottom. It catches the majority of issues in under a minute.

No signal on Tuner / Meters / Audio

  1. Open Settings → Audio. Confirm the input device matches what you've got plugged in.
  2. If using a USB interface, the channel chooser sits inside the same sheet - pick the channel your microphone or instrument is connected to.
  3. Open the Meters module. If the bars move you've got signal - the issue is downstream.

Crackles or feedback while recording

  1. Turn MONITOR off - feedback into the same chain you're printing causes runaway loops.
  2. Lower the system output level; some devices distort their own loopback past -6 dB.
  3. If using USB, check the cable. Bus-powered interfaces sometimes brown out under heavy DSP.

USB device disappears mid-session

  1. OSE recovers automatically through Android's audio device callbacks; give it a couple of seconds.
  2. If it still doesn't reappear, unplug and replug the device. The picker re-populates on hotplug.

Edits aren't saving

  1. Audio edits are virtual until you Bounce. Tap the Bounce button in the Audio Editor to commit.
  2. If a take seems lost, the original is still in the take's stash - Revert restores it.

Still stuck?

A short message, even just a screenshot, helps us help you. Bug reports go straight to the team that builds OSE.

Email us →