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.

Ruismaker - AU Drum Synthesizer

17810121320

Comments

  • edited June 2016

    That is TwistedWave app problem! Not the AUM recorder recording problem. :)

    AUM internal recording has no problem.

  • @Kaikoo2 said:
    That is TwistedWave app problem! Not the AUM recorder recording problem. :)

    AUM internal recording has no problem.

    NB. Twisted Wave was not used to record the sound :D

    So even when ModStep is 'Linked' it would be nice to be able to adjust the time-offset of the midi it sends.
    Oh well, I can still use Cubasis and 'freeze' the Ruismaker tracks to avoid this 'problem'.

    I've been using Trackers for too long so I almost expect sample-accurate timing of everything...

  • @samu ,

    I tested AUM hosting Ruisaker AU and DM2 IAA. Modstep only do midi sequencing and send notes to AUM.

    By recording AUM recorder with Link to Modstep, I then send original copy straight from Audioshare to Auria Pro to investigate the timing.

    I only do initial beat trimming inside Auria Pro, then I compare both the 1/4th beats. What I found is that there are very tiny milliseconds beats differences on each of their own notes. Even though that is something should not be there, but they are all within range as a whole, there won't be forever drifting away beats there!

    So I guess you are too picky on those 100.00000% shots!

    So I would not complain about any this things to developers.

    Cheers

    The upper track on photo is Ruis beats; lower one is DM2 beats.

  • Good to know...

    The reason I reacted was that I was about to create a 'loop library' but the clicks at the start and end of the recordings made that idea die. So in order to make it work better I need to record multiple bars and manually trim out the loop in the middle to make sure no sounds or transients are cut out :(

    I use the midi time-offset in Cubasis to cure some of the problem when recording IAA-Generators. With IAA-Instruments the freezing is mostly spot-on and well AU freezing in Cubasis is mostly flawless too so I expected the AU recording in ModStep to work at least as good as it works in Cubasis, guess we can't have everything :)

  • @Samu said:
    Good to know...

    The reason I reacted was that I was about to create a 'loop library' but the clicks at the start and end of the recordings made that idea die. So in order to make it work better I need to record multiple bars and manually trim out the loop in the middle to make sure no sounds or transients are cut out :(

    I use the midi time-offset in Cubasis to cure some of the problem when recording IAA-Generators. With IAA-Instruments the freezing is mostly spot-on and well AU freezing in Cubasis is mostly flawless too so I expected the AU recording in ModStep to work at least as good as it works in Cubasis, guess we can't have everything :)

    I think you might have misunderstood what kaikoo was trying to tell you. AUM does latency compensation. Modstep does not. So what most of us do is send only midi to au/IAA hosted in AUM. Best of both worlds that way.

  • >

    I think you might have misunderstood what kaikoo was trying to tell you. AUM does latency compensation. Modstep does not. So what most of us do is send only midi to au/IAA hosted in AUM. Best of both worlds that way.

    There is still need adjust the midi-delay by a few ms (found it in ModSteps tempo-settings) to avoid the 'wrap-around' effect. It's only a few ms to avoid the 'click' at the end of the loop recorded using Ruismaker hosted inside AUM fed with midi from ModStep.

    So ~2ms negative compensation in ModStep makes the Ruismaker loops recorded with AUM 'perfect'...

  • I am thoroughly confused about trying to use Ruismaker with Modstep's drum mode and my Akai MPD226 midi controller.

    If I have Modstep in melody mode, so the piano roll is a piano layout, everything works fine. I have Ruismaker in GM mode. I create a Modstep pad layout that has the first 8 pads mapped to Ruismakers GM layout (C2, D2, D#2, A2, C3, D3, F#2, A#2). I create the same mapping on my MPD pads. Everything is fine. Pad one on MPD triggers kick in Modstep piano roll and kick in Ruis:

    However, if I put Modstep in drum mode, so the piano roll has a drum layout, everything is wonky. Hitting kick on pad 1 on my MPD (C2) triggers G#4 in Modstep. Hitting snare on pad 2 on the MPD (D2) plays A#4 in Modstep, so it's transposing it by the same number of unwanted steps for every pad.

    Here is a screenshot of me sending it C2 but it highlighting G#4:

  • edited June 2016

    @Samu said:

    >

    I think you might have misunderstood what kaikoo was trying to tell you. AUM does latency compensation. Modstep does not. So what most of us do is send only midi to au/IAA hosted in AUM. Best of both worlds that way.

    There is still need adjust the midi-delay by a few ms (found it in ModSteps tempo-settings) to avoid the 'wrap-around' effect. It's only a few ms to avoid the 'click' at the end of the loop recorded using Ruismaker hosted inside AUM fed with midi from ModStep.

    So ~2ms negative compensation in ModStep makes the Ruismaker loops recorded with AUM 'perfect'...

    Yes, Master Sergeant!

    Should I give you a 'wind gauge'?

  • @brambos said:

    Tapping the name to change the pad instrument to say 'cowbell' or 'rim' - does that simply change the parameters on that pad or does it actually get in and change the core synth engine for that pad to something different?

    That's indeed what happens. Every sound has its own unique engine. It's more or less like in the TR-8: every sound emulates its own set of 'virtual hardware components on a virtual circuit board'.

    This has two major advantages: the sounds are not limited to what can be done with a one-size-fits-all general purpose synth engine. And no processing power is wasted on generic code overhead (hence the low CPU usage of Ruismaker).

    Does your modeling expertise lend itself to other kinds of instruments? Like say a DX7 II emulation? :) o:)

  • @Samu while your discussion of 2ms compensation of timing in recordings may seem tedious to some, there is no reason to not get it right if you know what you're after and it can be done. The nature of timing errors is that they accumulate over time and the minuscule can become large enough to where you hear the difference.

    Manually adjusting recordings to fix timing issues can be very tedious as well so being able to figure out how to do so in settings is ultimately less tedious as it can be done once rather than to every recording created with a setup having less than desired timing. If you're recording multiple sources driven by the same MIDI source, your post timing editing tasks will be further compounded so your advice and solutions in this regard, I would think, can help many struggling to get all of their sound sources in sync with each other.

  • @InfoCheck said:
    @Samu while your discussion of 2ms compensation of timing in recordings may seem tedious to some, there is no reason to not get it right if you know what you're after and it can be done. The nature of timing errors is that they accumulate over time and the minuscule can become large enough to where you hear the difference.

    Manually adjusting recordings to fix timing issues can be very tedious as well so being able to figure out how to do so in settings is ultimately less tedious as it can be done once rather than to every recording created with a setup having less than desired timing. If you're recording multiple sources driven by the same MIDI source, your post timing editing tasks will be further compounded so your advice and solutions in this regard, I would think, can help many struggling to get all of their sound sources in sync with each other.

    I know you have good writing! Thank you for your after thoughts. From my view, you guys has many false thinking. I urge you to re-think what you are thinking and doing. I am not try to break your hearts here, hopefully you all playing happily with Modstep. If I want to explain many things here from my experiences with Modstep, I think I would make it too annoying for you to see the truth about this timing with many false assumptions here, because I have practically tried what being said and known what is not known for many users. I wrote many tutorials, of which all are not trying to dig something un-learnable. I will not write a tutorial on this midi timing subject which is inconclusive and unhelpful. So please forgive me to poking around here.

  • MIDI timing on iOS is a really complicated thing, and very few apps do it properly. The thing is, a sequencer must send MIDI events in advance, with correct timestamps. The receiver of the events then can process them in time for the corresponding buffer render cycle. But to receive the events in advance through CoreMIDI virtual ports, one has to take care of a couple of things, and the standard ways of connecting virtual MIDI ports in most apps will ruin it by delaying the events until their timestamp comes (thus removing the "in advance" part of the equation). This is something I'm still working on finding a "best way" for, which I will then share with any interested developers. For now, current AUM version does not propagate these timestamps perfectly when coming through a virtual MIDI port and into an AU plugin or IAA app, so there will be a bit of jitter. Lower buffer sizes gives less jitter (but higher chance for glitches, as we all know).

  • If @j_liljedahl would incorporate a sequencer into AUM it would be very B)

  • @anickt said:
    If @j_liljedahl would incorporate a sequencer into AUM it would be very B)

    !This
    i was in shame to ask for that, when i was aksing about placing PADs into AUM

  • @Goozoon said:

    @anickt said:
    If @j_liljedahl would incorporate a sequencer into AUM it would be very B)

    !This
    i was in shame to ask for that, when i was aksing about placing PADs into AUM

    Ok, let's ask a 'Aksing Sequencer'. A very good app naming!

    The Aksing! :D

  • A great review up at MAB. of course, does John no any different ;)

    http://musicappblog.com/ruismaker-review/#comment-74342

  • edited June 2016

    FYI: I bought this app on Kaikoo2's emphatic recommendation :) and got several channels sequenced using AUM and Genome without problem. Very cool. Then, after seeing Doug's video and his mention of merge recordings... got that going nicely too.

    But, hadn't noticed that it's only supported on iPhone5s and up. Unfortunately I only have an iPhone5 at the moment, but it installed so I tried anyway.

    First off, it crashes Garageband almost immediately. And the only way to recover is deleting Ruismaker, then opening Gargageband, and then deleting the song you started. Otherwise, it crashes on launch trying to load an AU that Garageband on an iPhone5 doesn't support.

    However! It DOES sort of work in AUM on the iPhone5. It works, but the sides of it's control window are cut off and you can't scroll over to see it. I think this is actually an issue other supported iPhone users have mentioned that's being addressed by the dev already.

    So, since Garageband crashes... I was looking for an easy midi sequencer like Genome that runs on the iPhone, but couldn't find one. Anyone know of one? I wonder why no one has made a basic midi sequencer for the iPhone. Seems that wouldn't be that difficult and they'd rule as the only one?

    Anyway, I tried using Xynthesizr as a sequencer, and after getting the right scale set, was able to do some fairly productive sequences that sounded good, and then added some areas to randomly be filled in by Xynthesizr. Pretty cool actually! Though, I'd much rather have something like Genome on the iPhone for this sort of thing.

  • edited June 2016

    A sequencer would be nice B) @j_liljedahl

  • @skiphunt said:

    So, since Garageband crashes... I was looking for an easy midi sequencer like Genome that runs on the iPhone, but couldn't find one. Anyone know of one? I wonder why no one has made a basic midi sequencer for the iPhone. Seems that wouldn't be that difficult and they'd rule as the only one?

    Infinite Looper. Easy, fast, runs on iPhone, and exports MIDI so you can easily transfer your work to the iPad sequencer of your choice (provided it can import MIDI files). I just killed a half hour waiting at the Dr.s office with it, ruismaker, and AUM (on a 5s tho.)

  • @djjuniorpops said:
    A sequencer would be nice B) @j_liljedahl

    I would buy it as iap for 19, only from our master

  • @gburks said:
    I am thoroughly confused about trying to use Ruismaker with Modstep's drum mode and my Akai MPD226 midi controller.

    I get the same issue reecording into ModStep using a Korg Electribe SX. I think its a ModStep issue but I havent worked it out yet.

  • @wim said:

    @skiphunt said:

    So, since Garageband crashes... I was looking for an easy midi sequencer like Genome that runs on the iPhone, but couldn't find one. Anyone know of one? I wonder why no one has made a basic midi sequencer for the iPhone. Seems that wouldn't be that difficult and they'd rule as the only one?

    Infinite Looper. Easy, fast, runs on iPhone, and exports MIDI so you can easily transfer your work to the iPad sequencer of your choice (provided it can import MIDI files). I just killed a half hour waiting at the Dr.s office with it, ruismaker, and AUM (on a 5s tho.)

    Actually, don't even need Infinite. The same dev's "Nice to be Your Friend Synth" appears to work too... although, its exported midi crashed Genome.. but it might be usable for basic sequencing. thx! :)

  • For non-DAW apps that can sequence Ruismaker I'm guessing that Auxy (iPad) is the most basic and that Modstep (and Genome etc) are the most capable and complex.

    What other apps Can drive Ruismaker / anyone have a favorite that clicks?

  • @Proppa said:
    For non-DAW apps that can sequence Ruismaker I'm guessing that Auxy (iPad) is the most basic and that Modstep (and Genome etc) are the most capable and complex.

    What other apps Can drive Ruismaker / anyone have a favorite that clicks?

    Works great in GarageBand if you can deal with being restricted to that closed little world.

  • @wim said:
    Works great in GarageBand if you can deal with being restricted to that closed little world.

    Thanks and noting that tip -- I'm very tempted to use a DAW but am even more interested in a non-DAW (especially 1gig + footprint) sequencer. If current Auxy had the original full velocity control I think my search would be over / I'm definitely interested in something Simple.

  • Ruismaker has been updated to 1.01 on the App Store :)

  • edited June 2016

    @sirdavidabraham said:
    Ruismaker has been updated to 1.01 on the App Store :)

    Well now THATs a fine howdydo! With this update it now works fine with my iPhone5. I can see the whole panel now in AUM and it works fine in Garageband too!

    Tested a few loops in GarageBand on iPhone 5 and I think the dev can update the description to include iPhone 5 as compatible. :)

  • @Proppa said:

    @wim said:
    Works great in GarageBand if you can deal with being restricted to that closed little world.

    Thanks and noting that tip -- I'm very tempted to use a DAW but am even more interested in a non-DAW (especially 1gig + footprint) sequencer. If current Auxy had the original full velocity control I think my search would be over / I'm definitely interested in something Simple.

    Infinite Looper is the closest to Auxy IMO. You can't host Ruismaker in it, but you can host it in AUM while sequencing it in IL.

  • edited June 2016

    @wim what about bleep!box for easy iPhone sequencing of Ruis in AUM?

  • @skiphunt said:
    @wim what about bleep!box for easy iPhone sequencing of Ruis in AUM?

    Sorry, no idea. Don't have it.

Sign In or Register to comment.