Loopy Pro is here!

cuberoo_

@wim said:

@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.

thanks for the response, i am failing to find how to set the play/stop trigger when using midi learn independently. I can set play or stop to be controlled by a note on msg, but i don't seem to be able to find how to do have different note for play and stop. sorry if i'm missing something simple.

BladeRunner

If only it would be able to use the Lumbeat drum machines from within like Quantiloop does. The only way I found was using AUM with Ableton Link. But start and stop have to be done manually. Of course using AUM ads another layer of complexity which ruins the experience. Us guitar players like to be able to concentrate on our instruments and not so much on the software.
Even adding midi control is a bit convoluted IMHO.
Is there at least a way to fade out loops over time while recording over top like Quantiloop does?

wim

@cuberoo_ said:

@wim said:

@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.

thanks for the response, i am failing to find how to set the play/stop trigger when using midi learn independently. I can set play or stop to be controlled by a note on msg, but i don't seem to be able to find how to do have different note for play and stop. sorry if i'm missing something simple.

When you set up the action, there's a sub-menu underneath Play/Stop. It's there that you can choose only play or stop individually. So, you'd set up one binding for play and another for stop.

sigma79

@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 )

@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!

Yeah man.

I will be buying for when I get my turntable sorted. Always wanted to loop via record but loopy is good at making tracks with audio. Might even be enough but as a host. Might defeat loopy philosphy and because of cpu.

Loopy makes a sequencer. Which has p locks and tweak an auv3 for midi learn. Then just record audio loops. There will be background midi. Your best loops, you can just move a donut to a sequencer and it be midi but also it gives you the data of the preset you used for the audio because the save state is within loopy but it would actually be more cpu than either midi or audio. It would be midi and audio. Unless there be a background cpu effecient midi.

cuberoo_

@wim said:

@cuberoo_ said:

@wim said:

@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.

thanks for the response, i am failing to find how to set the play/stop trigger when using midi learn independently. I can set play or stop to be controlled by a note on msg, but i don't seem to be able to find how to do have different note for play and stop. sorry if i'm missing something simple.

When you set up the action, there's a sub-menu underneath Play/Stop. It's there that you can choose only play or stop individually. So, you'd set up one binding for play and another for stop.

Yes I tried that, but it seems you can only set either play or stop, not a different mapping for each.

sigma79

mpe via record. Cool idea. A digital deck with some sort of mpe stuff which is triggered via button near a xfader. Probably would be better with a haptic style jogwheel.

espiegel123

@cuberoo_ said:

@wim said:

@cuberoo_ said:

@wim said:

@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.

thanks for the response, i am failing to find how to set the play/stop trigger when using midi learn independently. I can set play or stop to be controlled by a note on msg, but i don't seem to be able to find how to do have different note for play and stop. sorry if i'm missing something simple.

When you set up the action, there's a sub-menu underneath Play/Stop. It's there that you can choose only play or stop individually. So, you'd set up one binding for play and another for stop.

Yes I tried that, but it seems you can only set either play or stop, not a different mapping for each.

Go into Midi Control.

Add Binding and choose the action (let’s say play). Send the midi to learn it or enter the midi trigger by hand.

Save the binding,

Add another binding for stop.

This can be done simply with midi learn too by learning two triggers then customizing the bindings created by midi learn

cuberoo_

@espiegel123 said:

@cuberoo_ said:

@wim said:

@cuberoo_ said:

@wim said:

@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.

thanks for the response, i am failing to find how to set the play/stop trigger when using midi learn independently. I can set play or stop to be controlled by a note on msg, but i don't seem to be able to find how to do have different note for play and stop. sorry if i'm missing something simple.

When you set up the action, there's a sub-menu underneath Play/Stop. It's there that you can choose only play or stop individually. So, you'd set up one binding for play and another for stop.

Yes I tried that, but it seems you can only set either play or stop, not a different mapping for each.

Go into Midi Control.

Add Binding and choose the action (let’s say play). Send the midi to learn it or enter the midi trigger by hand.

Save the binding,

Add another binding for stop.

This can be done simply with midi learn too by learning two triggers then customizing the bindings created by midi learn

thanks, all working now. failed to add a new binding before.

wim

@cuberoo_ said:
Yes I tried that, but it seems you can only set either play or stop, not a different mapping for each.

Yes, you can. Just set up two actions. One for play, and one for stop. I don't know how to explain it better than that. If it still doesn't make sense then I'll try do do a quick video.

[edit] oops. I noticed it's already handled after I posted that.

espiegel123

@danbobakov said:

@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.

Btw, if it picks hold, you can tap "on" in the binding setup. There is no need to start over with the binding.

Michael_R_Grant

@jonmoore said:

@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.

Yes, I think that’s it. I remember the prices being different between the two versions and being pleasantly surprised when it came to actually buy the app.

Michael_R_Grant

@mistercharlie said:
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!

Or put Perforator on a bus and add a send to the loop colours!

3sleeves

Can anyone advise if it is possible to have one-shot samples not be affected by the master tempo?

I’m trying to make a template for a live DJ set, which includes a page of one-shot pads, each with a 2-3 minute song loaded up. For whatever reason I cannot seem to get the settings right to make the songs play at their respective native tempos, independent of the master.

Is this something obvious I’m overlooking?

Michael_R_Grant

@3sleeves said:
Can anyone advise if it is possible to have one-shot samples not be affected by the master tempo?

I’m trying to make a template for a live DJ set, which includes a page of one-shot pads, each with a 2-3 minute song loaded up. For whatever reason I cannot seem to get the settings right to make the songs play at their respective native tempos, independent of the master.

Is this something obvious I’m overlooking?

