Latency compensation for Auto multi sampling

[Mfactory]

Add a field in the setup page of the automatic multi sample tool to select in milliseconds or samples the latency you expect from your audio source (for example, a DAW)
Trigger the midi note but wait for this lag to effectively record the audio onto the BB
This would avoid having blank audio in the beginning of each sample as we can see in most of the multisample packs shared by users, avoiding to keep on the BB the same "latency" while triggering the samples that the one that the audio source has
Currently, only way to get rid of this is to manually trim all the samples

[Steve]

Curious - which interface + software combination are you using? And what are your buffer settings?

[Mfactory]

Hello Steve, I am using a USB m audio quad capture interface with live 11, and I have the buffer at 128 or 256 samples depending on how heavy the processing on the vst instrument is.
I guess, when the BB triggers the midi the latency implies that the audio is a little bit delayed, thus explaining the little "attack" on the samples recorded?

[Steve]

Perhaps, but I have found smaller buffer settings create better Mx recordings. Depending on your VST and CPU, I would suggest going as low as possible during the MX recording process.

[Mfactory]

Sure, having audio interface set at 64 samples reduces the latency so that it becomes almost impossible to notice it but if BB could compensate that by adding a lag between midi out and start of recording it would be even better

[Steve]

Perhaps, but then you are asking the BB to something -- more. And doing "more' often comes at a price. This is not a huge drag on the CPU...but it is all cumulative. Since every computer and interface is different, it seems best to leave that to be managed by the interface. But I hear the request.