Hi! If your question relates to Loopy Pro, you may find a faster answer at one of the other Loopy Pro communities (https://loopypro.com/communities) – this forum has only a small number of active users.
So why has this not happened yet?
Every other looper out there has some form of record trigger
Usually it's a threshold trigger.
Either ways it been a long time waiting and loopyhd is getting long in the tooth now
And don't mention masterpiece cos that is not a contender or active solution right now and just places it on the long finger.
This is something was needed like yesterday and yet we are still waiting.
As a suggestion
Looking at the current interface the best way to implement this would be to place a "Triigger On/Off" button on the orange side bar for easy access. We could swipe to this option which would also have trigger treshold slider on the same bar.
I agree many people would find this useful.
I really don't think we'll get bigger feature revisions like this before version 3.0, also known as Loopy Masterpiece Edition.
In the meantime, the MIDI bindings execute very well with a foot pedal. I've finally gotten to the point where an audio threshold trigger is just not necessary.
Foot pedal solution you assume someone is always set up this way.. This is a mobile device so one cannot assume that we all have foot pedals always attached to our feet. Audio trigger IS an important missing feature and should have been prioritized along time ago and just forces me to have to use some other software instead of loopyhd to compensate for a well over due function that has been pointed out and requested along time ago but ignored. It is really frustrating when developers ignore the people that actually use a product in the real world and leave us hanging in the wind like this.
It's interesting that I have found Michael to be one of the most open, inquisitive, and responsive iOS developers. Loopy offers a superior UX as a result (I've tried most of the competitors). You are looking for a specific feature that he chose not to pursue. That's unfortunate for you because you haven't gotten the feature you desire, but it's like complaining that Picasso didn't use enough red in his blue period. Try the Looperverse app for the feature you are looking for.
There are many other apps that have the feature like
To mention a few
And so it's logical that they do, just as logical for loopy to have it too regardless of desire
Are we sure that audio trigger isn't going to be implemented in Loopy3?
Maybe it will or not but in there is a prob since we don't know or even when, we can't plan for it. It's all hoping for now and while we wait and wait it still don't resolve the current void which is lack of very needed functionality.
Don't get me wrong, I love loopyhd, it just now a shame I'm forced out of it for such a simple but needed feature.
I think we all have been frustrated by the lack of a feature we want in an app. But suggesting that the dev is ignoring users--when we have ample evidence that it's not true--takes it to a different level. Hope you do get the feature you want in Loopy 3 or elsewhere.
See we need to separate the difference between feature and function. A feature is an extra enhncement of a standard. A function is what something should do. Just like a front door can close but should have a lock and key.
You have to bring the human aspect to the table. We humans only have 2 hands and in music they are premium and needed to operate the instrument of choice and since this is a mobile device and we use other apps for sound how does one trigger loopy to record when it's no longer on the screen? MIDI is not always an option and as mentioned we don't always have foot pedals at our feet. So once again I would not call this a feature, rather a nessacery function that has been overlooked.
I don't really see the point in this topic.
We know for sure what you ask will be implemented in the next major release of Loopy, and is available already in some other looper apps.
I understand that you want really hard a feature, ans i won't discuss the obvious usefullness of the feature we are discussing here, but whining about it won't bring it in the app sooner.
We can ask for this or that for the futur of loopy but must respect the developer schedule (or go and find an alternative).
This feature WILL be part of loopy 3 and I'm certain it will also trickle down to the current version.
As others pointed out, if you can't live without it there are alternatives.
"don't really see the point in this topic."
Well then don't participate ignore it and don't inject your fustration on a topic by trying to turn a discussion into a wine. The discussion is conscise and logical. If you can't handle that KEEP OUT!
Anyway I digress,
We will I suppose just have to wait and see.
''there are alternatives.''
I'm already there
Just to jump in and try to cool this down - this is already implemented in Loopy 3, so rest assured it's in there. I don't have the time to retrofit into Loopy 2, unfortunately - it's just me here, and I need to prioritise work on 3 (for the sake of my family's finances, if nothing else!). I'm sorry you feel annoyed that I never got around to building the threshold trigger - it was just never high enough priority, compared to the other pressures on my time. Being a solo developer has its downsides. I don't ignore anyone, but I do have to triage from time to time, and those features requested by just a few users have fallen by the wayside.
Don't forget, though, that Loopy 3 is my answer to this - it's the 'director's cut' version of Loopy that I always wanted to make, based on conversations I've had with various users along the way. I know you discount it as irrelevant, @Quinnx, but it's anything but, for me, and I think people're going to be pleased when they see it!
Look forward to supporting loopy v3 you deserve it since we where quite spoiled with loopyhd which I think you under charged for and I think you discounted too.
I still think it's a great app,
And hurry with v3 so we can give you all our money