I don’t think that’s possible at the moment, but I’m hopeful it’s a feature that will be added sooner rather than later. I’ve just posted it again in the Slack channel.

celtic_elk

@Michael_R_Grant said:

@mistercharlie said:
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!

Or put Perforator on a bus and add a send to the loop colours!

Or Beatcutter, likewise.

3sleeves

@Michael_R_Grant said:

@3sleeves said:
Can anyone advise if it is possible to have one-shot samples not be affected by the master tempo?

I’m trying to make a template for a live DJ set, which includes a page of one-shot pads, each with a 2-3 minute song loaded up. For whatever reason I cannot seem to get the settings right to make the songs play at their respective native tempos, independent of the master.

Is this something obvious I’m overlooking?

I don’t think that’s possible at the moment, but I’m hopeful it’s a feature that will be added sooner rather than later. I’ve just posted it again in the Slack channel.

Thank you!
For now I may have a workaround with DramboAU and the shot sampler module, testing is going well so far. Next step is to map some buttons on the Loopy template to control DramboAU.

UPDATE: Auditor File Player is the perfect tool for this job. The files just have to be saved at the same sample rate as the Loopy Pro system settings.

ghost_forests

@hellquist said:
I do a lot of photography and photo editing. Late last year I came across a piece of software called Luminar. It looked great so I gave the free trial a spin, which was impressive, and I needed some of the functionality "NOW" (deadlines etc). During my trial they announced "the next version" (Luminar AI).

Ah yes, Luminar AI, otherwise known as the app that kills photography as an art form

tahiche

@espiegel123 said:

@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.

Ok I figured it out after reading some posts here. To clarify, I know that retrospective uses the master length. But that’s not “retrospective enough”, what I want is to decide how many bars I want to retro-record. So after reading some posts I did it with a gesture. It changes the master length and then records, but it’s instantaneous and after your playing, when you hit the rec button. So I’ve set up a couple of “retro recording “ buttons on a template, one for retro master (whatever master length is at that point), one for 2 bars, one for 8 bars and so on… works great.

espiegel123

@tahiche said:

@espiegel123 said:

@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.

Ok I figured it out after reading some posts here. To clarify, I know that retrospective uses the master length. But that’s not “retrospective enough”, what I want is to decide how many bars I want to retro-record. So after reading some posts I did it with a gesture. It changes the master length and then records, but it’s instantaneous and after your playing, when you hit the rec button. So I’ve set up a couple of “retro recording “ buttons on a template, one for retro master (whatever master length is at that point), one for 2 bars, one for 8 bars and so on… works great.

be aware that if you change the master length just before initiating the recording, the new master length needs to be less than the largest the master length has been. so if you plan on changing it at record time, you probably want to start with it set to the longest length you might want. For example, if you might want to retro record as far back as 16 measures....you should start with it at 16 measures. The master will hold 16 measures from then on even if the master length is shorter.

rickelal3

Wow played with the trial for a couple of days and just bought the full unlock today! What an app, thats all i can say! Blew all my expectations out the door. Is there any point of using AUM anymore? Is there anything AUM can do that loopy cant?

rickelal3

Is there anyway to connect a auv3 to midi app that’s not auv3 like soundprism or navichord?

espiegel123

@rickelal3 said:
Wow played with the trial for a couple of days and just bought the full unlock today! What an app, thats all i can say! Blew all my expectations out the door. Is there any point of using AUM anymore? Is there anything AUM can do that loopy cant?

AUM can handle IAA apps and handle multi input and output AUv3 and side-chaining.

espiegel123

@rickelal3 said:
Is there anyway to connect a auv3 to midi app that’s not auv3 like soundprism or navichord?

If they publish their virtual midi port or can direct their MIDI to Loopy Pro's virtual midi port, use Add Midi on the mixer page to add the appropriate MIDI port. you can then choose any AU in your project as a destination.

mistercharlie

@celtic_elk said:

@Michael_R_Grant said:

@mistercharlie said:
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!

Or put Perforator on a bus and add a send to the loop colours!

Or Beatcutter, likewise.

Or GlitchCore, which is turning out to be very Octatrack-like!

espiegel123

Someone asked how to switch one audio input between different colors with different effects, monitoring wet and recording dry

Michael

@uncledave said:

@szczyp said:
MIDI works as you said, 5 stars and review written.
Maybe in the future session midi network will be seen as midi port? At least on my iPad it is hidden in LP.
AUM can use network midi port, LoopyPro not (yet).

As a workaround, you could use another app to receive Network MIDI and forward it to a port LP can see. Possible apps are AUM, Audiobus, MidiFire, probably others.

I’m probably really late with the reply, but LP does do network MIDI; you should see the name of the remote devices come up in the midi list.

Michael

@slicetwo said:
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?

Interesting! Would you mind sending me your crackly project? ([email protected]). And also the one with the weird doubling of the tail?

Pierre118

@Michael I think the IAP price in the LP Testflight version not matched with the actual App Store IAP price. If downloaded from the App Store the pricing is matched correctly.

Happy Xmas!

Michael

@Pierre118 said:
@Michael I think the IAP price in the LP Testflight version not matched with the actual App Store IAP price. If downloaded from the App Store the pricing is matched correctly.

Happy Xmas!

Ah yeah I saw that after I posted the reply 😄 I’m a little behind! And phew, that’s a relief. Weird bug though (but Apple’s, not mine - hurray!)

Happy Xmas!

Michael_R_Grant

A very simple jam, this - I’m barely using Loopy Pro here, but it’s a lot of fun to play Animoog Z on a Roli Seaboard Block. I’m not exactly a keyboard player, but I love how expressive MPE can be.