Loopy Pro: FIRST LOOK

gregsmith

@lukesleepwalker said:

@gregsmith said:

@lukesleepwalker said:
OK, there will be following videos that show Loopy’s depth but I attempt in this video to address the use case that came up a few pages back around the beginner looper. I’ve been looping for a while so I have a pretty good handle on it but the feature to capture the first loop will certainly help a beginner as shown in this video (which is a waltz to show how the algo works, as well).

This is just my acoustic plugged directly into an audio interface and routed into Loopy Pro. Note that I could have put the Drambo pitch shifter on the input to hear the bass effect on the second loop but i was lazy and just assigned the effect to the blue color group. At least it’ll give some ideas for how flexible the fx routing is and how you could do some gee whizzz live looping. I do have brusfri loaded on the input.

Finally, the second and third loops use the retrospective looper. I played until i heard what i liked and then swiped down on the loop. This is a neat trick i learned from the beta test: you can set a gesture for the retro looper so that you can mix/match go forward looping (as usual, with a tap) with retro looping (any gesture you select). You can set retro looping as a default in the settings which gives you one added benefit: you can see the loop wave form in the doughnut which gives you a visual representation of the retro looping process. Anyhoo, lots of options for beginner and expert loopers.

Nice demo!

Any reason why you overdubbed on the first loop rather than doing a new donut each time? (I think that’s what you did?)

I’m really new to how this looping thing works so it’s great to see other people’s workflow.

Actually, i didn’t overdub. I created three different loops using the same input. The last two used retro loops.

So on that first donut, are there 3 loops? It looked like you recorded once and modified the loop, then recorded twice more on top of that loop, before moving onto the bass bit on another donut and the twiddly bit on another?

lukesleepwalker

@gregsmith said:

@lukesleepwalker said:

@gregsmith said:

@lukesleepwalker said:
OK, there will be following videos that show Loopy’s depth but I attempt in this video to address the use case that came up a few pages back around the beginner looper. I’ve been looping for a while so I have a pretty good handle on it but the feature to capture the first loop will certainly help a beginner as shown in this video (which is a waltz to show how the algo works, as well).

This is just my acoustic plugged directly into an audio interface and routed into Loopy Pro. Note that I could have put the Drambo pitch shifter on the input to hear the bass effect on the second loop but i was lazy and just assigned the effect to the blue color group. At least it’ll give some ideas for how flexible the fx routing is and how you could do some gee whizzz live looping. I do have brusfri loaded on the input.

Finally, the second and third loops use the retrospective looper. I played until i heard what i liked and then swiped down on the loop. This is a neat trick i learned from the beta test: you can set a gesture for the retro looper so that you can mix/match go forward looping (as usual, with a tap) with retro looping (any gesture you select). You can set retro looping as a default in the settings which gives you one added benefit: you can see the loop wave form in the doughnut which gives you a visual representation of the retro looping process. Anyhoo, lots of options for beginner and expert loopers.

Nice demo!

Any reason why you overdubbed on the first loop rather than doing a new donut each time? (I think that’s what you did?)

I’m really new to how this looping thing works so it’s great to see other people’s workflow.

Actually, i didn’t overdub. I created three different loops using the same input. The last two used retro loops.

So on that first donut, are there 3 loops? It looked like you recorded once and modified the loop, then recorded twice more on top of that loop, before moving onto the bass bit on another donut and the twiddly bit on another?

No, just one. The panel I opened let’s you pick different interpretations of the loop from the algorithm (or manually adjust as i did in the video). I’ll do another video that demos the different versions in that dialogue (it’s very slick).

espiegel123

@gregsmith said:

@lukesleepwalker said:

@gregsmith said:

@lukesleepwalker said:
OK, there will be following videos that show Loopy’s depth but I attempt in this video to address the use case that came up a few pages back around the beginner looper. I’ve been looping for a while so I have a pretty good handle on it but the feature to capture the first loop will certainly help a beginner as shown in this video (which is a waltz to show how the algo works, as well).

This is just my acoustic plugged directly into an audio interface and routed into Loopy Pro. Note that I could have put the Drambo pitch shifter on the input to hear the bass effect on the second loop but i was lazy and just assigned the effect to the blue color group. At least it’ll give some ideas for how flexible the fx routing is and how you could do some gee whizzz live looping. I do have brusfri loaded on the input.

