Loopy Pro is here!

celtic_elk

@Stuntman_mike said:
The sequencer reminds me of the old ACID days of painting loops. Loopy Pro is so fantastic, truly a labor of love!

Now there’s a blast from the past!

Krupa

@hellquist said:

@wim said:

@tja said:

@Krupa said:
Will the twelve month thing be a universal/global period (or 2022-23), or per user? The latter seems almost impossible for Michael to coordinate, especially allowing for bug fixes, even early seems like something that will get administratively worse for him as time goes on… I hope the model works out for him though, fully deserved as this thing is incredible!

Right, that was not made clear too!

Assuming it is implemented like in Working Copy, it is individual.
Meaning, you get all features from the moment you buy and the next 12 months.

I think that’s correct. I’m not sure of the mechanics, but I’m sure it doesn’t require intervention from Michael. Working Copy is the app he modeled this after.

Also the note-taking/calendar app Agenda , which is cross-platform for iOS/macOS, has the same model. Pay for the app and 12 months of updates. If you don't pay the renewal you still have the feature additions added whilst you paid for it. At any time I can continue to pay for another 12 months, and that also gives me the eventual features added between when I stopped paying and up to current date. Good model I think. Very fair. With Agenda I didn't pay for a full year as the feature additions didn't look that useful to me, then they added some new stuff that was very useful indeed and I got it all when I "continued" (as I had been a paying customer previously).

Also Agenda clearly tells the user, via lists in app, what features the user has paid for and which features that would be enabled if I pay for it again (I am currently, again, not paying for Agenda as I have changed how I take notes and manage calendar).

Yeah, it’s more than fair to the user, not what I expected, seems like a real workload for the dev, but maybe it’s trivial…

slicetwo

I hooked up LP to my 18i20 last night to really give it a go for my work flow. The goal was to record loops from 6 pieces of hardware. I ran into some issues/confusions as I worked through it.

1. I recorded some 4 bar drum loops and have it set to play the outro wrapped around, but now it’s actually doubling the drum loop the 2nd go around and causing phase issues. Same with a few instrument loops.

2. I am getting crackling at the beginning of almost every loop recorded. I’m starting the recordings then hitting play on my hardware since LP can’t sync, so it’s def capturing the proper beginnings.

3. I’m trying to do the 4 bar loop with 1 bar tail recording, but it seems like I have to arm LP, start the recording, then play the loop on the hardware, then stop it and try and edit the loop to fit with the tail. How, exactly, is the tail recording supposed to work?

gregsmith

@hellquist said:

@wim said:

@tja said:

@Krupa said:
Will the twelve month thing be a universal/global period (or 2022-23), or per user? The latter seems almost impossible for Michael to coordinate, especially allowing for bug fixes, even early seems like something that will get administratively worse for him as time goes on… I hope the model works out for him though, fully deserved as this thing is incredible!

Right, that was not made clear too!

Assuming it is implemented like in Working Copy, it is individual.
Meaning, you get all features from the moment you buy and the next 12 months.

I think that’s correct. I’m not sure of the mechanics, but I’m sure it doesn’t require intervention from Michael. Working Copy is the app he modeled this after.

Also the note-taking/calendar app Agenda , which is cross-platform for iOS/macOS, has the same model. Pay for the app and 12 months of updates. If you don't pay the renewal you still have the feature additions added whilst you paid for it. At any time I can continue to pay for another 12 months, and that also gives me the eventual features added between when I stopped paying and up to current date. Good model I think. Very fair. With Agenda I didn't pay for a full year as the feature additions didn't look that useful to me, then they added some new stuff that was very useful indeed and I got it all when I "continued" (as I had been a paying customer previously).

Also Agenda clearly tells the user, via lists in app, what features the user has paid for and which features that would be enabled if I pay for it again (I am currently, again, not paying for Agenda as I have changed how I take notes and manage calendar).

It must give the devs more motivation to add new features to keep people upgrading. When a new version of Ableton Live comes out, the devs make a big effort to make it worth the upgrade right?

