Can't move triggers on Beat Detective with 32nd notes

[Kourquie]

I typically use 16th notes when I edit using beat detective, but I'm editing a section with a lot of 32nd notes. All day, Beat Detective worked great at the 16th note setting. However, when I switched to 32nd notes, it won't allow me to move any of my triggers or add new ones.

I did the normal, capture selection, analyze, etc. The resolution is on Sub-Beats, and everything is normal...but I cannot edit 32nd notes. Any help?

[Kourquie]

Also, my selection lies on the downbeats of bars, so no problems there, either.

[suicune]

This has been a quirk of BD for a long time now, at least since v7 possible even for ever, I don't remember v5 days much any more. I never use it in higher than 16th resolution for this reason. A couple of workarounds:

First of all, check that BD is getting triggers right to the end of your selection. Sometimes it gives up if there are too many, in which case you need to work on smaller selections at a time. You'll have trouble editing triggers at any resolution when it does this.

If there's not masses of 32nds, I would suggest doing just the 16ths then splice the 32nds by hand. If there are loads, then I'd make sure all your tracks are in sample ref, and double the tempo. Work at 16ths, do your edit, then change it back afterwards.

[RedTriangle]

Nice tip ^^^ thanks :) Just joined this forum seething with frustration at all the changes in Beat Detective since 7.4 (just upgraded!)

32nd notes don't seem to trigger right at all in v.9 even with a really tight drummer...

[jonnyb8390]

Hey Fellas,
Still not reading 32nd notes in PT10. Haven't tried PT11, but I'm not too enthusiastic. Will not recognize or permit me to assign 32nd note values while "Contains" has 32nd notes selected.
Mayday!!!

-Jon