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.
CircuitBreaker: Open Source AUv3 Project
I'm working on a bigger iOS project that needs to be open source and I'm trying to figure out the best way to make it available through GitHub. So, I've created this little AUv3 to try and figure out the sticking points for people to use the bigger project.
The project is at https://github.com/NeonSilicon/CircuitBreaker
The AUv3 itself came out of some discussions here about hearing protection. It is a simple hard clip with a configurable level from -24 dB to +6 dB. It has a very basic UI. The code should be pretty efficient though, so it might be useful.
There are two important points to this project:
1) Figure out how to keep signing and company info out of the GitHub repository.
2) Get feedback about how much of a pain this whole idea is for potential users.
For point (1) I kinda need info from developers that basically know how Xcode and GitHub work. Although, I appreciate feedback from anyone that might be interested in the idea whatever their experience level is.
Point (2) is aimed at anyone. The obvious sticking points are the need of having a Mac (or access to one) and a dev account with Apple, either paid or not. There are several ways to get a project on an iOS device that have different strengths and weaknesses. I'm completely open to talking about these methods to try and figure out what might make the main project workable and also maybe help me figure out some future projects/tutorials I have in mind.
Comments
Great idea @NeonSilicon!
From what I've seen so far, most developers doing this are providing a free version readily available from the Appstore.
Any user owning a Mac can download XCode (mind you, that's a >12GB download!) and build the project themselves.
Out of curiosity, I've just done that with the "MIDI Tape Recorder" app.
The problem is that although Apple lets you create a free certificate to sign your compiled binary for installation on your own iDevice, that certificate will expire after 7 days (it used to be 3 months!) so that's not an option.
The iOS Developer University Program on the other hand is available for free only to qualified, degree granting, higher education institutions. Ruled out as well.
I'd love to know a better way to build my own apps and install them on my own iDevices without having them expire very soon.
The only option I know is jailbreaking the iDevice and make it allow for running unsigned apps. But even that has to be re-done after reboot.
I guess we'd see a few more quality apps if Apple didn't make it that hard to write and use our own apps for our own purpose in the first place. A certificate that expires after 7 days. C'mon Apple.
For the bigger project someone, probably not me, will release on the App Store. For this project, I don't even want to try to get something like this past the censors, um ... review team, at Apple.
This does bring up another potential issue with open source and the App Store. What happens when two developers release forks of my app on the store? Apple does block, sometimes, usage of conflicting IP. It's kinda like the situation of getting takedown notices on YouTube because you used a common IP unencumbered sample.
The seven day thing is just nonsense. To me, it's already bad that Apple blocks using compilers on iOS, but blocking people from using two Apple devices that they've paid for to develop and install software on their devices is pure garbage. There is no way that I can be convinced that this is because of security concerns.
Thank you for the feedback!
For anyone that might be interested in trying out the build and configuration process for this project, I've added some better instructions to the README.md file in the GitHub repository.