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!!!

1111214161782

Comments

  • edited September 2019

    @dendy said:

    Keep miRack away from AU hosting, keep it closed platform - it helps you keep it stable, efficient - and invest that time rather to adding app features and more interesting modules. Hands away from AU hosting.

    Can't agree more. Having Host module in VCV about 6 months I honestly used it 5 or 6 times. I think it's because eurorack has a lot to offer on its own, vcv is pretty covered in almost every area (except for distortion/saturation), and basic workflow with multiple popup windows just doesn't fit modular "all-in-one-place" approach.
    So if you would ask me, I'm in for more modules (valley! geodesics! maths!), built-in recorder and midi/link sync options.

  • @david_2017 said:

    @mifki said:
    Hey, one of the beta-testers reported degraded performance after upgrading iPad Pro 11" to iPadOS. Has anyone else noticed this?

    Let some time pass. Right after the Update the os is doing still stuff in the background (See battery life)... performances can be influenced by this also i think. So ask him to wait a day and see if these degraded performance will continue

    Hi,
    I'm the one reporting the performance degradation.
    I did that after 3 days from upgrading and compared performance differences between 2 different models: ipad pro 9.7 2016 (no degradation) vs ipad pro 11 2018 (degradation from 12.4.1).
    Today I'll update to 13.1.1 and in a few days I'll report an updated situation.

    Cheers
    GF

  • edited September 2019

    @dendy said:

    @mifki said:
    Several people asked about future possibility of hosting AUv3 modules inside miRack.

    I personally don't really like this idea because I'd prefer miRack to stay focused on Eurorack format / be seen as a Eurorack synth and not turn into a universal DAW. However if such support is done as just one of the modules, I don't see any problems with it and may even consider developing such a module myself.

    Ok, here is my opinion about this topic.

    Just don't go that way.

    One reason:
    If i good remember, miRack is internally locked to 44khz and it is resampling to device sample rate just final output - this would be first and major issue if you introduce AU hosting. Nanostudio 2 used same strategy at beginning (simply because it is standard solution used by desktop hosts), but in iOS world in combination with AU plugins this doesn't work. Many plugins implements improperly sample rate handling, they ignore sample rate set by host and they use always device sample rate. You can imagine issues which arise from this. At the end you will realize, that you need to give up and rework internal processing to adapt (in realtime - because sample rate switches between 44 and 48 on all devices with jack connector when you plug/unplug headphones ) to device sample rate.

    In general - AU hosting introduces crashes, problems, and lot of work including lot of communication with plugin devs. Until you will be not sure you have months for fine tuning this feature - don't do it. There is lot of unreliable plugins and you will spend lot of precious dev time by trying to solve why "this particular plugin is not crashing my app".

    Keep miRack away from AU hosting, keep it closed platform - it helps you keep it stable, efficient - and invest that time rather to adding app features and more interesting modules. Hands away from AU hosting.

    Mirack pitches correctly at 96khz. Personally I'm not fussed if mirack can have a specific module which is an auv3 but i think you are scare mongering here and you haven’t even developed an ios music app to my knowledge. I would just let the dev do his thing. Im not even sure if what the dev posted even suggested full auv3 hosting.

  • Well I was one who suggested that. My reasoning was more along the lines that there are plenty of nice fx already made to be used. Honestly it doesn't really matter. I'm definitely more interested in Eurorack modules than anything else. Even original ones you can come up with. My personal favorite would be blamsoft, nysthi or vult but they are closed source. Only Nysthi seems to have proposed something which is really nice. (he's super nice dude anyhow). This is too much of a nice project to be ignored by the VCV community. Anyways who no matter. I'm glad with what is available right now. Worth every penny.

    Cheers.

    p.s. Don't really care if this ever makes it into an AuV3. It is nice as it is. Some connectivity with other apps would be interesting though like some have suggested.

    @mifki said:
    Several people asked about future possibility of hosting AUv3 modules inside miRack.

    I personally don't really like this idea because I'd prefer miRack to stay focused on Eurorack format / be seen as a Eurorack synth and not turn into a universal DAW. However if such support is done as just one of the modules, I don't see any problems with it and may even consider developing such a module myself.

  • edited September 2019

    @[Deleted User] said:
    Mirack pitches correctly at 96khz.

    Yes, reason is (as @mifki mentioned) miRack is processing internally everything at 44khz sample rate and then only resamples output final audio stream to 48khz or 96khz if it is requested by device HW output

    With introducing AU plugins hosting, problem will arise, because some AU plugins are ignoring host sample rate, and they use sometimes 44, sometimes 48 - based on default device sample rate. And then there are also issues with buffer size handling in some plugins (especially if buffer is changed during playback or mixdown)..

    you haven’t even developed an ios music app to my knowledge.

    this is true, just to put things in context - i'm developer too, it's my job for 20+ years, although no ios audio apps.. But i have some basic knowledge about DSP coding too, plus i'm often discussing about implementation details and coding related issues needed to be solved with one unnamed coder of unnamed iOS AU host app ;-) ... so, i have at least a bit of theoretic knowledge :)

    I would just let the dev do his thing.

    Just wanted to add my 5 cents based on my experience and knowledge, that's all ..

    Im not even sure if what the dev posted even suggested full auv3 hosting.

    i replied to this:

    @mifki said:
    However if such support is done as just one of the modules, I don't see any problems with it and may even consider developing such a module myself.

  • @dendy said:

    @[Deleted User] said:
    Mirack pitches correctly at 96khz.

    i think you are scare mongering here and you haven’t even developed an ios music app to my knowledge.

    this is true, just to put things in context - i'm developer too, it's my job for 20+ years, although no ios audio apps.. But i have some basic knowledge about DSP coding too, plus i'm often discussing about implementation details and coding related issues needed to be solved with one unnamed coder of unnamed iOS AU host app ;-) ...

    With all due respect you saying you are a developer doesn't have much weight unless i can see what you have produced in regards to creating ios music app or any other software you created yourself. Indeed you help out beta testing for ios music apps (awesome work too 👍) which i do sometimes also but this unrelated to programing.

    Again in regards to dev discussing full auv3 hosting, i don’t believe he specifically said that was the plan and maybe there is a different way or form it can be implemented.

  • edited September 2019

    @mifki said:
    That person (I guess he's from here too) was saying only his 11" iPad Pro is affected, so other model reports do not help sorry.

    Well, you asked if "anyone else" had experienced problems. You didn't specify anyone else with an 11in. Sorry our non-11in feedback didn't help. Won't bother next time.

  • @[Deleted User] said:

    @dendy said:

    @mifki said:
    Several people asked about future possibility of hosting AUv3 modules inside miRack.

    I personally don't really like this idea because I'd prefer miRack to stay focused on Eurorack format / be seen as a Eurorack synth and not turn into a universal DAW. However if such support is done as just one of the modules, I don't see any problems with it and may even consider developing such a module myself.

    Ok, here is my opinion about this topic.

    Just don't go that way.

    One reason:
    If i good remember, miRack is internally locked to 44khz and it is resampling to device sample rate just final output - this would be first and major issue if you introduce AU hosting. Nanostudio 2 used same strategy at beginning (simply because it is standard solution used by desktop hosts), but in iOS world in combination with AU plugins this doesn't work. Many plugins implements improperly sample rate handling, they ignore sample rate set by host and they use always device sample rate. You can imagine issues which arise from this. At the end you will realize, that you need to give up and rework internal processing to adapt (in realtime - because sample rate switches between 44 and 48 on all devices with jack connector when you plug/unplug headphones ) to device sample rate.

    In general - AU hosting introduces crashes, problems, and lot of work including lot of communication with plugin devs. Until you will be not sure you have months for fine tuning this feature - don't do it. There is lot of unreliable plugins and you will spend lot of precious dev time by trying to solve why "this particular plugin is not crashing my app".

    Keep miRack away from AU hosting, keep it closed platform - it helps you keep it stable, efficient - and invest that time rather to adding app features and more interesting modules. Hands away from AU hosting.

    Mirack pitches correctly at 96khz. Personally I'm not fussed if mirack can have a specific module which is an auv3 but i think you are scare mongering here and you haven’t even developed an ios music app to my knowledge. I would just let the dev do his thing. Im not even sure if what the dev posted even suggested full auv3 hosting.

    Trevor, I am a former music software developer (though not iOS) and think I have a pretty good understanding of development details that a number of iOS music developers have shared publicly and privately. To a person, they have mentioned the challenges of being an AU host . It is a major headache. Each host has to work around quirks of individual AUs.

    AU and host developers often disagree about whether some problems are plugin, host or OS related. Every app I know of that supports AU and native plugins become less stable when AU hosting rather than using their native plugins.

    And I wouldn't be surprised if making mirack an AU host would reduce its impressive CPU efficiency if the architecture were changed to accommodate AU even if one doesn't use that capability.

    Obviously, the dev gets to make the call, but if he hasn’t implemented iOS AU hosting before, he might not realize what he is in for..some pretty capable developers have been surprised as to how much work it is and how hard it is to accommodate even just the most popular AU’s quirks.

  • edited September 2019

    @[Deleted User] So, is particle physicist not allowed to talk about problems of building particle accelerator, until he didn't build one with his own hands ? :)

    @espiegel123
    some pretty capable developers have been surprised as to how much work it is and how hard it is to accommodate even just the most popular AU’s quirks.

    This !

  • .

    @dendy said:
    @[Deleted User] So, is particle physicist not allowed to talk about problems of building particle accelerator, until he didn't build one with his own hands ? :)

    Are you a particle physicist too? 😉

  • I can see why people want AUv3 hosting but I still think my preference if I could choose one over the other, it would be miRack as an AUv3 itself. Now that we have (reportedly) unrestricted memory for AUs it should be a lot easier to make anything an AUv3 now so it's only the desire and time to make it standing in the way. :)

    This keeps the workflow separate and contained in an instance from other iOS midi and synth apps but able to combine it in a host much more easily. The zoomable gui is also perfect for AUv3 already.

    Just my opionion, but I see VCV is becoming officially VST next year and I think this is a better fit for it, making it more host friendly. :)

  • @Carnbot said:
    I can see why people want AUv3 hosting but I still think my preference if I could choose one over the other, it would be miRack as an AUv3 itself. Now that we have (reportedly) unrestricted memory for AUs it should be a lot easier to make anything an AUv3 now so it's only the desire and time to make it standing in the way. :)

    This keeps the workflow separate and contained in an instance from other iOS midi and synth apps but able to combine it in a host much more easily. The zoomable gui is also perfect for AUv3 already.

    Just my opionion, but I see VCV is becoming officially VST next year and I think this is a better fit for it, making it more host friendly. :)

    AUv3 would likely reduce the CPU efficiency significantly as well as the complexity of racks you can create. Dev mentioned that he makes use of parallel processing in a way that hosts can but plugins can't.

  • edited September 2019

    I can't see miRack being an AU easily though I too would love this. I have Softube Modular on desktop and it's practically unusable on my machine, which is really annoying given how much I have spent on it.

    I know nothing about DSP but making something like this resource efficient seems hard.

    So order of priority for me would be:

    1) recording module

    2) multi-audio out for audio interfaces with ADAT or hardware audio outputs

    3) AU hosting - would love to use to AU synths with module filters/modulation modules and sequencers

    4) miRack AU

  • @Carnbot said:
    I can see why people want AUv3 hosting but I still think my preference if I could choose one over the other, it would be miRack as an AUv3 itself. Now that we have (reportedly) unrestricted memory for AUs it should be a lot easier to make anything an AUv3 now so it's only the desire and time to make it standing in the way. :)

    This keeps the workflow separate and contained in an instance from other iOS midi and synth apps but able to combine it in a host much more easily. The zoomable gui is also perfect for AUv3 already.

    Just my opionion, but I see VCV is becoming officially VST next year and I think this is a better fit for it, making it more host friendly. :)

    I feel like making it auv3 would involve so much more programming than just adding an auv3 module would. I feel like connections between modules would be easier to follow if this were just a host and everything is contained within the app. It would be a lot more cpu efficient as well

  • edited September 2019

    @auxmux said:
    I can't see miRack being an AU easily though I too would love this. I have Softube Modular on desktop and it's practically unusable on my machine, which is really annoying given how much I have spent on it.

    I know nothing about DSP but making something like this resource efficient seems hard.

    So order of priority for me would be:

    1) recording module

    2) multi-audio out for audio interfaces with ADAT or hardware audio outputs

    3) AU hosting - would love to use to AU synths with module filters/modulation modules and sequencers

    4) miRack AU

    I like this list.

    By the way, I don't think users need to be protective of devs when they make a suggestion. I think the devs are capable of assimilating and filtering ideas, and sometimes improving upon them and then delighting their users - without user forum oversight. What serves devs most, I think, is a clearly stated idea for a new feature, enhancement, or capability. Then they, the devs, can figure out the whether, how, and when.

  • @espiegel123 said:

    @Carnbot said:
    I can see why people want AUv3 hosting but I still think my preference if I could choose one over the other, it would be miRack as an AUv3 itself. Now that we have (reportedly) unrestricted memory for AUs it should be a lot easier to make anything an AUv3 now so it's only the desire and time to make it standing in the way. :)

    This keeps the workflow separate and contained in an instance from other iOS midi and synth apps but able to combine it in a host much more easily. The zoomable gui is also perfect for AUv3 already.

    Just my opionion, but I see VCV is becoming officially VST next year and I think this is a better fit for it, making it more host friendly. :)

    AUv3 would likely reduce the CPU efficiency significantly as well as the complexity of racks you can create. Dev mentioned that he makes use of parallel processing in a way that hosts can but plugins can't.

    Maybe yes, although I'm not saying it would be easy to code. If Audulus 4 can be either host and plugin which is planned then so could miRack. I wouldn't mind losing some performance to have it in AUM etc :)

    The plugins could then be as simple or as complex as the host / ipad could manage.

  • @Carnbot said:

    @espiegel123 said:

    @Carnbot said:
    I can see why people want AUv3 hosting but I still think my preference if I could choose one over the other, it would be miRack as an AUv3 itself. Now that we have (reportedly) unrestricted memory for AUs it should be a lot easier to make anything an AUv3 now so it's only the desire and time to make it standing in the way. :)

    This keeps the workflow separate and contained in an instance from other iOS midi and synth apps but able to combine it in a host much more easily. The zoomable gui is also perfect for AUv3 already.

    Just my opionion, but I see VCV is becoming officially VST next year and I think this is a better fit for it, making it more host friendly. :)

    AUv3 would likely reduce the CPU efficiency significantly as well as the complexity of racks you can create. Dev mentioned that he makes use of parallel processing in a way that hosts can but plugins can't.

    Maybe yes, although I'm not saying it would be easy to code. If Audulus 4 can be either host and plugin which is planned then so could miRack. I wouldn't mind losing some performance to have it in AUM etc :)

    The plugins could then be as simple or as complex as the host / ipad could manage.

    Audulus is an interesting example. For those that aren't aware, the dev spent a year (more?) working on making Audulus AUv3 capable and thought he was close to being done when he realized that he needed to basically re-architect most of the app to make it possible. I think we are now a year after that re-implementation started and the app is still not close to being done. I look forward to Audulus 4 happening, but we still have no idea how well it will work as an AU and whether it will run on iPads that aren't high-powered. The AU-ification has been a long detour and no idea how long that detour will end up having been. And all that from a guy who has been deep in iOS DSP programming for years.

    miRack is impressive in what it can do without needing the best iPad.

  • @espiegel123 said:

    @Carnbot said:

    @espiegel123 said:

    @Carnbot said:
    I can see why people want AUv3 hosting but I still think my preference if I could choose one over the other, it would be miRack as an AUv3 itself. Now that we have (reportedly) unrestricted memory for AUs it should be a lot easier to make anything an AUv3 now so it's only the desire and time to make it standing in the way. :)

    This keeps the workflow separate and contained in an instance from other iOS midi and synth apps but able to combine it in a host much more easily. The zoomable gui is also perfect for AUv3 already.

    Just my opionion, but I see VCV is becoming officially VST next year and I think this is a better fit for it, making it more host friendly. :)

    AUv3 would likely reduce the CPU efficiency significantly as well as the complexity of racks you can create. Dev mentioned that he makes use of parallel processing in a way that hosts can but plugins can't.

    Maybe yes, although I'm not saying it would be easy to code. If Audulus 4 can be either host and plugin which is planned then so could miRack. I wouldn't mind losing some performance to have it in AUM etc :)

    The plugins could then be as simple or as complex as the host / ipad could manage.

    Audulus is an interesting example. For those that aren't aware, the dev spent a year (more?) working on making Audulus AUv3 capable and thought he was close to being done when he realized that he needed to basically re-architect most of the app to make it possible. I think we are now a year after that re-implementation started and the app is still not close to being done. I look forward to Audulus 4 happening, but we still have no idea how well it will work as an AU and whether it will run on iPads that aren't high-powered. The AU-ification has been a long detour and no idea how long that detour will end up having been. And all that from a guy who has been deep in iOS DSP programming for years.

    miRack is impressive in what it can do without needing the best iPad.

    Yeah I look forward to it as well when it lands, hope he can pull it off. I do like it when high powered ipads are targeted though, if that's what is necessary for it to exist. I think having software worth upgrading your hardware for is good for the market, just like it is on desktop land. Although I know, since the market is much smaller developers need to cover as much of the different models as possible.

  • edited September 2019

    Maybe this will contradict what I said myself earlier about AudioBus support, but now I'm thinking I'm not worried about compatibility that much in relation to AUv3 hosting as long as it doesn't require engine changes that would affect the performance and stability when AUv3 is not in use. This feature is a bit different to AudioBus and is not as widely requested and would not be as widely used as IAA/AudioBus support, so I think it can be available on "use at your own risk" basis. Just like I can not guarantee that 100% of other "normal" modules don't have any issues. If a unit that someone wants works for them, fine, if not, well, it's not supported.

  • Wow, nice! Yes, please!

  • edited September 2019

    @mifki said:
    Maybe this will contradict what I said myself earlier about AudioBus support, but now I'm thinking I'm not worried about compatibility that much in relation to AUv3 hosting as long as it doesn't require engine changes that would affect the performance and stability when AUv3 is not in use. This feature is a bit different to AudioBus and is not as widely requested and would not be as widely used as IAA/AudioBus support, so I think it can be available on "use at your own risk" basis. Just like I can not guarantee that 100% of other "normal" modules don't have any issues. If a unit that someone wants works for them, fine, if not, well, it's not supported.

    Interesting 👍

  • @mifki Thank you very much for trying! If it doesn't make your hair go all grey then that's very welcome of course. But expect people to complain anyway when something goes wrong, you know, the more you give the more we'll want :D

  • I tried several random effect units from the App Store, they seem to work (but it will be tricky to confirm that the audio they produce is exactly what it should be). What are some other popular units I can try to see if any of them have more obvious issues?

  • @mifki said:
    I tried several random effect units from the App Store, they seem to work (but it will be tricky to confirm that the audio they produce is exactly what it should be). What are some other popular units I can try to see if any of them have more obvious issues?

    A good way to check if auv3 units are pitching incorrectly is to run the ipad on a audio device at 96khz, its easier to detect the change of pitch at this sample rate.

  • Have you tried any midi auv3 stuff ? Like Rozeta or StepPolyArp

  • @mifki said:
    I tried several random effect units from the App Store, they seem to work (but it will be tricky to confirm that the audio they produce is exactly what it should be). What are some other popular units I can try to see if any of them have more obvious issues?

    Eventide Series ie Blackhole, FAC Bandit, Audio Damage ones, 4Pocket Ones to name just a few of many.

  • @reasOne said:
    Have you tried any midi auv3 stuff ? Like Rozeta or StepPolyArp

    Good call, a midi auv3 like Rozeta would be a good test.

  • Nope my small test implementation only has audio support atm.

  • Here’s some free AUs for testing:

    AU Instruments:

    Spectrum Synthesizer Bundle
    SynthMaster Player
    ROLI NOISE
    Blamsoft (Viking Synth)
    Primer

    AU Effects:

    Spectrum Synthesizer Bundle
    Neon Silicon (CuSnP, GyroVibe, LRC5, PhaseDelayArray)
    Blamsoft (DC-9, F-16, Resampler, Zero Chorus, Zero Reverb)
    Audio Damage (FuzzPlus 3, Rough Rider 2)
    DLYM
    Svep
    Stereo Lag Time
    Tonebridge

    AU MIDI Processors:

    Physicles
    MIDISpy - No MIDI Thru!
    StreamByter
    MFX Monitor - With MIDI Thru!
    Apps using JUCE: K7d, DLYM, Beatformer,

  • Hi, does anyone have audio glitch problems with iPad Pro 2015 12.9" and iOS 11.3.1? Here I have audio glitch on miRack even if I load really simple patch (eg: vco-1> vcf> vca> env> twelve-key taken from Fundamental modules) trought internal speaker or with headphones or an audiocard (UCX Fireface).
    iPad is fresh of restart and in airplane mode.
    iPad Pro 2015 12.9" - iOS 11.3.1
    Tato

Sign In or Register to comment.