Finally, the second and third loops use the retrospective looper. I played until i heard what i liked and then swiped down on the loop. This is a neat trick i learned from the beta test: you can set a gesture for the retro looper so that you can mix/match go forward looping (as usual, with a tap) with retro looping (any gesture you select). You can set retro looping as a default in the settings which gives you one added benefit: you can see the loop wave form in the doughnut which gives you a visual representation of the retro looping process. Anyhoo, lots of options for beginner and expert loopers.

Nice demo!

Any reason why you overdubbed on the first loop rather than doing a new donut each time? (I think that’s what you did?)

I’m really new to how this looping thing works so it’s great to see other people’s workflow.

Actually, i didn’t overdub. I created three different loops using the same input. The last two used retro loops.

So on that first donut, are there 3 loops? It looked like you recorded once and modified the loop, then recorded twice more on top of that loop, before moving onto the bass bit on another donut and the twiddly bit on another?

Maybe what is confusing to some watching is that after that first loop is recorded, you are hearing audio and thinking that it is being recorded to the loop that is playing. That's not what is happening.

What is going on is this:

• the first loop gets recorded and auto-trimmed by Loopy.
• you then see Loopy's dialog that lets you manually adjust the auto-looped recording
• you then hear guitar playing. this playing is not being recorded into a donut. this live playing is also being captured in Loopy's buffers (the retrospective looper). it isn't yet a track
• when he is happy with his last take, lukesleepwalker swipes to capture that take from Loopy's retrospective looper to the donut he swiped on. when he swipes, you see the new blue donut created. it is pitched an octave down at that point because Drambo is processing that track with a pitch shifter.
• then he plays some more and swipes again to capture his last take to a new orange donut

tahiche

@ervin said:

And as a bonus, here she comes doing Hide and Seek with the gloves

Science fiction. 😳 The general rule seems to be that she does everything way before you do and does it way better than you ever will 🤷

Fuck me!. Are those midi gloves?. She makes it look easy, but imagine having an itch and you can’t scratch or you’ll trigger CC 84 cutoff resonance…

gregsmith

@espiegel123 said:

@gregsmith said:

@lukesleepwalker said:

@gregsmith said:

@lukesleepwalker said:
OK, there will be following videos that show Loopy’s depth but I attempt in this video to address the use case that came up a few pages back around the beginner looper. I’ve been looping for a while so I have a pretty good handle on it but the feature to capture the first loop will certainly help a beginner as shown in this video (which is a waltz to show how the algo works, as well).

This is just my acoustic plugged directly into an audio interface and routed into Loopy Pro. Note that I could have put the Drambo pitch shifter on the input to hear the bass effect on the second loop but i was lazy and just assigned the effect to the blue color group. At least it’ll give some ideas for how flexible the fx routing is and how you could do some gee whizzz live looping. I do have brusfri loaded on the input.

Finally, the second and third loops use the retrospective looper. I played until i heard what i liked and then swiped down on the loop. This is a neat trick i learned from the beta test: you can set a gesture for the retro looper so that you can mix/match go forward looping (as usual, with a tap) with retro looping (any gesture you select). You can set retro looping as a default in the settings which gives you one added benefit: you can see the loop wave form in the doughnut which gives you a visual representation of the retro looping process. Anyhoo, lots of options for beginner and expert loopers.

Nice demo!

Any reason why you overdubbed on the first loop rather than doing a new donut each time? (I think that’s what you did?)

I’m really new to how this looping thing works so it’s great to see other people’s workflow.

Actually, i didn’t overdub. I created three different loops using the same input. The last two used retro loops.

So on that first donut, are there 3 loops? It looked like you recorded once and modified the loop, then recorded twice more on top of that loop, before moving onto the bass bit on another donut and the twiddly bit on another?

Maybe what is confusing to some watching is that after that first loop is recorded, you are hearing audio and thinking that it is being recorded to the loop that is playing. That's not what is happening.

What is going on is this:

• the first loop gets recorded and auto-trimmed by Loopy.
• you then see Loopy's dialog that lets you manually adjust the auto-looped recording
• you then hear guitar playing. this playing is not being recorded into a donut. this live playing is also being captured in Loopy's buffers (the retrospective looper). it isn't yet a track
• when he is happy with his last take, lukesleepwalker swipes to capture that take from Loopy's retrospective looper to the donut he swiped on. when he swipes, you see the new blue donut created. it is pitched an octave down at that point because Drambo is processing that track with a pitch shifter.
• then he plays some more and swipes again to capture his last take to a new orange donut

Ah yes, that was exactly the mistake I was making.

Thanks for explaining.

lukesleepwalker

@espiegel123 said:

@gregsmith said:

@lukesleepwalker said:

@gregsmith said:

@lukesleepwalker said:
OK, there will be following videos that show Loopy’s depth but I attempt in this video to address the use case that came up a few pages back around the beginner looper. I’ve been looping for a while so I have a pretty good handle on it but the feature to capture the first loop will certainly help a beginner as shown in this video (which is a waltz to show how the algo works, as well).

This is just my acoustic plugged directly into an audio interface and routed into Loopy Pro. Note that I could have put the Drambo pitch shifter on the input to hear the bass effect on the second loop but i was lazy and just assigned the effect to the blue color group. At least it’ll give some ideas for how flexible the fx routing is and how you could do some gee whizzz live looping. I do have brusfri loaded on the input.

Finally, the second and third loops use the retrospective looper. I played until i heard what i liked and then swiped down on the loop. This is a neat trick i learned from the beta test: you can set a gesture for the retro looper so that you can mix/match go forward looping (as usual, with a tap) with retro looping (any gesture you select). You can set retro looping as a default in the settings which gives you one added benefit: you can see the loop wave form in the doughnut which gives you a visual representation of the retro looping process. Anyhoo, lots of options for beginner and expert loopers.

Nice demo!

Any reason why you overdubbed on the first loop rather than doing a new donut each time? (I think that’s what you did?)

I’m really new to how this looping thing works so it’s great to see other people’s workflow.

Actually, i didn’t overdub. I created three different loops using the same input. The last two used retro loops.

So on that first donut, are there 3 loops? It looked like you recorded once and modified the loop, then recorded twice more on top of that loop, before moving onto the bass bit on another donut and the twiddly bit on another?

Maybe what is confusing to some watching is that after that first loop is recorded, you are hearing audio and thinking that it is being recorded to the loop that is playing. That's not what is happening.

What is going on is this:

• the first loop gets recorded and auto-trimmed by Loopy.
• you then see Loopy's dialog that lets you manually adjust the auto-looped recording
• you then hear guitar playing. this playing is not being recorded into a donut. this live playing is also being captured in Loopy's buffers (the retrospective looper). it isn't yet a track
• when he is happy with his last take, lukesleepwalker swipes to capture that take from Loopy's retrospective looper to the donut he swiped on. when he swipes, you see the new blue donut created. it is pitched an octave down at that point because Drambo is processing that track with a pitch shifter.
• then he plays some more and swipes again to capture his last take to a new orange donut

LOL, I need you to explain more things in my life! That was spot on. Thank you!

ervin

@tahiche said:

Fuck me!. Are those midi gloves?. She makes it look easy, but imagine having an itch and you can’t scratch or you’ll trigger CC 84 cutoff resonance…

🎖️ I just woke up half the block with the horse-sounding laugh this one generated. Well played, amigo

[Deleted User]

The user and all related content has been deleted.

espiegel123

@Max_Free said:
Do I actually need to look at the screen to use Loopy Pro? I hope not, so that it is fully able to be remotely controlled, with Midi controllers, pedals or other apps. Looping is not the visual focus for me, it should just do its thing (under control from some spare limbs or from other tools, like sequencers) in the background. I would like to perceive it as a module (or set of modules), like an audio sampling/recording/triggering/looping engine, well-integrated in a complex acoustic/hardware/software music-making scenario, rather than as do-it-all DAW replacement, grabbing a lot of focus.

Muscle memory rules for me. Ideally, at the highest level, music is a thing you can do in your sleep, while dreaming, with eyes closed.

I actually once had a night dream about this, about using Ableton Push while dreaming.

If this ever happens for me in real life... will it be Push controlling Loopy Pro?

you don't need to look at the screen. fwiw, the existing Loopy HD has very deep midi control that allos everything to be controlled by midi.

