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 FM 1.01 update in the AppStore

12357

Comments

  • @Matt_Fletcher_2000 said:
    Basically we need Gadget, but for AUs/IAAs. Kind of AUM crossed with Gadget.

    With the upcoming update and better AU stability/support, surely this is ModStep, with the added benefit of individual clip launching ?

  • edited August 2016

    I just downloaded the new update to 'beat-machine' and it has a nice setting of IAA-Record compensation.
    I guess it's there to overcome the flaws in DAWs that do not have automatic plug-in delay compensation.

    I know that when Ruismaker and Ruismaker FM are used with Cubasis the output arrives too early when a track is frozen, so until the host calculates the 'delay value' the only way to overcome this is to add an empty bar at the beginning and manually trim out the silence...

  • @brambos Can I request that if possible there could be different CC assigned to randomising each track and also the whole kit, this would be super useful for trying out new sounds quickly. :)

  • @Carnbot said:
    @brambos Can I request that if possible there could be different CC assigned to randomising each track and also the whole kit, this would be super useful for trying out new sounds quickly. :)

    edit: I see there already is a randomise CC, is that for the whole kit? will give it a try

  • @Carnbot said:

    @Carnbot said:
    @brambos Can I request that if possible there could be different CC assigned to randomising each track and also the whole kit, this would be super useful for trying out new sounds quickly. :)

    edit: I see there already is a randomise CC, is that for the whole kit? will give it a try

    In Ruismaker FM it is for the currently selected instrument. But as requested earlier in this thread I will add a mechanism for randomizing the entire kit as well. When doing it via CC I will probably let you select the instrument to randomize via the CC value (send randomize CC with a value of 3 to randomize channel 3, etc.).

    Would that work?

  • @brambos said:

    @Carnbot said:

    @Carnbot said:
    @brambos Can I request that if possible there could be different CC assigned to randomising each track and also the whole kit, this would be super useful for trying out new sounds quickly. :)

    edit: I see there already is a randomise CC, is that for the whole kit? will give it a try

    In Ruismaker FM it is for the currently selected instrument. But as requested earlier in this thread I will add a mechanism for randomizing the entire kit as well. When doing it via CC I will probably let you select the instrument to randomize via the CC value (send randomize CC with a value of 3 to randomize channel 3, etc.).

    Would that work?

    Thanks, yes that would make it easier to randomise different tracks without having to select each track manually etc

  • @Samu said:
    I just downloaded the new update to 'beat-machine' and it has a nice setting of IAA-Record compensation.
    I guess it's there to overcome the flaws in DAWs that do not have automatic plug-in delay compensation.

    I know that when Ruismaker and Ruismaker FM are used with Cubasis the output arrives too early when a track is frozen, so until the host calculates the 'delay value' the only way to overcome this is to add an empty bar at the beginning and manually trim out the silence...

    Is this Freeze bug or an ADC bug? I assume Freeze should function as what you hear is what you get. ADC or lack thereof should lead to identical results whether playing back via MIDI data or frozen track.

    I'd be more inclined to report this as a Freeze bug.

  • How does this FM baby sound in comparison to SeekBeats or ED? Can you make any sound?
    Thanks.

  • @brambos said:

    @Nkersov said:
    So, working under AUM, what is your preferred app for driving RuisMaker FM?

    For jamming: certainly Patterning because it easily lets you split a single pattern into multiple midi output channels. That way you can host multiple instances of Ruismaker/FM with different effect chains - effectively simulating multiple outputs.

    So this! Best part of the whole AU thing in general, and the ruismaker family in particular!

  • And hopefully that family keeps growing ;)

  • edited August 2016

    @sirdavidabraham said:

    @Samu said:
    I just downloaded the new update to 'beat-machine' and it has a nice setting of IAA-Record compensation.
    I guess it's there to overcome the flaws in DAWs that do not have automatic plug-in delay compensation.

    I know that when Ruismaker and Ruismaker FM are used with Cubasis the output arrives too early when a track is frozen, so until the host calculates the 'delay value' the only way to overcome this is to add an empty bar at the beginning and manually trim out the silence...

    Is this Freeze bug or an ADC bug? I assume Freeze should function as what you hear is what you get. ADC or lack thereof should lead to identical results whether playing back via MIDI data or frozen track.

    I'd be more inclined to report this as a Freeze bug.

    Just analyzed a bit more. Freeze renders early, Mixdown renders even earlier than Freeze. We're probably talking about at least 10ms here...enough to alter the feel. I'll report to Steinberg.

  • edited August 2016

    @sirdavidabraham said:

    Is this Freeze bug or an ADC bug? I assume Freeze should function as what you hear is what you get. ADC or lack thereof should lead to identical results whether playing back via MIDI data or frozen track.

    I'd be more inclined to report this as a Freeze bug.

    It's been reported long, long time ago together with screenshots (where the frozen audio is 'off the grid' compared to the midi-notes) explaining the situation...

    The 'freeze bug' affects all AU-X and IAA-Instruments (and even the built-in Micrologue) in the 'host' that we're all awaiting to get the hyped 2.0 update.

    The other internal instruments (MicroSonic and MiniSampler) work properly as expected...

    There is not much the developer can do as this is host-ralated...

  • @Samu said:

    @sirdavidabraham said:

    Is this Freeze bug or an ADC bug? I assume Freeze should function as what you hear is what you get. ADC or lack thereof should lead to identical results whether playing back via MIDI data or frozen track.

    I'd be more inclined to report this as a Freeze bug.

    It's been reported long, long time ago together with screenshots (where the frozen audio is 'off the grid' compared to the midi-notes) explaining the situation...

    The 'freeze bug' affects all AU-X and IAA-Instruments (and even the built-in Micrologue) in the 'host' that we're all awaiting to get the hyped 2.0 update.

    The other internal instruments (MicroSonic and MiniSampler) work properly as expected...

    There is not much the developer can do as this is host-ralated...

    Oh thanks for confirming that it's a known thing in Cubasis, because I just tried in GarageBand iOS and things line up fine. Hopefully Cubasis 2.0 will address this...¡muy importante!

  • >

    Oh thanks for confirming that it's a known thing in Cubasis, because I just tried in GarageBand iOS and things line up fine. Hopefully Cubasis 2.0 will address this...¡muy importante!

    Yeah, some things do work very well in Garageband (GB 'Autofreezes' tracks to save CPU).
    Even the 'beloved' ModStep has issues when recording AU-X/IAA-instruments but that's supposed to be fixed in the 'next' update or something, hope they bring new colour schemes too, I can't use it with the current scheme for too long without eye-strain :(

    Now imagine if GB got automation-lanes for AU-Parameters and editing of at least basic Midi-CC (Pitch-Bend and Modwheel can be recorded but not edited). That would make me use GB a lot more :D

  • @Samu said:

    Now imagine if GB got automation-lanes for AU-Parameters and editing of at least basic Midi-CC (Pitch-Bend and Modwheel can be recorded but not edited). That would make me use GB a lot more :D

    Also at least support AU Effects....iOS9 will soon be a year old. GB should be leading the way here.

  • @sirdavidabraham said:

    @Samu said:

    Now imagine if GB got automation-lanes for AU-Parameters and editing of at least basic Midi-CC (Pitch-Bend and Modwheel can be recorded but not edited). That would make me use GB a lot more :D

    Also at least support AU Effects....iOS9 will soon be a year old. GB should be leading the way here.

    Who knows what apps we'll see when iOS10 comes out?
    I mean most of the WWDC'16 was circling around iOS10 anyway :)

  • @Samu said:

    >

    Oh thanks for confirming that it's a known thing in Cubasis, because I just tried in GarageBand iOS and things line up fine. Hopefully Cubasis 2.0 will address this...¡muy importante!

    Yeah, some things do work very well in Garageband (GB 'Autofreezes' tracks to save CPU).
    Even the 'beloved' ModStep has issues when recording AU-X/IAA-instruments but that's supposed to be fixed in the 'next' update or something, hope they bring new colour schemes too, I can't use it with the current scheme for too long without eye-strain :(

    Now imagine if GB got automation-lanes for AU-Parameters and editing of at least basic Midi-CC (Pitch-Bend and Modwheel can be recorded but not edited). That would make me use GB a lot more :D

    you keep mentioning the color scheme ... what is wrong with it? and you can choose your own colors, too

  • @nick said:

    you keep mentioning the color scheme ... what is wrong with it? and you can choose your own colors, too

    I can't help that my vision is degrading with age and that high contrast UIs easily cause headaches...
    (The thin white lines on the black background feel like a knife drilling/carving straight into my brain).

    There is no way to change the black background to something more 'less contrasty' and just inverting the colours is not an option. The only thing that is changeable in ModStep are the clip colours.

    Ableton Live has different colour schemes so the user can adapt it to taste...

  • @Samu said:

    @nick said:

    you keep mentioning the color scheme ... what is wrong with it? and you can choose your own colors, too

    I can't help that my vision is degrading with age and that high contrast UIs easily cause headaches...
    (The thin white lines on the black background feel like a knife drilling/carving straight into my brain).

    There is no way to change the black background to something more 'less contrasty' and just inverting the colours is not an option. The only thing that is changeable in ModStep are the clip colours.

    Ableton Live has different colour schemes so the user can adapt it to taste...

    ah, I see. Thanks for explaining. yes, there is lots of thin and ultra thin lines in mod step. it is definitely a high contrast app with its dominant black and white. Maybe they could add an option for a different background color, even a dark gray could already make a difference and a slightly broken white

  • @brambos said:

    @Nkersov said:
    So, working under AUM, what is your preferred app for driving RuisMaker FM?

    For jamming: certainly Patterning because it easily lets you split a single pattern into multiple midi output channels. That way you can host multiple instances of Ruismaker/FM with different effect chains - effectively simulating multiple outputs.

    Okay, thanks for that. Will give it a bash via headphones. Here on the IOW it's Scooter Weekend, and around 6000 mods are arriving.

  • @nick said:

    @Samu said:

    @nick said:

    you keep mentioning the color scheme ... what is wrong with it? and you can choose your own colors, too

    I can't help that my vision is degrading with age and that high contrast UIs easily cause headaches...
    (The thin white lines on the black background feel like a knife drilling/carving straight into my brain).

    There is no way to change the black background to something more 'less contrasty' and just inverting the colours is not an option. The only thing that is changeable in ModStep are the clip colours.

    Ableton Live has different colour schemes so the user can adapt it to taste...

    ah, I see. Thanks for explaining. yes, there is lots of thin and ultra thin lines in mod step. it is definitely a high contrast app with its dominant black and white. Maybe they could add an option for a different background color, even a dark gray could already make a difference and a slightly broken white

    It's quite a common problem or common in similar ways. I know I spend too long on my iPad and I have a head pain condition anyway, but some apps really are more difficult visually for some.

  • @Samu said:

    @nick said:

    you keep mentioning the color scheme ... what is wrong with it? and you can choose your own colors, too

    I can't help that my vision is degrading with age and that high contrast UIs easily cause headaches...
    (The thin white lines on the black background feel like a knife drilling/carving straight into my brain).

    There is no way to change the black background to something more 'less contrasty' and just inverting the colours is not an option. The only thing that is changeable in ModStep are the clip colours.

    Ableton Live has different colour schemes so the user can adapt it to taste...

    Turn the brightness down ?

  • @AndyPlankton said:

    @Samu said:

    @nick said:

    you keep mentioning the color scheme ... what is wrong with it? and you can choose your own colors, too

    I can't help that my vision is degrading with age and that high contrast UIs easily cause headaches...
    (The thin white lines on the black background feel like a knife drilling/carving straight into my brain).

    There is no way to change the black background to something more 'less contrasty' and just inverting the colours is not an option. The only thing that is changeable in ModStep are the clip colours.

    Ableton Live has different colour schemes so the user can adapt it to taste...

    Turn the brightness down ?

    Or stop working in candle light unless the light attracks zombies :p

  • Or wear some of these B)

  • @AndyPlankton said:
    Or wear some of these B)

    With anti-reflecting coating on my sun-glasses I would see nada :D
    It's the black back-ground and bright details that causes the problem, not the 'brightness' of the screen.

  • xx> @Samu said:

    @AndyPlankton said:
    Or wear some of these B)

    With anti-reflecting coating on my sun-glasses I would see nada :D
    It's the black back-ground and bright details that causes the problem, not the 'brightness' of the screen.

    Sucks. If you're spending a lot of time buried in Modstep, you might be able to alleviate the symptoms with a combination of the iPad's Accessibility Settings by inverting the colors and darkening(lightening) the screen, but if you're jumping around to other apps too, it would be maddening.

  • Errrr, nope. Still no sound. MIDI has always been a black art to me, the original midiiot. I've selected what look like the logical settings, but Patterning is only playing its own sounds. I wish, for those who like me find this baffling, that RuisMaker FMA came with a few preconfigured settings that could alter whatever needed to be altered.

  • edited August 2016

    @Nkersov said:
    Errrr, nope. Still no sound. MIDI has always been a black art to me, the original midiiot. I've selected what look like the logical settings, but Patterning is only playing its own sounds. I wish, for those who like me find this baffling, that RuisMaker FMA came with a few preconfigured settings that could alter whatever needed to be altered.

    I wish I could do that, but it is fully out of my control.I have no influence over the host's settings.

    That said, here are the settings I use in Patterning and AUM, which work instantly for me (no setting changes needed in Ruismaker FM itself):

  • @Nkersov said:
    Errrr, nope. Still no sound. MIDI has always been a black art to me, the original midiiot. I've selected what look like the logical settings, but Patterning is only playing its own sounds. I wish, for those who like me find this baffling, that RuisMaker FMA came with a few preconfigured settings that could alter whatever needed to be altered.

    If you send some screenshots, or detailed description of your settings, I bet people will be able to help you out.

  • edited August 2016

    @wim said:

    @Nkersov said:
    Errrr, nope. Still no sound. MIDI has always been a black art to me, the original midiiot. I've selected what look like the logical settings, but Patterning is only playing its own sounds. I wish, for those who like me find this baffling, that RuisMaker FMA came with a few preconfigured settings that could alter whatever needed to be altered.

    If you send some screenshots, or detailed description of your settings, I bet people will be able to help you out.

    maybe you get the issue i get sometimes, that not only i need to have the app sending midi to AUM checked but also the "AUM" destination as well. sometimes i get sound from without it, sometimes i need to have that other one checked as well.

    look at this screenshot bambros posted - https://forum.audiob.us/uploads/editor/yr/i2nciztl5iwy.jpg

    maybe having the AUM destination checked might give you sound, along with patterning of course.

Sign In or Register to comment.