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)

1235

Comments

  • edited April 27

    @Gavinski said:
    I don't think this is the right tone to strike, it's needlessly rude.

    Rude is a point of view. Some of us get to speak the way they want here. While others, through no fault of their own, are forced to ignore their cultural background and speak in a way that is alien to them. If I spoke here the way I was brought up I'd be banned by tomorrow. No offense meant, just, there is another side to every coin.

  • edited April 28

    @rototom said:

    @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?

    It seems to be something to do with short or zero attack, if you even just flick through the factory presets, you'll start to hear that a fair few have clicking. May depend on filter or other settings too, can't remember offhand, but it's clearly audible on many factory presets regardless. (At least, it is in my setup, and dev confirmed there is a bug)

  • edited April 28

    @Ailerom said:

    @Gavinski said:
    I don't think this is the right tone to strike, it's needlessly rude.

    Rude is a point of view. Some of us get to speak the way they want here. While others, through no fault of their own, are forced to ignore their cultural background and speak in a way that is alien to them. If I spoke here the way I was brought up I'd be banned by tomorrow. No offense meant, just, there is another side to every coin.

    I get your point. Like many Irish people, I love cursing. But we all have to adjust how we speak depending on where we are, that's the reality of shared spaces, they all have their own norms. And the tone considered acceptable here is different from, say, Reddit. It's true that that tone will come easier to some than to others.

    But tone is important, let's not pretend otherwise. Text messages are ripe for misinterpretation, especially between strangers and especially when someone's being critical. There's no face to read, no body language, no intonation, there's often vagueness as to what the other's intent might be. So, yeah, I think it's right that we pick our words here more carefully than we might do down the pub with our mates, say.

  • I can understand that sentiment too.

    But it's also impractical for moderators to attempt to interpret things in social context. Out of necessity we do our best to apply the rules the same to everyone. That's difficult enough without trying to adjudicate between different points of view - something we're not willing to do and would never be able to do fairly.

  • In bitcrust the text in the left column is too small and hard to read with plenty of empty space around the current text allowing it to be larger. It’s easier to read with certain color themes but still could be larger overall.

  • cool, thank you for 1.0.4!

    if i could make a wish...
    the popup window for sync and ring should stay open to wiggle knobs while playing the touch keyboard.
    thank you. and please don't drop the virgin.:)

  • Hi there. 1.0.5 with dsp fixes is out, and will soon be shipping to your iPads as soon as apple gets to review it.

    If you have a Mac, get the desktop version for free now. It’s on my GitHub. Since apple has been lagging (maybe I’d better say neglecting) the macOS App Store releases, I’ve decided to give the desktop version for free for as long as they don’t take the desktop market seriously again.

    I am doing my best taking notes from your requests here. If something’s slipped my attention, please drop me a line at [email protected] and I’ll make sure it gets properly tracked. Thank you.

  • @yowza said:
    In bitcrust the text in the left column is too small and hard to read with plenty of empty space around the current text allowing it to be larger. It’s easier to read with certain color themes but still could be larger overall.

    With “left column” you mean the display area? Oscilloscope, etc?

  • @rototom said:
    cool, thank you for 1.0.4!

    if i could make a wish...
    the popup window for sync and ring should stay open to wiggle knobs while playing the touch keyboard.
    thank you. and please don't drop the virgin.:)

    I suggest you get a proper midi controller and midi map those controls with midi learn. But I’ll see if I can make it work like you said.

  • @anode_labs said:

    @yowza said:
    In bitcrust the text in the left column is too small and hard to read with plenty of empty space around the current text allowing it to be larger. It’s easier to read with certain color themes but still could be larger overall.

    With “left column” you mean the display area? Oscilloscope, etc?

    Yes

  • edited April 28

    @anode_labs said:

    @rototom said:
    cool, thank you for 1.0.4!

    if i could make a wish...
    the popup window for sync and ring should stay open to wiggle knobs while playing the touch keyboard.
    thank you. and please don't drop the virgin.:)

    I suggest you get a proper midi controller and midi map those controls with midi learn. But I’ll see if I can make it work like you said.

    It is a multi-touch device, so it shouldn't be necessary to use a midi controller to be able to tweak those, just because the in-app keyboard is being used. That's definitely abnormal behaviour tbh

  • @Rob_Jackson_Music said:
    Getting big Claude Code Vibes though...

    What caught my eye was the main homepage tagline:

    “Boutique audio plugins from scratch — clean-room DSP, modern C++, no shortcuts. One product so far. More to come.”

    The "clean-room DSP" part stood out to me, because in the traditional sense a real clean-room process involves at least two people, with one person separated from the original code. So in a one-person shop, the DSP would have to be written by AI to be compliant.

    More importantly, as a framework developer, I'll admit the "from scratch" phrasing gives me a little pause when the product is clearly built on top of an existing audio framework (JUCE).

    My guess is that the line is aimed more at legal distinction, meaning the GPL-sensitive code was not copied directly, but newly written through a process meant to create some separation. I have no idea how to do that in a legally defensible way, because that opens a much bigger can of worms. Just because a specific chat hasn't seen the original code, AI models are trained on unknown source material... what does "clean-room" even mean anymore? And how much will Apple tolerate?

    This is something I've been thinking about a lot. My hot take is that we may be one serious lawsuit away from stores getting much more cautious about anything even remotely GPL-adjacent, especially if AI is involved in the story somewhere.

    None of that is meant to discourage anyone from buying this app. It's $2, and I think the bigger discussion here is less about this specific release and more about where software law is headed.

    For a $2 app, @anode_labs seems to be very generous and taking the feedback like a champ!

  • @AnalogMatthew said:

    @Rob_Jackson_Music said:
    Getting big Claude Code Vibes though...

    What caught my eye was the main homepage tagline:

    “Boutique audio plugins from scratch — clean-room DSP, modern C++, no shortcuts. One product so far. More to come.”

    The "clean-room DSP" part stood out to me, because in the traditional sense a real clean-room process involves at least two people, with one person separated from the original code. So in a one-person shop, the DSP would have to be written by AI to be compliant.

    More importantly, as a framework developer, I'll admit the "from scratch" phrasing gives me a little pause when the product is clearly built on top of an existing audio framework (JUCE).

    My guess is that the line is aimed more at legal distinction, meaning the GPL-sensitive code was not copied directly, but newly written through a process meant to create some separation. I have no idea how to do that in a legally defensible way, because that opens a much bigger can of worms. Just because a specific chat hasn't seen the original code, AI models are trained on unknown source material... what does "clean-room" even mean anymore? And how much will Apple tolerate?

    This is something I've been thinking about a lot. My hot take is that we may be one serious lawsuit away from stores getting much more cautious about anything even remotely GPL-adjacent, especially if AI is involved in the story somewhere.

    None of that is meant to discourage anyone from buying this app. It's $2, and I think the bigger discussion here is less about this specific release and more about where software law is headed.

    ****For a $2 app, @anode_labs seems to be very generous and taking the feedback like a champ!

    I’ll go one further … he seems to be putting in more work in this than certain other developers do once something is released (not referring to anyone who posts here , as the two specific ones I’m thinking of don’t come here )

  • @AnalogMatthew the website is what bugs me a little, because it clearly is AI generated content that makes claims about the app that aren’t accurate or have been contradicted in this thread. And if the website isn’t being reviewed, can we trust that the code is being reviewed? I really respect the developers behind Augmetic and Dante for being forthright about their vibe coding, not because vibe coding is inherently wrong but because there are obvious pitfalls for the consumer, even if the product is cheap. Here, I’m more wary when everything from the release notes to some of the forum replies are obviously Claude-generated. Of course everyone can make their own decision over what products to support, but it’s better when developers are up front about things like AI use… especially when it’s so obvious.

  • edited April 29

    @timfromtheborder said:
    @AnalogMatthew the website is what bugs me a little, because it clearly is AI generated content that makes claims about the app that aren’t accurate or have been contradicted in this thread. And if the website isn’t being reviewed, can we trust that the code is being reviewed? I really respect the developers behind Augmetic and Dante for being forthright about their vibe coding, not because vibe coding is inherently wrong but because there are obvious pitfalls for the consumer, even if the product is cheap. Here, I’m more wary when everything from the release notes to some of the forum replies are obviously Claude-generated. Of course everyone can make their own decision over what products to support, but it’s better when developers are up front about things like AI use… especially when it’s so obvious.

    I hear you. Especially when even the post which addresses the question is written in such generic AI-style language. It's clear to me that many of this new wave of AI-assisted developers don't realize how damaging it is to their image to lean heavily on LLMs for things like email correspondence, forum posts, AppStore blurbs, manuals, website text, and more. Maybe not every reader or potential buyer is sensitive to this, but certainly many are. At this point, I really dislike reading text with the clear stamp of AI on it, it's highly off-putting on multiple levels.

  • @Gavinski agreed, it’s so impersonal and in a world where there is already an app for everything, the relationship a developer has with their customers is actually important. No different than that of a musician to their audience.

  • edited April 29

    @timfromtheborder said:
    @Gavinski agreed, it’s so impersonal and in a world where there is already an app for everything, the relationship a developer has with their customers is actually important. No different than that of a musician to their audience.

    It is hugely important, yes. We're in a battle for the soul of the internet.

    I do understand btw that the temptation might be higher for devs who aren't native speakers. It still doesn't fly for me, as an excuse though. And I say that as someone who's been a language teacher for 30 years and has lived abroad for most of that time. There are ways to use AI to clean up your mistakes while still retaining your authentic human voice.

    @anode_labs none of this to take away from all your great work on fixing bugs, the very fair pricing of the app etc. I know this thread has likely been a grueling experience and I sympathize.

    But this is nevertheless a really, really important conversation to have, and one that everyone will - hopefully anyway - benefit from in the long term.

  • edited April 29

    I’d rather have a vibe coded app with real dev responses than a “coded from scratch” app with 100% AI responses.

    Edit: which, I’ll add, has kept me away from getting the app. The web page, update notes, App Store, UI, and especially responses here makes it feel like every facet of this is AI. Like there’s 0% human in any response. Is this app a Sammy Jenkins project creation?

    https://sammyjankis.com/home.html

  • edited April 29

    It sure is fun getting Turing tested on an internet forum. You are entitled to your own opinion and I'm glad we're having the AI discourse because it's a new thing and it has open moral/ethic issues that we'll be addressing over the coming years but make no mistake: I am indeed human and I get royally pissed if someone says my website is inaccurate given the amount of autistic level focus I put in reviewing every freaking sentence and punctuation mark in it.

    If you produce something and put it out there, you'll be judged, and that's fine and dandy with me. But you are all getting a little ridicolous on picking on someone who is just trying to learn a little dsp and make something someone out there might find mildly enjoyable.

  • It’s all definitely feeling a bit Monty Python, maybe we can start weighing against feathers, might be a more sensible option😅

  • I would definitely enjoy a Monty Python's philosophers football match sketch where Socrates and Marx argue about the merits vs. perils of AI.

  • hi @anode_labs
    in the effects page, when i load any effect and i twiggle a knob, the whole page moves.
    i have to touchhold an empty space to lock the background.

  • @rototom said:
    in the effects page, when i load any effect and i twiggle a knob, the whole page moves.
    i have to touchhold an empty space to lock the background.

    Thanks for reporting this. The sea-sickness effect fix is locked and coming in next release.

  • Hi there. As bitcrust 1.0.6 is now live, you can find the latest lab notes here.

  • edited May 1

    That’s wassup. Kinda a big announcement with it going universal.

    Keep pushin’ brother. It was already pretty ambitious, good stuff. Brutal community at times- so on behalf of iPhone folks, thx.

  • This sounds really good. One complaint is the text on the left side graphs is hard to read.

  • edited May 1

    Nice with the chord pads (tap keyboard icon) but the colour doesn't stick on whatever pad you use with hold and that goes on the keyboard as well. It's coloured when you press down but not on release.

    I really like the sounds I can get with this synth, just wanna say that again.

    Hold issue

  • @FizzyLizzy27 said:
    This sounds really good. One complaint is the text on the left side graphs is hard to read.

    The displays were more of an aesthetic thing when I added them but I believe they are quite functional and, dare I say, useful? So, yeah, readability wasn't on top of my priorities but I guess a little redesign there might actually make them properly useful. It's in the to do list.

  • edited May 2

    @Pxlhg said:
    Nice with the chord pads (tap keyboard icon) but the colour doesn't stick on whatever pad you use with hold and that goes on the keyboard as well. It's coloured when you press down but not on release.

    I see, also noted, thanks.

  • @anode_labs said:

    @Pxlhg said:
    Nice with the chord pads (tap keyboard icon) but the colour doesn't stick on whatever pad you use with hold and that goes on the keyboard as well. It's coloured when you press down but not on release.

    I see, also noted, thanks.

    Nice update!

    I note the manual mentions swiping on the grid to play steps. But this can lead to weird results. Eg tap on the top step in a column of the grid, then swipe all the way down to the bottom step. You'll hear it keeps getting louder on each step. When you reverse the movement, swiping from bottom to top, it gets quieter - so much so that by the time you get to the top step, it's generally inaudible.

Sign In or Register to comment.