[Deleted User]

The user and all related content has been deleted.

Hmtx

@Max_Free said:
So I hope all these fancy swiping-gestures and so on will have their complement in Midi/AU-Automation. Both on current track/fx-slot and individuals.

Yes, any action you create as a gesture could also be set up as a response to midi input from an external controller.

“MIDI automation” ? If by that you mean recording and looping midi data… it is on the roadmap. It won’t be in v 1.0

Toastedghost

Did not want to burden Michael with any more questions, but can anyone answer, is it possible to Loopy into a silent monitor mode? Meaning to say record a signal as a sample without it being monitored and then instantly play back. I do this with Enso but it is not relieable. Thanks

Michael_R_Grant

@Toastedghost said:
Did not want to burden Michael with any more questions, but can anyone answer, is it possible to Loopy into a silent monitor mode? Meaning to say record a signal as a sample without it being monitored and then instantly play back. I do this with Enso but it is not relieable. Thanks

I'm sure you can turn monitoring off so that the signal doesn't come through the iPad speakers or headphones while recording. Is that what you mean?

Toastedghost

@Michael_R_Grant said:

@Toastedghost said:
Did not want to burden Michael with any more questions, but can anyone answer, is it possible to Loopy into a silent monitor mode? Meaning to say record a signal as a sample without it being monitored and then instantly play back. I do this with Enso but it is not relieable. Thanks

I'm sure you can turn monitoring off so that the signal doesn't come through the iPad speakers or headphones while recording. Is that what you mean?

No sorry, in Enso I can set it to record but the signal is not outputted but the wav is recorded then I can bring the wav in by pulling up the volume

tahiche

@lukesleepwalker said:

This is just my acoustic plugged directly into an audio interface and routed into Loopy Pro. Note that I could have put the Drambo pitch shifter on the input to hear the bass effect on the second loop but i was lazy and just assigned the effect to the blue color group. At least it’ll give some ideas for how flexible the fx routing is and how you could do some gee whizzz live looping. I do have brusfri loaded on the input.

So you’re using the same input for both groups, and you record into one or the other by pressing a donut in that group… right?. Now, to monitor the “bass pitcher” you’d put the effect on the input?. Isn’t it possible to monitor from the blue group?. That way you wouldn’t have to switch fx on/off on the input depending on what you want to record…

Foleslaw

Does the new Loopy loaded as an AU in AUM (or other hosts) allow to use that audioclip timeline that is shown in the preview video? Doing something similar to 4pockets Multitrack but maybe allowing more clips and editing options?

lukesleepwalker

@tahiche said:

@lukesleepwalker said:

This is just my acoustic plugged directly into an audio interface and routed into Loopy Pro. Note that I could have put the Drambo pitch shifter on the input to hear the bass effect on the second loop but i was lazy and just assigned the effect to the blue color group. At least it’ll give some ideas for how flexible the fx routing is and how you could do some gee whizzz live looping. I do have brusfri loaded on the input.

So you’re using the same input for both groups, and you record into one or the other by pressing a donut in that group… right?. Now, to monitor the “bass pitcher” you’d put the effect on the input?. Isn’t it possible to monitor from the blue group?. That way you wouldn’t have to switch fx on/off on the input depending on what you want to record…

So I mentioned i was being lazy but there are also so many ways to do things in LP that it didn’t occur to me to put the pitch shifter on the input and turn it on/off, which is super easy in the UI. The FX along the bottom are toggle buttons so I could have toggled on the shifter for that one loop, yes. Just didn’t think about it in the moment.

tahiche

@lukesleepwalker said:

@tahiche said:

@lukesleepwalker said:

This is just my acoustic plugged directly into an audio interface and routed into Loopy Pro. Note that I could have put the Drambo pitch shifter on the input to hear the bass effect on the second loop but i was lazy and just assigned the effect to the blue color group. At least it’ll give some ideas for how flexible the fx routing is and how you could do some gee whizzz live looping. I do have brusfri loaded on the input.

So you’re using the same input for both groups, and you record into one or the other by pressing a donut in that group… right?. Now, to monitor the “bass pitcher” you’d put the effect on the input?. Isn’t it possible to monitor from the blue group?. That way you wouldn’t have to switch fx on/off on the input depending on what you want to record…

