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.

FRMS - Granular Synthesizer from Imaginando

1…1819212324…26

Comments

  • sinosoidalsinosoidal

    @Identor said:

    @sinosoidal said:

    @Identor said:
    Just installed on iPhone X. The stand-alone version got overlapping menu items. It all look cluttered. The onscreen keyboard takes almost half of the screen. Would be better to have the option to hide the keyboard to get more screen real-estate.

    Can you please share a screenshot?

    Sorry for the late reply. Here are the screenshots:





    It is just a normal iPhone X.

    It would be Cool to see the waveform and the knobs in one screen as an option (no keyboard)

    Thanks for sharing this screenshots. We will see what we can do. :blush:

  • sinosoidalsinosoidal

    @Identor said:

    @sinosoidal said:

    @Identor said:
    Just installed on iPhone X. The stand-alone version got overlapping menu items. It all look cluttered. The onscreen keyboard takes almost half of the screen. Would be better to have the option to hide the keyboard to get more screen real-estate.

    Can you please share a screenshot?

    Sorry for the late reply. Here are the screenshots:





    It is just a normal iPhone X.

    It would be Cool to see the waveform and the knobs in one screen as an option (no keyboard)

    Are you on the TestFlight?

  • celtic_elkceltic_elk

    An idle question: how are we meant to pronounce FRMS? "Frames"? "Forms"? "Firimus"? "For a mess"?

  • SamuSamu

    @celtic_elk said:
    An idle question: how are we meant to pronounce FRMS? "Frames"? "Forms"? "Firimus"? "For a mess"?

    Based on the sound design videos so far I think it's 'Frames' :sunglasses:

  • celtic_elkceltic_elk

    @Samu said:

    @celtic_elk said:
    An idle question: how are we meant to pronounce FRMS? "Frames"? "Forms"? "Firimus"? "For a mess"?

    Based on the sound design videos so far I think it's 'Frames' :sunglasses:

    Which I suppose corresponds nicely with the UI design. Still, there's a part of me that wants to be contrary and refer to it as "For-a-moose" or something. Since my wife is the only person likely to ever hear me say that out loud, it hardly matters. :D

  • sinosoidalsinosoidal
    edited October 2021

    @celtic_elk said:

    @Samu said:

    @celtic_elk said:
    An idle question: how are we meant to pronounce FRMS? "Frames"? "Forms"? "Firimus"? "For a mess"?

    Based on the sound design videos so far I think it's 'Frames' :sunglasses:

    Which I suppose corresponds nicely with the UI design. Still, there's a part of me that wants to be contrary and refer to it as "For-a-moose" or something. Since my wife is the only person likely to ever hear me say that out loud, it hardly matters. :D

    I'm glad you asked. We have just published this :blush:

  • celtic_elkceltic_elk

    @sinosoidal :D :D :D

  • PoppadocrockPoppadocrock
    edited October 2021

    Beta versions dropping like whoa! Lol. Fine by me.

  • Philandering_BastardPhilandering_Bastard

    @celtic_elk said:

    @Samu said:

    @celtic_elk said:
    An idle question: how are we meant to pronounce FRMS? "Frames"? "Forms"? "Firimus"? "For a mess"?

    Based on the sound design videos so far I think it's 'Frames' :sunglasses:

    Which I suppose corresponds nicely with the UI design. Still, there's a part of me that wants to be contrary and refer to it as "For-a-moose" or something. Since my wife is the only person likely to ever hear me say that out loud, it hardly matters. :D

    This is now canon. For a moose.

  • celtic_elkceltic_elk

    @Philandering_Bastard said:

    @celtic_elk said:

    @Samu said:

    @celtic_elk said:
    An idle question: how are we meant to pronounce FRMS? "Frames"? "Forms"? "Firimus"? "For a mess"?

    Based on the sound design videos so far I think it's 'Frames' :sunglasses:

    Which I suppose corresponds nicely with the UI design. Still, there's a part of me that wants to be contrary and refer to it as "For-a-moose" or something. Since my wife is the only person likely to ever hear me say that out loud, it hardly matters. :D

    This is now canon. For a moose.

    My most enduring contribution to ABF culture, no doubt. ;)

  • _ki_ki
    edited October 2021

    @sinosoidal For the last n beta‘s (woo-hoo, they are comming in really fast) i noticed that the ‚favorite‘ icon doesn‘t show up in the preset browser if a patch has a long list of tags.

    For the standalone on my iPad Pro 10.5, i found the following examples: Most of the patches of the „Supremeja“ pack have a long tag list and these don‘t show the icon - but the preset „Like Candy SJA“ with just 7 tags shows the ‚favorite“ icon when selecting the preset. In the ‚Glitches’ bank the preset „Perplex On - Pads for love“ is just able to show the icon moved to the right border.

    .

    The problem is very easy to reproduce with the AUv3 in AUM:

    In the AUv3, open the preset browser , choose the ‚Glitches‘ bank and select the first patch ‚Perplex On - Binareal Eyes‘. For the default AUv3 window size in AUM, the fav icon is visible. Now shrink the width of the window step-by-step and when the icon gets nearer to the tag list, it starts to shifted to the right to keep a distance to the end of the tag-list. One is able to detect the mimal width when icon starts to get clipped at the right border:

    The same icon-shift-and-clipping happens, if the patch name is longer than it‘s taglist and the window width gets smaller.

    .

    Maybe just ignore the fact that tags/names and icon might overlapp, just draw it above :) I suspect that the tags are still readable, as they are positioned a bit lower. For super-long names only a few letters will be affected.

  • _ki_ki

    @sinosoidal Nearly forgot: I only noticed that moving fav-icon problem, because i want to hunt down another problem with the favorites. I have lots and lots of them pointing into the purchased libaries, but when an update hit and i had to re-load the packs, these favorites didn‘t update. I can‘t select them (or delete them). At one time i started to set them up again - and another update hit and resulted in two unselectable versions marked as n/a (not available) even though the bank is there :)

  • sinosoidalsinosoidal

    @_ki said:
    @sinosoidal For the last n beta‘s (woo-hoo, they are comming in really fast) i noticed that the ‚favorite‘ icon doesn‘t show up in the preset browser if a patch has a long list of tags.

    For the standalone on my iPad Pro 10.5, i found the following examples: Most of the patches of the „Supremeja“ pack have a long tag list and these don‘t show the icon - but the preset „Like Candy SJA“ with just 7 tags shows the ‚favorite“ icon when selecting the preset. In the ‚Glitches’ bank the preset „Perplex On - Pads for love“ is just able to show the icon moved to the right border.

    .

    The problem is very easy to reproduce with the AUv3 in AUM:

    In the AUv3, open the preset browser , choose the ‚Glitches‘ bank and select the first patch ‚Perplex On - Binareal Eyes‘. For the default AUv3 window size in AUM, the fav icon is visible. Now shrink the width of the window step-by-step and when the icon gets nearer to the tag list, it starts to shifted to the right to keep a distance to the end of the tag-list. One is able to detect the mimal width when icon starts to get clipped at the right border:

    The same icon-shift-and-clipping happens, if the patch name is longer than it‘s taglist and the window width gets smaller.

    .

    Maybe just ignore the fact that tags/names and icon might overlapp, just draw it above :) I suspect that the tags are still readable, as they are positioned a bit lower. For super-long names only a few letters will be affected.

    @_ki said:
    @sinosoidal Nearly forgot: I only noticed that moving fav-icon problem, because i want to hunt down another problem with the favorites. I have lots and lots of them pointing into the purchased libaries, but when an update hit and i had to re-load the packs, these favorites didn‘t update. I can‘t select them (or delete them). At one time i started to set them up again - and another update hit and resulted in two unselectable versions marked as n/a (not available) even though the bank is there :)

    Thanks for reporting. I've already submitted 1.4.2 for review on App Store. We will leave this fixes for the next iteration. :blush:

  • RockBottomRockBottom
    edited October 2021

    I launched frms today and noticed that the bicho preset was replicated 6 times in the factory bank:


    My frms copy is version 1.4.1; is there a way I can restore the factory bank without losing the other custom banks or the favorites?

  • sinosoidalsinosoidal

    @RockBottom said:
    I launched frms today and noticed that the bicho preset was replicated 6 times in the factory bank:


    My frms copy is version 1.4.1; is there a way I can restore the factory bank without losing the other custom banks or the favorites?

    We have released 1.4.2 yesterday which should fix a few problem inluding this one. Can you please try it and let me know? :blush:

  • RockBottomRockBottom
    edited October 2021

    okay, updated — now frms 1.4.2 sees only 2 identical copies of bicho in the factory bank:


    Is this expected?

  • PxlhgPxlhg

    I get a lot of crashes when working/creating in the latest release. Very abrupt but not sure what I'm doing to cause it

  • sinosoidalsinosoidal

    @Pxlhg said:
    I get a lot of crashes when working/creating in the latest release. Very abrupt but not sure what I'm doing to cause it

    Hi. Are you using 1.4.1 or 1.4.2 that came out on Friday?

  • sinosoidalsinosoidal

    @RockBottom said:
    okay, updated — now frms 1.4.2 sees only 2 identical copies of bicho in the factory bank:


    Is this expected?

    If Bicho was the preset that was selected before closing the app, then yes, it is expected as it means it was state restore that put it there.

  • RockBottomRockBottom

    Ah, thank you: this bolsters my confidence!

  • PxlhgPxlhg
    edited October 2021

    @sinosoidal said:

    @Pxlhg said:
    I get a lot of crashes when working/creating in the latest release. Very abrupt but not sure what I'm doing to cause it

    Hi. Are you using 1.4.1 or 1.4.2 that came out on Friday?

    1.4.2
    I had done some new imports and worked from default state to do something fresh. But, as I said before I can't really tell what preceded the crashes. I'll test some more when I can. :)

  • sinosoidalsinosoidal

    @Pxlhg said:

    @sinosoidal said:

    @Pxlhg said:
    I get a lot of crashes when working/creating in the latest release. Very abrupt but not sure what I'm doing to cause it

    Hi. Are you using 1.4.1 or 1.4.2 that came out on Friday?

    1.4.2
    I had done some new imports and worked from default state to do something fresh. But, as I said before I can't really tell what preceded the crashes. I'll test some more when I can. :)

    Thanks for the feedback. Maybe you could install 1.4.2 from TestFlight. If it keeps crashing we have better crash reports to analyze.

  • IdentorIdentor

    @sinosoidal Thanks for the update, it fits now on my iPhone X.
    There's only 1 workflow issue i have. I constantly have to switch between the waveform and control window with every tweak i do, especially when tweaking size and offset. It would be cool to alternate between the keyboard and a downsized version of the waveform, so you could see directly at the waveform when tweaking.

  • PxlhgPxlhg
    edited October 2021

    @sinosoidal said:

    @Pxlhg said:

    @sinosoidal said:

    @Pxlhg said:
    I get a lot of crashes when working/creating in the latest release. Very abrupt but not sure what I'm doing to cause it

    Hi. Are you using 1.4.1 or 1.4.2 that came out on Friday?

    1.4.2
    I had done some new imports and worked from default state to do something fresh. But, as I said before I can't really tell what preceded the crashes. I'll test some more when I can. :)

    Thanks for the feedback. Maybe you could install 1.4.2 from TestFlight. If it keeps crashing we have better crash reports to analyze.

    I'm no longer on the Beta.
    Now, I started a new session with some freshly made samples I made, one happened to be 2124* and thus not within the limit. When I pressed yes on the deletion confirmation dialog - the app crashed. I'll do some more work tonight because this was not the cause the last time, see if something else comes up.

    *Audioshare, for one, doesn't show the detailed decimals so you just get 2.0Mb (see image) and thus thinks it's ok. Happened to me too many times, any chance you could add some tolerance there? Say a 2-300 but it still says max 2Mb of course. :)

  • sinosoidalsinosoidal
    edited October 2021

    @Pxlhg said:
    Now, I started a new session with some freshly made samples I made, one happened to be 2124* and thus not within the limit. When I pressed yes on the deletion confirmation dialog - the app crashed.

    I didn't get this one. If the sample was not accepted due to file size limit, why did you need to delete it? Sorry, can you please clarify?

    We have some crash reports. From what I can see, the crash can occur during sample loading/unloading while playing, this can also occur while playing and changing preset. There aren't many crash, but the problem is there. If you find a sistematic way of reproducing it, please let me know.

    *Audioshare, for one, doesn't show the detailed decimals so you just get 2.0Mb (see image) and thus thinks it's ok. Happened to me too many times, any chance you could add some tolerance there? Say a 2-300 but it still says max 2Mb of course. :)

    We might raise the limit a bit further in future releases.

  • PxlhgPxlhg
    edited October 2021

    @sinosoidal said:

    @Pxlhg said:
    Now, I started a new session with some freshly made samples I made, one happened to be 2124* and thus not within the limit. When I pressed yes on the deletion confirmation dialog - the app crashed.

    I didn't get this one. If the sample was not accepted due to file size limit, why did you need to delete it? Sorry, can you please clarify?

    It accepts to be imported and it's not until you try to use it you get the prompt that the size is not accepted so there is no need to have it remain in an already very long list and beside that; it also takes up space, right?. FRMS takes up 919MB on my machine. I did not delete it from the folder I originally saved it to.

    We have some crash reports. From what I can see, the crash can occur during sample loading/unloading while playing, this can also occur while playing and changing preset. There aren't many crash, but the problem is there. If you find a sistematic way of reproducing it, please let me know.

    *Audioshare, for one, doesn't show the detailed decimals so you just get 2.0Mb (see image) and thus thinks it's ok. Happened to me too many times, any chance you could add some tolerance there? Say a 2-300 but it still says max 2Mb of course. :)

    We might raise the limit a bit further in future releases.

    Sounds good. :)

  • joegrant413joegrant413

    Just bought this late last night. My 1274th synth app.

    Swear this the last one. For awhile.

  • sinosoidalsinosoidal

    @Pxlhg said:

    @sinosoidal said:

    @Pxlhg said:
    Now, I started a new session with some freshly made samples I made, one happened to be 2124* and thus not within the limit. When I pressed yes on the deletion confirmation dialog - the app crashed.

    I didn't get this one. If the sample was not accepted due to file size limit, why did you need to delete it? Sorry, can you please clarify?

    It accepts to be imported and it's not until you try to use it you get the prompt that the size is not accepted so there is no need to have it remain in an already very long list and beside that; it also takes up space, right?. FRMS takes up 919MB on my machine. I did not delete it from the folder I originally saved it to.

    We have some crash reports. From what I can see, the crash can occur during sample loading/unloading while playing, this can also occur while playing and changing preset. There aren't many crash, but the problem is there. If you find a sistematic way of reproducing it, please let me know.

    *Audioshare, for one, doesn't show the detailed decimals so you just get 2.0Mb (see image) and thus thinks it's ok. Happened to me too many times, any chance you could add some tolerance there? Say a 2-300 but it still says max 2Mb of course. :)

    We might raise the limit a bit further in future releases.

    Sounds good. :)

    We have recently uploaded 1.4.3 (build 60) which should fix the crashes that were happening. Please tell me if you can notice the difference.

  • PxlhgPxlhg

    @sinosoidal said:

    @Pxlhg said:

    @sinosoidal said:

    @Pxlhg said:
    Now, I started a new session with some freshly made samples I made, one happened to be 2124* and thus not within the limit. When I pressed yes on the deletion confirmation dialog - the app crashed.

    I didn't get this one. If the sample was not accepted due to file size limit, why did you need to delete it? Sorry, can you please clarify?

    It accepts to be imported and it's not until you try to use it you get the prompt that the size is not accepted so there is no need to have it remain in an already very long list and beside that; it also takes up space, right?. FRMS takes up 919MB on my machine. I did not delete it from the folder I originally saved it to.

    We have some crash reports. From what I can see, the crash can occur during sample loading/unloading while playing, this can also occur while playing and changing preset. There aren't many crash, but the problem is there. If you find a sistematic way of reproducing it, please let me know.

    *Audioshare, for one, doesn't show the detailed decimals so you just get 2.0Mb (see image) and thus thinks it's ok. Happened to me too many times, any chance you could add some tolerance there? Say a 2-300 but it still says max 2Mb of course. :)

    We might raise the limit a bit further in future releases.

    Sounds good. :)

    We have recently uploaded 1.4.3 (build 60) which should fix the crashes that were happening. Please tell me if you can notice the difference.

    Yeah, that one has not come to the store just yet, i.e here in Sweden. I have been working quite a lot lately with FRMS (1.4.2) and it's been pretty stable. There are some sound issues sometimes going to right channel only but a restart of the app fixes that, I think it's a certain preset I been working on that causes it every time. I'll get back to you on that when I have some time for it.
    I did a pretty heavy project in AUM using 5 instances FRMS with some pretty heavy presets and it works fine which is awesome. It's such a cool synth.
    I'll keep an eye open for the update, thank you :)

  • sinosoidalsinosoidal

    @Pxlhg said:

    @sinosoidal said:

    @Pxlhg said:

    @sinosoidal said:

    @Pxlhg said:
    Now, I started a new session with some freshly made samples I made, one happened to be 2124* and thus not within the limit. When I pressed yes on the deletion confirmation dialog - the app crashed.

    I didn't get this one. If the sample was not accepted due to file size limit, why did you need to delete it? Sorry, can you please clarify?

    It accepts to be imported and it's not until you try to use it you get the prompt that the size is not accepted so there is no need to have it remain in an already very long list and beside that; it also takes up space, right?. FRMS takes up 919MB on my machine. I did not delete it from the folder I originally saved it to.

    We have some crash reports. From what I can see, the crash can occur during sample loading/unloading while playing, this can also occur while playing and changing preset. There aren't many crash, but the problem is there. If you find a sistematic way of reproducing it, please let me know.

    *Audioshare, for one, doesn't show the detailed decimals so you just get 2.0Mb (see image) and thus thinks it's ok. Happened to me too many times, any chance you could add some tolerance there? Say a 2-300 but it still says max 2Mb of course. :)

    We might raise the limit a bit further in future releases.

    Sounds good. :)

    We have recently uploaded 1.4.3 (build 60) which should fix the crashes that were happening. Please tell me if you can notice the difference.

    Yeah, that one has not come to the store just yet, i.e here in Sweden. I have been working quite a lot lately with FRMS (1.4.2) and it's been pretty stable. There are some sound issues sometimes going to right channel only but a restart of the app fixes that, I think it's a certain preset I been working on that causes it every time. I'll get back to you on that when I have some time for it.

    It was not released to the store yet. It is on TestFlight! :blush:

    I did a pretty heavy project in AUM using 5 instances FRMS with some pretty heavy presets and it works fine which is awesome. It's such a cool synth.

    Glad to hear! :blush:

    I'll keep an eye open for the update, thank you :)

    :blush:

Sign In or Register to comment.