Loopy Pro is here!

orand

@wim said:
It's funny because I was one of the earliest whiners back when it was first said that MIDI looping would be sometime after the initial release. My thinking was that there are already more than enough audio loopers but really nothing that has both, so what better way to rise clearly above the competition?

Beta testing caused me to spend a good portion of time every day creating with no MIDI "safety net" and it was transformative. I've never had so much freedom and creativity released. Not being able to go back and endlessly tweak has really been freeing.

So, now I'm awaiting MIDI looping with mixed emotions. I know it's coming and that Michael will do a fabulous job with it, but I'm almost not looking forward to it. Very weird.

Finally what I came here to say ... I know it would cause a shitstorm of complaining, but I almost wish that MIDI looping would come with no editor beyond the trim and repositioning, and the import and export, exist for audio now.

This makes a pretty good case for “just” incorporating @GeertBevin ’s MIDI Tape Recorder source code into Loopy Pro, since it shares the same philosophy. It is licensed under a Creative Commons Attribution 4.0 International License, which appears to have no downsides for this scenario.
https://creativecommons.org/licenses/by/4.0/

lukesleepwalker

@orand said:

@wim said:
It's funny because I was one of the earliest whiners back when it was first said that MIDI looping would be sometime after the initial release. My thinking was that there are already more than enough audio loopers but really nothing that has both, so what better way to rise clearly above the competition?

Beta testing caused me to spend a good portion of time every day creating with no MIDI "safety net" and it was transformative. I've never had so much freedom and creativity released. Not being able to go back and endlessly tweak has really been freeing.

So, now I'm awaiting MIDI looping with mixed emotions. I know it's coming and that Michael will do a fabulous job with it, but I'm almost not looking forward to it. Very weird.

Finally what I came here to say ... I know it would cause a shitstorm of complaining, but I almost wish that MIDI looping would come with no editor beyond the trim and repositioning, and the import and export, exist for audio now.

This makes a pretty good case for “just” incorporating @GeertBevin ’s MIDI Tape Recorder source code into Loopy Pro, since it shares the same philosophy. It is licensed under a Creative Commons Attribution 4.0 International License, which appears to have no downsides for this scenario.
https://creativecommons.org/licenses/by/4.0/

This is the EXACT reason to use MRT in Loopy Pro. Once you let go of perfection, you both tell better and more human stories with music and become a better musician. The machines are already taking over—the only way to beat them is to be more human.

hat_cake

Is it currently possible to configure a button to play a random loop, and on every button press, it'd randomise again?

wim

@hat_cake said:
Is it currently possible to configure a button to play a random loop, and on every button press, it'd randomise again?

Sorry, no.

wim

@wim said:

@hat_cake said:
Is it currently possible to configure a button to play a random loop, and on every button press, it'd randomise again?

Sorry, no.

I suppose you could set up midi note bindings to launch clips, then use something like the Rounder Robin Mozaic script to send random notes to trigger them.

hat_cake

@wim said:

@wim said:

@hat_cake said:
Is it currently possible to configure a button to play a random loop, and on every button press, it'd randomise again?

Sorry, no.

I suppose you could set up midi note bindings to launch clips, then use something like the Rounder Robin Mozaic script to send random notes to trigger them.

ooh, thanks! thats a clever workaround idea
either that, or something along those lines, should be quite powerful..

GLacey

Is it normal that I can still hear (not hallucinating ) Loopy pro through my iPad's loudspeaker even if I turn the volume off? I don't understand how it is possible at all.
Ok, you might think this guy is a weirdo that he wants to play with loopy without sound
The simple explanation is that I woke up too early this morning and since I didn't have my headphones with me in the bed (but I had my wife in sleep mode ) I turned down the volume to zero and started exploring LoopyPro's menu and functions.

uncledave

@GLacey said:
Is it normal that I can still hear (not hallucinating ) Loopy pro through my iPad's loudspeaker even if I turn the volume off? I don't understand how it is possible at all.
Ok, you might think this guy is a weirdo that he wants to play with loopy without sound
The simple explanation is that I woke up too early this morning and since I didn't have my headphones with me in the bed (but I had my wife in sleep mode ) I turned down the volume to zero and started exploring LoopyPro's menu and functions.

Which volume did you turn off? If it's the iPad volume, I believe it only affects normal audio (music and voice), not "sounds", which Loopy Pro may be sending.

GLacey

@uncledave said:

@GLacey said:
Is it normal that I can still hear (not hallucinating ) Loopy pro through my iPad's loudspeaker even if I turn the volume off? I don't understand how it is possible at all.
Ok, you might think this guy is a weirdo that he wants to play with loopy without sound
The simple explanation is that I woke up too early this morning and since I didn't have my headphones with me in the bed (but I had my wife in sleep mode ) I turned down the volume to zero and started exploring LoopyPro's menu and functions.

Which volume did you turn off? If it's the iPad volume, I believe it only affects normal audio (music and voice), not "sounds", which Loopy Pro may be sending.

Yes, it's the iPad volume. But Loopy Pro's volume is changing as it should as I push the volume up or down buttons, but it still can be heard well at the zero setting, despite it should be silent, in other words the volume does not go under a certain level. I have never seen (heard) such thing in my other music apps.

Don't misunderstand me, it has zero effect on the productivity or the user experience, just simply don't understand how it is possible.

lukesleepwalker

@hat_cake said:

@wim said:

@wim said:

@hat_cake said:
Is it currently possible to configure a button to play a random loop, and on every button press, it'd randomise again?

Sorry, no.

I suppose you could set up midi note bindings to launch clips, then use something like the Rounder Robin Mozaic script to send random notes to trigger them.

ooh, thanks! thats a clever workaround idea
either that, or something along those lines, should be quite powerful..

This feature request has been made several times so here’s hoping the master can fit it in.

[Deleted User]

@GLacey said:

@uncledave said:

@GLacey said:
Is it normal that I can still hear (not hallucinating ) Loopy pro through my iPad's loudspeaker even if I turn the volume off? I don't understand how it is possible at all.
Ok, you might think this guy is a weirdo that he wants to play with loopy without sound
The simple explanation is that I woke up too early this morning and since I didn't have my headphones with me in the bed (but I had my wife in sleep mode ) I turned down the volume to zero and started exploring LoopyPro's menu and functions.

Which volume did you turn off? If it's the iPad volume, I believe it only affects normal audio (music and voice), not "sounds", which Loopy Pro may be sending.

Yes, it's the iPad volume. But Loopy Pro's volume is changing as it should as I push the volume up or down buttons, but it still can be heard well at the zero setting, despite it should be silent, in other words the volume does not go under a certain level. I have never seen (heard) such thing in my other music apps.

Don't misunderstand me, it has zero effect on the productivity or the user experience, just simply don't understand how it is possible.

@GLacey said:

@uncledave said:

@GLacey said:
Is it normal that I can still hear (not hallucinating ) Loopy pro through my iPad's loudspeaker even if I turn the volume off? I don't understand how it is possible at all.
Ok, you might think this guy is a weirdo that he wants to play with loopy without sound
The simple explanation is that I woke up too early this morning and since I didn't have my headphones with me in the bed (but I had my wife in sleep mode ) I turned down the volume to zero and started exploring LoopyPro's menu and functions.

Which volume did you turn off? If it's the iPad volume, I believe it only affects normal audio (music and voice), not "sounds", which Loopy Pro may be sending.

Yes, it's the iPad volume. But Loopy Pro's volume is changing as it should as I push the volume up or down buttons, but it still can be heard well at the zero setting, despite it should be silent, in other words the volume does not go under a certain level. I have never seen (heard) such thing in my other music apps.

Don't misunderstand me, it has zero effect on the productivity or the user experience, just simply don't understand how it is possible.

Try turning off echo cancellation in Loopy. Having this on might result in these strange volume behaviors. I understand it’s an IOS/iPad thing..

NoiseFloored

Quick question: can timestretching be disabled when changing the playback speed of a loop?

echoopera

I know that this might seem slightly counter productive, but I love using LoopyPro so much, that I am starting to use Ableton as a sound module for it. My iPad is slowly becoming a hub for all my recordings courtesy of LoopyPro.

So freaking cool and fun

espiegel123

@NoiseFloored said:
Quick question: can timestretching be disabled when changing the playback speed of a loop?

It is coming very soon as a clip and one-shot property

NoiseFloored

@espiegel123 said:

@NoiseFloored said:
Quick question: can timestretching be disabled when changing the playback speed of a loop?

It is coming very soon as a clip and one-shot property

Thank you!

Michael

@lukesleepwalker said:

@hat_cake said:

@wim said:

@wim said:

@hat_cake said:
Is it currently possible to configure a button to play a random loop, and on every button press, it'd randomise again?

Sorry, no.

I suppose you could set up midi note bindings to launch clips, then use something like the Rounder Robin Mozaic script to send random notes to trigger them.

ooh, thanks! thats a clever workaround idea
either that, or something along those lines, should be quite powerful..