So I mentioned i was being lazy but there are also so many ways to do things in LP that it didn’t occur to me to put the pitch shifter on the input and turn it on/off, which is super easy in the UI. The FX along the bottom are toggle buttons so I could have toggled on the shifter for that one loop, yes. Just didn’t think about it in the moment.

Yes, I understand that, but I’m not fond of putting fx on the input… if I’m not mistaken if the fx is on the input it’d get recorded to the donut with effects. Right?. So you’re stuck with that sound.
What I was trying to say is that the best way imo would be to be able to monitor the input with whatever fx are on the group you’re going to record to. Does that make sense?.
Say you have, one input and 2 groups:

• blue group: Drambo pitch shifter to do bass
• Orange group: guitar track with Nembrini amp, delays and whatever…

I would like to monitor what I’m gonna play with the effects of the group I’m gonna record to. If I’m going to do do a bass loop, monitor with exactly what’s on the blue bass group… if I’m gonna do a guitar loop play with the Orange group fx.

Is this possible?. It should be. Just like in any daw, you record while monitoring with whatever is on that track.

espiegel123

@tahiche said:

@lukesleepwalker said:

@tahiche said:

@lukesleepwalker said:

This is just my acoustic plugged directly into an audio interface and routed into Loopy Pro. Note that I could have put the Drambo pitch shifter on the input to hear the bass effect on the second loop but i was lazy and just assigned the effect to the blue color group. At least it’ll give some ideas for how flexible the fx routing is and how you could do some gee whizzz live looping. I do have brusfri loaded on the input.

So you’re using the same input for both groups, and you record into one or the other by pressing a donut in that group… right?. Now, to monitor the “bass pitcher” you’d put the effect on the input?. Isn’t it possible to monitor from the blue group?. That way you wouldn’t have to switch fx on/off on the input depending on what you want to record…

So I mentioned i was being lazy but there are also so many ways to do things in LP that it didn’t occur to me to put the pitch shifter on the input and turn it on/off, which is super easy in the UI. The FX along the bottom are toggle buttons so I could have toggled on the shifter for that one loop, yes. Just didn’t think about it in the moment.

Yes, I understand that, but I’m not fond of putting fx on the input… if I’m not mistaken if the fx is on the input it’d get recorded to the donut with effects. Right?. So you’re stuck with that sound.
What I was trying to say is that the best way imo would be to be able to monitor the input with whatever fx are on the group you’re going to record to. Does that make sense?.
Say you have, one input and 2 groups:

• blue group: Drambo pitch shifter to do bass
• Orange group: guitar track with Nembrini amp, delays and whatever…

I would like to monitor what I’m gonna play with the effects of the group I’m gonna record to. If I’m going to do do a bass loop, monitor with exactly what’s on the blue bass group… if I’m gonna do a guitar loop play with the Orange group fx.

Is this possible?. It should be. Just like in any daw, you record while monitoring with whatever is on that track.

The full mixer and bussing architecture has not yet been implemented. There are things that will be possible that were not yet implemented when that video was made.

wim

Ooooh. That's a little disappointing. I'm with @tahiche, I like to hear the processed track when recording but record the dry only.

Or am I misunderstanding, and this is actually possible?

espiegel123

@wim said:
Ooooh. That's a little disappointing. I'm with @tahiche, I like to hear the processed track when recording but record the dry only.

Or am I misunderstanding, and this is actually possible?

You can record dry and have effects only applied to the output. And, as I posted earlier, the mixer and bus architecture is not yet fully implemented.

wim

@espiegel123 said:

@wim said:
Ooooh. That's a little disappointing. I'm with @tahiche, I like to hear the processed track when recording but record the dry only.

Or am I misunderstanding, and this is actually possible?

You can record dry and have effects only applied to the output. And, as I posted earlier, the mixer and bus architecture is not yet fully implemented.

Yes, but can you monitor with the post FX as you record dry. I'm not clear from your answers on that point.

espiegel123

@wim said:

@espiegel123 said:

@wim said:
Ooooh. That's a little disappointing. I'm with @tahiche, I like to hear the processed track when recording but record the dry only.

Or am I misunderstanding, and this is actually possible?

