Multi-mic merge unequal length issue

[d.healey]

I've just been trying to merge some multi mic samples but I was getting an Unequal length at sample N message. So I checked the length of the samples it flagged and re-trimmed them just in case and tried again, got the same error. So then I removed those sampler entirely and tried again, got the same error but pointing to a different sample, and so on.

Anyway I solved the problem, instead of dragging in all my samples and mapping with velocity spread, I dragged in and mapped one velocity layer at a time, then I merged the mics without issue. So I figure something was getting messed up with the auto mapping.

[dustbro]

Interesting... I got this error too. On my end, it ended up that some samples I exported from Cubase were shorter by 1 sample! I think it's an error with their crossfade math, but haven't looked closer yet.

[d.healey]

I just came across this issue again with a different sample set. Again the solution was to drag in each velocity layer one at a time instead of using velocity spread. So I'm pretty sure this is a velocity spread bug.

[LightandSound]

@d-healey

Just came up against this issue without using velocity spread - so I don't think it's specifically that.

[d.healey]

@LightandSound said in Multi-mic merge unequal length issue:

Just came up against this issue without using velocity spread - so I don't think it's specifically that.

Are your samples definitely the same length?

[LightandSound]

@d-healey to the sample yeah

[d.healey]

Did you convert them to monoliths before you tried to merge?

[LightandSound]

@d-healey if I come up against it again I'll update here

[LightandSound]

@d-healey Issue was due to velocity ranges of 1 not being permitted and I missed it. Implemented a quick fix.

[d.healey]

@LightandSound said in Multi-mic merge unequal length issue:

@d-healey Issue was due to velocity ranges of 1 not being permitted

They are in my build although I haven't tested with multi-mic samples.

[LightandSound]

@d-healey I'll test out your build - though looking at the commit in your build it changes the sampler to allow it, but not the import method unless that was in an earlier commit - since FileNamePartComponent takes the value for the high velocity and adds + 1 (when importing at fixed velocity that is)

[d.healey]

@LightandSound Yeah I didn't fiddle with the import method at all. At the time I'd already imported my samples and then decided I wanted them on a single velocity.

[LightandSound]

@d-healey I've got about 13,000 samples to import to this one sampler so I'm definitely not doing this manually xD