This feature request has been made several times so here’s hoping the master can fit it in.

Yep, that’s coming soon, both as a clip target for actions and also as a feature of play groups

lukesleepwalker

@Michael said:

@lukesleepwalker said:

@hat_cake said:

@wim said:

@wim said:

@hat_cake said:
Is it currently possible to configure a button to play a random loop, and on every button press, it'd randomise again?

Sorry, no.

I suppose you could set up midi note bindings to launch clips, then use something like the Rounder Robin Mozaic script to send random notes to trigger them.

ooh, thanks! thats a clever workaround idea
either that, or something along those lines, should be quite powerful..

This feature request has been made several times so here’s hoping the master can fit it in.

Yep, that’s coming soon, both as a clip target for actions and also as a feature of play groups

HUZZAH! And the clouds did part and heavenly beams of light doth shine upon us.

Michael

Yea and verily, for I am a beneficent developer

wim

Verily! And we the recipients of thy bounty do revere thee.

gregsmith

@Michael I'm experimenting with using donut follow actions to trigger LK clips on and off. It's working really well except for one thing. When I have a group of donuts set so only 1 will play at a time, and go from one to the other, sometimes the stop follow action from first one will trigger before the play follow action from the next one, and sometimes the other way round. Is there any logic to this? It'd be good if the stop action of donut one always fires before the play action of donut two for my purposes. Not sure about other scenarios.

wim

@gregsmith said:
@Michael I'm experimenting with using donut follow actions to trigger LK clips on and off. It's working really well except for one thing. When I have a group of donuts set so only 1 will play at a time, and go from one to the other, sometimes the stop follow action from first one will trigger before the play follow action from the next one, and sometimes the other way round. Is there any logic to this? It'd be good if the stop action of donut one always fires before the play action of donut two for my purposes. Not sure about other scenarios.

Could it possibly have something to do with FX tails? I wonder when the stop action fires if the loop is set to play the tail on stop.

espiegel123

@wim said:

@gregsmith said:
@Michael I'm experimenting with using donut follow actions to trigger LK clips on and off. It's working really well except for one thing. When I have a group of donuts set so only 1 will play at a time, and go from one to the other, sometimes the stop follow action from first one will trigger before the play follow action from the next one, and sometimes the other way round. Is there any logic to this? It'd be good if the stop action of donut one always fires before the play action of donut two for my purposes. Not sure about other scenarios.

Could it possibly have something to do with FX tails? I wonder when the stop action fires if the loop is set to play the tail on stop.

I think I reported a bug a while ago that was the result of something like this. It prevents one from implementing the equivalent of record and select next.

gregsmith

@espiegel123 said:

@wim said:

@gregsmith said:
@Michael I'm experimenting with using donut follow actions to trigger LK clips on and off. It's working really well except for one thing. When I have a group of donuts set so only 1 will play at a time, and go from one to the other, sometimes the stop follow action from first one will trigger before the play follow action from the next one, and sometimes the other way round. Is there any logic to this? It'd be good if the stop action of donut one always fires before the play action of donut two for my purposes. Not sure about other scenarios.

Could it possibly have something to do with FX tails? I wonder when the stop action fires if the loop is set to play the tail on stop.

I think I reported a bug a while ago that was the result of something like this. It prevents one from implementing the equivalent of record and select next.

On closer inspection, it seems to have something to do with the order of the donut group.

In this screenshot, the empty donuts in the grid trigger the corresponding grid positions in the LK instance. Because of the way LK works, the stop action on all the blue donuts triggers the stop at the bottom of the blue column in LK. The donut groups are set so that only one donut will play at a time.

If I tap blue 1, then blue 2, then blue 3 working downwards, it works as intended with the stop action stopping the LK column, then the start action of the next donut starting the next LK clip.

However, if I go upwards, from blue 3 to blue 2 for instance, blue 3 stops in LK, but blue 2 doesn’t start. I think this is because the stop action of blue 3 donut is firing after the stop action of the blue 2 donut.

I hope this makes sense to someone! 😂
Hopefully @Michael will understand my rambling and can confirm my suspicions.

If anyone’s wondering why I’m bothering with all this, I reckon if I can get this working, we have midi donuts and automation donuts that can be arranged on the loopy timeline along with normal audio donuts.

GLacey

Question. I imported a sample into a 2 bars loop. The sample is somewhat shorter than 2 bars. The problem is that the sample is getting retriggered immediately at its end not just the beginning of the next loop.
Can you please advise how to setup the loop to trigger the sample only at the beginning of each loop?

