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.

Jim Audio Groove Rider 2 - RELEASED

13536373941

Comments

  • @wim said:
    I got into the synth a lot deeper last night after having thoughts triggered by reading the manual. You can do some amazing things using synth layers on a part. If you think of a part as a modular synthesizer, you can beat out a lot of synths in terms of features. Independent filter, envelope, panning, FX, tuning, polyphony, and other things per layer is hugely powerful.

    I started whipping up a basic 3 oscillator "synth" with three layers and ended up with some amazing patches. I immediately loved having a totally separate filter for each oscillator, and especially something I always miss in every non-modular synth ... panning per oscillator. But the real icing on the cake was being able to have separate FX per layer. One oscillator to a ping-pong delay, one to a chorus, one to a slicer ...

    Sure, there are lots of limitations, but there's also pretty much unlimited potential for sound design in a package that's easier to deal with than a modular environment.

    Don't ask me for patches. I didn't save any. 😂

    That synth is hella flexible. Also, if I'm, say, creating a sustained bass sound using a String Basses soundfont, and the low-end is lacking, I just pop a synth oscillator on the next layer with a sine wave, and voila! Beefed up the String Basses soundfont. I've never used a groovebox that's so damn flexible before. 😳 Can do a LOT with it within its limitations.

    Yeah, I'll shut up now before I start another ramble on about how amazing GR2 is.

  • wimwim
    edited February 20

    Ahhh ... just discovered that you can route a part directly to FXA or FXB with the button below output in the part. That makes using AUv3 as an insert FX possible, sort of.

  • @wim said:
    Ahhh ... just discovered that you can route a part directly to FXA or FXB. That makes using AUv3 as an insert FX possible, sort of.

    Wait, you can do that?! I didn't know that. That's pretty sick not gonna lie. 😱

  • I started using the wave table, downloaded some pretty good tables that I already had a while ago: https://www.echosoundworks.com/eswcorewavetables

    It has an excellent selection of classic oscillators, instruments and digital wavetables in folder

    Now, anyone understands parameter sets? I understand that they save two different set of synth parameters for the same layer, but why? How do you use it, can you program it?

  • @jwmmakerofmusic said:

    @wim said:
    Ahhh ... just discovered that you can route a part directly to FXA or FXB. That makes using AUv3 as an insert FX possible, sort of.

    Wait, you can do that?! I didn't know that. That's pretty sick not gonna lie. 😱

    It was implemented on the last update

  • @cokomairena said:

    @jwmmakerofmusic said:

    @wim said:
    Ahhh ... just discovered that you can route a part directly to FXA or FXB. That makes using AUv3 as an insert FX possible, sort of.

    Wait, you can do that?! I didn't know that. That's pretty sick not gonna lie. 😱

    It was implemented on the last update

    Cool beans.

  • wimwim
    edited February 20

    @cokomairena said:
    I started using the wave table, downloaded some pretty good tables that I already had a while ago: https://www.echosoundworks.com/eswcorewavetables

    It has an excellent selection of classic oscillators, instruments and digital wavetables in folder

    Now, anyone understands parameter sets? I understand that they save two different set of synth parameters for the same layer, but why? How do you use it, can you program it?

    It lets you use different part level settings per clip. (!)
    Long press a clip and you can choose the Parameter Set.

    Different oscillator settings, FX, ... everything. 😎
    I can't even quite get my head around how powerful that is yet.

    It also explains why Jim didn't allow AU FX on part inserts. That kind of swapping around with AUv3's would kill any app.

  • I understood parameter sets!

    Once you have them created you can assign them to clips, so you can have radically different sounds for different clips.

    The key is creating the parameters first, then assign them on the clip view long tapping a clip

  • @wim said:

    @cokomairena said:
    I started using the wave table, downloaded some pretty good tables that I already had a while ago: https://www.echosoundworks.com/eswcorewavetables

    It has an excellent selection of classic oscillators, instruments and digital wavetables in folder

    Now, anyone understands parameter sets? I understand that they save two different set of synth parameters for the same layer, but why? How do you use it, can you program it?

    It lets you use different part level settings per clip(!)
    Long press a clip and you can choose the Parameter Set.

    Different oscillator settings, FX, ... everything. 😎
    I can't even quite get my head around how powerful that is.

    It also explains why Jim didn't allow AU FX on part inserts. That kind of swapping around with AUv3's would kill any app.

    Thanks!

  • You can also assign the on the timeline!

    The key is creating them first, incredible

  • Being able to change the ifx is just mindbending

  • The only thing I'm missing big-time in the parameter sets is the state of the arp button. I wrote Jim to suggest he add that.

  • This is so gonna need a wiki.

  • Layers should technically have separate midi clips. It would make things truly multi-timbral. Have done this in Drambo.

  • @auxmux said:
    Layers should technically have separate midi clips. It would make things truly multi-timbral. Have done this in Drambo.

    Isn't that what parts are for?

  • @wim said:

    @auxmux said:
    Layers should technically have separate midi clips. It would make things truly multi-timbral. Have done this in Drambo.

    Isn't that what parts are for?

    Kind of, but let's say you want to have some layers pass through same FX. It's like instrument racks in Ableton. Or imagine multi-part synths like JV2080.

    I should correct that I meant that layers should have one clip but you can choose which notes pass to which layer.

  • wimwim
    edited February 20

    @auxmux said:

    @wim said:

    @auxmux said:
    Layers should technically have separate midi clips. It would make things truly multi-timbral. Have done this in Drambo.

    Isn't that what parts are for?

    Kind of, but let's say you want to have some layers pass through same FX.

    You can do that. There are multiple routing options. Parallel, Series, Mixed, and you can select to which insert each layer goes to. The options aren't unlimited, but they're pretty extensive.

    It's like instrument racks in Ableton. Or imagine multi-part synths like JV2080.

    I get that, but I don't see any practical distinction when you have multiple parts to work with. I'm happy with the simpler, more groove box oriented approach. It's a groove box that acts like a daw more than a daw that acts like a groove box.

    What I do wish for is the opposite - midi routing between parts, so that I could have one clip playing multiple parts.

    I should correct that I meant that layers should have one clip but you can choose which notes pass to which layer.

    That would be pretty cool. Don't think I'd use it myself though. I don't want that much clutter in my patterns. I'd separate them out to different parts. The disadvantage is not seeing how the notes in the clips relate to each other. I'd rather see "ghost" tracks than loading them all into a single clip to help with that.

    Nice ideas for sure. I'm just tossing out my own preferences.

  • @wim said:
    I got into the synth a lot deeper last night after having thoughts triggered by reading the manual. You can do some amazing things using synth layers on a part. If you think of a part as a modular synthesizer, you can beat out a lot of synths in terms of features. Independent filter, envelope, panning, FX, tuning, polyphony, and other things per layer is hugely powerful.

    I started whipping up a basic 3 oscillator "synth" with three layers and ended up with some amazing patches. I immediately loved having a totally separate filter for each oscillator, and especially something I always miss in every non-modular synth ... panning per oscillator. But the real icing on the cake was being able to have separate FX per layer. One oscillator to a ping-pong delay, one to a chorus, one to a slicer ...

    Sure, there are lots of limitations, but there's also pretty much unlimited potential for sound design in a package that's easier to deal with than a modular environment.

    Don't ask me for patches. I didn't save any. 😂

    Ooh this sounds nice. Thanks for the tips Wim.

  • @wim said:

    It also explains why Jim didn't allow AU FX on part inserts. That kind of swapping around with AUv3's would kill any app.

    But this means we’re still limited to only two aufx as inserts right? Still really limiting for those that use fx as a key part of their sound design.

  • edited February 21

    A good way to learn GR2 is to take one of the demo songs and start playing with the sounds and effects and change them to your liking. Here I took Affected and used ScaleBud 2 to change the scale, got rid of all of the built in sounds and used only SF2 and AuV3… Sunrizer, OB-XD3, VCS3, TAL U-No-LX, iSEM, Model 15, SynthMaster 2. The drum kit is a SoundFont. I also used Barkfilter as the final effect in the FX chain.

  • @auxmux said:

    @wim said:

    @auxmux said:
    Layers should technically have separate midi clips. It would make things truly multi-timbral. Have done this in Drambo.

    Isn't that what parts are for?

    Kind of, but let's say you want to have some layers pass through same FX. It's like instrument racks in Ableton. Or imagine multi-part synths like JV2080.

    I should correct that I meant that layers should have one clip but you can choose which notes pass to which layer.

    You can choose which notes are passed to each layer:

  • @Cambler said:

    @wim said:

    It also explains why Jim didn't allow AU FX on part inserts. That kind of swapping around with AUv3's would kill any app.

    But this means we’re still limited to only two aufx as inserts right? Still really limiting for those that use fx as a key part of their sound design.

    Two buses of 3 auv3s each

    Plus you could route an extra layer (or many) to the first master auv3 and have a 3rd bus of auv3

  • @Coloobar said:
    A good way to learn GR2 is to take one of the demo songs and start playing with the sounds and effects and change them to your liking. Here I took Affected and used ScaleBud 2 to change the scale, got rid of all of the built in sounds and used only SF2 and AuV3… Sunrizer, OB-XD3, VCS3, TAL U-No-LX, iSEM, Model 15, SynthMaster 2. The drum kit is a SoundFont. I also used Barkfilter as the final effect in the FX chain.

    https://on.soundcloud.com/5H1DcGZLZdBEA5mY6

    That’s wild, good exercise!

  • @cokomairena said:

    @Cambler said:

    @wim said:

    It also explains why Jim didn't allow AU FX on part inserts. That kind of swapping around with AUv3's would kill any app.

    But this means we’re still limited to only two aufx as inserts right? Still really limiting for those that use fx as a key part of their sound design.

    Two buses of 3 auv3s each

    Plus you could route an extra layer (or many) to the first master auv3 and have a 3rd bus of auv3

    For my own purposes I need to have the usual ability to apply fix at the “track” level. I realise you can have multiple fix on each bus but there’s only two busses. Maybe Jim will add more busses at some point.

  • @Cambler said:

    @wim said:

    It also explains why Jim didn't allow AU FX on part inserts. That kind of swapping around with AUv3's would kill any app.

    But this means we’re still limited to only two aufx as inserts right? Still really limiting for those that use fx as a key part of their sound design.

    Actually, you can have up to 9 AUv3 effects in total. 3 on send buss A, 3 on send buss B, and 3 on the master effects buss. However, I find I rarely need to use any AUv3 effects outside of Grand Finale 2 and NoLimits 2 on the master effects buss. The built-in ones are solid.

    And you get three per part and can route them in many various ways (serial, parallel, etc) as well as route each layer of a part to a specific one. For instance, say you load a choir soundfont and a synth, but you want to only apply the chorus to the synth, right? Have the synth routed to IFX 1 where the chorus is and the choir soundfont to IFX 2 to bypass the chorus.

    The audio signal routing capabilities in GR2 are rather robust. It may not be how you're used to sound design with effects, but there are many other creative ways to affect sound.

    I wonder, what genre of music do you produce the most?

  • @cokomairena said:

    @auxmux said:

    @wim said:

    @auxmux said:
    Layers should technically have separate midi clips. It would make things truly multi-timbral. Have done this in Drambo.

    Isn't that what parts are for?

    Kind of, but let's say you want to have some layers pass through same FX. It's like instrument racks in Ableton. Or imagine multi-part synths like JV2080.

    I should correct that I meant that layers should have one clip but you can choose which notes pass to which layer.

    You can choose which notes are passed to each layer:

    Ah, good call.

  • @jwmmakerofmusic said:

    @Cambler said:

    @wim said:

    It also explains why Jim didn't allow AU FX on part inserts. That kind of swapping around with AUv3's would kill any app.

    But this means we’re still limited to only two aufx as inserts right? Still really limiting for those that use fx as a key part of their sound design.

    Actually, you can have up to 9 AUv3 effects in total. 3 on send buss A, 3 on send buss B, and 3 on the master effects buss. However, I find I rarely need to use any AUv3 effects outside of Grand Finale 2 and NoLimits 2 on the master effects buss. The built-in ones are solid.

    And you get three per part and can route them in many various ways (serial, parallel, etc) as well as route each layer of a part to a specific one. For instance, say you load a choir soundfont and a synth, but you want to only apply the chorus to the synth, right? Have the synth routed to IFX 1 where the chorus is and the choir soundfont to IFX 2 to bypass the chorus.

    The audio signal routing capabilities in GR2 are rather robust. It may not be how you're used to sound design with effects, but there are many other creative ways to affect sound.

    I wonder, what genre of music do you produce the most?

    Hey JW, thanks for the info. I appreciate the number of effects per bus however there’s still only two proper busses so that’s only two distinct treatments I can apply. The built in effects are solid but are pretty plain. I work across ambient and electronic and other territories but leaning in to the more experimental edges.

    Obviously there are lots of wonderful things about GR2, I’m just whinging as it’s not really suiting my own approach to making music 😝

  • @Cambler said:

    @jwmmakerofmusic said:

    @Cambler said:

    @wim said:

    It also explains why Jim didn't allow AU FX on part inserts. That kind of swapping around with AUv3's would kill any app.

    But this means we’re still limited to only two aufx as inserts right? Still really limiting for those that use fx as a key part of their sound design.

    Actually, you can have up to 9 AUv3 effects in total. 3 on send buss A, 3 on send buss B, and 3 on the master effects buss. However, I find I rarely need to use any AUv3 effects outside of Grand Finale 2 and NoLimits 2 on the master effects buss. The built-in ones are solid.

    And you get three per part and can route them in many various ways (serial, parallel, etc) as well as route each layer of a part to a specific one. For instance, say you load a choir soundfont and a synth, but you want to only apply the chorus to the synth, right? Have the synth routed to IFX 1 where the chorus is and the choir soundfont to IFX 2 to bypass the chorus.

    The audio signal routing capabilities in GR2 are rather robust. It may not be how you're used to sound design with effects, but there are many other creative ways to affect sound.

    I wonder, what genre of music do you produce the most?

    Hey JW, thanks for the info. I appreciate the number of effects per bus however there’s still only two proper busses so that’s only two distinct treatments I can apply. The built in effects are solid but are pretty plain. I work across ambient and electronic and other territories but leaning in to the more experimental edges.

    I love that genre of music a lot! It's amazing. :) I think GR2 is great for more melodic Ambient, whereas Cubasis 3 is what you'll want for producing more experimental Ambient. (Note to self - produce a piece of Ambient in GR2 for @Pierre118 .) Cubasis 3 comes jam packed full of IAP sound libraries that rendered most of my romplers (except Beathawk) obsolete.

    Obviously there are lots of wonderful things about GR2, I’m just whinging as it’s not really suiting my own approach to making music 😝

    😂🤣 Yeah, GR2 has its own specific workflow, so to survive in that environment, you must adapt. It's still a great deal of fun though for my purposes, but yeah, I'm more into Cubasis for Experimental Ambient, Musique Concrete, and other such Outsider types of music.

  • @jwmmakerofmusic said:

    I love that genre of music a lot! It's amazing. :) I think GR2 is great for more melodic Ambient, whereas Cubasis 3 is what you'll want for producing more experimental Ambient. (Note to self - produce a piece of Ambient in GR2 for @Pierre118 .) Cubasis 3 comes jam packed full of IAP sound libraries that rendered most of my romplers (except Beathawk) obsolete.

    Indeed, and Cubasis is my poison of choice for composition on iPad, although I would use Logic more if it wasn't sub.

    Obviously there are lots of wonderful things about GR2, I’m just whinging as it’s not really suiting my own approach to making music 😝

    😂🤣 Yeah, GR2 has its own specific workflow, so to survive in that environment, you must adapt. It's still a great deal of fun though for my purposes, but yeah, I'm more into Cubasis for Experimental Ambient, Musique Concrete, and other such Outsider types of music.

    Yes, I am still persisting with GR2 and once I get more fluent in its ways I am sure there are styles of music it'll work for. My biggest gripe though is its export options. That really does need to change. We need to be able to export both midi and most importantly stems.

  • @Cambler said:

    @jwmmakerofmusic said:

    I love that genre of music a lot! It's amazing. :) I think GR2 is great for more melodic Ambient, whereas Cubasis 3 is what you'll want for producing more experimental Ambient. (Note to self - produce a piece of Ambient in GR2 for @Pierre118 .) Cubasis 3 comes jam packed full of IAP sound libraries that rendered most of my romplers (except Beathawk) obsolete.

    Indeed, and Cubasis is my poison of choice for composition on iPad, although I would use Logic more if it wasn't sub.

    Oh thank heavens you don't use Logic Pro. It's good, but has bugs. 😂 The biggest gripe is how Logic will occasionally forget plugin parameters. It did it with Poison-202, with FluxMini2, and most grievous, with its own bloody adaptive limiter? 😆 AND, when I used AI Mastering Assistant for my "In Search of a New DAW" EP from a couple months back, Logic rendered my audio with the stereo field reversed (left is right, and right is left). Not worth the sub in my opinion (not that I'm against subs, but Logic Pro is a disappointment for me personally, ymmv).

    That said, Cubasis 3 has many amazing IAP packs. From Waves plugins, to amazing sound libraries like Iconica Sketch and Halion to FMClassics and NeoFM. All these rendered most of my romplers obsolete (except for Beathawk). The only gripe I have with Cubasis 3 is a lack of an internal drum module. However, Koala Sampler works swimmingly well as a drum module. That "EQ per pad" is killer.

    Obviously there are lots of wonderful things about GR2, I’m just whinging as it’s not really suiting my own approach to making music 😝

    😂🤣 Yeah, GR2 has its own specific workflow, so to survive in that environment, you must adapt. It's still a great deal of fun though for my purposes, but yeah, I'm more into Cubasis for Experimental Ambient, Musique Concrete, and other such Outsider types of music.

    Yes, I am still persisting with GR2 and once I get more fluent in its ways I am sure there are styles of music it'll work for. My biggest gripe though is its export options. That really does need to change. We need to be able to export both midi and most importantly stems.

    I think I read somewhere that stem export should be coming. Not sure how long it'll take, but hopefully sooner rather than later. :)

Sign In or Register to comment.