If nanostudio 2 had this model, would we have audio tracks by now? That isn’t supposed to be antagonistic, just a thought.

klownshed

I’m very much looking forward to getting loopy pro very soon, as soon as the Xmas craziness slows down (three over excited under 10s off school means no time to think!)

I’m thinking it will be a really good substitute (or perhaps addition to) my current favourite way of working on iOS which is to use BlocsWave to > @jonmoore said:

@Michael

The UK price in-app has gone up to £28.99 from £25.99 and the 'upgrade' is now listed in-app as £18.99 up from £16.99. The listing on the app store has the old prices.

It's not an issue for me as I'm not in the market for Loopy Pro (what you've achieved is very polished, it's simply not something I would find myself using on a regular basis). I'll reassess things as the MIDI side of the app gets fleshed out, but my instinct right now is that AUM in tandem with Enso/Gaus more than furfills my occasional forays into looping.

The conversion from US currency to UK currency is far worse than that you get with other apps (a $29.99 app becomes £28.99). Plus, I don't think it's sending out the right message to those that downloaded Loopy Pro at launch that the price has mysteriously gone up by £3. The money isn't the issue but it gives the impression that you might move the goalposts with the yearly maintenance. For comparison ref currency differences, Staffpad is listed at the moment for $39.99 and the UK price is £34.99. Your original UK pricing was at a similar ratio to Staffpad.

There's rightly a lot of loyalty here on the AB forum for what you've done for the iOS audio community over the years, but you need to think about your offer to those that don't frequent the AB forum as these are the folk that will make up the majority of your user base in the long run.

Weird. It’s showing as £25.99 for me still…

sigma79

Might be cool. If you made your own sequencer where you can p-lock but save midi of the audio. Background midi. You could use loopy for audio as it fast to record loops but then copy and paste audio ( which would be midi )

So just making loops but then all audio copies would actually have a midi save. Maybe it wouldnt be good for cpu.

[Deleted User]

The user and all related content has been deleted.

Gdub

Been on the beta for a few months
Been a blast
Got pretty good at understanding everything
Then last few days it has really clicked
This is a marvel, I wake up with so many ideas, templates,
I have gone from having massive AUM sessions straining my iPad to collections of loops from those projects
Have made 4 songs in 4 days, that’s more than I made in the last year, when automation comes to the sequencer happy days
Thanks for the super hard work you put into this @Michael
To the people that are struggling, sit in there, it will click
Watch some of the videos
Make some new projects and just try everything,
Download some of the templates
Pick the bits you need, copy them and paste into a new project, or select the item, go into edit mode and see what was done to achieve it’s actions
Go make some beats !!

gregsmith

@sigma79 said:
Might be cool. If you made your own sequencer where you can p-lock but save midi of the audio. Background midi. You could use loopy for audio as it fast to record loops but then copy and paste audio ( which would be midi )

So just making loops but then all audio copies would actually have a midi save. Maybe it wouldnt be good for cpu.

I’m really hoping there will be a way to do something along these lines. Currently if you feed all input through an atom 2 instance, you could record the midi and audio simultaneously, but it’d be a right faff to setup!

espiegel123

@tahiche said:

@ronnieb said:

@AudioGus said:

@ronnieb said:

@AudioGus said:

@gregsmith said:

@AudioGus said:

@gregsmith said:

@AudioGus said:

@lukesleepwalker said:

@Michael_R_Grant said:

@Kashi said:

@suitsus said:

@Kashi said:

You can set quantisation per individual loop so I think you can achieve what you want. Suggest you download and try before you buy!

Ok thanks I’ll look into that. Do you mean there might be a “no quantisation “ option which is what I will need. I realise that wanting things to NOT sync up with each other is anathema to most looping/sequencing software/hardware, and will confuse some forum members, but that really is what I want!

Yes, you can set loops to be free rather than 'Phase Locked'. Also, you should explore the record and play quantisation options to configure how you want to start and stop loops. You can record an FX tail after the loop ends, and an intro before the main body of the loop starts, too!

Yeah, all these things! It's simply amazing how many options you have to start/stop loops. Download and try for free?