You can record dry and have effects only applied to the output. And, as I posted earlier, the mixer and bus architecture is not yet fully implemented.

Yes, but can you monitor with the post FX as you record dry. I'm not clear from your answers on that point.

Today, you cannot monitor wet as far as I know BUT as I said, the full mixer and bussing architecture has not yet been implemented. So, even if it isn't implemented today that doesn't mean it won't be. So, I wouldn't be disappointed based on what is implemented today. If this isn't already intended, I am sure Michael will give it some thought.

wim

@espiegel123 said:

@wim said:

@espiegel123 said:

@wim said:
Ooooh. That's a little disappointing. I'm with @tahiche, I like to hear the processed track when recording but record the dry only.

Or am I misunderstanding, and this is actually possible?

You can record dry and have effects only applied to the output. And, as I posted earlier, the mixer and bus architecture is not yet fully implemented.

Yes, but can you monitor with the post FX as you record dry. I'm not clear from your answers on that point.

Today, you cannot monitor wet as far as I know BUT as I said, the full mixer and bussing architecture has not yet been implemented. So, even if it isn't implemented today that doesn't mean it won't be. So, I wouldn't be disappointed based on what is implemented today. If this isn't already intended, I am sure Michael will give it some thought.

Thanks for answering. I'm imagine there are ways to accomplish this using routing outside the app in the meantime. It's a pretty big omission though, so I hope it's up there somewhere near the top of the to-do list.

celtic_elk

@wim said:
Thanks for answering. I'm imagine there are ways to accomplish this using routing outside the app in the meantime. It's a pretty big omission though, so I hope it's up there somewhere near the top of the to-do list.

Currently on the "Post-1.0 Release Target" list at https://loopypro.com/beta/: "Send monitor audio through currently-recording group’s effects"

wim

@celtic_elk said:

@wim said:
Thanks for answering. I'm imagine there are ways to accomplish this using routing outside the app in the meantime. It's a pretty big omission though, so I hope it's up there somewhere near the top of the to-do list.

Currently on the "Post-1.0 Release Target" list at https://loopypro.com/beta/: "Send monitor audio through currently-recording group’s effects"

Thanks for that confirmation and the link to where to find the list. That should eliminate a lot of my questions.

Do you know if the post 1.0 list is in any kind of approximate order (priority or time)?

lukesleepwalker

.

espiegel123

@wim said:

@espiegel123 said:

@wim said:

@espiegel123 said:

@wim said:
Ooooh. That's a little disappointing. I'm with @tahiche, I like to hear the processed track when recording but record the dry only.

Or am I misunderstanding, and this is actually possible?

You can record dry and have effects only applied to the output. And, as I posted earlier, the mixer and bus architecture is not yet fully implemented.

Yes, but can you monitor with the post FX as you record dry. I'm not clear from your answers on that point.

Today, you cannot monitor wet as far as I know BUT as I said, the full mixer and bussing architecture has not yet been implemented. So, even if it isn't implemented today that doesn't mean it won't be. So, I wouldn't be disappointed based on what is implemented today. If this isn't already intended, I am sure Michael will give it some thought.

Thanks for answering. I'm imagine there are ways to accomplish this using routing outside the app in the meantime. It's a pretty big omission though, so I hope it's up there somewhere near the top of the to-do list.

Big omission? As noted in my two previous messages, there are features that are planned but not yet implemented. One can’t implement everything at once.

It is in beta and not yet feature complete.

wim

@espiegel123 said:
Big omission? As noted in my two previous messages, there are features that are planned but not yet implemented. One can’t implement everything at once.

Jesus. You'll quibble about anything.

OK, "important feature to have missing". Better?
I should know better than to engage with you. Pisses me off every time.

espiegel123

@wim said:

@espiegel123 said:
Big omission? As noted in my two previous messages, there are features that are planned but not yet implemented. One can’t implement everything at once.

Jesus. You'll quibble about anything. OK, "important feature to have missing". Better?
I should know better than to engage with you. Pisses me off every time.

I simply think it isn't reasonable to label things as "big omissions" and "disappointments" when for all you know, the features will be there. Saying "important feature to have missing" is no more reasonable. You are implying that it isn't going to be implemented.

It was pointed out to you that new features are being actively added in this area.