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 Store

Loopy Pro is your all-in-one musical toolkit. Try it for free today.

bitcrust by Michele Caserta (Released)

1246

Comments

  • justaglovejustaglove

    pompousness should be met with rudeness, in my opinion.

  • catboxcatbox

    @justaglove said:

    @anode_labs said:
    @justaglove: I don't owe anyone a performance contract on a forum reply from an anonymous account. The optimisations are on my list, as I said. The hectoring isn't going to move them up it.

    I don't care about your list lol. Nobody is asking for a contract, but we will tell you when your shit is lackluster and is acting irregular compared to what we expect. You tried to state it was because of old hardware, it's not, it's because of the shit you're serving.

    Please ease it with the “we” here. You are only talking for yourself, and frankly stepping quite over the line of what is ok in your hounding of the dev here, no matter your oppinion on the app in question.

  • justaglovejustaglove

    @catbox said:

    @justaglove said:

    @anode_labs said:
    @justaglove: I don't owe anyone a performance contract on a forum reply from an anonymous account. The optimisations are on my list, as I said. The hectoring isn't going to move them up it.

    I don't care about your list lol. Nobody is asking for a contract, but we will tell you when your shit is lackluster and is acting irregular compared to what we expect. You tried to state it was because of old hardware, it's not, it's because of the shit you're serving.

    Please ease it with the “we” here. You are only talking for yourself, and frankly stepping quite over the line of what is ok in your hounding of the dev here, no matter your oppinion on the app in question.

    I'm not hounding the dev, I'm just looking at what is being presented by them and how they're acting in replies. I have not made personal attacks, requests for them, or anything of the sort. If you want to coddle incompetence, go for it.

  • thesoundtestroomthesoundtestroom

    @justaglove Please do not take that attitude with anyone, it’s aggressive and unproductive.

  • wimwim
    edited April 26

    Ugh. I just came home to all this. I second what Doug says. That kind of aggressiveness is totally out of line for this forum. Enough for a ban if it happens again, @justaglove.

    Sorry @anode_labs. That isn't the way "we" like to treat anyone around here.

  • lasselulasselu

    @wim said:
    Ugh. I just came home to all this. I second what Doug says. That kind of aggressiveness is totally out of line for this forum. Enough for a ban if it happens again, @justaglove.

    Sorry @anode_labs. That isn't the way "we" like to treat anyone around here.

    +1

  • anode_labsanode_labs

    Thanks everyone for stepping in on the gratouitous hate. I can see this is a nice place. I am myself a big fan of Loopy Pro. I find it an incredible piece of software and, again, this community is surprising me with constructive feedback. You all have been invaluable. I can stand the random, anonymous internet forum bully, no worries :smiley:

    Today I woke up to v1.0.3 for ipad hitting the app store and reaching #3 in the Music category charts, above some big names I revere and can only look up to. That was a huge surprise. So, again, thanks everyone. I hope you are making some great music, or even just having fun tickling the virtual ivories/strings.

    I was thinking we live in a world where beauty and music are more important than ever and, if my little experiment in dsp and juce programming can bring a little enjoyment to even a single person, that'd be more than enough for me.

    And, as always, please modulate responsibly :wink:

  • GavinskiGavinski

    @anode_labs said:
    Thanks everyone for stepping in on the gratouitous hate. I can see this is a nice place. I am myself a big fan of Loopy Pro. I find it an incredible piece of software and, again, this community is surprising me with constructive feedback. You all have been invaluable. I can stand the random, anonymous internet forum bully, no worries :smiley:

    Today I woke up to v1.0.3 for ipad hitting the app store and reaching #3 in the Music category charts, above some big names I revere and can only look up to. That was a huge surprise. So, again, thanks everyone. I hope you are making some great music, or even just having fun tickling the virtual ivories/strings.

    I was thinking we live in a world where beauty and music are more important than ever and, if my little experiment in dsp and juce programming can bring a little enjoyment to even a single person, that'd be more than enough for me.

    And, as always, please modulate responsibly :wink:

    Just read the update notes, looks good. I’m keen to check out how Osc Sync sounds now, and thanks for the shoutout on the store release notes. I always appreciate that

  • GavinskiGavinski

    Suggestion btw: add something, a little dot or something, to buttons which respond to long presses, like Sync and Ringmod - otherwise users have no idea, from the UI, that a long presses will do something.

  • GavinskiGavinski

    @Gavinski said:
    Suggestion btw: add something, a little dot or something, to buttons which respond to long presses, like Sync and Ringmod - otherwise users have no idea, from the UI, that a long presses will do something.

    i still don’t properly get the way Osc Sync works here when set to ‘Internal’. On that setting, it doesn’t seem to respond to freq changes on the other 2 oscillators - so what is it syncing to exactly?

  • anode_labsanode_labs

    @Gavinski said:

    @Gavinski said:
    Suggestion btw: add something, a little dot or something, to buttons which respond to long presses, like Sync and Ringmod - otherwise users have no idea, from the UI, that a long presses will do something.

    i still don’t properly get the way Osc Sync works here when set to ‘Internal’. On that setting, it doesn’t seem to respond to freq changes on the other 2 oscillators - so what is it syncing to exactly?

    Yeah, Internal sync works like this: this VCO is syncing to a hidden shadow oscillator running at (this VCO's own frequency × Sync Ratio). Default ratio is 1.5×. When SYNC is on and the mode is Internal, the VCO's phase resets every time that shadow's master phase wraps. The shadow only knows about this VCO's own frequency, so the other two VCOs are intentionally irrelevant.

    That's why changing freq on VCO 2 or VCO 3 does nothing in Internal mode. It's self-sync; the master reference is derived from this same oscillator's frequency register, not from a sibling.

    If you want the classic envelope-driven hard-sync sweep (where modulating the master pitch gives you the rising sync tone), set the sync source to "VCO 2" or "VCO 3" instead. In those modes the slave's master ratio scales with the chosen source's actual frequency, so an LFO or envelope on the source VCO's coarse tune sweeps the slave audibly.

    What does change the sound in Internal mode: the Sync Ratio knob (sets the harmonic relationship, try 2.0 / 3.0 / 1.333) and Sync Detune (-100 to +100 cents on the shadow, gives chorus-y beating). Both are routable as mod destinations, so you can get a sweep by automating the ratio with an envelope, just driven by the ratio rather than by a sibling VCO's pitch.

    TL;DR: Internal is ratio-locked. For the classic "sweep the master" sound, switch sync source to VCO 2 or 3.

    Suggestion btw: add something, a little dot or something, to buttons which respond to long presses, like Sync and Ringmod - otherwise users have no idea, from the UI, that a long presses will do something.

    Great suggestion, noted, thanks.

  • GavinskiGavinski
    edited April 26

    @anode_labs said:

    @Gavinski said:

    @Gavinski said:
    Suggestion btw: add something, a little dot or something, to buttons which respond to long presses, like Sync and Ringmod - otherwise users have no idea, from the UI, that a long presses will do something.

    i still don’t properly get the way Osc Sync works here when set to ‘Internal’. On that setting, it doesn’t seem to respond to freq changes on the other 2 oscillators - so what is it syncing to exactly?

    Yeah, Internal sync works like this: this VCO is syncing to a hidden shadow oscillator running at (this VCO's own frequency × Sync Ratio). Default ratio is 1.5×. When SYNC is on and the mode is Internal, the VCO's phase resets every time that shadow's master phase wraps. The shadow only knows about this VCO's own frequency, so the other two VCOs are intentionally irrelevant.

    That's why changing freq on VCO 2 or VCO 3 does nothing in Internal mode. It's self-sync; the master reference is derived from this same oscillator's frequency register, not from a sibling.

    If you want the classic envelope-driven hard-sync sweep (where modulating the master pitch gives you the rising sync tone), set the sync source to "VCO 2" or "VCO 3" instead. In those modes the slave's master ratio scales with the chosen source's actual frequency, so an LFO or envelope on the source VCO's coarse tune sweeps the slave audibly.

    What does change the sound in Internal mode: the Sync Ratio knob (sets the harmonic relationship, try 2.0 / 3.0 / 1.333) and Sync Detune (-100 to +100 cents on the shadow, gives chorus-y beating). Both are routable as mod destinations, so you can get a sweep by automating the ratio with an envelope, just driven by the ratio rather than by a sibling VCO's pitch.

    TL;DR: Internal is ratio-locked. For the classic "sweep the master" sound, switch sync source to VCO 2 or 3.

    Suggestion btw: add something, a little dot or something, to buttons which respond to long presses, like Sync and Ringmod - otherwise users have no idea, from the UI, that a long presses will do something.

    Great suggestion, noted, thanks.

    Got ya. Filter is very clicky at high res and medium to low cutoff - sent you vid
    Edit: it’s clicky at lower cutoff settings on any Resonance setting actually, surely not supposed to be like that, something is broken I think
    Edit: the filter, for some reason, is not acting on the click that’s there when attack is 0 or low, that seems to be the problem. I dunno if this is modeled on the original chip?
    Edit: no, definitely something broken, even going through factory presets, the ones with short attack times are all very clicky sounding.

  • GavinskiGavinski
    edited April 26

    Reset preset to default state button would be useful, as, when you’re on Init and make some changes, pressing Init again doesn’t have any effect. Also, really not ideal to have to scroll to bottom of preset list every time you want to init a patch! Maybe having an init button at the top would also be good

  • PxlhgPxlhg

    VCO on/off (green dot) still unresponsive and so is the filter as far as I can make out of it.

    Having some fun with the global random, crazy sounds! :)

  • GavinskiGavinski

    @Pxlhg said:
    VCO on/off (green dot) still unresponsive and so is the filter as far as I can make out of it.

    Having some fun with the global random, crazy sounds! :)

    Changing filter settings won't do anything unless VCF button is Al's toggled on under audible oscillators

  • rototomrototom

    is it possible to have the chosen color theme beeing persistent?
    now it always falls back to the default one after a reload.

  • anode_labsanode_labs

    macOS beta is up while the App Store version goes through review.

    https://github.com/anode-audio/bitcrust/releases/tag/v1.0.3.680-beta

    One zip, three formats (Standalone .app, VST3, AU). README in the bundle covers install paths and the unsigned-build first-launch trick (xattr -dr com.apple.quarantine /Applications/bitcrust.app and similar for the plugins.

    New since 1.0.3: the Standalone has an integrated MIDI player. 🎼 toggle in the lower-right footer opens a popover with transport, scrubber, file picker, and a one-click "sync to standalone BPM" toggle. Bundles eight Bach Well-Tempered Clavier prelude/fugue pairs (BWV 846, 849, 870, 873) so it works out of the box for poking at presets without digging up MIDI files. The on-screen keyboard at the bottom of the editor lights up in time with the played notes, so you can see what's happening even when you're auditioning across patches at speed.

    Plugin builds (VST3/AU) intentionally don't carry the player. Drag a .mid onto an instrument track in your DAW like you would for any other synth.

    Known stuff in this build that I'd love eyes on:

    Bug reports go in https://github.com/anode-audio/bitcrust/issues. Useful to include macOS version, DAW, format, and steps. Audio capture if the bug is audible.

    Thanks to everyone who's been testing the App Store build and pushing things back.

  • anode_labsanode_labs

    @rototom said:
    is it possible to have the chosen color theme beeing persistent?
    now it always falls back to the default one after a reload.

    That sounds like a bug. It's supposed to stay persistent across reloads. Noted, thanks.

  • anode_labsanode_labs

    @Pxlhg said:
    VCO on/off (green dot) still unresponsive and so is the filter as far as I can make out of it.

    Having some fun with the global random, crazy sounds! :)

    Those green dots aren't buttons, they're voice-activity LEDs. They light up when that VCO is currently producing sound on at least one held voice, so you can tell at a glance which oscillators are actually contributing to what you're hearing. Same for the filter LED if you mean the one on the VCF panel: lights when audio is passing through.

    To actually mute a VCO, drop its VOL knob to zero. To take a VCO out of the filter path, click its VCF button (per-VCO filter routing toggle, the small one in the VCO panel). And the filter as a whole only audibly does anything if at least one of its modes (LP/BP/HP) is on AND at least one VCO is routed into it via the VCF button.

  • anode_labsanode_labs

    @Gavinski said:

    @Pxlhg said:
    VCO on/off (green dot) still unresponsive and so is the filter as far as I can make out of it.

    Having some fun with the global random, crazy sounds! :)

    Changing filter settings won't do anything unless VCF button is Al's toggled on under audible oscillators

    Yep, exactly that. The global VCF only does anything when (a) at least one of its modes (LP/BP/HP) is on, AND (b) at least one VCO has its per-VCO VCF button toggled on so its signal is actually routed into the filter. If neither is the case the cutoff/resonance knobs spin freely with no audible effect.

    It's the most common "wait, is the filter broken?" trap by a wide margin. There's a Quick Help line on the VCF panel that spells the rule out (hover the section while QuickHelp is open), but it's clearly not enough on its own. Stronger visual cue would help, dimming the filter section when nothing is routed into it, blinking the VCF buttons on the VCO panels, something. I'm open to suggestions here.

  • PxlhgPxlhg

    @anode_labs said:

    @Gavinski said:

    @Pxlhg said:
    VCO on/off (green dot) still unresponsive and so is the filter as far as I can make out of it.

    Having some fun with the global random, crazy sounds! :)

    Changing filter settings won't do anything unless VCF button is Al's toggled on under audible oscillators

    Yep, exactly that. The global VCF only does anything when (a) at least one of its modes (LP/BP/HP) is on, AND (b) at least one VCO has its per-VCO VCF button toggled on so its signal is actually routed into the filter. If neither is the case the cutoff/resonance knobs spin freely with no audible effect.

    It's the most common "wait, is the filter broken?" trap by a wide margin. There's a Quick Help line on the VCF panel that spells the rule out (hover the section while QuickHelp is open), but it's clearly not enough on its own. Stronger visual cue would help, dimming the filter section when nothing is routed into it, blinking the VCF buttons on the VCO panels, something. I'm open to suggestions here.

    Right, thanks! ☺️

  • jwmmakerofmusicjwmmakerofmusic

    Okay, so reading all of the above, I'm a little confused about Bitcrust and what it can do basically, but it's only $2 so...what the hell, why not? 😂 A new plugin to make Ambient with. I bet I can get some good bleeps and bloops out of it and into Koala for frippertronics-styled Ambient.

    Also, welcome @anode_labs ! Always a joy to see new people here (for me at least). :) You seem a good-hearted person, so stick around mate.

  • rototomrototom

    seems the gui is not scaling as it should when hosted in drambo.
    in aum it looks ok.
    ipad a16, 26.2.1

  • anode_labsanode_labs

    bitcrust 1.0.4 went out today. Submitted to App Store review for both iPad and macOS.

    Highlights you'd actually notice:

    • Force-quit on iPad Standalone no longer drops your theme, last preset, nav tab, monitor mode, or keyboard visibility. Pick phosphor, kill the app from the switcher, relaunch, phosphor's still there.
    • INIT button in the header. One tap loads a blank patch. Asks first if you have unsaved changes.
    • The "I clicked VCF on a VCO but the cutoff knob does nothing" trap is unreachable. Enabling a VCO route auto-engages LP if no filter mode is selected, and clicking the only-on mode is a no-op (it stays on instead of swapping to a different mode).
    • SYNC. and RING. (note the trailing dot) signal that those buttons have long-press popovers with Source / Ratio / Detune / Depth controls. The popovers shipped in 1.0.3 but were completely invisible. The dot is the affordance.
    • Confirmation dialogs (Save, Delete, Init, Randomize) now match the active theme instead of looking like a stock JUCE white box parachuting in.
    • Per-VCO peak meter moved out from beside the VOL knob to a horizontal strip directly under the live wave preview. Reads as one paired unit now.
    • Theme switching is roughly 100x faster. The whole one-second freeze was an accidental font reshape on the about-panel licence text.
    • Compact panel layouts kick in at smaller editor heights so you can shrink the window without controls disappearing off the bottom.

    While Apple chews on review, the unsigned macOS direct-download with the Gatekeeper workaround lives on GitHub:
    https://github.com/anode-audio/bitcrust/releases/tag/v1.0.4

    Linux and Windows on Gumroad as usual. Bug reports: https://github.com/anode-audio/bitcrust/issues

    Thanks to everyone in this thread who flagged the routing trap and the long-press discoverability problem. Both got fixed because someone said something.

  • GavinskiGavinski

    @anode_labs said:
    bitcrust 1.0.4 went out today. Submitted to App Store review for both iPad and macOS.

    Highlights you'd actually notice:

    • Force-quit on iPad Standalone no longer drops your theme, last preset, nav tab, monitor mode, or keyboard visibility. Pick phosphor, kill the app from the switcher, relaunch, phosphor's still there.
    • INIT button in the header. One tap loads a blank patch. Asks first if you have unsaved changes.
    • The "I clicked VCF on a VCO but the cutoff knob does nothing" trap is unreachable. Enabling a VCO route auto-engages LP if no filter mode is selected, and clicking the only-on mode is a no-op (it stays on instead of swapping to a different mode).
    • SYNC. and RING. (note the trailing dot) signal that those buttons have long-press popovers with Source / Ratio / Detune / Depth controls. The popovers shipped in 1.0.3 but were completely invisible. The dot is the affordance.
    • Confirmation dialogs (Save, Delete, Init, Randomize) now match the active theme instead of looking like a stock JUCE white box parachuting in.
    • Per-VCO peak meter moved out from beside the VOL knob to a horizontal strip directly under the live wave preview. Reads as one paired unit now.
    • Theme switching is roughly 100x faster. The whole one-second freeze was an accidental font reshape on the about-panel licence text.
    • Compact panel layouts kick in at smaller editor heights so you can shrink the window without controls disappearing off the bottom.

    While Apple chews on review, the unsigned macOS direct-download with the Gatekeeper workaround lives on GitHub:
    https://github.com/anode-audio/bitcrust/releases/tag/v1.0.4

    Linux and Windows on Gumroad as usual. Bug reports: https://github.com/anode-audio/bitcrust/issues

    Thanks to everyone in this thread who flagged the routing trap and the long-press discoverability problem. Both got fixed because someone said something.

    Great. But no mention of fixing the clicking sounds audible in certain synth settings (DC artefacts, you suspected)?

  • anode_labsanode_labs

    @Gavinski said:

    Great. But no mention of fixing the clicking sounds audible in certain synth settings (DC artefacts, you suspected)?

    It’s next on the menu. It’s just me against the clock. In Mexico they say: “o cargo la virgen, o trueno los cuetes”.

  • rototomrototom

    @anode_labs said:

    @Gavinski said:

    Great. But no mention of fixing the clicking sounds audible in certain synth settings (DC artefacts, you suspected)?

    It’s next on the menu. It’s just me against the clock. In Mexico they say: “o cargo la virgen, o trueno los cuetes”.

    may i ask: where is this clicking sound to find?

  • Rob_Jackson_MusicRob_Jackson_Music
    edited April 27

    @timfromtheborder said: I’m also curious as to how much of this is vibe coded

    I didn't see an answer to this, and I'm curious too.

    Getting big Claude Code Vibes though...

    Am I right @anode_labs? I'm not saying that's bad. I'm not saying it's good either. I just think it's good to be open about the use of AI code generation tools.

  • anode_labsanode_labs

    @Rob_Jackson_Music said:

    @timfromtheborder said: I’m also curious as to how much of this is vibe coded

    I didn't see an answer to this, and I'm curious too.

    Getting big Claude Code Vibes though...

    Am I right @anode_labs? I'm not saying that's bad. I'm not saying it's good either. I just think it's good to be open about the use of AI code generation tools.

    I wrote about it here.

  • Rob_Jackson_MusicRob_Jackson_Music

    Thanks for the clarification @anode_labs. So the answer is yes, partly.

    I respect the statement that you review the generated code - It's good to hear you do that.

    Good look with this, and your other projects and may all your bugs be squished. -Rob

Sign In or Register to comment.