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'm really enjoying them... Love how we can add breath/bow expressiveness to the wind/bowed-string instruments
Introducing GeoShred 6.5!
Select Collection Discounts
20% Off May 30 - June 14, 2024
New Preset Management, iCloud Preset Synchronization and Automation and numerous bug fixes.
Discounts: In GeoShred go to Menu> Store
GeoSWAM Collection I & II, discounted from $119.99 USD, to $95.99 USD
Naada Collection I & II & III, discounted from $179.99 USD, to $143.99 USD
*Note: All Prices are in US Dollars (USD). Apple sets the local territory price and may add additional local charges such as VAT, GST, HST. Check the store in your territory for the local price.
Looking good with this update and thank you, @moForte.
It appears the Automation function is really for the desktop AU version to ensure all of the subtleties of a performance are recorded and this will be coming out later really to enhance the desktop version of the app?
You can use it with Logic on the iPad as well. Also look at the app note. You can automate all 1000+ GeoShred Parameters as well as MIDI/MPE automation. Application note here:
Note that the music you hear in the background is a full ensemble. 11 instances of GeoShred on my iPad Pro, performed by me into Logic for iPad and heavily articulated using both Parameter Automation and MIDI/MPE automation. The play back is all 11 instances in real time ... on an freaking iPad !
That was a fantastic update. 🤩 I would be happy if you even just promised to work on patch management. iCloud sync works perfectly, and finally, we are able to expose all those automation parameters. Now, only the sky is the limit. Thank you very much. The future is bright for GeoShred.
I also encountered a problem using “plugin tile” in LP4i. What are those parameters exposed to, and when you start using them, they break LP4i? I can’t find any help or information on the official site.
Are these deals only available if I’ve upgraded to geoshred pro? Not entirely clear. I don’t play wit Geoshred enough…it really does sound fantastic
Look in the App Note for the release.
Automation is covered starting at 4:20.
Why does GeoShred have 1000+ automatable parameters? There are 33 different instrument models, each like it's own application, each with it's own unique parameters. There are 22 different effects units, each like it's own application, each with it's own unique parameters. There are about 160 performance parameters.
We build an indirection mechanism where you select which of the 1000+ parameters to expose to the parameter tree. It's covered in the application note video for GeoShred 6.5 starting at around 4:20.
You may ask, why don't you just fill the parameter tree with just the parameters in the current preset. We have been trying to do that for years, but there is a bug with how Apple allocates the parameter tree causing it to NOT be re-allocate-able after plugin initialization. We reported this bug to Apple over 6 years ago and even met in person with them and to date it has not been fixed.
WRT LP4i, crashing, let's connect directly about that. It's most likely caused by an old project with the earlier layout of the parameter tree. There is a procedure shown in the video (10:23) for how to address this. Basically
Again this is a limitation for how Auv3 handles changes in the layout of the parameter tree. Basically Apps can never add parameters without crashing the plugin.
If you are still having a challenge, please reach out to us directly [email protected]. We can even do a zoom call if needed.
Anyone?
Please, can you try this after the notes, with the latch record? Use whatever control you like.
Assigning “userParam” and painting automations with Pencil in automation view works just fine, but not recording controls from the AU interface.
Also, can you decipher parameters in the GeoShred plug-in tile?
I might try more in-depth testing later on (GeoShred is NOT essential for me and I'd rather spend time with some other apps) but I did notice that somehow that GeoShred reloads the current preset when playback loops if I had previously recorded some vibrato automation...
No, but some plug-in tiles show the first 3 available parameters.
I'm not sure but I think there's a way for developers to choose which knobs to show in the plug-in tiles but as Logic is the only app with 'plug-in tiles' I think many won't bother. AUM as an example shows the first parameter by default.
In all honesty I don't even know why I still have GeoShred installed.
It was almost 3 months ago I last played around with it prior to the recent update
Hopefully there's someone else here on the forum that can devote some time to troubleshoot GeoShred related issues.
Cheers!
It’s not a cheap app, time will be spent well. You see, I’m trying to sell you the thing, haha.
I don’t need to say how helpful you are, even just caring. Thank you for that! And please, do not feel obligated to do anything, just forget if you have anything better to do. 🤗
I know, I sometimes it as a sound module for regular keyboard playing/sequencing.
Not a fan of playing the UI to be honest, playing on a regular keyboard makes editing easier too since everything is on the same midi-channel and not that 'MPE Garbage' with random midi-channel per note and its CCs.
No worries
The Store with the discounted collections is available in GeoShred Pro, GeoShred Play, GeoShred Play+Pro (Play ugraded to the functionality of Pro) and GeoShred Control+Pro (Control upgraded to the functionality of Pro).
Look in GeoShred under "Menu> Store"
Cool update! But - enabling automation breaks Auv3 presets.
I use Loopy Pro as host and have saved Auv3 user presets for Geoshred. When I have Geoshred automation enabled and try to load the presets, it crashes Geoshred and also makes it impossible to reload until restarting LP.
Once I turn off automation, they work fine again.
The update did also change all my Auv3 presets to different actual Geoshred presets than the ones they were saved with, specifically to presets with instruments I don't even own, which was a bit of a bother as I had to manually re-save all the LP Auv3 presets for Geoshred.
I don't know if that could have been handled better, but I thought I'd mention it.
Actually got out Swam trumpets ( which iv never used )
Generally always though, mpe wernt recordable etc ( perhaps only xequence )
but thought.
If you do make an ok keyboard and cc controller setup.
Then it would be recorded as regular note and automated cc ( Drambo ) anyway.
Which means buying the array of trumpets. Could be good.
Geoshred has microtonal tuning built in, with all the scales you could ever want. I would even say that if you have GS you don't really need Etonal.
This is an known issue with AuV3, when the parameter tree signature changes, Auv3 will thow out the plugin. There is a procedure to convert your projects.
The procedure is covered in the video here:
13:30 Automation Considerations
14:00 Loading/Saving AuV3 Projects Created with Earlier Versions of GeoShred
14:40 Procedure to Convert Older Projects
15:40 Summary - Procedure to Convert Older Projects
We don't agree with Apple's design decisions with regard to AUv3 parameter automation. Here are notes
Apple's Auv3 design has a provision for plugins to expose internal parameters. It's called a Parameter Tree.
Their design intention appears to be that the Parameter tree contains just a handful of parameters, and it's static and NEVER grows beyond some undefined small limit and NEVER changes over the lifetime of a plugin.
If a host project is saved with OriginalParameterTree, and then the plugin is updated with NewParameterTree, AUv3 will kick the plugin out at load time. This is a consequence of a single fixed static allocation of the parameter tree. It's not a GeoShred problem, its an AUv3 problem and lots of plugins have had need to add a parameter, then the plugin will crash, and there needs to be a manual procedure to convert old projects to new projects. This is how GeoShred is dealing with it.
-If you have a project (Loopy Pro in your case) with OriginalParameterTree,
-Turn Automation OFF in stand-alone GeoShred,
-Load the project (Loopy Pro in your case)
-Turn ON Automation in the GeoShred Plugin
-Save the Project.
-This will save the project using NewParameterTree. It will load just fine moving forward.
What's flabbergasting about Apple's architectural decisions around AUv3's parameter tree, is that having a plugin architecture with a dynamic number of parameters, that change over time is an OLD and solved problem dating back to the 1980s. COBRA, COM (Microsoft), DCOM, JAVA WSDL. All of these mechanism have a provision to change the signature of the plugin parameters using version numbers so that the number of parameters can change with product revisions, and NO CRASHES. This is basic. It's unclear how this got past product design and code review for Auv3. We have filed a bug with Apple about this issue.
This should not be happening. We expended special effort to make sure that old/new setlist:preset was not disrupted with the release. Would you be willing to work with us to understand why this is happening?
Yes, here's an update - I had to re-make all Auv3 presets with Automation mode enabled as well, meaning a separate bunch of the same presets to use with automation enabled.
These load normally, contrary to the Auv3 presets created previously, with different parameter tree - which crash and break Geoshred until restart as mentioned, and vice versa when I disable automation; the old Auv3 presets created without automation enabled load fine, but the ones made with automation crash.
So I have 2 separate sets of the same presets now. Working fine.
This is understandable though in regards to what you say about Apple, Auv3 and parameter tree etc.
I'm fine with using separate presets for automation enabled. Was a bit of a hassle to re-make, but no worries.
And aside from that, yes the old Auv3 presets after Geo update were broken in the sense that they didn't refer to the correct Geo preset anymore; as I have mentioned before in another post about another Geo update that messed with my Auv3 presets, it seemed the order of Geo presets were changed and thus the presets that the Auv3 presets/ state saves refer to have been mixed up.
In this case, the Geo presets that the old Auv3 presets loaded up now were Naada instruments I don't own, but my Auv3 presets were specifically only referring to my own user presets in Geoshred.