SUPPORT
SOMETHING
NOT RIGHT?
SAY SO.
One person makes REK., so you get a reply from the person who wrote the code. Most problems below have an answer already. If yours does not, write in.
Get in touch
Expect a reply within a few days. There is no ticket system, no chatbot and no queue position.
What to include
The more of this you send, the faster it gets fixed. None of it is required.
- Your iPhone model and iOS version
- The REK. version, from the SYSTEM screen
- The audio interface, if one was connected, and how it was powered
- The sample rate and route you were recording at
- What you did, what you expected, and what happened instead
- Whether it happens every time or only sometimes
Please do not send recordings unless asked. They are yours, and they are usually large.
Common situations
My USB-C interface does not appear as an input
REK. takes class-compliant USB-C interfaces as ordinary inputs, at 44.1, 48 or 96 kHz. If yours is not listed, check that it is class-compliant rather than driver-dependent, that the cable carries data and not only power, and that the interface has enough power of its own — bus-powered units on a phone are the usual culprit. A powered hub often settles it.
I think I recorded too hot
You almost certainly did not lose anything. The record path is 32-bit float by default, so there is no clipping ceiling on the way in. GAIN sets what you monitor, not what is written. The PK lamp latches so that you know a peak happened, and it holds until you clear it.
The app closed in the middle of a take
A failed write keeps the take. The audio already committed to disk stays on disk, and the take appears in the library named for when it started. If a take is missing after a crash, write in and say roughly when it was recorded.
I ran out of storage
Low storage warns rather than refuses. REK. tells you before the room runs out instead of stopping a pass without explanation. Export what you need, then clear takes from the library.
I cannot find my recordings
They are in Files.app, on the phone, named for when they happened. The files themselves are the source of truth rather than a database, so anything you can see in Files.app is the real take. Sidecars repair themselves if one goes missing.
Playback sounds slower or faster than the recording
Check the varispeed fader. It runs ×0.50 to ×1.50 and is moved by hand, so it stays where you left it. Master OUTPUT applies makeup to the playback path only — whatever it is set to, the file on disk is untouched.
I cannot hear myself while recording
Monitoring has AUTO, ON and OFF. AUTO deliberately steps aside for playback, so if you are hearing a take back rather than the live input, that is the mode doing its job. Set it to ON if you want the input at all times.
The exported file is not the level I expected
Normalize to −0.1 dBFS exists and is switched off by default, so an ordinary export is a bit-exact copy of the take. If a file is quieter than you assumed it would be, that is the bit-exact copy behaving correctly. Turn normalize on if you want the louder version.
I use VoiceOver
VoiceOver is supported throughout, and LCD content honours Dynamic Type. The deck itself is deliberately fixed so that controls stay where your thumb learned them. If a control reads badly or is unreachable, that is a bug worth reporting — please say which control and what it announced.
Things REK. does not do
These are decisions rather than gaps, so support cannot switch them on. They are here so that you know quickly whether REK. is the wrong tool for what you are doing.
- No overdubbing or layering. A pass always makes a new take — that is the whole model.
- No stems and no MP3. Export is WAV, AIFF or AAC, and WAV follows the take’s own depth.
- No iPad and no Android build. It is an iPhone app, sized for one hand and one thumb.
- No cloud, no sync and no account, so there is nothing to restore and nothing to sign in to.
- The deck layout is fixed and not user-arrangeable.
Bugs, ideas and refunds
Reporting a bug
Send it to support@rekaudio.app with the details from section 01. A bug that reproduces on demand is worth ten that happened once, so if you find the steps that trigger it, lead with those.
Asking for a feature
Worth sending, and worth reading the list above first. REK. stays small on purpose, so most additions are declined — but the ones that fit the model tend to arrive because somebody wrote in.
Refunds
Purchases go through the App Store, so refunds are handled by Apple rather than by REK. Request one at reportaproblem.apple.com. If the reason is a bug, write in as well — the refund is Apple’s to give, but the bug is ours to fix.
Privacy
REK. collects nothing, sends nothing and has no account system. The privacy policy explains exactly what that means.