Does the retrospective looper let you select the length of the uhhh, captured retrospection, after you have already been retrospecting, ala the Endlesss advanced looper setting?

I ask because I don't want to be blow my 7 day trial just yet.

You can indeed set the length of the loop beforehand. Just swipe up on the donut and set it there. It works beautifully with 1 bar, but I’ve had some problems with 4 bars for some reason.

I know you can set it beforehand but that is not what I am asking. In Endlesss you can choose to capture either the previous 1,2,4 or 8 bars on the fly, simply by tapping the waveform in one of the four quadrants. This is the best thing about Endlesss for me and why I would still use it over any other looper.

Only being able to set the length beforehand kind of limits the free flow creative potential of retrospective looping.

Oh I see! I’m not sure. It seems to capture a bar if you don’t set the length beforehand and there doesn’t seem to be a way to lengthen it that I can see.

Someone else might know different.

Edit: just seen @espiegel123 replied above

Yes, but I think he assumed I was asking the same thing that you thought, size of the overall buffer and not wether or not you could capture a portion of that buffer on the fly, again ala Endlesss. I assume at this point that it cannot be done.

Not able to test atm but I think you could just setup 4 buttons to retrospective record for 1/2/4/8 bars no?
Or what I have is separate clips for each length. I am certain if you spend some time with the widgets you could figure out a way to implement this that works for you.

I think that is still different though because then you are still locked in at that point to committing to filling X bars.

Not if you’re using retrospective recording which is what endless is doing. My super basic bare bones auv3 template kinda does this. The orange clips are standard recording, the yellow clips are set to retrospective record, top row has specific lengths and the bottom just follow the master cycle. Is this not similar to what you’re looking for?

How do you set specific lengths for retrospective recording?. Can’t find it anywhere. Count out options are grayed out when choosing retrospective.
Cheers

@tahiche : the master (cycle) length sets the retrospective loop length.

espiegel123

@slicetwo : when recording a tail, loopy is waiting for the level to drop to silence. The tail outro is going to be the audio that plays from when recording hit the “stop” point till it dies back down to zero. You can hear what is in the outro by playing the loop and tapping it to stop and listening to what plays.

jonmoore

@tja said:
@jonmoore What do you do with your AUM / Enso / Gauss loops?
Recording them into a DAW for mixing and mastering, or just live playing without further processing?

I occasionally use my iPad for tape loop/delay fx where AUM is used to create the feedback loops with added saturation and degradation. A good example was when I recreated the tape loop fx for my Roxy Music remix of 2HB (a beatless ambient-ish affair). Audio is routed from my desktop DAW to my iPad and then routed back out to my DAW. I'm effectively using my iPad as an outboard fx unit. The link below is the full remix to stream and download.

The tape looping is used in both the midsection and the outro. This was a vinyl-only release so I'm only going to leave the 320k MP3 download active over the Xmas period (but I'll leave streaming active in perpetuity). I've also linked to the 60-second teaser Ferry posted on his YT when the vinyl was in store.

https://d.pr/a/80clEU

jonmoore

@klownshed said:
I’m very much looking forward to getting loopy pro very soon, as soon as the Xmas craziness slows down (three over excited under 10s off school means no time to think!)

I’m thinking it will be a really good substitute (or perhaps addition to) my current favourite way of working on iOS which is to use BlocsWave to > @jonmoore said:

@Michael

The UK price in-app has gone up to £28.99 from £25.99 and the 'upgrade' is now listed in-app as £18.99 up from £16.99. The listing on the app store has the old prices.

It's not an issue for me as I'm not in the market for Loopy Pro (what you've achieved is very polished, it's simply not something I would find myself using on a regular basis). I'll reassess things as the MIDI side of the app gets fleshed out, but my instinct right now is that AUM in tandem with Enso/Gaus more than furfills my occasional forays into looping.

The conversion from US currency to UK currency is far worse than that you get with other apps (a $29.99 app becomes £28.99). Plus, I don't think it's sending out the right message to those that downloaded Loopy Pro at launch that the price has mysteriously gone up by £3. The money isn't the issue but it gives the impression that you might move the goalposts with the yearly maintenance. For comparison ref currency differences, Staffpad is listed at the moment for $39.99 and the UK price is £34.99. Your original UK pricing was at a similar ratio to Staffpad.