Jumpercollins

@gregsmith said:

@espiegel123 said:

@wim said:

@gregsmith said:
@Michael I'm experimenting with using donut follow actions to trigger LK clips on and off. It's working really well except for one thing. When I have a group of donuts set so only 1 will play at a time, and go from one to the other, sometimes the stop follow action from first one will trigger before the play follow action from the next one, and sometimes the other way round. Is there any logic to this? It'd be good if the stop action of donut one always fires before the play action of donut two for my purposes. Not sure about other scenarios.

Could it possibly have something to do with FX tails? I wonder when the stop action fires if the loop is set to play the tail on stop.

I think I reported a bug a while ago that was the result of something like this. It prevents one from implementing the equivalent of record and select next.

On closer inspection, it seems to have something to do with the order of the donut group.

In this screenshot, the empty donuts in the grid trigger the corresponding grid positions in the LK instance. Because of the way LK works, the stop action on all the blue donuts triggers the stop at the bottom of the blue column in LK. The donut groups are set so that only one donut will play at a time.

If I tap blue 1, then blue 2, then blue 3 working downwards, it works as intended with the stop action stopping the LK column, then the start action of the next donut starting the next LK clip.

However, if I go upwards, from blue 3 to blue 2 for instance, blue 3 stops in LK, but blue 2 doesn’t start. I think this is because the stop action of blue 3 donut is firing after the stop action of the blue 2 donut.

I hope this makes sense to someone! 😂
Hopefully @Michael will understand my rambling and can confirm my suspicions.

If anyone’s wondering why I’m bothering with all this, I reckon if I can get this working, we have midi donuts and automation donuts that can be arranged on the loopy timeline along with normal audio donuts.

@gregsmith You may find StreamByter Nimble Midi Looper and TF Visual Swift Music new TX/RX Midi and Audio Modules if you can grab the beta from @Jorge come in handy for experimenting with midi connections and combining midi and audio with Loopy Pro at least until we get the midi update.

Doc_T

Two questions. I MIDI map a Korg NanoStudio controller to LP. The faders control the volume of the colors. The Hardware fader sends value 127 but the fader in LP does not go beyond 0dB. Is this correct? How can I set the controller to cover the whole range of the LP slider?

I know that current launchpads (mk3) get automapped with corresponding colors etc. I have a Launchpad mk2 and would like to map this like the newer models. Is this possible from the UI of LP? Or does this require some deep dive into the app and some obscure MIDI sysex commands to work properly? How is the binding of the automapped Launchpads done?

I hope this was not covered before.

gregsmith

@Jumpercollins said:

@gregsmith said:

@espiegel123 said:

@wim said:

@gregsmith said:
@Michael I'm experimenting with using donut follow actions to trigger LK clips on and off. It's working really well except for one thing. When I have a group of donuts set so only 1 will play at a time, and go from one to the other, sometimes the stop follow action from first one will trigger before the play follow action from the next one, and sometimes the other way round. Is there any logic to this? It'd be good if the stop action of donut one always fires before the play action of donut two for my purposes. Not sure about other scenarios.

Could it possibly have something to do with FX tails? I wonder when the stop action fires if the loop is set to play the tail on stop.

I think I reported a bug a while ago that was the result of something like this. It prevents one from implementing the equivalent of record and select next.

On closer inspection, it seems to have something to do with the order of the donut group.

In this screenshot, the empty donuts in the grid trigger the corresponding grid positions in the LK instance. Because of the way LK works, the stop action on all the blue donuts triggers the stop at the bottom of the blue column in LK. The donut groups are set so that only one donut will play at a time.

If I tap blue 1, then blue 2, then blue 3 working downwards, it works as intended with the stop action stopping the LK column, then the start action of the next donut starting the next LK clip.

However, if I go upwards, from blue 3 to blue 2 for instance, blue 3 stops in LK, but blue 2 doesn’t start. I think this is because the stop action of blue 3 donut is firing after the stop action of the blue 2 donut.

I hope this makes sense to someone! 😂
Hopefully @Michael will understand my rambling and can confirm my suspicions.

If anyone’s wondering why I’m bothering with all this, I reckon if I can get this working, we have midi donuts and automation donuts that can be arranged on the loopy timeline along with normal audio donuts.

@gregsmith You may find StreamByter Nimble Midi Looper and TF Visual Swift Music new TX/RX Midi and Audio Modules if you can grab the beta from @Jorge come in handy for experimenting with midi connections and combining midi and audio with Loopy Pro at least until we get the midi update.

