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

1…3537394041

Comments

  • CamblerCambler

    @cokomairena said:

    @Cambler said:

    @cokomairena said:

    @Cambler said:
    I can't see it, but in case I have GUI blindness - is there an option in the clip editor to reverse the order of selected notes? I really miss this in Cubasis.

    That sounds useful, os not here, please suggest it!

    Yes definitely! What’s the best channel to offer app suggestions ?

    Mail the developer, he answer the mail!

    jimaudiodsp gmail.com

    Thanks and done!

  • cokomairenacokomairena

    @auxmux said:

    @cokomairena said:

    @auxmux said:
    Nice updates. This fun as a sampler as well. Still hoping AUs in insert slots. Come on, Jim!

    Maybe asking to load midi fx on the layers would make more sense? That way it limits the amount of au per part…

    Yeah, that's what I'm thinking as well. Definitely need a way to throw Blackhole on every track. 😎

    Do you send the mail? XD

  • gardengarden

    @wim said:

    @EdZAB said:

    @garden said:
    Odd finding: Set up chordjam as midi fx on first layer, simple pad on second layer. Do the print midi thing. Printed chords appear to have not captured note off, so they run to infinity and their lengths can't be edited. I was able to correct it for chords at the end by shortening them in the Chordjam sequencd, but then it happened to the first chord.

    Interesting - I found similar behavior today on a project that I was using before the 1.06 update a couple of days ago. It was 3 layers with (1) Helium, (2) Synth and (3) Continua. After printing to a clip, and saying "yes" to switch to printed clip, Continua continues to play the last note, even after the clip has been stopped and the main transport is stopped. I can reproduce the issue with the project consistently.

    I wonder if those apps are sending Note-ON / Velocity zero instead of Note-OFF. That's perfectly "legal" MIDI, but some apps don't always handle it correctly. mfxMonitor or Streambyter would show what exactly is being sent.

    Good idea... I just checked, and Chordjam does send out Note Off. I also just ran a test - one Chordjam, nothing else - and the midi print worked fine. Evidently the issue is more context-dependent.

  • TentypeTentype

    @Tentype said:
    Probably been answered, but can the piano roll record and edit MPE data?

    This is always my million dollar question when I'm looking at a new DAW.

    Bump

  • solncekreezesolncekreeze
    edited February 17

    Perhaps this question has already been asked. And from the internal keyboard of plug-ins or midifx I can't write to the edit menu? I've seen this done through print midi. But only with the reels. And I need to use chord progressions.
    This can be done through a second midifx with recording capability. Figured it out. But it takes another layer. In general, it is strange that this cannot be done initially. I have to record with two layers of midifx. Although maybe I'm doing something wrong.

  • EdZABEdZAB
    edited February 17

    @Tentype said:

    @Tentype said:
    Probably been answered, but can the piano roll record and edit MPE data?

    This is always my million dollar question when I'm looking at a new DAW.

    Bump

    Similar to a question I had. Incorrect - edited - The automation in GR2 seems to be only able to be defined by initially actively recording it from a knob or panel control defined within the app, after which you can manually manipulate it within the clip.

    If I load up Helium MIDI Sequencer as a layer, and add pitch bend data or other MIDI CC data to the controller lane, it does not appear to record that as an automation. Also in the Helium layer there is a MIDI Pitch knob and manually moving it during playback will modify the pitch, but again, it does not appear possible to record the automation of that movement into the piano roll or clip.

    I could be wrong about some of this, so if I’m missing a trick or a technique please fill me in. 👍

    **Edit: To clarify what I am describing with the MIDI learn and automation, here’s two different scenarios, one of which does what I want and one does not appear to:

    (1) Loading a Helium project in AUM and sending the MIDI out to the GR2 virtual port while also running GR2 in the background will MIDI learn on the incoming CC and assign it to any knob that supports mapping, as well as record the automation.

    (2) Loading Helium and the project into a layer in GR2 there does not appear to be a way to MIDI learn on the CC data that is coming from Helium or to record the MIDI CC data. It will print the notes to MIDI, but that is all.

  • wimwim

    @EdZAB said:
    (2) Loading Helium and the project into a layer in GR2 there does not appear to be a way to MIDI learn on the CC data that is coming from Helium or to record the MIDI CC data. It will print the notes to MIDI, but that is all.

    That is correct. There isn't any way to direct CC output from a midi fx in a layer to the AU parameter automation system.

    The only way to manage it is to send the data in from outside, either from a standalone program or one loaded in a host like AUM. In that situation you can only record, not "print" the automation.

  • wimwim
    edited February 17

    @Tentype said:
    Probably been answered, but can the piano roll record and edit MPE data?

    Nope.

    I tried sending MPE from KB-1 outside GR-2. It played notes and I could hear pitch bend. I recorded to a clip and only the note was captured.

    I tried sending MPE from KB-1 loaded inside GR-2. That would play notes, but there was no pitch bend. Then I tried in non-MPE mode and also with Xequence AU Keys. That will play notes, but you cannot record them to the piano roll.

    From what I've been able to test:

    External

    • Can record MPE notes but not other MPE data from external sources.
    • Can record mod wheel from external sources.
    • Can play, but not record pitch wheel from external sources.
    • Can record automation from external sources if midi mapped to a control. It doesn't record raw CC data, but rather records the resulting knob movements.

    Internal

    • Can play note from an internal midi fx instrument such as a keyboard or Geoshred, but can't record live playing.
    • Can't send or record CC data from internal midi FX.
    • Can only "print" midi generated from AU Midi FX, not record it live.
  • UprightmusicUprightmusic

    Has he added P-Locks?

  • tk32tk32
    edited February 18

    I love how GRII has made soundfonts cool again… but this is literally me 5 minutes after loading one… :D

    (apologies for the off-topic, but I suspect this will bring some light relief to everyone here)

  • cokomairenacokomairena

    @Uprightmusic said:
    Has he added P-Locks?

    Have you asked for it?

  • wimwim

    @wim said:

    @momosa289 said:
    Hi, im new here! really appreciate it if anyone can share more details on the sampler and the live timestretch/warp? as im still planning on getting the apps or not.

    Ask and ye shall receive.

    https://forum.loopypro.com/discussion/comment/1386275/#Comment_1386275

    ... and two more for good measure.

  • TentypeTentype

    @wim said:

    @Tentype said:
    Probably been answered, but can the piano roll record and edit MPE data?

    Nope.

    I tried sending MPE from KB-1 outside GR-2. It played notes and I could hear pitch bend. I recorded to a clip and only the note was captured.

    I tried sending MPE from KB-1 loaded inside GR-2. That would play notes, but there was no pitch bend. Then I tried in non-MPE mode and also with Xequence AU Keys. That will play notes, but you cannot record them to the piano roll.

    From what I've been able to test:

    External

    • Can record MPE notes but not other MPE data from external sources.
    • Can record mod wheel from external sources.
    • Can play, but not record pitch wheel from external sources.
    • Can record automation from external sources if midi mapped to a control. It doesn't record raw CC data, but rather records the resulting knob movements.

    Internal

    • Can play note from an internal midi fx instrument such as a keyboard or Geoshred, but can't record live playing.
    • Can't send or record CC data from internal midi FX.
    • Can only "print" midi generated from AU Midi FX, not record it live.

    Thanks for this 👍🏽

    Kind of a relief that now i won't buy it and have to learn another new thing. 😂

  • UprightmusicUprightmusic

    @cokomairena said:

    @Uprightmusic said:
    Has he added P-Locks?

    Have you asked for it?

    No I haven’t. Where should I ask exactly?

  • jwmmakerofmusicjwmmakerofmusic

    @Uprightmusic said:

    @cokomairena said:

    @Uprightmusic said:
    Has he added P-Locks?

    Have you asked for it?

    No I haven’t. Where should I ask exactly?

    jimaudiodsp @ gmail.com

  • auxmuxauxmux

    Moving this to first page for convenience. 😄

  • UprightmusicUprightmusic

    Thanks @jwmmakerofmusic done.

  • jwmmakerofmusicjwmmakerofmusic

    @Uprightmusic said:
    Thanks @jwmmakerofmusic done.

    Glad to hear. :) Mr. Pavloff is a very responsive developer, so hopefully you do hear back. Best of luck.

  • DhamDham

    The GR2 manual is available: https://www.jimaudio.pro/grooverider2/GrooveRider2_Manual.pdf

  • pedropedro

    @Dham said:
    The GR2 manual is available: https://www.jimaudio.pro/grooverider2/GrooveRider2_Manual.pdf

    Cool! Got me some good bedtime reading!
    And quite an effort it seems, from just a quick skimming of the material

  • cyberheatercyberheater

    @Dham said:
    The GR2 manual is available: https://www.jimaudio.pro/grooverider2/GrooveRider2_Manual.pdf

    Great. Something to get my teeth into.

  • jwmmakerofmusicjwmmakerofmusic

    @Dham said:
    The GR2 manual is available: https://www.jimaudio.pro/grooverider2/GrooveRider2_Manual.pdf

    Excellent! Thanks for posting it. Time to dig in. 🍽️

  • reezyglereezygle

    Maybe it’s a feature but one thing that I noticed during making my last song is that clip automation works at the part level not the clip level. Meaning if you for example have automation to reduce volume in one clip of the part, you have to bring it back up to the original part volume at the end of the clip so that the other clips for the part have the same starting point as the track. This is especially an issue to consider when you have a 1 shot clip (looping turned off in the editor). Personally I’d prefer if track automation and clip automation were independent. By track I mean the vertical group of clips for a part in the clip launcher view.

    As shown, I have to bring up the volume to the track level so that other clips have the right starting point for volume.

  • wimwim

    @reezygle said:
    Maybe it’s a feature but one thing that I noticed during making my last song is that clip automation works at the part level not the clip level.

    I don't see how that could work. How would you record the automation at the track level when you could be changing clips order around after the fact?

  • reezyglereezygle

    @wim said:

    @reezygle said:
    Maybe it’s a feature but one thing that I noticed during making my last song is that clip automation works at the part level not the clip level.

    I don't see how that could work. How would you record the automation at the track level when you could be changing clips order around after the fact?

    I’m thinking 2 separate automations. One for the shared parameters for a part in the mixer (global part automation), like volume, pan, etc. And another for the specific knobs on the part limited to the clip itself. Basically a hierarchical model. The clip automation would become a child of the track automation, working within the bound of the track settings.

    But I can see that this approach would complicate things. So more of an observation than a feature request. No big deal.

  • wimwim

    @reezygle said:

    @wim said:

    @reezygle said:
    Maybe it’s a feature but one thing that I noticed during making my last song is that clip automation works at the part level not the clip level.

    I don't see how that could work. How would you record the automation at the track level when you could be changing clips order around after the fact?

    I’m thinking 2 separate automations. One for the shared parameters for a part in the mixer (global part automation), like volume, pan, etc. And another for the specific knobs on the part limited to the clip itself. Basically a hierarchical model. The clip automation would become a child of the track automation, working within the bound of the track settings.

    But I can see that this approach would complicate things. So more of an observation than a feature request. No big deal.

    I see where you're coming from, but I think by that time you're just about in the ballpark of of using the timeline.

    I wonder what happens if you do the record to timeline thing from the clip sequencer while performing automation. I wonder if the automation gets recorded.

  • reezyglereezygle

    @wim said:

    @reezygle said:

    @wim said:

    @reezygle said:
    Maybe it’s a feature but one thing that I noticed during making my last song is that clip automation works at the part level not the clip level.

    I don't see how that could work. How would you record the automation at the track level when you could be changing clips order around after the fact?

    I’m thinking 2 separate automations. One for the shared parameters for a part in the mixer (global part automation), like volume, pan, etc. And another for the specific knobs on the part limited to the clip itself. Basically a hierarchical model. The clip automation would become a child of the track automation, working within the bound of the track settings.

    But I can see that this approach would complicate things. So more of an observation than a feature request. No big deal.

    I see where you're coming from, but I think by that time you're just about in the ballpark of of using the timeline.

    Yup you are right. It’s me not the tool :smile: I like to compose full songs just by launching clips live and recording the audio. Now that I know better, the best approach is to move the clips to the linear song timeline to make a real song vs playing the clips live while recording the audio in AUM.

    I wonder what happens if you do the record to timeline thing from the clip sequencer while performing automation. I wonder if the automation gets recorded.

    Just tried. It works the same. You have to readjust the automation back to the original setting in a subsequent timeline region of the part. When you record the clips to the timeline, the clip is recorded to a region (I’m using the Logic Pro terminology) in the timeline and each region’s automation starts from where the last region left off. So regardless, you have to readjust the automation for each clip before recording to the timeline.

    This is the case even if you are solely recording to the timeline and not using clips. Each region of the part in the timeline carries over the prior regions settings. There is no automation that covers an entire track because there is no track automation.

    All good now that I know how it works. Embrace the limitations is my moto.

  • wimwim

    @reezygle said:

    @wim said:

    @reezygle said:

    @wim said:

    @reezygle said:
    Maybe it’s a feature but one thing that I noticed during making my last song is that clip automation works at the part level not the clip level.

    I don't see how that could work. How would you record the automation at the track level when you could be changing clips order around after the fact?

    I’m thinking 2 separate automations. One for the shared parameters for a part in the mixer (global part automation), like volume, pan, etc. And another for the specific knobs on the part limited to the clip itself. Basically a hierarchical model. The clip automation would become a child of the track automation, working within the bound of the track settings.

    But I can see that this approach would complicate things. So more of an observation than a feature request. No big deal.

    I see where you're coming from, but I think by that time you're just about in the ballpark of of using the timeline.

    Yup you are right. It’s me not the tool :smile: I like to compose full songs just by launching clips live and recording the audio. Now that I know better, the best approach is to move the clips to the linear song timeline to make a real song vs playing the clips live while recording the audio in AUM.

    I wonder what happens if you do the record to timeline thing from the clip sequencer while performing automation. I wonder if the automation gets recorded.

    Just tried. It works the same. You have to readjust the automation back to the original setting in a subsequent timeline region of the part. When you record the clips to the timeline, the clip is recorded to a region (I’m using the Logic Pro terminology) in the timeline and each region’s automation starts from where the last region left off. So regardless, you have to readjust the automation for each clip before recording to the timeline.

    This is the case even if you are solely recording to the timeline and not using clips. Each region of the part in the timeline carries over the prior regions settings. There is no automation that covers an entire track because there is no track automation.

    All good now that I know how it works. Embrace the limitations is my moto.

    What I meant, in case it wasn't clear, is I wonder if you perform automation on a track while recording a clip performance to the timeline, if that automation gets recorded to the timeline. Something I guess I'll try out at some point.

    Now that I think about it, I don't even know if that would be possible.
    nvm. Just spit ballin' here.

    I get you about track automation. I just don't see how it could work in practice, and my brain isn't up to taking it further right now. 😂

  • soundtemplesoundtemple
    edited February 19

    @Dham said:
    The GR2 manual is available: https://www.jimaudio.pro/grooverider2/GrooveRider2_Manual.pdf

    For those that don't like reading, try the Google NotebookLM Podcast!! Created by uploading the manual and one click to create a podcast.

    Listen here.

  • tk32tk32

    For those who have not yet voraciously consumed all 52 pages of the GRII manual yet (and why not?!) there is a nice surprise on the last page…

Sign In or Register to comment.

© Vanilla Keystone Theme 2025