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

11415161820

Comments

  • I think the Modstep guys will have to answer this one.
    I don't remember having to do anything special in Modstep to make Ruismaker appear in the list.

  • @brambos said:
    I think the Modstep guys will have to answer this one.
    I don't remember having to do anything special in Modstep to make Ruismaker appear in the list.

    Cool man no worries was hoping someone had a quick fix.

  • @Kkani what device are you using ? anything below an Ipad4 is unable to even see AUx. regardless of host.
    i know this from experience since my Ipad3 cannot see AUx at all. you need a mini2 or ipad4 and above.

  • edited July 2016

    @Brambos ,

    Thank you for the V 1.03 update today.

    It is nice even that I have the drum pad on the play, the CC#109 just instantly on the fly to new all sounds from randomizer.

    Here is a new photo to add it (pinkish) to controller. Awesome!

  • @gonekrazy3000 said:
    @Kkani what device are you using ? anything below an Ipad4 is unable to even see AUx. regardless of host.
    i know this from experience since my Ipad3 cannot see AUx at all. you need a mini2 or ipad4 and above.

    Good info,noticed a difference in Modstep on the mini and mini2.On the mini it has the CC but the mini 2 shows a plug sign.Think that's the reason why no au inst on mini and no iaa HoneyChord ,Chronium,synth Retronyms,Clawtar,ChordUp,Arp & Dr Pad Yamaha.Shame no response from support.

  • edited July 2016

    @Dchild and all,

    My version v 1.01 coming out...

    Adding 8 more sticky buttons to the middle, so two kind of plays combined.

    Middle part of pinky is for holding Cream automatically, the other 8 buttons is at your will to add flavors. Any touch of colorful buttons will also automatically cancel the automation of those pinky buttons. It is very good.

  • @Kaikoo2 , you are a veritable MIDI virtuoso B)

  • edited July 2016

    Thank you @Brambos.

    The benefit of Ruismaker on AUM is that other app such as Gadget Madrid Bass can be mixing into this play. Madrid have the London side-chain. In the meantime, London has midi channel one out from Cream to AUM, so that Madrid Bass can be harmonized by Ruismaker from your finger on Midi Studio Pro.

    So how do you guys think?

    Ruismaker AU drum synthesizer is top notch on giving drumming foundation to all the plays by midi CC power on host. Just a hit you guys can do it without programming language.

    Cheers

  • @Samu said:

    @Goozoon said:
    @brambos Wont you consider adding note selecting buttons, please?

    This would be really nice and we could avoid clutter in the General->Settings for Ruismaker.

    I know, I suggested GM settings in addition to the default mapping but being able to manually customise all the notes would be even better :)

    The note-mapping could come in handy when running multiple instances of Ruismaker at the same time.

    One octave per Ruismaker Instance as an example?

    This way we could re-direct one midi-source to multiple instances of Ruismaker and access all the sounds using different note-numbers. (Like accessing two Ruismaker instances with the 16-pads on the iRig Pads).

    So to aid in 'note-mapping' Ruismaker could have an 'instance-selector' (1-10) that could use a default mapping such as instance 1 notes C-0 -- +9 notes, instance 2 C-1 -- +9, instance 3 notes C-2 -- +9 etc or 10 'instance snapshots' with 'midi-learnable' notes (Select a pad, hit a key on the controller etc.).

    Does it make sense or am I just too 'up in the blue?' :D

    @Samu I run 2 instances of Ruismaker now across 16 pads of my Akai MPD226. Nice that in the Akai I can set pads to different channels, so I have 8 pads going to the first instance of Ruis on channel 10 and the next 8 pads going to instance two of Ruis on channel 11. Fun.

  • Just got ruismaker. Have problems to get it to work with classic GM keys though. Changed it in Ios seetings as in the manual, but no matter what I do it only responds to "black keys". Don' t know if I do something wrong or if this got broken in the latest release?

  • @NoonienS said:
    Just got ruismaker. Have problems to get it to work with classic GM keys though. Changed it in Ios seetings as in the manual, but no matter what I do it only responds to "black keys". Don' t know if I do something wrong or if this got broken in the latest release?

    I'll look into it, thanks for letting me know.

  • @brambos, could I ask you for a small thing....? Could you please rearrange the "numbers" of instruments (in the manual) from low to high and update the content to include new instruments and group them by type ascending, no matter what drum it is, so I can choose what I want to include per drum type? (like hats together, snares together etc...)
    Thanks

    For example I would like to assign kicks CC-22 values from 10-18. This is from old manual, (you added more kits, so I would have to change values)....so if I record the movement of kick, there will be always a drum playing. (I am assigning and using the new global random)

    I'm using Ruismaker a lot and since it has really good midi, I am making a template combined with midiSTEPs sequencer on my Remote SLMKII.
    It would make it so much easier to select and assign...
    Thanks in advance

  • @Brambos ,

    Is there a possible way to under setting page to allow bypassing same instruments instances on 8 channels without 'choking' each others.

    I am running problem with controller app (Midi Studio Pro) that when selecting a instrument for a channel on a knob, normally new knob will be passing through the same midi CC number of another knob's CC number, the sound of another knob just vanished. I have to reposition the original knob.

    It is very annoying that it is not possible at this moment to choose whatever knob midi CC number to allow hand picking instruments on all 8 channels because of this conflicting CC number between 8 knobs.

    Can you design a way to bypass a CC number that already taken by other knobs (channel)?

  • @Brambos ,

    AUM parameters need you to take care of CC 108 and CC 109. They are not on the list. Thank you.

  • @Kaikoo2 said:
    AUM parameters need you to take care of CC 108 and CC 109. They are not on the list. Thank you.

    They cannot be AU Parameters, so they're only implemented as CC commands. If they would be AU parameters then state-saving hosts would cause total chaos (e.g. triggering randomize-commands at inconvenient moments, etc.).

  • wimwim
    edited July 2016

    @Kkani said:
    Shame no response from support.

    Did you report it directly to the devs through their web site, or only here? There's no reason ModStep devs would necessarily think to monitor a thread titled "RuisMaker - AU Drum Machine."

    It's the weekend too. Even app developers don't all work 24x7. It's also summer in Europe. People do take substantial vacations in Europe this time of year.

  • @wim said:

    @Kkani said:
    Shame no response from support.

    Did you report it directly to the devs through their web site, or only here? There's no reason ModStep devs would necessarily think to monitor a thread titled "RuisMaker - AU Drum Machine."

    It's the weekend too. Even app developers don't all work 24x7. It's also summer in Europe. People do take substantial vacations in Europe this time of year.

    What's it got to do with you?

  • @Kaikoo2 said:
    @Brambos ,

    Is there a possible way to under setting page to allow bypassing same instruments instances on 8 channels without 'choking' each others.

    I am running problem with controller app (Midi Studio Pro) that when selecting a instrument for a channel on a knob, normally new knob will be passing through the same midi CC number of another knob's CC number, the sound of another knob just vanished. I have to reposition the original knob.

    It is very annoying that it is not possible at this moment to choose whatever knob midi CC number to allow hand picking instruments on all 8 channels because of this conflicting CC number between 8 knobs.

    Can you design a way to bypass a CC number that already taken by other knobs (channel)?

    @Brambos ,

    You should allow different Midi CC number such as CC 22 and CC 23 to play same instruments on different AU channels, because any two controller knobs that has the same CC 'Value' or passing that same value number will choke or turn off the sounds of other 7 AU channels.

    Please,

    reconsider design a way to have the same sound to all 8 channels

    or

    Design a way to bypass the same 'CC value' that already selected by other 'CC numbers' from your 22 to 29 list on the manual.

    At this moment Ruismaker render no usefulness for external virtual controller to control individuals of those 8 AU channels instrument selection.

    Thank you so much, will listen your comment on this issue.

  • The easiest way around this is not to map "instrument change" to a knob or a slider but to something that sends a single end-value with no in-between values.

    I'm considering other scenarios, but they all have other unwanted side effects.

  • wimwim
    edited July 2016

    @Kkani said:

    @wim said:

    @Kkani said:
    Shame no response from support.

    Did you report it directly to the devs through their web site, or only here? There's no reason ModStep devs would necessarily think to monitor a thread titled "RuisMaker - AU Drum Machine."

    It's the weekend too. Even app developers don't all work 24x7. It's also summer in Europe. People do take substantial vacations in Europe this time of year.

    What's it got to do with you?

    Wow. Just a little friendly comment meant to help explain why you might not have gotten an answer yet. I thought that's what we did around here. Guess not? I'll keep in mind not to comment on your posts in the future. Sorry for offending you.

  • edited July 2016

    brambos said:
    The easiest way around this is not to map "instrument change" to a knob or a slider but to something that sends a single end-value with no in-between values.

    I'm considering other scenarios, but they all have other unwanted side effects.

    Ok, Brambos, those things if changed will bring other conflicting things I guess.

    Good weekend.

  • @brambos said:
    The easiest way around this is not to map "instrument change" to a knob or a slider but to something that sends a single end-value with no in-between values.

    I'm considering other scenarios, but they all have other unwanted side effects.

    Would a button do? Assigned to increments, min. val.10, max 17, in increments of 1? In case of drum-1. Just cycles through the selected values

  • edited July 2016

    Everybody playing new Gadget, I am not at this moment.

    Because this drum synthesizer is far more powerful and interesting with both Turnado and Effectrix at the same time from Cream with my newly designed all in one page setup with 36 XY pads.

    All on midi channel 1, except Turnado and Effecteix on channel5. A few photos here to help your designing thoughts. I am totally impressed by this that I have never heard of and seeing on YouTube.

    It is so sisisiccck......... So efficient that my Air2 handling this so well.

  • @Kaikoo2 , is there a Cream tutorial (e.g. on Youtube) that you can recommend? It looks interesting, but seems to have quite a learning curve...

  • @brambos said:
    @Kaikoo2 , is there a Cream tutorial (e.g. on Youtube) that you can recommend? It looks interesting, but seems to have quite a learning curve...

    It is really hard that Cream needs so much time to know intricacy. For Ruismaker, here is hint... Try more with SEQ, Transpose (grid) and Order tabs.

    The importance I show this is because that AUM route setting photos. If users have not much experiences, It won't be setting well on AUm with external vertual controller with apps. This is reason I show this photo if someone follow this up.

    I have tremendous fun with Ruismaker with Turnado and Effectrix mixing. No matter users want live play or recording purpose, this setup is quite perfect for me.

    I will design many buttons later on for specific instrument selection for those 8 AU channel on only for this midi channel 1 to bypass the issue we talked before. So I can have more way to match instrument sound with Turnado.

    So everyone don't hurry yourself to Cream Mobile. Just take time.

    Btw, Turnado and Effectrix inserted by music effect method, so AUm can control the playhead of both app for sync (delay) and midi channel 5 routed to my Midi Stuido Pro. Too full the midi CC on channel 1. :D

    I want to play new Gadget update, but this is too much fun (sonic mayhem). Hehe.

    Cheers.

  • Thanks; off to play with it right now ;)

  • edited July 2016

    That Midi Studio Pro photo has 7 new Effectrix sequencer tracks selection by midi triggering.

    The Sync button is for one press all sound start/stop.

    Dictator is for Turnado all 8 effects modulation.

    So flashingly powerful stuff by its real time looking. Ya, hand crafted. :)

  • I also has that AUM volume faders for dry/wet on my controller.

  • @wim said:

    @Kkani said:

    @wim said:

    @Kkani said:
    Shame no response from support.

    Did you report it directly to the devs through their web site, or only here? There's no reason ModStep devs would necessarily think to monitor a thread titled "RuisMaker - AU Drum Machine."

    It's the weekend too. Even app developers don't all work 24x7. It's also summer in Europe. People do take substantial vacations in Europe this time of year.

    What's it got to do with you?

    Wow. Just a little friendly comment meant to help explain why you might not have gotten an answer yet. I thought that's what we did around here. Guess not? I'll keep in mind not to comment on your posts in the future. Sorry for offending you.

    You were far more compassionate than many would be (self included).

  • edited July 2016

    brambos said:
    @Kaikoo2 , is there a Cream tutorial (e.g. on Youtube) that you can recommend? It looks interesting, but seems to have quite a learning curve...

    @Brambos ,

    Cream has 4 midi tracks. The basic thing is if you have patterns always on SEQ and randomized, you always end up a bit too many instruments on every steps. The trick is to have your Kick with fixed pattern such as 4 1/4 beats for 16 steps. The photos here, you can see I have 2nd track fixed that pattern only for Kick. So depending on the style and speed to adjust the top Rate button.

    Then we go back to 1st track, you can see If I looking for a pattern, I have 1st track first row of SEQ wiped off after being randomized. So in this way, all other 7 instruments follow the lead of that 2nd track Kick. You can have 2 independent Rate knob on top for two tracks. Then you go on to Transpose grid section and Order section to reduce instruments used to eliminate crowding sounds. The top Rate speed is important again, because my finger can have finger patterns for those 7 Midi Studio Pro keypads, I leave the 1st keypad for that 2nd track sequencer automation. I use my fingers to dance those 7 instruments on 1st track made patterns.

    After good sounding patterns, now time goes to mix in the Turnado or Effectrix. All in all, Cream produces quite many counts on sequencer steps. It really need you go on by reduction and elimination method to find excellent results. It is not Cream's problem, it is the way to get good randomization (it scattering so well on grids).

    Too many tricks here on Cream Mobile, patience is a virtue applies here for anyone with it. :)

    2nd track on midi channel 1.

    See the 1st track 1st row here, wiped off.

Sign In or Register to comment.