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.

Autony: Question on long clocks+long gates.. Why are notes stopping?

So I've started to play with Autony a bit as an AU alternative to PolyPhase, but I've run into a bit of weirdness...

For example:
If I have Clock set to 4 bars and Gate set to like 150% and reliability set to 100%, it seems to me that once the sequence starts there should ALWAYS be a note playing due to the gate being over 100% (i.e. notes should overlap) and the 100% on reliability means no gaps...

But that's not what's happening. Every once and a while I'll get silence...

Anyone know why? Is this a bug? It seems like a bug...

Comments

  • I've noticed the same effect...

  • Hmm. Probably a bug although if the same note plays twice you’d get two note ons and then two note offs for the same note. A lot of synths will stop playing a note at that point. Could it be that?

    I’ll have a look tomorrow though and see if I can reproduce

  • edited December 2018

    OK, I think I figured it out. I'd consider it a bug, but no idea if the devs would:

    What seems to be happening is that when you have a note, followed by an identical note and a gate length of over 100%, when the noteoff from note1 happens, it essentially ends the note, even though there is still a noteon hanging out there from note2...

    Seems to me the code should change so that it checks for an outstanding note on, which would be the case if gate>99%, before it sends a note off so you can get longer ties...

    If it's not changed, then it kind of defeats to purpose of being able to have gate len >100% (which is a cool feature).

    Hopefully this gets addressed/fixed...

  • Yeah. That might be better behaviour TBH. I’ll see what I can do

  • Ahh. If I could only get StepPolyArp to do just the opposite...turn them off-!

  • @pagefall said:
    Yeah. That might be better behaviour TBH. I’ll see what I can do

    Cool, just clicked you're the dev! :)

    Also, the knobs are REALLY fiddly... But I do appreciate all the midi/AUparam control you put in!

    It would also be nice if it was resizeable... But that's just a little thing.

  • resizable layout coming - as is another revision of the knob behaviour.

    I figured out how to do ties for notes that overlap and will add that - I think that behaviour makes sense - it does for the next app too (which is very close but guessing just after christmas since app store submissions closes on the 23rd)

  • Also, the knobs are REALLY fiddly... But I do appreciate all the midi/AUparam control you put in!

    out of interest - what device are you using it on? Different people seem to be having different experiences - for me on the iPad they seem ok now so I'm not sure what needs changing

  • @pagefall said:

    Also, the knobs are REALLY fiddly... But I do appreciate all the midi/AUparam control you put in!

    out of interest - what device are you using it on? Different people seem to be having different experiences - for me on the iPad they seem ok now so I'm not sure what needs changing

    I use Autony on an iPad Pro (10.5 inch) and it’s impossible to dial in precise values with the knobs as they behave now - they are moving too fast and even the ‘fingerlifting thing’ you implemented earlier doesn’t work always. Maybe an inputdialog after double tapping for values and a listbox for scales?

  • I use Autony on an iPad Pro (10.5 inch) and it’s impossible to dial in precise values with the knobs as they behave now - they are moving too fast and even the ‘fingerlifting thing’ you implemented earlier doesn’t work always. Maybe an inputdialog after double tapping for values and a listbox for scales?

    TBH I'd rather get the knobs working - there is no reason they couldn't do what is needed - I'll give them another go and then failing that look at allowing typed values as well

  • @pagefall said:

    I use Autony on an iPad Pro (10.5 inch) and it’s impossible to dial in precise values with the knobs as they behave now - they are moving too fast and even the ‘fingerlifting thing’ you implemented earlier doesn’t work always. Maybe an inputdialog after double tapping for values and a listbox for scales?

    TBH I'd rather get the knobs working - there is no reason they couldn't do what is needed - I'll give them another go and then failing that look at allowing typed values as well

    I'd describe the issue the same way. My guess is you just need to reduce whatever iOS uses as a touch sensativity, or maybe just put in some kind of time-based averaging... Like 500ms average value or something just to reduce the jitter...

    Or honestly, personally, I've always though "dials" are a stupid idea on touch interfaces. Rotary movement of dials in touch is pointless, thus most devs allow dials to be "linear". well then why the F are they a damn dial then! :)

    "Sliders" make more sense if you ask me. Not that you did. :)

  • always interested in views :-)

    oddly I prefer sliders in the physical world - perhaps i should have gone that route

    Sadly - it isn't "what iOS provides" it's my own maths - wherein lies the issue ;-)

    will have another tweak - maybe I'll put sliders on the next app instead......working on the UI of that tomorrow anyway - might give it a go

  • @pagefall said:
    always interested in views :-)

    oddly I prefer sliders in the physical world - perhaps i should have gone that route

    Sadly - it isn't "what iOS provides" it's my own maths - wherein lies the issue ;-)

    will have another tweak - maybe I'll put sliders on the next app instead......working on the UI of that tomorrow anyway - might give it a go

    A UI paradigm I messsed with (granted it was on PC) was to have a circle/radial display of the value (i.e. it looks like a pie chart kinda thing so it's kinda like a dial, but only for looks/space/readability) but the actual input modality is just a vector magnitude type thing. So you put your finger on the circle, then the distance you drag away from the circle sets the value. So... Kinda like a knob with linear movement, but not quite. It felt more like a rubber band.

    The best example of this kind of thing is in TC-11/TC-Data... but that's prob. overkill for this! :)

  • @pagefall Not that you're asking ... but I'd prefer sliders as well. :)
    Either way, it's a great app and I'm sure you'll get it solved.

  • @pagefall Another "bug".. When midi mapping gate len in AUM (using AUM/AU params, not mapping in AU), Gate length in Autonomy bottoms out at 20%... Even if cc value =0 gate len only goes to 20%. Is that by design?

  • @MonkeyDrummer said:
    @pagefall Another "bug".. When midi mapping gate len in AUM (using AUM/AU params, not mapping in AU), Gate length in Autonomy bottoms out at 20%... Even if cc value =0 gate len only goes to 20%. Is that by design?

    Nah definitely a bug. Guessing it’s a typo in the code or something. Thank you for spotting it!

  • @MonkeyDrummer said:
    @pagefall Another "bug".. When midi mapping gate len in AUM (using AUM/AU params, not mapping in AU), Gate length in Autonomy bottoms out at 20%... Even if cc value =0 gate len only goes to 20%. Is that by design?

    Dang, EagleEyeMonkeyDrummer.
    :)

  • pivoting to sliders!!

  • The problem with sliders is that they take up so much screen real estate. With knobs, you can have a compact set of rows with knobs. As long as they respond in the same way as a slider (adjust by sliding up/down, way outside the knob's area), you get the same functionality and can pack in many more knobs!

  • edited December 2018

    so clearly nothing I choose will make everyone happy :-)

    I quite like the sliders I've made and they probably suit my new app - so going to give them a go

    I'll see if I can take the logic I've just made for the sliders and make the Autony knobs work in the same way - I'm a little uncomfortable dramatically changing the UI for Autony anyway TBH

  • @pagefall said:
    so clearly nothing I choose will make everyone happy :-)

    I quite like the sliders I've made and they probably suit my new app - so going to give them a go

    I'll see if I can take the logic I've just made for the sliders and make the Autony knobs work in the same way - I'm a little uncomfortable dramatically changing the UI for Autony anyway TBH

    That looks pretty fun. Definitely getting that new app of yours.

  • edited December 2018

    Using the slider logic for the knobs movement seems to be good!

    Planning a reasonably big update for Autony in the new year: velocity functions, compact layout for phones, new knobs (might have a go at how they look too - dunno) and maybe triplets!

    I'll probably do a mini beta for the kind people who have already offered just to try the new knob logic before I release it as well

  • Looks good, and sounds great!

Sign In or Register to comment.