Loopy Pro: Create music, your way.
What is Loopy Pro? — Loopy Pro is a powerful, flexible, and intuitive live looper, sampler, clip launcher and DAW for iPhone and iPad. At its core, it allows you to record and layer sounds in real-time to create complex musical arrangements. But it doesn’t stop there—Loopy Pro offers advanced tools to customize your workflow, build dynamic performance setups, and create a seamless connection between instruments, effects, and external gear.
Use it for live looping, sequencing, arranging, mixing, and much more. Whether you're a live performer, a producer, or just experimenting with sound, Loopy Pro helps you take control of your creative process.
Download on the App StoreLoopy Pro is your all-in-one musical toolkit. Try it for free today.
Comments
That’s weird not to have a knob for that I think, no? Can’t even set up modulation at all in the AUv3 currently. This was very clearly not suffficiently beta tested at all….
Can’t select from drop down menus when a key is being held on the internal keyboard, dear god…
agreed, it's weird.
i'm no expert on SID/chiptune but i thought PWM was a core element of it
I’ll bet it’s just because he didn’t think he could squeeze another knob into the UI…
Check out how long the list in the drop down menu is for assigning mod destinations…mega clunky
I haven’t been able to get Osc Sync or Ring Mod working. Anyone? I do feel that Ring Mod should be a knob, surely, too, rather than a button?
I also don’t understand why each OSC has a Sync button - how to set which is master, which is slave?
Dev replied quickly to email:
"I'm aware of the Loopy Pro forum thread. I just signed up there myself and I'm currently waiting for moderator approval before I can interact in the discussion...I already have a fix in the queue for the AUv3 dropdown GUI elements not responding — I reproduced it locally in Loopy Pro and I'm on it. Expect an update soon."
If it's anything like the SID the sync syncs to the previous oscillator, so when enabling sync for osc2 it syncs to osc1, and when enabling sync for osc3 it syncs to osc2, and if sync is set for osc1 it syncs to osc 3.
Interesting, thnx, still can't hear it make any difference at all. As the Ring Mod button beside it also doesn't make any difference, it makes me think something must be broken or missing.
I was planning to chime in here and say that, while confused about Sync heirarchy, I did get different tones when Sync was selected. But I just tried it again and there was no change to tone. Scratching my head here, coulda sworn I got some Sync action before. Will try to recreate it
At least on the SID on the oscillator with SYNC enabled the frequency must be higher than the oscillator it syncs to.
No matter how I set envelopes they seem to cut off at about the same duration. Not seeing expected ADSR behavior. Anyone else? 😎✌🏼
On the SID each oscillator can independently be sent to the filter, I saw something about this in the screenshots of this app.
See above, I found release sometimes making a difference, sometimes not, very inconsistent behaviour
yeah the way the FX knobs are divided (so each knob gets a heading) rather than united under one heading, takes up a lot of space and needs long scroll to find what you want. this definitely coulda been optimised before launch
Yeah but I’ve been tweaking around with everything and shut off VCF but not getting a normal expected ADSR result. Release shows a max of 24 seconds but it actually tops out around 3 seconds no matter how I set the envelopes. I expect the dev will address this once he reviews this thread. It does sound good for the most part.
😎✌🏼
Got mail from him hours ago saying he's waiting for member approval to this site!? (He can't see any comments without it, obviously) I thought that was instant? @wim
Edit: Comments can be seen but not replied to, or write one. He tells me fixes are on the way...
It's not instant because without manual review of new applicants we get overrun by spammers. Response times are usually less than 2-4 hours, but depending on time zones and our availability it can take up to 12 hours.
They're approved now.
it's good!
i'm not disappointed.
Massive thanks for the feedback so far: kind, brutal, and "is-this-a-feature-or-a-bug" flavored alike. All of it noted, nothing lost.
Issue tracker is live.
Bugs, feature requests, and knob-related complaints all welcome. Filing there helps me way more than it sounds.
Quick heads-up: the macOS desktop build is currently sitting in Apple's review queue and should land soon — free update for everyone who already bought the iPadOS version. Universal Purchase, as it should be.
More coming. Thanks for making the first day of bitcrust genuinely fun.
Mirko
@anode_labs welcome to the forum and good luck with the app 👋
Yep, welcome Mirko!
Hi everyone — Mirko here, solo developer of bitcrust. Getting caught up
on this thread today, thanks for the detailed testing.
Short version: 1.0.2 is in Apple's review queue as of today. It
fixes most of what's been reported here, and documents the rest.
In 1.0.2 (submitted 2026-04-24, pending Apple review)
AUv3 dropdowns are dead → fixed. FX slot type, LFO shape, mod
matrix sources/destinations, SETUP MIDI channel, theme selector —
all now anchor where they should in AUv3 hosts. Verified in Loopy
Pro end-to-end. Root cause was a JUCE display-list bug specific to
the iPadOS AUv3 sandbox.
Save-preset / Randomize dialogs opening off-screen → fixed.
sync between the Standalone app and the AUv3 plugin automatically
(App Group shared container). Export via native iOS share sheet.
Drag-drop import. Visible Delete button. Swipe-to-delete on user
presets.
Targeted for 1.0.3 (work starting now)
Audio cutting out when moving a VCO frequency via the on-screen
keyboard (external MIDI controllers are unaffected)
Envelope release knob's upper range not producing the long tails
the UI value suggests
Held-note parameter changes (volume / detune / spread / PW) not
propagating until the note retriggers
Polyphony allocation — slow-release tails dropping, second notes
not behaving polyphonically
Stuck notes
Documentation / UX pass on Osc Sync (the per-VCO Sync buttons need
clearer master/slave telegraphy) and Ring Mod (which is
architecturally tied to the triangle waveform on real SID chips —
will be greyed out when incompatible, docs updated)
PW knob on the VoicePanel so it doesn't require a mod-matrix slot
Public bug tracker
I set up a public GitHub repo for bug reports and roadmap
visibility: https://github.com/anode-audio/bitcrust
The pinned "Known issues" post there is the live status doc — I
update it as fixes land.
Credit
@Pxlhg, @Gavinski, @anickt, @drewinnit, @Samu, and everyone else who
put bitcrust through its paces in the first 24 hours: the coverage
you generated cut the debug surface down massively. Several of the
DSP issues above were narrowed to specific repro paths from
Gavinski's screen recordings alone — would have taken a week without
them.
On the "was this tested?" angle that came up in the thread: honest
answer is the pre-release public beta had essentially zero
engagement, so I went in with far less real-world coverage than I
should have. Should have held release until the feedback surface was
fuller. That's on me, and it's a lesson that sticks for the next
Anode Labs release.
Cheers,
Mirko
Anode Labs · anode-labs.com/bitcrust
Looking forward to seeing this improve , nice turnaround @anode_labs 🙌
Did anyone mention that ‘drawable’ sequencer lanes are fun?
Wondering if there’s any probability hidden in the sequencer as well…
That sounds like a cool feature for an upcoming release. Noted. Tks.
thanks @anode_labs ! good to know you're on the case.
the sequencer is great, it can animate simple sounds into wild places
👀
Someone wrote on the sales thread:
"This sounds like nowhere near the SID"
https://forum.loopypro.com/discussion/comment/1468003/#Comment_1468003
Would anyone with more familiarity with the SID sound like to comment on this claim?
no
https://www.plogue.com/products/chipsynth-c64.html
Which part of "SID style/inspired" is not clear? There's plenty of down-to-the-silicon accurate software emulations out there. Bitcrust is not that, it's a "let's consider the SID architecture as a creative starting point and go from there" kind of thing.
Also, many don't seem to catch the difference between an indie dev, solo project and a full audio company with a licensing budget, a reverse-engineering team, and the legal appetite to ship something that sits very close to the original ROM. Those projects exist — mostly on desktop, mostly in the quiet corners of the C64-IP enforcement map. Which is also pretty much why there is no bit-accurate SID plugin on the iOS App Store today: the App Store doesn't have quiet corners.
Bitcrust is explicitly not that. It's a clean-room DSP written from the public MOS 6581 register map and general DSP literature — the SID architecture (three osc per voice, ring mod, hard sync, PWM, the filter shape), minus the ROM, minus the legal risk. It won't nail the exact grit of a specific 1982 wafer, and that was never the goal. The SID is the blueprint, not the target.
If someone wants the exact sound of a working C64, the options are running a real 6581/6582 chip in hardware, or a desktop emulator that can afford to live in the license gray zone. Bitcrust is neither — and honestly, I didn't set out to build either.