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 need to dig a little on this.
Ironically, spent an hour on iFunbox trying to change an XML file a certain unnamed app.
New file system, doesn't mean that they will give us mortals access to it though. I'm guessing the sandboxing is not about to go away.
My conspiracy theory is that Lattner left and this happening means either a move away from Swift... or something that's generally disruptive...
Yes, didn't see anything about making it easy to put stuff in there. Excellent chance there will be less, if iFunbox ceases to work because of the change.
In addition, this is both good, and worrisome:
"The new file system prioritizes the apps you are using over background activity, which (for Mac users) should spell an end to those annoying spinning beachballs when systems hang."
It may be helpful for preserving CPU for your DAW. But at the same time, it may rob background processes that you are using such as Audiobus or an AU or IAA plugin of cycles they need to run.
I'll definitely let someone else go first on this one.
Looks like a potential disaster. But I guess we don't have to worry too much as Apple of course will refund all apps that that are not compatible with or gets crippled by APFS.
Unless apps use 'custom hacks' to manage files I don't see any major issues...
This is a good idea, long overdue. HFS+ is simply antiquated.
My iOS and computer savvy is limited but this looks huge. What we've been talking about for eons it seems.. The beginning of what could eventually be "logic" for iOS.
Here are some other links that discuss things:
http://arstechnica.co.uk/apple/2017/01/ios-10-3-apfs-details/
http://arstechnica.com/apple/2016/06/a-zfs-developers-analysis-of-the-good-and-bad-in-apples-new-apfs-file-system/
New file systems aren't going to result in anything visible or particularly different to how things are done now, at least not immediately. You won't know you're running on a particular file system any more than you do or don't know you're running on HFS+ now.
Linux users tend to fuss about file systems more than most people because when one installs linux, a choice can be made and as with all things linux, nobody dares advise you on which one is the best, because they all suddenly fail to know what best means, despite there being dictionaries around, so you're on your own (and this never stops). I've been doing linux long enough to have formatted everything with ReiserFS many years ago because, well, it was one of the choices. One day, lost every fucking thing on all three drives at once. Except the file names.
There's nothing in the previous file system that would technically prevent them from exposing file management in iOS, it's been always about simplifying UX for casual users and trying to push their file-less vision of computing.
At least it didn't kill you1
Sorry, tech joke opportunity https://en.wikipedia.org/wiki/ReiserFS ;↩︎
“[Apple File System] is optimized for Flash/SSD storage and features strong encryption, copy-on-write metadata, space sharing, cloning for files and directories, snapshots, fast directory sizing, atomic safe-save primitives, and improved file system fundamentals.”
Is that what it sounds like?
Hmm, they mentioned all of this in the last keynote, so nothing new really. No sign of a change in file management and accessibility for users, that I could find. It does seem like a great opportunity but also like a good chance to mess things up...
Not sure what it sounds like, but it's about allowing partitions that don't have a fixed size and can transparently allocate more space if needed. The actual space underneath can be used with any of the partitions, so it's called a shared space.
Could have been good fodder for a series of "WTF Does This File Do?" videos.
In reading the Ars Technica article and comments @MusicInclusive provided, it seems the greatest benefit to users would be eliminating the need for automatic file duplication by iOS due to sandboxing between apps. Instead of creating another copy of a file, iOS would create a clone of the file which would be much smaller than the original file. This effectively gives you more storage on the same iOS device versus the current file system.
Some have also speculated that Apple is updating the file system to be ready for new devices perhaps 3-5 years down the line that will have hardware where the new AFPS approach will be needed to effectively use it.
As others have said, our access to iOS files on iOS will still be the same sandbox model rather than how it is on computer OS setups.
I don't see any specific mention in any of the linked articles of "file management." This seems like a behind-the-scenes update.
Ok, here it is the best thing about this new update/ file system:
iOS 10.3 beta 1/ iPad Pro 9.7
Before the update: 15.09 GB free
After the update: 20.09 GB free
Gained 5 GB of storage
iOS 10.3 beta 1/ iPad Pro 12.9
Before the update: 24.6 GB free
After the update: 29.6 GB free
Gained 5 GB of storage
Good news but my first reaction was "What has it uninstalled?" ... That's the techie sceptic in me ...
Alrighty...let me know how it goes guys. Not gonna risk f-cking up my system as I'm in the middle of an involved dance/pop production on Auria.
My guess is that it has done something with the new file block sharing that was being touted and optimized the underlying file storage where there are duplicates of various files. This is akin to what one would do with UNIX symbolic links *** only implemented right down at the metadata level. As I read the tech reports last year, it did seem to be closer to symlinks rather than links (hard links) in that there was a concern raised that removing a file might end up with other programs that had only been referencing it now not seeing it any longer. I do not know for certain how this has ended up being implemented, so we'll have to see.
In any case, instead of having, say, 5 copies of a file - taking up 5 identical amounts of space - I think this might be evidence of that sharing so that one only now has one copy and 5 pointers to it.
Again - this should be entirely transparent to the user - and does not (I don't think - haven't tried any betas yet) affect the overlying UNIX filesystem architecture that both iOS and macOS implement presently.
I.e. all the file permissions, directories, links, symbolic links, UNIX domain sockets, named pipes, etc. will all still be there, but now implemented underneath by APFS instead.
I hope
(*** If you are a Windoze person, the analogy is like shortcuts).
i.e. in addition to file sharing at the block level one can also (I hope, still) have regular UNIX links and symbolic links in the filesystem. (It'll be easier to tell what they've done by looking at macOS, but I haven't played with APFS there either yet.)
This is my understanding as well and why it's such a great thing for iOS, especially for musicians so we can use the same file with multiple apps without having duplicate copies of it using up all of our storage. With such a fundamental change to the underlying file system, it's interesting that Apple chose to go with iOS 10.3 rather than 11.0.
Interesting insights @MusicInclusive and @InfoCheck, thanks.
Sharing files sounds great until you potentially run into the iOS version of DLL Hell.
I guess it's all going to be heavily tested and peachy but I'm not going to be the first to make the leap. In fact it may
be some considerably time before I do so voluntarily. But I do have a small capacity iPad so ...
Windows has had symbolic links since Windows Vista. Have been using them for years.
People with far better knowledge already answered with their theories about what's happening behind the scenes , The only thing I can say it's that no data was lost in the process, everything's fine, nothing corrupted or deleted whatsoever. Overall great update even if there aren't any new flashy features.
Yes, interesting. Maybe they decided they want to stay on 10 forever like they did on macOS. iOS 10.11, 10.12, 10.13, 10.20, 10.100 etc...
I wonder what the strategy is when one app fundamentally alters the cloned data that is published to various other apps that subscribe to it (assuming the clone mechanism works like pub/sub )? If app x changes data 1 to a new state and app b relied on data 1 being in some prior state, would app x perhaps keep data 1 in the original state and create some kind of 'overlay'? Much like what happens when you install a portable linux usb stick - changes and system updates don't alter the original installation, but form a new 'overlay' or ghosted file that is integrated with the original one when it is booted up. The original one stays that way forever, but you don't see it that way, you only see it through the more recent overlay.
If I've understood the developer documentation correctly it works like 'subscribing to a linked file'.
You can 'check out' a file for editing and while it's 'checked out' no other app can modify it but they can read the content 'on the fly'.(In practice a 'live' read-only copy to the file that is being edited, so every time a change is made a 'change notification' is sent so the apps that subscribe to the file can update/refresh their content).
Naturally this would assume that all apps store their files in a common place such as a file-container provided by iCloud Drive or say AudioShare or any app that shares it's files using iOS-FileProvider Extensions.
The biggest challenge is to migrate to the mind-set that no app really fully 'owns' the file(s) and also make a fundamental change in thinking to never store the files inside an apps own private & unshared container.
This is where it gets 'interesting' from the copyright and rights management perspective...