There's rightly a lot of loyalty here on the AB forum for what you've done for the iOS audio community over the years, but you need to think about your offer to those that don't frequent the AB forum as these are the folk that will make up the majority of your user base in the long run.

Weird. It’s showing as £25.99 for me still…

My download is the Testflight version so maybe that accounts for the difference.

slicetwo

@espiegel123 said:
@slicetwo : when recording a tail, loopy is waiting for the level to drop to silence. The tail outro is going to be the audio that plays from when recording hit the “stop” point till it dies back down to zero. You can hear what is in the outro by playing the loop and tapping it to stop and listening to what plays.

Cool. I’m off for the week so I plan to really test it out more.

ronnieb

@tahiche said:

@ronnieb said:

@AudioGus said:

@ronnieb said:

@AudioGus said:

@gregsmith said:

@AudioGus said:

@gregsmith said:

@AudioGus said:

@lukesleepwalker said:

@Michael_R_Grant said:

@Kashi said:

@suitsus said:

@Kashi said:

You can set quantisation per individual loop so I think you can achieve what you want. Suggest you download and try before you buy!

Ok thanks I’ll look into that. Do you mean there might be a “no quantisation “ option which is what I will need. I realise that wanting things to NOT sync up with each other is anathema to most looping/sequencing software/hardware, and will confuse some forum members, but that really is what I want!

Yes, you can set loops to be free rather than 'Phase Locked'. Also, you should explore the record and play quantisation options to configure how you want to start and stop loops. You can record an FX tail after the loop ends, and an intro before the main body of the loop starts, too!

Yeah, all these things! It's simply amazing how many options you have to start/stop loops. Download and try for free?

Does the retrospective looper let you select the length of the uhhh, captured retrospection, after you have already been retrospecting, ala the Endlesss advanced looper setting?

I ask because I don't want to be blow my 7 day trial just yet.

You can indeed set the length of the loop beforehand. Just swipe up on the donut and set it there. It works beautifully with 1 bar, but I’ve had some problems with 4 bars for some reason.

I know you can set it beforehand but that is not what I am asking. In Endlesss you can choose to capture either the previous 1,2,4 or 8 bars on the fly, simply by tapping the waveform in one of the four quadrants. This is the best thing about Endlesss for me and why I would still use it over any other looper.

Only being able to set the length beforehand kind of limits the free flow creative potential of retrospective looping.

Oh I see! I’m not sure. It seems to capture a bar if you don’t set the length beforehand and there doesn’t seem to be a way to lengthen it that I can see.

Someone else might know different.

Edit: just seen @espiegel123 replied above

Yes, but I think he assumed I was asking the same thing that you thought, size of the overall buffer and not wether or not you could capture a portion of that buffer on the fly, again ala Endlesss. I assume at this point that it cannot be done.

Not able to test atm but I think you could just setup 4 buttons to retrospective record for 1/2/4/8 bars no?
Or what I have is separate clips for each length. I am certain if you spend some time with the widgets you could figure out a way to implement this that works for you.

I think that is still different though because then you are still locked in at that point to committing to filling X bars.

Not if you’re using retrospective recording which is what endless is doing. My super basic bare bones auv3 template kinda does this. The orange clips are standard recording, the yellow clips are set to retrospective record, top row has specific lengths and the bottom just follow the master cycle. Is this not similar to what you’re looking for?

How do you set specific lengths for retrospective recording?. Can’t find it anywhere. Count out options are grayed out when choosing retrospective.
Cheers

You can just set the length of the clips individually in the clip settings

espiegel123

@ronnieb said:

@tahiche said:

@ronnieb said:

@AudioGus said:

@ronnieb said:

@AudioGus said:

@gregsmith said:

@AudioGus said:

@gregsmith said:

@AudioGus said:

@lukesleepwalker said:

@Michael_R_Grant said:

@Kashi said:

@suitsus said:

@Kashi said:

You can set quantisation per individual loop so I think you can achieve what you want. Suggest you download and try before you buy!

Ok thanks I’ll look into that. Do you mean there might be a “no quantisation “ option which is what I will need. I realise that wanting things to NOT sync up with each other is anathema to most looping/sequencing software/hardware, and will confuse some forum members, but that really is what I want!

Yes, you can set loops to be free rather than 'Phase Locked'. Also, you should explore the record and play quantisation options to configure how you want to start and stop loops. You can record an FX tail after the loop ends, and an intro before the main body of the loop starts, too!

Yeah, all these things! It's simply amazing how many options you have to start/stop loops. Download and try for free?

Does the retrospective looper let you select the length of the uhhh, captured retrospection, after you have already been retrospecting, ala the Endlesss advanced looper setting?

I ask because I don't want to be blow my 7 day trial just yet.

You can indeed set the length of the loop beforehand. Just swipe up on the donut and set it there. It works beautifully with 1 bar, but I’ve had some problems with 4 bars for some reason.

I know you can set it beforehand but that is not what I am asking. In Endlesss you can choose to capture either the previous 1,2,4 or 8 bars on the fly, simply by tapping the waveform in one of the four quadrants. This is the best thing about Endlesss for me and why I would still use it over any other looper.

Only being able to set the length beforehand kind of limits the free flow creative potential of retrospective looping.

Oh I see! I’m not sure. It seems to capture a bar if you don’t set the length beforehand and there doesn’t seem to be a way to lengthen it that I can see.

Someone else might know different.

Edit: just seen @espiegel123 replied above

Yes, but I think he assumed I was asking the same thing that you thought, size of the overall buffer and not wether or not you could capture a portion of that buffer on the fly, again ala Endlesss. I assume at this point that it cannot be done.

Not able to test atm but I think you could just setup 4 buttons to retrospective record for 1/2/4/8 bars no?
Or what I have is separate clips for each length. I am certain if you spend some time with the widgets you could figure out a way to implement this that works for you.

I think that is still different though because then you are still locked in at that point to committing to filling X bars.

Not if you’re using retrospective recording which is what endless is doing. My super basic bare bones auv3 template kinda does this. The orange clips are standard recording, the yellow clips are set to retrospective record, top row has specific lengths and the bottom just follow the master cycle. Is this not similar to what you’re looking for?

How do you set specific lengths for retrospective recording?. Can’t find it anywhere. Count out options are grayed out when choosing retrospective.
Cheers

You can just set the length of the clips individually in the clip settings

You can also use the master length available in the tempo panel without presenting the clip length.

You may know this but I mention it since it seems like this is a point confusion for some.

sch

@tja said:

If nanostudio 2 had this model, would we have audio tracks by now? That isn’t supposed to be antagonistic, just a thought.

I would pay the original price again to get audio tracks. Finally.

Count me in too!

sch

Just left a 5-star review as part of the Canadian contingent!

mistercharlie

It would be good to move the discussion of the price over to the dedicated thread…

https://forum.audiob.us/discussion/46425/breakout-discussion-of-pricing-business-models-from-loopy-pro-thread

… And leave this one for talking about all the great stuff in the app.

Also—just had an Octatrack moment. I realized I can load a stutter AU (Perforator) as an effect into a color channel. Let’s say the yellow channel

Then, I just resample anything into a yellow loop, and it gets glitched, instantly. It’s like sampling into a pre-sliced buffer on Octatrack. Wild stuff!

danbobakov

I’m trying to setup control of loopy pro with my Morningstar mc8 and can’t get a loop without lag from the switch to the time it starts recording.
The midi switcher is in looper mode so there shouldn’t be any latency. And I have the buffer setting on 64 on loopy pro.
Tried with midi over usb and with midi din through a presonus interface.

Before I used this exact setup with the Morningstar switcher to an rc505 and had no latency at all.

I know everything is pretty new here with loopy, but I figured I’d ask if anyone here has any latency with foot switch controllers there using. Using a launchpad mini there was no latency at all.
I’m using a 2021 ipad 10.2

