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.

[ Meow | Audio Editor ] Public Beta

2456717

Comments

  • @Krupa said:

    @SevenSystems said:

    You can drag the ruler left/right to adjust the zero point!

    I just thought I’d point that out in case anyone missed it 😇 (I was cursing like a trooper for a couple of minutes until I spotted that I could move it 😄)

    I think I'll put in a help system, similar to Trinity's, for these kinds of things that are undoubtedly easy to miss!

  • @espiegel123 said:

    @SevenSystems said:

    @espiegel123 said:
    I feel like the ruler needs MUCH finer granularity of its labels with easily viewable tickmarks indicating meaningful subdivisions , and the granularity should increase as one zooms in.

    Yes agree. Probably will look into providing something similar to Xequence when in 'Auto' Grid mode. i.e. when you zoom in further, each beat gets divided by 2, then again by 2, etc. (poor people with triplets though!)

    I'd like to be able to calculate BPM from the selection by indicating how many beats are in the selection. If that option is already there, it isn't obvious how to access it. Imo, this is essential for a beats based timeline to really be useful.

    That sounds good and actually straightforward. So just a button in the BPM menu "Get from selection" or something, rounding to maybe 0.5 BPM so you don't have to be extremely precise with your selection?

    No rounding at that granularity..unless there is an option to not. When making and refining a selection that loops perfectly, it is often necessary to have a really precise setting.

    No I mean, when the app calculates the BPM from the selection's length, it should round the BPM to maybe 0.5 or 1 BPM. Otherwise, you'd have to make an extremely precise selection, which would be very tedious. Most music will have a BPM that is spot-on a whole number, or maybe 130.5 BPM. But never 125.824239842. Or an I misunderstanding?

    While samples mode is only useful when zoomed in, sometimes you need the milliseconds.

    OK. More meaningful ruler markings / snapping when zoomed in further in general is something I'll explore.

    Another feature I consider essential is a display (either in the main u.i. or a get info panel) of the precise numerical values of the playhead position and, selection start, end and duration....preferably with a way to edit them.

    OK noted! (out of curiosity, can you give me an example of when you would use this so I can understand the use cases better?)

    For example, I am relatively frequently making a selection and need to know how long it is...and sometimes I might need to move the playhead to a precise location and measure the distance (by making a selection) to the start or the end of a note.

    OK.


    BUG
    If i have loaded a file, I find that if i switch out of the app amd stay out for too long, when i return to the app, it reloads as if launched from scratch rather than reloading the audio (and restoring the selection).

    That can happen when iOS kills the app, there's no full session restore yet. Did you have a very large audio file loaded?

    The file was not large. Maybe 4 bars long.

    Alright. It might have crashed while in the background due to other reasons then. In any case, proper session restore is of course needed and will be added!

  • @SevenSystems said:

    @gregsmith said:
    Just had a quick play and it’s lovely as expected. Those left/right handles at the bottom work so much better than trying to do it straight on the wav visualisation, and helps prevent accidentally moving them, which happened all the time to me in twisted wave.

    That's funny, you're saying the opposite of the others 😄 It looks like something that I wanted to avoid -- a preferences menu -- might be needed in the future!

    Oh 😂

    It might be cos I’m on iPhone and haven’t tried on iPad yet. I haven’t used twisted wave for ages tbf, but distinctly remember spending ages zooming right in and painstakingly selecting the perfect in out points then losing it all with one miss tap.

    It’s like the piano roll in xequence. So much easier using bigger handles to move the notes around rather than zooming in and out trying to tap on the notes and drag them, without accidentally getting the ‘make smaller’ hit point.

  • @Samu said:

    @SevenSystems said:
    @Samu oh btw. Do you think the zoom factor when using 'View to selection start/end' is useful? It currently zooms to +/- 50 ms.

    For me it's useful as it leaves a bit of margin to move the start and end points.
    If they were 'pinned to the side walls' one would have to 'zoom out' before being able to move them :)

    Yes, that margin is integral to how the UI is designed :) I might even make this margin configurable. I wanted to avoid a "Preferences" menu for now, but I'm sure it'll be needed at some point.

    Cheers!

  • @gregsmith said:

    @SevenSystems said:

    @gregsmith said:
    Just had a quick play and it’s lovely as expected. Those left/right handles at the bottom work so much better than trying to do it straight on the wav visualisation, and helps prevent accidentally moving them, which happened all the time to me in twisted wave.

    That's funny, you're saying the opposite of the others 😄 It looks like something that I wanted to avoid -- a preferences menu -- might be needed in the future!

    Oh 😂

    It might be cos I’m on iPhone and haven’t tried on iPad yet. I haven’t used twisted wave for ages tbf, but distinctly remember spending ages zooming right in and painstakingly selecting the perfect in out points then losing it all with one miss tap.

    It’s like the piano roll in xequence. So much easier using bigger handles to move the notes around rather than zooming in and out trying to tap on the notes and drag them, without accidentally getting the ‘make smaller’ hit point.

    Yes, I'm generally fond of the "Handles" concept as you can see. But I get others' viewpoints as well. I might offer both in the future and make it configurable. But for now, this is already there and will probably stick to it for the first release.

    If there's any significant sales from the app (i.e. more than EUR 30 per month), I will keep updating it :)

  • @SevenSystems said:

    @espiegel123 said:

    @SevenSystems said:

    @supadom said:
    Incompatible hardware.
    Won’t work on iPhone 6s aka last iPhone with a headphone Jack.

    Can you give me more details? And what iOS version is your iPhone on?

    iPhone 6s can’t go beyond iOS 15

    Thanks. I don't have a device with iOS 15 to test, but I might just enable iOS 15 for the next beta and see if I see any problem reports!

    iOS 15.8.1 Happy to test it for ya

  • @supadom said:

    @SevenSystems said:

    @espiegel123 said:

    @SevenSystems said:

    @supadom said:
    Incompatible hardware.
    Won’t work on iPhone 6s aka last iPhone with a headphone Jack.

    Can you give me more details? And what iOS version is your iPhone on?

    iPhone 6s can’t go beyond iOS 15

    Thanks. I don't have a device with iOS 15 to test, but I might just enable iOS 15 for the next beta and see if I see any problem reports!

    iOS 15.8.1 Happy to test it for ya

    Right, thanks, I do expect problems but it'll be good to confirm. Will try to push out the update today or tomorrow at the latest :)

  • Here's something for the brainstorming list. I think it would be a nice distinguishing feature that I don't think other editors have.

    I'd love to see a "wrap edit". By that I mean a way to move the audio within a selection but have it wrap around, preserving the length of the audio but wrapping the end to the beginning as you move it right and the beginning to the end as you move it left.

    Think of a loop where your timing was early starting it, so that the initial transient is at the end and the start is late. Move the audio to the right until the starting transient wraps around to the beginning and is in the correct position. That kind of thing.

  • Great name btw!
    Just an inspiration? Or is there an acronym in there somewhere?

    My guess is you have a cat that loves to try to walk on your keyboard when you're working.

  • Thanks for sharing and being involved again @SevenSystems

    Sampling is the vast majority of my workflow so I’ll 100% be putting this through its paces. I’m stoked, this looks like it has potential to be my go-to for this kind of thing.

  • @wim said:
    Here's something for the brainstorming list. I think it would be a nice distinguishing feature that I don't think other editors have.

    I'd love to see a "wrap edit". By that I mean a way to move the audio within a selection but have it wrap around, preserving the length of the audio but wrapping the end to the beginning as you move it right and the beginning to the end as you move it left.

    Think of a loop where your timing was early starting it, so that the initial transient is at the end and the start is late. Move the audio to the right until the starting transient wraps around to the beginning and is in the correct position. That kind of thing.

    Haha, exactly what @Samu requested too. I think I need to bump this on the roadmap! 🛣

  • @wim said:
    Great name btw!
    Just an inspiration? Or is there an acronym in there somewhere?

    My guess is you have a cat that loves to try to walk on your keyboard when you're working.

    Well, I never "properly" had a cat, but random cats always appear where I live or even just have my regular walks, and I'm quite fond of them indeed 😊 I actually had a "Meow" startup sound in mind (sampled from one of not-my cats!), but maybe that would be slightly annoying. But I do have something small along those lines for the next beta update...

    No acronym. Just Meow! 'nuff said. 🍻

  • @HotStrange said:
    Thanks for sharing and being involved again @SevenSystems

    Sampling is the vast majority of my workflow so I’ll 100% be putting this through its paces. I’m stoked, this looks like it has potential to be my go-to for this kind of thing.

    Sounds good! I was actually working on the internal "Record" feature today, I hope to be able to squeeze it in until tomorrow.

  • @SevenSystems said:

    @espiegel123 said:

    @SevenSystems said:

    @espiegel123 said:
    I feel like the ruler needs MUCH finer granularity of its labels with easily viewable tickmarks indicating meaningful subdivisions , and the granularity should increase as one zooms in.

    Yes agree. Probably will look into providing something similar to Xequence when in 'Auto' Grid mode. i.e. when you zoom in further, each beat gets divided by 2, then again by 2, etc. (poor people with triplets though!)

    I'd like to be able to calculate BPM from the selection by indicating how many beats are in the selection. If that option is already there, it isn't obvious how to access it. Imo, this is essential for a beats based timeline to really be useful.

    That sounds good and actually straightforward. So just a button in the BPM menu "Get from selection" or something, rounding to maybe 0.5 BPM so you don't have to be extremely precise with your selection?

    No rounding at that granularity..unless there is an option to not. When making and refining a selection that loops perfectly, it is often necessary to have a really precise setting.

    No I mean, when the app calculates the BPM from the selection's length, it should round the BPM to maybe 0.5 or 1 BPM. Otherwise, you'd have to make an extremely precise selection, which would be very tedious. Most music will have a BPM that is spot-on a whole number, or maybe 130.5 BPM. But never 125.824239842. Or an I misunderstanding?

    I think you are misunderstanding. I am talking about the user having made a precise perfectly looping selection. Then telling Meow that the selection is 8 beats long. If you round to 1/2 bpm or 1 bpm, that would be a problem.

  • @SevenSystems said:
    No acronym. Just Meow! 'nuff said. 🍻

    It's very catchy. 👍🏼
    I'll be hunting for the Easter egg that unlocks the Hello Kitty inspired theme.

  • @espiegel123 said:

    @SevenSystems said:

    @espiegel123 said:

    @SevenSystems said:

    @espiegel123 said:
    I feel like the ruler needs MUCH finer granularity of its labels with easily viewable tickmarks indicating meaningful subdivisions , and the granularity should increase as one zooms in.

    Yes agree. Probably will look into providing something similar to Xequence when in 'Auto' Grid mode. i.e. when you zoom in further, each beat gets divided by 2, then again by 2, etc. (poor people with triplets though!)

    I'd like to be able to calculate BPM from the selection by indicating how many beats are in the selection. If that option is already there, it isn't obvious how to access it. Imo, this is essential for a beats based timeline to really be useful.

    That sounds good and actually straightforward. So just a button in the BPM menu "Get from selection" or something, rounding to maybe 0.5 BPM so you don't have to be extremely precise with your selection?

    No rounding at that granularity..unless there is an option to not. When making and refining a selection that loops perfectly, it is often necessary to have a really precise setting.

    No I mean, when the app calculates the BPM from the selection's length, it should round the BPM to maybe 0.5 or 1 BPM. Otherwise, you'd have to make an extremely precise selection, which would be very tedious. Most music will have a BPM that is spot-on a whole number, or maybe 130.5 BPM. But never 125.824239842. Or an I misunderstanding?

    I think you are misunderstanding. I am talking about the user having made a precise perfectly looping selection. Then telling Meow that the selection is 8 beats long. If you round to 1/2 bpm or 1 bpm, that would be a problem.

    OK, I think I get it now. I thought you meant a quick way to set the BPM by setting a quick selection that roughly represents eg. 1 bar and then having the app calculate the roundabout BPM from that, instead of the user slowly adjusting the BPM slider until the grid lines match up with the waveform.

  • @wim said:

    @SevenSystems said:
    No acronym. Just Meow! 'nuff said. 🍻

    It's very catchy. 👍🏼
    I'll be hunting for the Easter egg that unlocks the Hello Kitty inspired theme.

    😄

  • @SevenSystems said:

    @espiegel123 said:

    @SevenSystems said:

    @espiegel123 said:

    @SevenSystems said:

    @espiegel123 said:
    I feel like the ruler needs MUCH finer granularity of its labels with easily viewable tickmarks indicating meaningful subdivisions , and the granularity should increase as one zooms in.

    Yes agree. Probably will look into providing something similar to Xequence when in 'Auto' Grid mode. i.e. when you zoom in further, each beat gets divided by 2, then again by 2, etc. (poor people with triplets though!)

    I'd like to be able to calculate BPM from the selection by indicating how many beats are in the selection. If that option is already there, it isn't obvious how to access it. Imo, this is essential for a beats based timeline to really be useful.

    That sounds good and actually straightforward. So just a button in the BPM menu "Get from selection" or something, rounding to maybe 0.5 BPM so you don't have to be extremely precise with your selection?

    No rounding at that granularity..unless there is an option to not. When making and refining a selection that loops perfectly, it is often necessary to have a really precise setting.

    No I mean, when the app calculates the BPM from the selection's length, it should round the BPM to maybe 0.5 or 1 BPM. Otherwise, you'd have to make an extremely precise selection, which would be very tedious. Most music will have a BPM that is spot-on a whole number, or maybe 130.5 BPM. But never 125.824239842. Or an I misunderstanding?

    I think you are misunderstanding. I am talking about the user having made a precise perfectly looping selection. Then telling Meow that the selection is 8 beats long. If you round to 1/2 bpm or 1 bpm, that would be a problem.

    OK, I think I get it now. I thought you meant a quick way to set the BPM by setting a quick selection that roughly represents eg. 1 bar and then having the app calculate the roundabout BPM from that, instead of the user slowly adjusting the BPM slider until the grid lines match up with the waveform.

    I mean the user carefully adjusts the selection by dragging the start and stop points till the loop is perfect then telling meow: “calculate the bpm from the selection “. The user would need a way to tell more how many beats long the selection is.

  • @espiegel123 said:

    @SevenSystems said:

    @espiegel123 said:

    @SevenSystems said:

    @espiegel123 said:

    @SevenSystems said:

    @espiegel123 said:
    I feel like the ruler needs MUCH finer granularity of its labels with easily viewable tickmarks indicating meaningful subdivisions , and the granularity should increase as one zooms in.

    Yes agree. Probably will look into providing something similar to Xequence when in 'Auto' Grid mode. i.e. when you zoom in further, each beat gets divided by 2, then again by 2, etc. (poor people with triplets though!)

    I'd like to be able to calculate BPM from the selection by indicating how many beats are in the selection. If that option is already there, it isn't obvious how to access it. Imo, this is essential for a beats based timeline to really be useful.

    That sounds good and actually straightforward. So just a button in the BPM menu "Get from selection" or something, rounding to maybe 0.5 BPM so you don't have to be extremely precise with your selection?

    No rounding at that granularity..unless there is an option to not. When making and refining a selection that loops perfectly, it is often necessary to have a really precise setting.

    No I mean, when the app calculates the BPM from the selection's length, it should round the BPM to maybe 0.5 or 1 BPM. Otherwise, you'd have to make an extremely precise selection, which would be very tedious. Most music will have a BPM that is spot-on a whole number, or maybe 130.5 BPM. But never 125.824239842. Or an I misunderstanding?

    I think you are misunderstanding. I am talking about the user having made a precise perfectly looping selection. Then telling Meow that the selection is 8 beats long. If you round to 1/2 bpm or 1 bpm, that would be a problem.

    OK, I think I get it now. I thought you meant a quick way to set the BPM by setting a quick selection that roughly represents eg. 1 bar and then having the app calculate the roundabout BPM from that, instead of the user slowly adjusting the BPM slider until the grid lines match up with the waveform.

    I mean the user carefully adjusts the selection by dragging the start and stop points till the loop is perfect then telling meow: “calculate the bpm from the selection “. The user would need a way to tell more how many beats long the selection is.

    Got it! Thanks!

  • wimwim
    edited February 6

    Don't ever let it in the house. 😂

  • @wim said:
    Don't ever let it in the house. 😂

    😄 awesome. Too late though!

  • wimwim
    edited February 6

    I'm gonna go on record as saying I prefer the tap on the bracket thing for moving the selection over tapping directly on the waveform. I think you'll get lots of requests for tapping on the waveform directly, but IMO that method sucks compared to your method.

    So ... just confirming ... you can't please everyone.

  • @wim said:
    I'm gonna go on record as saying I prefer the tap on the bracket thing for moving the selection over tapping directly on the waveform. I think you'll get lots of requests for tapping on the waveform directly, but IMO that method sucks.

    So ... just confirming ... you can't please everyone.

    👍 yes, I do get both viewpoints. That's why I'll have to add options shmoptions...

  • By the way. Is anyone using Meow with a keyboard and/or mouse? The app has also been designed with desktop in mind, so I'd be happy to hear opinions.

  • With a fade out and/or fade in set, tapping outside the wave-form selection clears the fades.

  • wimwim
    edited February 6

    Will there be any way (or did I just miss it?) to save a project in-process without exporting to a wav file? Often I'm interrupted or want to return to something I was working on earlier.

  • I think the file open and save dialogs should default to the last folder used.

  • @wim said:
    With a fade out and/or fade in set, tapping outside the wave-form selection clears the fades.

    Yes, that's intentional -- the fades are currently cleared on all "major" selection operations:

    • Select All
    • Select None
    • Select Played
    • Drag-Select with mouse

    It's a bit of a tough one. When does the user "intend" to ditch the old fades? I suspect in all of the above scenarios (tapping outside the selection invokes "Select None"). I could of course always leave the fades intact and have the user always clear them manually by dragging, but to me, setting fades is more of a "temporary" thing, like before exporting the selection, or for quickly doing a fade and then hitting "Process -> Apply Fades", so I don't think it would be good if they stayed there all the time, especially not when you switch into a different "mindset", which is indicated by a major selection change.

    That is the reasoning behind this behaviour.

  • @wim said:
    Will there be any way (or did I just miss it?) to save a project in-process without exporting to a wav file? Often I'm interrupted or want to return to something I was working on earlier.

    There is a concept of "Project" in the app including project-related settings etc., but currently there is no way to load or save projects. I might add this at some point, and what definitely will be added for the first release is automatic session restore when the app was killed in the background by iOS.

  • wimwim
    edited February 6

    I've done a fair run-through on the iPad. I'm super impressed so far! It's amazingly responsive and fluid. A real pleasure to use. Enough so that I can pretty much forgive the "no plugin" ethos. 😎

    Next up - testing with keyboard, then on my current iPhone and my retired iPhone 7. I'll fire up the older iPad too.

Sign In or Register to comment.