Quantize Beats within Soundbites broken in 9.1?

[Robert Randolph]

I'm seeing some really weird behaviour today when I try to use quantize with 'Beats within Soundbites'.

Here is what happens in 9.02. This is the correct behaviour:



----

Here's what happens in 9.1




Note that in 9.1, it quantizes correctly then for some reason it jumps back to the previous place. I've found that if I merge soundbites on the soundbite, it suddenly works correctly!

I've tried deleting beats and finding them again, and that does nothing. I've tried re-adjusting beats. Newly recorded parts have the same issue.

Is anyone seeing similar behaviour at all?

I was working on a video tutorial for a common workflow I encounter, and this kept coming up. I want to make sure I'm not screwing something up here before I post a tutorial video!

[bayswater]

I'm seeing some really weird behaviour today when I try to use quantize with 'Beats within Soundbites'.
Here's what happens in 9.1

I can't reproduce this. Seems to work OK on my laptop.

[Robert Randolph]

Thanks for checking.

This is so weird. Sometimes it works if I make a selection, and sometimes not. Sometimes I get garbage results too where the resulting sound is not right.

I've tried trashing prefs, deleting the analysis files, dropping the files in to a fresh project... trying to think of what else I can try.

[Robert Randolph]

A quick gif of me simply re-quantizing the same section repeatedly.

Different result each time! Same beat assignments, same audio.

[bayswater]

That's very odd. I tried it several times with undo between and it behaves as expected consistently. I'll try it on the iMac when I'm there next.

Could it be a corrupt audio file? Have you tried it with entirely different audio files? Erased and replaced the beats?

[Robert Randolph]

Could it be a corrupt audio file? Have you tried it with entirely different audio files? Erased and replaced the beats?

I've tried other audio files, erased and replaced beats.

Only thing that seems to work is if 'merge soundbites' on something first. Goes for any audio file in any project in 9.1 for me.

Surely there's something that I'm missing here. I'll mess with it more tomorrow... for now I figured out the workaround so I could keep on keeping on.

[bayswater]

Anything locked?

[Robert Randolph]

Well, this just popped up in 9.02 now, and merging soundbites isn't fixing it this time.

Not only is it not quantizing to the correct division, but it doesn't quantize to the same place if I quantize/undo/quantize!

I'm becoming frustrated This is so bewildering.

[Robert Randolph]

Ok! I've found a cause. For some strange reason, DP was having some very weird sample rate mismatch.

I only found it because I enable the 'Project Settings' option in the transport. This is what I saw:



The project was playing back audio fine. Soundcard (either RME Fireface or Saffire Pro 40 stack) was showing the correct sample rate.

I sent a project with this issue to 5 other people, and they all had the same quantizing issue. So it must be some weird project corruption?

How to fix it:

1. Open a project with the issue.
2. Go to Setup->Configure Audio System->Configure Hardware Driver
3. Set the sample rate here to the correct value for your projects.
4. Close DP. DO NOT SAVE THE PROJECT WHEN IT ASKS.
*5. Open your soundcard's control panel.
*6. Set the sample rate to the correct value here.

* Not necessary on all devices

This fixed the issue for me. Now the affect projects quantize correctly. I only had to do this once on an affected project.

This issue appears to be related. It also was happening occasionally, and now it hasn't happened all afternoon since figuring out this 'fix'.

What caused it? I have no clue. I've used various sample rates due to necessity with no problem in the past. The issue was reproducible on other DP user's systems given just an affected project.

4 days of later... and finally work can continue at a normal pace.

[bayswater]

Ok! I've found a cause. For some strange reason, DP was having some very weird sample rate mismatch.

Makes sense. Suggests it's something to do with how DP and your audio interface interact.