Loopy Pro not recording first few ms of a loop? (SOLVED!)

Nathi94

Hi there I have the problem that then I try to record a drumloop Loopy doesn’t seem to get the first few ms of that loop. Noticeable that the transient on the first kick gets lost and it sounds more like a kick with a slow attack. And on the end of the loop seems to be a bit of extra sound recorded (screenshot). I’m not sure if this is a bug or a mistake on my end.
iPhone 13 Pro ios 17.2.1 and iPad 8 gen ipados 17.2.1

espiegel123

@Nathi94 said:
Hi there I have the problem that then I try to record a drumloop Loopy doesn’t seem to get the first few ms of that loop. Noticeable that the transient on the first kick gets lost and it sounds more like a kick with a slow attack. And on the end of the loop seems to be a bit of extra sound recorded (screenshot). I’m not sure if this is a bug or a mistake on my end.
iPhone 13 Pro ios 17.2.1 and iPad 8 gen ipados 17.2.1

If you trigger the loop, does the transient play the first time through ?

There is a setting in Clip Settings called Loop Boundary cross fade. By default it is set to 50 ms. It crossfades the end and beginning of a loop to ensure clickless looping. This will blur a sharp transient at the beginning of a loop when it loops. You can set it as low as 0 ms.

Does that solve the problem?

If not, can you describe the setup and settings being used to capture the loop?

As for the part at the end, depending on your settings, Loopy might capture a little bit of audio beyond a measure’s end..but doesn’t play it unless you move the end marker.

Nathi94

@espiegel123 said:

If you trigger the loop, does the transient play the first time through ?

There is a setting in Clip Settings called Loop Boundary cross fade. By default it is set to 50 ms. It crossfades the end and beginning of a loop to ensure clickless looping. This will blur a sharp transient at the beginning of a loop when it loops. You can set it as low as 0 ms.

Does that solve the problem?

If not, can you describe the setup and settings being used to capture the loop?

As for the part at the end, depending on your settings, Loopy might capture a little bit of audio beyond a measure’s end..but doesn’t play it unless you move the end marker.

If the loop is triggered the transient doesn’t play the first time, only after the first play the transient plays through.
I’ve tried with the Boundary cross fade unfortunately it doesn’t solved the problem.

The setup in this is very simple just Drambo with a Kick playing (tried also Hammerhead and Drumcomputer with same results). No plugins in the fx slots. Buffer duration is 256 also changed to lower but same outcome.
I’ve attached a few screenshots from the clip settings since I‘m not sure which parts would be the most important to show.

Ah good to know with the recording at the end as I thought maybe the wavefile would be shifted.
Not sure if this is related to it by also when I put several loops of the same loop in a row in the sequencer the loops sometimes stop to play and start again.

espiegel123

@Nathi94 : is this when Drambo is loaded as as an AU? Do you have a sequence running in Drambo that is triggering sounds loaded in Drambo?

Try the following at let me know if it makes a difference.

Start with an empty project.

Set the loop boundary crossfade to 0.

Turn off the microfade on the fade in setting.

Turn off auto loop detection .

rs2000

So you're recording from an AUv3 hosted inside Loopy Pro and the AUv3 starts its playback when you start recording in LP (via AUv3 host sync)?
If that's the case then there might be an offset indeed.

espiegel123

@rs2000 said:
So you're recording from an AUv3 hosted inside Loopy Pro and the AUv3 starts its playback when you start recording in LP (via AUv3 host sync)?
If that's the case then there might be an offset indeed.

There isn’t an offset setting for host sync…and it shouldn’t be needed.

I’ll post a video in a sec of loopy capturing quantized Sitala kicks triggered by Drambo running as a midi AU.

rs2000

@espiegel123 said:

@rs2000 said:
So you're recording from an AUv3 hosted inside Loopy Pro and the AUv3 starts its playback when you start recording in LP (via AUv3 host sync)?
If that's the case then there might be an offset indeed.

There isn’t an offset setting for host sync…and it shouldn’t be needed.

I’ll post a video in a sec of loopy capturing quantized Sitala kicks triggered by Drambo running as a midi AU.

No, what I mean is the recording scenario with host sync because @Nathi94 might be recording from the microphone instead of from the AUv3 directly.
That would explain the recording latency.
Recording directly from the host-synced AUv3 definitely works as it should, I've just tried.

espiegel123

Here are sharp kicks captured from hammerhead. It took me a sec to mute hammerhead after the capture. So there is a little bogosity before I mute it.

https://youtube.com/shorts/ryrddDTq4JE?si=HNWLqcjvQQOeCd3X

Nathi94

@espiegel123 @rs2000 yeah I forgot to mention Drambo is loaded as an Auv3 Instrument. And the sequencer in Drambo is triggering the sounds inside Drambo

espiegel123

@Nathi94 said:
@espiegel123 @rs2000 yeah I forgot to mention Drambo is loaded as an Auv3 Instrument. And the sequencer in Drambo is triggering the sounds inside Drambo

Did you try my suggestions yet?

How are you triggering recording start?

Nathi94

@espiegel123 said:
@Nathi94 : is this when Drambo is loaded as as an AU? Do you have a sequence running in Drambo that is triggering sounds loaded in Drambo?

Try the following at let me know if it makes a difference.

Start with an empty project.

Set the loop boundary crossfade to 0.

Turn off the microfade on the fade in setting.

Turn off auto loop detection .

I just tried it and it seems to solved the problem. It’s working just like in your Video. Big Thank you!

espiegel123

Great. If you turn the micro fades back on, is it ok?

I wonder if auto loop detection was the culprit.

Nathi94

@espiegel123 said:

@Nathi94 said:
@espiegel123 @rs2000 yeah I forgot to mention Drambo is loaded as an Auv3 Instrument. And the sequencer in Drambo is triggering the sounds inside Drambo

Did you try my suggestions yet?

How are you triggering recording start?

Yep. I triggered it just like in your video and it worked. I triggered it also without the transport running and the beginning sounded a bit different but I lowered the buffer duration and everything sounded exactly as it should be.

Nathi94

@espiegel123 said:
Great. If you turn the micro fades back on, is it ok?

I wonder if auto loop detection was the culprit.

It seems it was the micro fades. I turned it back on and the problem was there again. Turning on or off the loop detection seems to be no problem.

espiegel123

@Nathi94 said:

@espiegel123 said:

@Nathi94 said:
@espiegel123 @rs2000 yeah I forgot to mention Drambo is loaded as an Auv3 Instrument. And the sequencer in Drambo is triggering the sounds inside Drambo

Did you try my suggestions yet?

How are you triggering recording start?

Yep. I triggered it just like in your video and it worked. I triggered it also without the transport running and the beginning sounded a bit different but I lowered the buffer duration and everything sounded exactly as it should be.

I can imagine that if the transport isn't running already that there might be a millisecond or few as the clients get locked in.

Nathi94

@espiegel123 said:

@Nathi94 said:

@espiegel123 said:

@Nathi94 said:
@espiegel123 @rs2000 yeah I forgot to mention Drambo is loaded as an Auv3 Instrument. And the sequencer in Drambo is triggering the sounds inside Drambo

Did you try my suggestions yet?

How are you triggering recording start?

Yep. I triggered it just like in your video and it worked. I triggered it also without the transport running and the beginning sounded a bit different but I lowered the buffer duration and everything sounded exactly as it should be.

I can imagine that if the transport isn't running already that there might be a millisecond or few as the clients get locked in.

Yeah probably.