espiegel123

@danbobakov said:
I’m trying to setup control of loopy pro with my Morningstar mc8 and can’t get a loop without lag from the switch to the time it starts recording.
The midi switcher is in looper mode so there shouldn’t be any latency. And I have the buffer setting on 64 on loopy pro.
Tried with midi over usb and with midi din through a presonus interface.

Before I used this exact setup with the Morningstar switcher to an rc505 and had no latency at all.

I know everything is pretty new here with loopy, but I figured I’d ask if anyone here has any latency with foot switch controllers there using. Using a launchpad mini there was no latency at all.
I’m using a 2021 ipad 10.2

what midi event is the footswitch sending? i am not experiencing lag with my blueboard. how much lag are you experiencing?

can you post a screen shot of your midi binding?

danbobakov

@espie

what midi event is the footswitch sending? i am not experiencing lag with my blueboard. how much lag are you experiencing?

can you post a screen shot of your midi binding?

It was a simple cc message on binding.
I used a midi monitor to triple check everything.

So crazy thing is then I just had the idea to try if it would have lag as an auv3 in AUM and now everything works perfect.

Exited out of AUM and tried stand-alone loopy again and now everything works as it should….

danbobakov

It was like 35ms lag so extremely noticeable playing a rhythm loop.

espiegel123

@danbobakov said:
It was like 35ms lag so extremely noticeable playing a rhythm loop.

I haven't seen anything like that. Once or twice (in hundreds of hours of use) , I have seen other MIDI weirdness that went away after a reboot.

danbobakov

@espiegel123 said:

@danbobakov said:
It was like 35ms lag so extremely noticeable playing a rhythm loop.

I haven't seen anything like that. Once or twice (in hundreds of hours of use) , I have seen other MIDI weirdness that went away after a reboot.

Yeah.. I rebooted the iPad so maybe that was it

wim

I've had cases where when midi learn assigned "Hold" as the message type. This resulted in delays. Changing it to "On" fixed the delay. That doesn't appear to be what happened here but I thought I'd toss it out there in case anyone else ran into that.

cuberoo_

Having fun with Loopy Pro... I do have a couple of simple questions:

• is it possible to set the midi notes for Play and Stop of a donut independently?
• it is possible, like in Live for example, to re-trigger a donut to play, so you could press play for example on a multi bar loop and it would restart once it reaches the re-trigger quantization?

+1 for midi channel filtering, on everything including anything set via midi learn

espiegel123

@cuberoo_ said:
Having fun with Loopy Pro... I do have a couple of simple questions:

• is it possible to set the midi notes for Play and Stop of a donut independently?

yes you can set separate play and stop midi triggers.

• it is possible, like in Live for example, to re-trigger a donut to play, so you could press play for example on a multi bar loop and it would restart once it reaches the re-trigger quantization?

see if setting the play/stop quantization gets yu what you want. you could even set up gestures with different quantizations.

+1 for midi channel filtering, on everything including anything set via midi learn

wim

@cuberoo_ said:
Having fun with Loopy Pro... I do have a couple of simple questions:

• is it possible to set the midi notes for Play and Stop of a donut independently?

Yes.

• it is possible, like in Live for example, to re-trigger a donut to play, so you could press play for example on a multi bar loop and it would restart once it reaches the re-trigger quantization?

I was able to make this work by setting up a button that stops the clip on press and restarts it on release. As long as you have just a very little bit of delay between press and release it works. There may be other ways to do it.

+1 for midi channel filtering, on everything including anything set via midi learn

There is already midi channel filtering, though you can currently only set one channel or all, not combinations of channels like you can in AUM.

Midi mapping can be done by channel too.

danbobakov

@wim said:
I've had cases where when midi learn assigned "Hold" as the message type. This resulted in delays. Changing it to "On" fixed the delay. That doesn't appear to be what happened here but I thought I'd toss it out there in case anyone else ran into that.

It was doing that at first and I just exited out before it assigned the hold. And also checked with my midi monitor to make sure all I was sending was an “on” message.