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.

miRack by mifki Limited - Live!!!

18911131482

Comments

  • edited September 2019

    As far as recording out of the app goes, remember that iOS screen recorder in iOS13 / iPadOS now supports stereo!

  • @mifki double-tap to open the browser is nice. I actually tried that when I fired mirack for the 1st time.

    Maybe a bit far fetched but what about module to load auv3 in the future? I know plugins like auv3 aren’t made for audiorate modulation but still.

  • @Michael_R_Grant said:
    As far as recording out of the app goes, remember that iOS screen recorder in iOS13 / iPadOS now supports stereo!

    Ah, thanks @Michael_R_Grant ! Didn't know that. Makes it all the more useful.

  • edited September 2019

    @Jocphone said:

    @Michael_R_Grant said:
    As far as recording out of the app goes, remember that iOS screen recorder in iOS13 / iPadOS now supports stereo!

    Ah, thanks @Michael_R_Grant ! Didn't know that. Makes it all the more useful.

    I assumed it wasn't like that originally because of Youtube et al. Surprised and happy... will have to test to see if any apps block it.

  • edited September 2019

    The UI is quite good already, pretty snappy as it is, except for the zooming/scrolling but I tend to make small patches anyways.

    I have a question though. Will it ever have a midi out Module converting cv signal to midi CC? Would be fun to use my midi to cv converter to interface with mother32 and 0-coast.

    Also, I take back what I said about long press, in some case it might be useful. I use an apple pencil to build patches and bringing the pop up menu with a long press on any areas that are not a knob or button or -atch point could be nice.

  • edited September 2019

    @Michael_R_Grant said:
    As far as recording out of the app goes, remember that iOS screen recorder in iOS13 / iPadOS now supports stereo!

    what is fastest way to extract audio from recorded video, directly in iPad - is it possible for example in iMovie ?

  • @dendy said:

    @Michael_R_Grant said:
    As far as recording out of the app goes, remember that iOS screen recorder in iOS13 / iPadOS now supports stereo!

    what is fastest way to extract audio from recorded video, directly in iPad - is it possible for example in iMovie ?

    There may be better ways but I found this which seems to work

    https://www.guidingtech.com/extract-audio-from-video-ios/

    The first suggestion using Shortcuts, I was able to get it to convert to M4A and ask where to save the audio file.

  • cool thanks

  • Open the screen recording in AudioShare. Save as wav.

  • I've published a new update:

    • Double tap on a control to reset its value.
    • Double tap or touch with two fingers on an empty space to show the module browser and place a new module at that location.
    • Fixed an issue with long module menus not fitting the screen in landscape mode. Now the menus are scrollable.
    • Fixed incorrect behaviour of Zoom to Fit X Rows and Reset Zoom functions in some cases.
    • Changed Fundamental panels look and updated some of the component graphics.
    • Returned back the original Befaco panel graphics.
    • Fixed a crash when opening some incorrectly formatted or corrupted files.

    Sorry, dealing with the licensing stuff took all my time, I didn't add support for opening zipped patches are I promised. Will do it next time.

  • @mifki said:
    I've published a new update:

    • Double tap on a control to reset its value.
    • Double tap or touch with two fingers on an empty space to show the module browser and place a new module at that location.
    • Fixed an issue with long module menus not fitting the screen in landscape mode. Now the menus are scrollable.
    • Fixed incorrect behaviour of Zoom to Fit X Rows and Reset Zoom functions in some cases.
    • Changed Fundamental panels look and updated some of the component graphics.
    • Returned back the original Befaco panel graphics.
    • Fixed a crash when opening some incorrectly formatted or corrupted files.

    Sorry, dealing with the licensing stuff took all my time, I didn't add support for opening zipped patches are I promised. Will do it next time.

    Well Done!

    How far off in time is the built-in Audio Recorder?
    (For me personally It would be enough to just to be able to record the audio output to a folder with a patch name & time-stamp as the filename and maybe with some options for sample-rate and bit-depth).

  • @Samu said:
    How far off in time is the built-in Audio Recorder?

    I'll start working on it next. I guess it will require a bit more testing than the previous changes.

    Would it be useful to have some sort of a built-in action recorder? That would record control and cable changes, show them on a timeline, and obviously replay later.

  • Would it be useful to have some sort of a built-in action recorder? That would record control and cable changes, show them on a timeline, and obviously replay later.

    don't think something sophisticated is needed.. but ok, simple Undo/Redo would be handy in some situation.. but i think there are other more inportant things..

    simple audio recorder, ideally with trigger input so it willbe possible stsrt recording for example with note ON and stop it with note OFF would be game changer for many people...

  • @mifki said:

    @Samu said:
    How far off in time is the built-in Audio Recorder?

    I'll start working on it next. I guess it will require a bit more testing than the previous changes.

    Would it be useful to have some sort of a built-in action recorder? That would record control and cable changes, show them on a timeline, and obviously replay later.

    That would almost be like a form of gesture record?

  • For recording, I think something like Audiobus or IAA integration would be ideal since that opens the possibilities of using miRack with other audio apps on iOS. Or is something like that planned for later? This would be more of a v1 for audio recording?

  • @mifki said:

    @Samu said:
    How far off in time is the built-in Audio Recorder?

    I'll start working on it next. I guess it will require a bit more testing than the previous changes.

    Would it be useful to have some sort of a built-in action recorder? That would record control and cable changes, show them on a timeline, and obviously replay later.

    That would be a ‘bonus’, a simple record output to file (patch name=time.wav) would be enough.
    Ideally recording should start when the rack starts to produce audio.
    Optionally the start and stop could be synced to a clock for creating loops.

    Being able to set the output folder could also be handy to avoid file overload (ie. a separate ‘Recordings’ folder).

    Some might need an option to use multiple recorders in the rack for more complex setups and multi channel mixing of the outputs files in a DAW.

    I’d be happy with just a basic tape recorder with manual start and stop.

  • Simple internal recorder would suffice imo. Audiobus routing would be REALLY awesome. Would make recording into our app of choice a dream.

  • @mifki said:
    I've published a new update:

    • Double tap on a control to reset its value.
    • Double tap or touch with two fingers on an empty space to show the module browser and place a new module at that location.
    • Fixed an issue with long module menus not fitting the screen in landscape mode. Now the menus are scrollable.
    • Fixed incorrect behaviour of Zoom to Fit X Rows and Reset Zoom functions in some cases.
    • Changed Fundamental panels look and updated some of the component graphics.
    • Returned back the original Befaco panel graphics.
    • Fixed a crash when opening some incorrectly formatted or corrupted files.

    Sorry, dealing with the licensing stuff took all my time, I didn't add support for opening zipped patches are I promised. Will do it next time.

    Thank you !

  • @mifki said:

    @Samu said:
    How far off in time is the built-in Audio Recorder?

    I'll start working on it next. I guess it will require a bit more testing than the previous changes.

    Would it be useful to have some sort of a built-in action recorder? That would record control and cable changes, show them on a timeline, and obviously replay later.

    I don't even need an internal recorder. If it could connect to audiobus, I could use a recorder I already have :)

  • Purchased this app days ago and I’ve had zero free time of any length to dig in to this. It’s killing me!

  • @mifki I keep accidentally moving modules that I don't want to move... then it gets kinda fiddly to move them back. Once I get them were I want them... wish I could sorta temporarily lock them down or something.

  • Thanks for the impending update :)

    There seems to be recorder modules available for VCV, it seems to make sense to add anything like that as modules.
    eg this has trigger recording https://steemit.com/utopian-io/@buckydurddle/vcv-rack-simple-recorder

    Then you can choose what to record in the patch rather than the whole output or then you can record multiple streams.

    And then also add on Audiobus support etc :)

    @espiegel123 said:

    @mifki said:

    @Samu said:
    How far off in time is the built-in Audio Recorder?

    I'll start working on it next. I guess it will require a bit more testing than the previous changes.

    Would it be useful to have some sort of a built-in action recorder? That would record control and cable changes, show them on a timeline, and obviously replay later.

    I don't even need an internal recorder. If it could connect to audiobus, I could use a recorder I already have :)

  • @Carnbot said:
    Thanks for the impending update :)

    There seems to be recorder modules available for VCV, it seems to make sense to add anything like that as modules.
    eg this has trigger recording https://steemit.com/utopian-io/@buckydurddle/vcv-rack-simple-recorder

    Then you can choose what to record in the patch rather than the whole output or then you can record multiple streams.

    And then also add on Audiobus support etc :)

    @espiegel123 said:

    @mifki said:

    @Samu said:
    How far off in time is the built-in Audio Recorder?

    I'll start working on it next. I guess it will require a bit more testing than the previous changes.

    Would it be useful to have some sort of a built-in action recorder? That would record control and cable changes, show them on a timeline, and obviously replay later.

    I don't even need an internal recorder. If it could connect to audiobus, I could use a recorder I already have :)

    Didn't know this existed. Something like this would be perfect as v1.

  • The idea to record a performance as actions is a separate thing, it doesn't affect the work on audio recording that will be done first.

    I'll add audio recording to the app first. I know many of you suggest that supporting AudioBus would be a simpler way, but in fact that would require more work and more testing to ensure compatibility. I'll likely implement my own recording module, it's easier than to port any of the existing ones to iOS.

    @skiphunt said:
    @mifki I keep accidentally moving modules that I don't want to move... then it gets kinda fiddly to move them back. Once I get them were I want them... wish I could sorta temporarily lock them down or something.

    There's a Lock Modules option in the Tools menu.

  • IAA though defecated, would also allow recording in hosts.
    I’m I right to assume that since it is sort of the basic routing architecture used by apple, that it should be simpler to implement?

  • @Philippe said:
    IAA though defecated, would also allow recording in hosts.
    I’m I right to assume that since it is sort of the basic routing architecture used by apple, that it should be simpler to implement?

    I’m sorry but I can’t just ignore “defecated”. :)

  • edited September 2019

    @mifki said:
    I know many of you suggest that supporting AudioBus would be a simpler way, but in fact that would require more work and more testing to ensure compatibility. I'll likely implement my own recording module, it's easier than to port any of the existing ones to iOS.

    in the spirit of modular, I do hope that eventually the Audiobus SDK is added so that audio and midi can more easily be routed to and fro in real time. I don't really use any apps as an island to themselves.

    Mirack will only get a lot of use in my case if I can use it in tandem with other hardware and softwares.

  • Any plans for giving it auv3 hosting?

  • edited September 2019

    @Philippe said:
    I’m I right to assume that since it is sort of the basic routing architecture used by apple, that it should be simpler to implement?

    Not quite so. First, both things are relatively simple to implement. IAA/AudioBus, in fact, a bit harder than in-app recording because I need to ensure compatibility with third-party apps which always requires more development and testing.

    However I mentioned many times before is that the main reason why I don't rush to add IAA/AudioBus support is any potential performance issues.

    miRack's excellent performance is achieved by using two audio processing threads working at high priority. So both cores on non-Pro iPads are taken and not too much CPU resources are left for other audio apps.

    I understand that 1. iPad Pros have 4 cores, so this should not be a problem at all, 2. recording and other simple audio processing should be fine even on 2-core devices, and 3. it's up to users to not create patches and IAA configurations that their hardware can not support. However, people will still complain about it. I can not limit IAA to audio recording only or to Pro models only or to small patches only, so I do not want to add it until I make sure that the user experience will be good in all usage scenarios. Please understand.

  • This is actually very good reasoning.

Sign In or Register to comment.