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

1246717

Comments

  • edited February 7

    @nuno_agogo said:
    no audio from meeow. loaded mp3 and wav file formats. the cursor ist moving but no sound.

    ipad 6th gen, ipadOS 16.7.2

    Hey. Can you try disabling the "Mute" switch as @Krupa suggested? It's a years old bug in an Apple framework Meow is using and I don't think they're up to fixing it...

  • @Shabudua said:

    @espiegel123 said:

    @SevenSystems said:

    @espiegel123 said:
    Can one paste audio from the system clipboard to start a file?

    No, the clipboard is currently internal to the app, but I have using the system clipboard on my list! Currently, you can either drag & drop or use "Open".

    Being able to get data into and out of the app via the system clipboard would enormously increase the app’s utility for me…making it a convenient adjunct to Loopy Pro

    +1. For Meow to be really useful to me, I need to be able to get clips to/from other apps with maximum speed and minimum effort.

    Definitely! System clipboard support will be coming. It might be slightly slower than the internal clipboard for very large selections, so I might add a switch for toggling between the two.

  • @Samu said:
    @SevenSystems At some point I’m going to be requesting sustain loop-editing for creating instrument samples, loop-metadata is usually stored in the ‘smpl’ chunk within a .wav file.

    You can already loop very short sections and adjust by individual samples... there was also ping-pong looping, but I ditched it again for the time being... is ping-pong used a lot in practice? Probably for longer loops like pads etc...

    This will likely happen when the app gets built-in recording capabilities, input-selection etc.

    I hope to push an update out today with basic recording, for now only using the current default input.

    When that time comes a ‘keyboard’ to audtion the sample at various pitches (or slices) might also come in handy.

    Sorry, I think I would consider this outside the scope for the app for the midterm 🥵 but it all depends on the sales!

  • edited February 7

    @Samu said:
    @SevenSystems I think I've bumped into a nasty one...

    After I've made a selection using the Apple Pencil and try to use my fingers to 'pinch zoom' the waveform the UI kinda gets 'locked up'. I can no longer move the start/end brackets and after a while trying to use the other icons to select all, or zoom selection etc. I get this freaky error message :sunglasses:

    Here's one of the crash-logs that follow after the 'lockup'.

    Cheers!

    Thanks! Only the second proper crash reported so far 🥳 you've somehow managed to move the playhead to an invalid position while penning! Will investigate.

    And the freaky error message is part of my app framework's AMAZING crash handler! Other apps would just crash to the Homescreen 😄😉

  • @SevenSystems said:

    You can already loop very short sections and adjust by individual samples... there was also ping-pong looping, but I ditched it again for the time being... is ping-pong used a lot in practice? Probably for longer loops like pads etc...

    I never use ping-pong looping as it creates an annoying 'pulsating' sound when the sample gets pitched up, same with cross-
    fade looping...

    I know I can play short loops, but think playing the file from start of the file to the 'sustain loop' like regular instruments.

    I hope to push an update out today with basic recording, for now only using the current default input.

    Goodie, in that case we most definitely would need a 'mono conversion' and/or 'channel selection' that allows us to pick Left, Right or Mix/Stereo as most connected devices that become 'default inputs' will be stereo and when recording a mono-source (input 1 or 2) we would end up with a stereo recording which could be a 'dual mono' or 'stereo' depending on if the primary input channel can be selected.

    Sorry, I think I would consider this outside the scope for the app for the midterm 🥵 but it all depends on the sales!

    Gotcha, no need to add, it's just 'wishful thinking' :sunglasses:

    Cheers!

  • @Samu said:

    @SevenSystems said:

    You can already loop very short sections and adjust by individual samples... there was also ping-pong looping, but I ditched it again for the time being... is ping-pong used a lot in practice? Probably for longer loops like pads etc...

    I never use ping-pong looping as it creates an annoying 'pulsating' sound when the sample gets pitched up, same with cross-
    fade looping...

    I know I can play short loops, but think playing the file from start of the file to the 'sustain loop' like regular instruments.

    Ah yes gotcha. It's not trivial because of Meow's architecture, when the loop is enabled, it actually limits many internal processes to the selected range, that includes playback. But I will keep it in mind!

    I hope to push an update out today with basic recording, for now only using the current default input.

    Goodie, in that case we most definitely would need a 'mono conversion' and/or 'channel selection' that allows us to pick Left, Right or Mix/Stereo as most connected devices that become 'default inputs' will be stereo and when recording a mono-source (input 1 or 2) we would end up with a stereo recording which could be a 'dual mono' or 'stereo' depending on if the primary input channel can be selected.

    OK, that does sound useful.

    In the first iteration, the recording feature will always resample to the sample rate of the current file, and just merge stereo channels to mono if the current file is mono, or duplicate mono channels to stereo if the current file is stereo. If there is no current file yet, it will keep the input channels and sample rate.

    Note that you can already do channel shenenigans in Process -> Channels (those always apply to the whole file though, not just the selection)

    So even without channel selection, you could already do the following if, say, you want to only keep the left channel:

    • Record
    • Process -> Channels -> Mono L
    • Edit -> Copy
    • Undo
    • Edit -> Paste

    But yeah, not straightforward!

  • edited February 7

    @SevenSystems said:

    @nuno_agogo said:
    no audio from meeow. loaded mp3 and wav file formats. the cursor ist moving but no sound.

    ipad 6th gen, ipadOS 16.7.2

    Hey. Can you try disabling the "Mute" switch as @Krupa suggested? It's a years old bug in an Apple framework Meow is using and I don't think they're up to fixing it...

    Was having the same issue of no audio coming out from iPhone 12 mini speaker .. I can confirm that disabling mute switch on side of phone solved it. Thanks.

  • edited February 7

    @SevenSystems said:

    @nuno_agogo said:
    no audio from meeow. loaded mp3 and wav file formats. the cursor ist moving but no sound.

    ipad 6th gen, ipadOS 16.7.2

    Hey. Can you try disabling the "Mute" switch as @Krupa suggested? It's a years old bug in an Apple framework Meow is using and I don't think they're up to fixing it...

    ok, i disabled the mute. now there is sound. but it is very cluttered, the type of sound your hear when very low buffer sizes are used.

    edit: the effect is stronger when playing mp3 instead of wav file format.

  • @nuno_agogo said:

    @SevenSystems said:

    @nuno_agogo said:
    no audio from meeow. loaded mp3 and wav file formats. the cursor ist moving but no sound.

    ipad 6th gen, ipadOS 16.7.2

    Hey. Can you try disabling the "Mute" switch as @Krupa suggested? It's a years old bug in an Apple framework Meow is using and I don't think they're up to fixing it...

    ok, i disabled the mute. now there is sound. but it is very cluttered, the type off sound your hear when very low buffer sizes are used.

    edit: the effect is stronger when playing mp3 instead of wav file format.

    The sound is fine for me. What sample rate was your audio? What sample rate is your hardware using?

  • @nuno_agogo said:
    ok, i disabled the mute. now there is sound. but it is very cluttered, the type off sound your hear when very low buffer sizes are used.

    Yes, this is a known problem on older devices, I get the same on my 2017 iPad Pro unless I force a larger buffer size. I will look into bumping it up for the next update :)

  • Congratulations on the new app @SevenSystems I’ll give it a go. Cheers!

  • @Poppadocrock said:
    Congratulations on the new app @SevenSystems I’ll give it a go. Cheers!

    🤘

  • Oh, looking for an opinion here regarding the automatic crossfades:

    They currently default to 'Off' both for Edit and Process operations. I used to have them both at 20 ms as default, but I thought maybe not having "unexpected" stuff happening in the background would be wiser.

    What does everyone think, should they stay off for new default projects, or if not, what would be reasonable defaults (in ms)?

  • edited February 7

    @SevenSystems said:
    Oh, looking for an opinion here regarding the automatic crossfades:

    They currently default to 'Off' both for Edit and Process operations. I used to have them both at 20 ms as default, but I thought maybe not having "unexpected" stuff happening in the background would be wiser.

    What does everyone think, should they stay off for new default projects, or if not, what would be reasonable defaults (in ms)?

    Have I understood it correctly that the automatic crossfade would be applied when doing copy/paste operations and to avoid glitches when processing a selection?

  • @Samu said:

    @SevenSystems said:
    Oh, looking for an opinion here regarding the automatic crossfades:

    They currently default to 'Off' both for Edit and Process operations. I used to have them both at 20 ms as default, but I thought maybe not having "unexpected" stuff happening in the background would be wiser.

    What does everyone think, should they stay off for new default projects, or if not, what would be reasonable defaults (in ms)?

    Have I understood it correctly that the automatic crossfade would be applied when doing copy/paste operations and to avoid glitches when processing a selection?

    Exactly, and they can be both set separately in the respective menus. Open for any tweak suggestions here...

    (the 'Process' crossfade area is also visualized in a slight gradient in the selection overlay)

  • @SevenSystems said:
    Oh, looking for an opinion here regarding the automatic crossfades:

    They currently default to 'Off' both for Edit and Process operations. I used to have them both at 20 ms as default, but I thought maybe not having "unexpected" stuff happening in the background would be wiser.

    What does everyone think, should they stay off for new default projects, or if not, what would be reasonable defaults (in ms)?

    I’d probably make the default be off AND have a few tips panels at first startup that mentions this and other important defaults.

  • @espiegel123 said:

    @SevenSystems said:
    Oh, looking for an opinion here regarding the automatic crossfades:

    They currently default to 'Off' both for Edit and Process operations. I used to have them both at 20 ms as default, but I thought maybe not having "unexpected" stuff happening in the background would be wiser.

    What does everyone think, should they stay off for new default projects, or if not, what would be reasonable defaults (in ms)?

    I’d probably make the default be off AND have a few tips panels at first startup that mentions this and other important defaults.

    Yes, will definitely do.

  • Loop point edition is not included?

  • @espiegel123 said:

    @SevenSystems said:
    Oh, looking for an opinion here regarding the automatic crossfades:

    They currently default to 'Off' both for Edit and Process operations. I used to have them both at 20 ms as default, but I thought maybe not having "unexpected" stuff happening in the background would be wiser.

    What does everyone think, should they stay off for new default projects, or if not, what would be reasonable defaults (in ms)?

    I’d probably make the default be off AND have a few tips panels at first startup that mentions this and other important defaults.

    +1 for defaulting to off.
    20ms seems like a long time for default crossfade. I would think more like 2ms - just enough to reduce clicks.

    Off topic:

    I hate to bring up the "A" word, but Audacity has an amazingly useful "fix" function where you can highlight a small portion of audio and it automatically removes glitches in that section. It makes you select a small enough section of audio that it thinks it can successfully handle. It works great.

    I used it to remove pops from some old vinyls and I couldn't believe how well it worked.

  • @cokomairena said:
    Loop point edition is not included?

    You mean storing loop points in the Metadata of a saved file? Then no, that's currently not supported.

  • I tried it today and it’s really smooth.
    No crashes here at all.
    @samu’s and @wim’s suggestions
    are bang on.

    Nice one.

  • edited February 7

    @wim said:

    @espiegel123 said:

    @SevenSystems said:
    Oh, looking for an opinion here regarding the automatic crossfades:

    They currently default to 'Off' both for Edit and Process operations. I used to have them both at 20 ms as default, but I thought maybe not having "unexpected" stuff happening in the background would be wiser.

    What does everyone think, should they stay off for new default projects, or if not, what would be reasonable defaults (in ms)?

    I’d probably make the default be off AND have a few tips panels at first startup that mentions this and other important defaults.

    +1 for defaulting to off.

    OK

    20ms seems like a long time for default crossfade. I would think more like 2ms - just enough to reduce clicks.

    I think there's two distinct uses for them:

    • Avoid clicks, very short
    • Make smoother audible transitions between processed portions, or when cutting/pasting stuff around, for example in vocals. Longer.

    I hate to bring up the "A" word

    😁

    but Audacity has an amazingly useful "fix" function where you can highlight a small portion of audio and it automatically removes glitches in that section. It makes you select a small enough section of audio that it thinks it can successfully handle. It works great.

    I used it to remove pops from some old vinyls and I couldn't believe how well it worked.

    Maybe outside the scope of Meow for now. But you might have luck with crossfade 😊 and Edit -> Delete, or Process -> Filter -> Lowpass.

  • @Gravitas said:
    I tried it today and it’s really smooth.
    No crashes here at all.

    Wait until the next beta is out! 😂 (no, it should actually improve things.)

    @samu’s and @wim’s suggestions
    are bang on.

    Nice one.

    🤘

  • New Beta has been sent to Apple and hopefully gets approved. I'll be on a family visit for a few days so won't be able to be around here that much. But everything will be closely watched and monitored! 😊

    CHANGELOG:

    We have enabled experimental iOS 15 support. If you are on iOS 15, please let us know if everything's working.

    IMPROVEMENTS:

    • Don't needlessly restart playback when toggling 'Snap' doesn't change anything.
    • Edit -> Trim: Keep playhead position if it was in the trimmed region before trimming.
    • Clear fades when dragging a new selection.
    • The 'Tempo' slider now shows two decimal places. The tempo can be set to any accuracy by tapping on the slider and entering a value.
    • Added a bell to the cat.
    • Better handling of empty buffer.

    FIXES:

    • Fix white lines in UI when using light system theme.
    • Fix menus hanging around when app is resized.
    • Fix occasional crash while moving selection handles.
    • Fix occasional disappearance of playhead until the next time 'Play' is pressed.
    • Fix occasional flickering while dragging file into the editor.
    • Fix crash when importing a file with an unsupported sample rate.
    • Fix layout glitch when changing system text size.
    • Prevent erratic behaviour when fingers crossed during pinch zoom.
    • Prevent zero-length selections and associated crashes.
    • When enabling Loop while playhead is outside the selection, move it to beginning.
  • @SevenSystems : the welcome screen says something about pressing Record. Is there a record button somewhere that I am not seeing?

    In the Save panel, it would be nice to have option of selection or whole file.

    Playback stops when switching out of Meow.

  • @espiegel123 said:
    @SevenSystems : the welcome screen says something about pressing Record. Is there a record button somewhere that I am not seeing?

    Oh, sorry, forgot to remove that again. The 'Record' feature is almost done, but I have decided to skip it in this beta still.

    In the Save panel, it would be nice to have option of selection or whole file.

    I'm a bit hesitant to add a switch for this (technically easy) -- you can achieve the same by tapping on 'Select All' in the bottom toolbar first?

    Playback stops when switching out of Meow.

    Yes, I didn't plan on including background playback for now. It's a bit of technical overhead on iOS.

  • @SevenSystems said:

    @espiegel123 said:ave decided to skip it in this beta still.

    In the Save panel, it would be nice to have option of selection or whole file.

    I'm a bit hesitant to add a switch for this (technically easy) -- you can achieve the same by tapping on 'Select All' in the bottom toolbar first?

    For me, it would be a drag to lose my selection order to save the whole file.

  • @espiegel123 said:

    @SevenSystems said:

    @espiegel123 said:ave decided to skip it in this beta still.

    In the Save panel, it would be nice to have option of selection or whole file.

    I'm a bit hesitant to add a switch for this (technically easy) -- you can achieve the same by tapping on 'Select All' in the bottom toolbar first?

    For me, it would be a drag to lose my selection order to save the whole file.

    You can undo after saving! 😜 (Undo includes all selection operations, not just actual modifications)

  • Love the name

  • @SevenSystems Toggling loop on/of momentarily interrupts playback.

    Recording doesn’t work (apps should on first run ask for permission to use the microphone).

    Kinda puzzling that 8Khz samples are supported but 24Khz and 32Khz samples pop up an error message.
    I get it that in order for filters etc to work a somewhat realiably a fixed sample rate is needed.

    Maybe add an option to ‘auto convert’ to preferred sample-rate and skip the error popup?

    An option to ‘close’ the current file could be handy to ‘start fresh’ without having to quit and relaunch the app.

    I have a suggestion for ‘alternate zoom gesture’ (total rip-off from Twisted Wave), swipe up to zoom in and swipe down to zoom out. Auditor also uses this gesture.

    A double-tap on the waveform could fully zoom out as this saves a trip to the toolbars and keeps focus.

    I’ll try to keep the suggestion relevant to the app with speed and usability in focus.

    Cheers!

Sign In or Register to comment.