Thanks @Jumpercollins I’ll have a look.

I’ve actually got a really good working solution triggering atom2 clips with empty donuts. It’s working great. Will make a video soon.

Thing is, this is the only thing holding back using LK which would give us automation as well as midi. It’s completely working apart from this one detail which I think will be easy for @Michael to sort if my theory is correct.

Jumpercollins

@gregsmith said:

@Jumpercollins said:

@gregsmith said:

@espiegel123 said:

@wim said:

@gregsmith said:
@Michael I'm experimenting with using donut follow actions to trigger LK clips on and off. It's working really well except for one thing. When I have a group of donuts set so only 1 will play at a time, and go from one to the other, sometimes the stop follow action from first one will trigger before the play follow action from the next one, and sometimes the other way round. Is there any logic to this? It'd be good if the stop action of donut one always fires before the play action of donut two for my purposes. Not sure about other scenarios.

Could it possibly have something to do with FX tails? I wonder when the stop action fires if the loop is set to play the tail on stop.

I think I reported a bug a while ago that was the result of something like this. It prevents one from implementing the equivalent of record and select next.

On closer inspection, it seems to have something to do with the order of the donut group.

In this screenshot, the empty donuts in the grid trigger the corresponding grid positions in the LK instance. Because of the way LK works, the stop action on all the blue donuts triggers the stop at the bottom of the blue column in LK. The donut groups are set so that only one donut will play at a time.

If I tap blue 1, then blue 2, then blue 3 working downwards, it works as intended with the stop action stopping the LK column, then the start action of the next donut starting the next LK clip.

However, if I go upwards, from blue 3 to blue 2 for instance, blue 3 stops in LK, but blue 2 doesn’t start. I think this is because the stop action of blue 3 donut is firing after the stop action of the blue 2 donut.

I hope this makes sense to someone! 😂
Hopefully @Michael will understand my rambling and can confirm my suspicions.

If anyone’s wondering why I’m bothering with all this, I reckon if I can get this working, we have midi donuts and automation donuts that can be arranged on the loopy timeline along with normal audio donuts.

@gregsmith You may find StreamByter Nimble Midi Looper and TF Visual Swift Music new TX/RX Midi and Audio Modules if you can grab the beta from @Jorge come in handy for experimenting with midi connections and combining midi and audio with Loopy Pro at least until we get the midi update.

Thanks @Jumpercollins I’ll have a look.

I’ve actually got a really good working solution triggering atom2 clips with empty donuts. It’s working great. Will make a video soon.

Thing is, this is the only thing holding back using LK which would give us automation as well as midi. It’s completely working apart from this one detail which I think will be easy for @Michael to sort if my theory is correct.

@gregsmith
Looking forward to seeing how your achieving everything on your video once you get time to post it.

sisterkate

@robosardine said:

Talking about making another Loopy Pro @Michael. I was wondering if you would ever consider making a Loopy Pro ‘Lite’ at some time in the future - which would only have the basic functionality of importing and looping audio with a few more useful select features thrown in? I’m about to purchase Loopy Pro when my trial runs out shortly (and a work of art it truly is) - but I won’t be using many the features - like live looping etc
I’m thinking along the lines that you would sell a real barrowload of them at a smaller price, and it could act as a gateway to the bigger one.
iOS needed a good AU clip launcher up until now, a Lite version would fill that space and be a lot less complex to work with, it would also be a real challenge to any other budget clip launchers out there and so would likely occupy a considerable chunk of that market. There’s maybe a lot of folk that are reluctant to shell out for the big Pro one when they only want to have a bit of fun launching off some clips.
It’s not going to affect me like I say as I’m getting it anyway (though funnily enough I would probably buy a Lite version as well).
Just a curious thought. I z

• 1

Doc_T

@Doc_T said:
I know that current launchpads (mk3) get automapped with corresponding colors etc. I have a Launchpad mk2 and would like to map this like the newer models. Is this possible from the UI of LP? Or does this need some deep dive into the app and some obscure MIDI sysex commands to work properly? How is the binding of the automapped launchkeys done?

Interesting is, that I can load LK as a MIDI source in LP and the Launchpad will connect to LK instead of LP. I guess I could make a grid in LK that would mirror the LP grid and MIDIlearn the Launchpad to LP. That way I could have a colored layout on the Launchpad mkII - similar to a 'native' automapped device. Interestingly the Launchpad could than also act as a MIDI Looper with Ableton like MIDI loops in LK to drive AUs in LP. Sounds somehow smart - but maybe take to much time to develop a workflow.