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.

Axon 2 vs Ruismaker FM

2»

Comments

  • edited November 2017

    @Littlewoodg said:
    @skiphunt just ran DM1with it without the midifire...

    Don’t have DM1 but tried DM2 as well as 6 others. No luck here. Will wait to see if some one else also gets it working as you have before trying again.

  • The midi is certainly working on some apps eg Elastic Drums and Stroke machine. But a lot of apps don't like the midi unfortunately. it works on a lot of drum apps but not synth apps so much. One good thing is the volume sliders affect the midi out and is good for muting/unmuting midi.

    I think also it needs some way of changing patterns. It will be better when the AU gets midi out so you can change patterns that way.

  • @skiphunt said:

    @Carnbot said:
    It's weird, it triggers some things with higher success than others depending on the app, but if you check with Midiflow the note on offs go off then on. If you try it on a synth it hardly works at all.. For me anyway. I gave up with it but hope that the AU gets a midi out update along with a fix.

    Senode does this kind of thing in a much deeper way so I'm hoping that gets Linked up soon. :)

    Midifire is great. And actually there's probably a way to correct the midi data with it using the stream byter but I don't know how and I'm not skilled with it to even attempt something like that :wink:

    My experience too. I haven't bought Senode yet. It's at the very top of my list. I know it's on launch discount already, but some apps went even lower... even though they were on launch discount last year, so I waited to see if this one would too.

    Didn't, so I'll be nabbing it soon. It just looks like it really fits with the kind of sequencing interface I've been looking for. And, my somewhat loose budget for "black Friday/Cyber Monday" allowed for buying Senode no matter if it was discounted more or not. :)

    Yeah Senode is really interesting, but still waiting on a few things so hopefully the dev will update before christmas, but who knows? :)

  • @Carnbot said:
    The midi is certainly working on some apps eg Elastic Drums and Stroke machine. But a lot of apps don't like the midi unfortunately. it works on a lot of drum apps but not synth apps so much. One good thing is the volume sliders affect the midi out and is good for muting/unmuting midi.

    I think also it needs some way of changing patterns. It will be better when the AU gets midi out so you can change patterns that way.

    I had it somewhat working in standalone and sent to the AD synth Phosphor 2, but it wasn’t consistent. Haven’t tried Elastic Drums though. I was avoiding that one because others have said it’s midi can be tricky.

  • @skiphunt said:

    @Carnbot said:
    The midi is certainly working on some apps eg Elastic Drums and Stroke machine. But a lot of apps don't like the midi unfortunately. it works on a lot of drum apps but not synth apps so much. One good thing is the volume sliders affect the midi out and is good for muting/unmuting midi.

    I think also it needs some way of changing patterns. It will be better when the AU gets midi out so you can change patterns that way.

    I had it somewhat working in standalone and sent to the AD synth Phosphor 2, but it wasn’t consistent. Haven’t tried Elastic Drums though. I was avoiding that one because others have said it’s midi can be tricky.

    The issue with Axon MIDI out is that it's sending the Note Off command at the same time as the Note On. If you look at a MIDI monitor app with timestamps, it's literally the same time for both (at least to millisecond resolution). Compare this with something like Patterning where there's a ~62ms gap between Note On and Note Off.

    A lot of drum apps ignore Note Off. Since the sounds are not sustaining it's fine to just listen for the Note On trigger and let the sound run its course. Synths, however, need a discrete Note On and Note Off. If the gap between the two is too short they can get confused, hence the sometimes-you-hear-a-blip,-sometimes-you-don't.

    @Chris_Randall just needs to add a bit of delay between the Note On and Note Off to get this properly sorted.

  • @aplourde said:

    @skiphunt said:

    @Carnbot said:
    The midi is certainly working on some apps eg Elastic Drums and Stroke machine. But a lot of apps don't like the midi unfortunately. it works on a lot of drum apps but not synth apps so much. One good thing is the volume sliders affect the midi out and is good for muting/unmuting midi.

    I think also it needs some way of changing patterns. It will be better when the AU gets midi out so you can change patterns that way.

    I had it somewhat working in standalone and sent to the AD synth Phosphor 2, but it wasn’t consistent. Haven’t tried Elastic Drums though. I was avoiding that one because others have said it’s midi can be tricky.

    The issue with Axon MIDI out is that it's sending the Note Off command at the same time as the Note On. If you look at a MIDI monitor app with timestamps, it's literally the same time for both (at least to millisecond resolution). Compare this with something like Patterning where there's a ~62ms gap between Note On and Note Off.

    A lot of drum apps ignore Note Off. Since the sounds are not sustaining it's fine to just listen for the Note On trigger and let the sound run its course. Synths, however, need a discrete Note On and Note Off. If the gap between the two is too short they can get confused, hence the sometimes-you-hear-a-blip,-sometimes-you-don't.

    @Chris_Randall just needs to add a bit of delay between the Note On and Note Off to get this properly sorted.

    Thanks for the confirmation, I thought too that was the case, I originally posted about this note on off error too and Chris Randall acknowledged it but hasn't addressed it yet.

    It's a bit hard work when you have to test everything thoroughly these days, it sometimes doesn't pay to be an early adopter ;)

  • @aplourde said:

    @skiphunt said:

    @Carnbot said:
    The midi is certainly working on some apps eg Elastic Drums and Stroke machine. But a lot of apps don't like the midi unfortunately. it works on a lot of drum apps but not synth apps so much. One good thing is the volume sliders affect the midi out and is good for muting/unmuting midi.

    I think also it needs some way of changing patterns. It will be better when the AU gets midi out so you can change patterns that way.

    I had it somewhat working in standalone and sent to the AD synth Phosphor 2, but it wasn’t consistent. Haven’t tried Elastic Drums though. I was avoiding that one because others have said it’s midi can be tricky.

    The issue with Axon MIDI out is that it's sending the Note Off command at the same time as the Note On. If you look at a MIDI monitor app with timestamps, it's literally the same time for both (at least to millisecond resolution). Compare this with something like Patterning where there's a ~62ms gap between Note On and Note Off.

    A lot of drum apps ignore Note Off. Since the sounds are not sustaining it's fine to just listen for the Note On trigger and let the sound run its course. Synths, however, need a discrete Note On and Note Off. If the gap between the two is too short they can get confused, hence the sometimes-you-hear-a-blip,-sometimes-you-don't.

    @Chris_Randall just needs to add a bit of delay between the Note On and Note Off to get this properly sorted.

    That makes perfect sense. I wonder why I couldn’t get it work with DM2 though. Is that because DM2 is more synth than regular drum app?

  • @skiphunt said:

    @aplourde said:

    @skiphunt said:

    @Carnbot said:
    The midi is certainly working on some apps eg Elastic Drums and Stroke machine. But a lot of apps don't like the midi unfortunately. it works on a lot of drum apps but not synth apps so much. One good thing is the volume sliders affect the midi out and is good for muting/unmuting midi.

    I think also it needs some way of changing patterns. It will be better when the AU gets midi out so you can change patterns that way.

    I had it somewhat working in standalone and sent to the AD synth Phosphor 2, but it wasn’t consistent. Haven’t tried Elastic Drums though. I was avoiding that one because others have said it’s midi can be tricky.

    The issue with Axon MIDI out is that it's sending the Note Off command at the same time as the Note On. If you look at a MIDI monitor app with timestamps, it's literally the same time for both (at least to millisecond resolution). Compare this with something like Patterning where there's a ~62ms gap between Note On and Note Off.

    A lot of drum apps ignore Note Off. Since the sounds are not sustaining it's fine to just listen for the Note On trigger and let the sound run its course. Synths, however, need a discrete Note On and Note Off. If the gap between the two is too short they can get confused, hence the sometimes-you-hear-a-blip,-sometimes-you-don't.

    @Chris_Randall just needs to add a bit of delay between the Note On and Note Off to get this properly sorted.

    That makes perfect sense. I wonder why I couldn’t get it work with DM2 though. Is that because DM2 is more synth than regular drum app?

    I’ve had so many issues trying to drive DM-2 midi that I deleted it (in favor of the other 20 drumsynths I have :D)

    Then I noticed Bram Bos included note maps for it in Rozeta, so I tried it in AUM with XoX etc. worked like a charm for some reason.

    But anywhere else, including driving it via Axon, no can do.

  • @aplourde said:

    @skiphunt said:

    @Carnbot said:
    The midi is certainly working on some apps eg Elastic Drums and Stroke machine. But a lot of apps don't like the midi unfortunately. it works on a lot of drum apps but not synth apps so much. One good thing is the volume sliders affect the midi out and is good for muting/unmuting midi.

    I think also it needs some way of changing patterns. It will be better when the AU gets midi out so you can change patterns that way.

    I had it somewhat working in standalone and sent to the AD synth Phosphor 2, but it wasn’t consistent. Haven’t tried Elastic Drums though. I was avoiding that one because others have said it’s midi can be tricky.

    The issue with Axon MIDI out is that it's sending the Note Off command at the same time as the Note On. If you look at a MIDI monitor app with timestamps, it's literally the same time for both (at least to millisecond resolution). Compare this with something like Patterning where there's a ~62ms gap between Note On and Note Off.

    A lot of drum apps ignore Note Off. Since the sounds are not sustaining it's fine to just listen for the Note On trigger and let the sound run its course. Synths, however, need a discrete Note On and Note Off. If the gap between the two is too short they can get confused, hence the sometimes-you-hear-a-blip,-sometimes-you-don't.

    @Chris_Randall just needs to add a bit of delay between the Note On and Note Off to get this properly sorted.

    That is what I felt like was happening. However since there’s been no fix and the storm of iOS ports is seemingly over (I would’ve guessed that he’d’ve ported the bandpass multi-filter by now as he hinted at in his ‘suggestions’ thread months ago), on top of his absence from the forums since the initial Axon release, I get the feeling Mr. Randall may not be too interested in continuing his work for iOS, whether at this time or for good.

Sign In or Register to comment.