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
I don't have any regrets moving to Big Sur. I do find it ugly though, especially in light mode which I like to use during the day. I don't like the increased size of empty space in the UI. But, I can't think of any compelling reason to move to or stay off of Big Sur. At this point, I'd probably wait to upgrade to Monterey myself. I haven't been on the beta of Monterey though, so I don't have any feelings about what it's like yet either.
I have been using the betas of the upcoming version of Xcode. If the tool/side bar icons from the Xcode beta are any indication of what is going to happen in Monterey in general, I'll be pretty happy with that. They feel inline with the SF Symbol like typography in the UI and look good while being distinct and clear.
Hopefully all the audio interface drivers will carry over to Monterey without issue. It took forever to get some drivers out for Big Sur. At least with macOS you can install whichever OS you need/want.
Nothing in System Preferences > Users & Groups > Login Items?
@tja I never used sleep or hibernate on any of my computers or operating systems, as I find the whole concept a bit vague and adding too many unknown variables in general. Also, I've been burnt by Desktop Linux in that regard since 1997 when proper support for that was non-existent anyway. So I gave up early and just properly shutdown and reboot all the time
You can change the default app back to TextEdit by selecting "Get Info" (⌘I) on the file and modifying the "Open with" field shown in the screenshot above (click "Change all" when you've selected the appropriate application).
Do you have the link to that stackoverflow post? TextEdit (and other text editors) still open .plist files for me – this seems like it may be more of a permissions issue. I'm guessing that's one of the system configuration .plists
Oh yeah – the com.apple.* plists tend to be in a binary plist format unlike many of the others that can be edited directly.
The solution offered there is pretty good? I ran
plutil -convert xml1 com.apple.loginwindow.plistand was able to open with TextEdit exactly as you'd imagine.Ah sure – I thought you wanted to open in TextEdit
I advise against using TextEdit to edit anything that is a system or configuration file. Long ago TextEdit was a text editor. Now, it's mainly an RTFD editor and you don't want to accidentally change the file type to an RTFD directory because of some random character or paste you did while editing a system configuration file.
You could use TextEdit easily by launching TextEdit and then navigating to the file in TextEdit's file browser. You can get to any compatible doc type this way without having to deal with the preferred application type stuff.
Personally, I do this sort of thing from the command line using iTerm with nano. I feel safer that way and it's easier too.
I'm curious - what is the thinking here? If some kind of hack was able to wake up your computer, the damage would be done in well under 5 minutes ... more like under 5 seconds.
Five minutes is an eternity for a hacker. In my penetration testing days, I could be leisurely in and out, have taken the time to cover up my tracks, and stopped to chug a Red Bull, in under a minute easily.
Ahhh where's the popcorn. Another episode in the "@tja trying to do F1 racing with a bulldozer"
(no offense intended!)
Regarding Cut & Paste, I've once heard the argument that the concept of "cutting" files somewhere and then "pasting" them somewhere else is apparently "too abstract" for the average Mac user and thus doesn't exist...
I seem to remember that the "always copy, not move" thing apparently depends on whether either of the folders is on a network share. I just wanted to try myself, but unfortunately when I try to access a Linux SMB share from Finder, it suddenly says "The operation can't be completed because the original item for <sharename> can't be found"
I think the general vibe here is that people might accidentally "lose" stuff because the object disappears at the original location and they don't know why.
Ah yeah, I think as soon as the two folders are not effectively on the same filesystem (mount), it always copies. It's what commands like 'mv' do too (because it's technically not possible to just 'move' files between filesystems), but at least they do delete the original file after the copy
>
Or simply 'Drag'n'Drop' (that works when the files are on the same 'device'), then you have the 'option drag' as well when the files are elsewhere...
But yeah, for 'keyboard warriors' it might be a bit problematic