Not exactly quantizing

[italodisco]

I'm wondering what's causing this issue - I looked in the PDF manual for relative grid stuff and I'm not really sure that's what's happening.

Using DP8.06. I cut a piece of audio - let's say a drum hit - nice and tight so I have the transient right at the start. I select the soundbite, quantize to 16th notes - it snaps over to 5.1.000...or so I thought.

If I zoom WAYYY in and it actually isn't quantized right - it's on 5.1.003. I hit quantize again while zoomed in, it jumps to 5.1.000.

Please tell me what I'm doing wrong. Thanks in advance.

[italodisco]

(And by "what I'm doing wrong" I mean how can I not have to zoom and quantize twice?)

[italodisco]

Even though there have been no replies on here, I just confirmed with MOTU tech support that the problem (at least not quantizing right onto the exact beat) is replicable. Unlike me, the tech could not get the soundbite to further quantize when moved in.

Major flaw even though it's on such a small level as not to be easily heard in most cases, but still strange and looking forward to an explanation, which I hope to receive. Failing that, looking forward to a fix.

[Tritonemusic]

Thanks for the followup. It's good info to have.

[Shooshie]

Small tolerances, but very much enough to cause phasing issues, and it's completely NOT "sample accurate." If they're going to say that DP is sample accurate, which has always been one of its big selling points, then it definitely needs to BE sample accurate, especially when you hit "Quantize." If there's any time it needs to be sample accurate, that is certainly it.

I didn't know that was happening, and I have to admit that it makes me a little angry. The programmers need to check for stuff like that. Sample-accurate, boys and girls. That means... oh you know what it means. Just do it! (pretty please?)

I'm starting to think that the guys who wrote DP the first time around were giants. Not that the new guys won't catch up to them, but little things like this have to be absorbed as lessons, not tossed off as "sh*t happens."

Shoosh

[italodisco]

If it's not user error or something I'm not aware of, I agree it's an outrage (at least scaled to DAW outrage levels)… Here's hoping it's something we haven't thought of that explains the behavior. It was suggested I try "Clear Sync Point" on all the Soundbites, but I haven't set any and it's my own recorded audio (not imported) meaning it's doubtful there are errant sync points. Nonetheless the next time I notice the issue I'll try this suggestion and report back.

[labman]

I concur wholeheartedly with SHooshie. If this is true, then it needs to be addressed pronto. There are enough other sources of bad phase relationships in audio, that we need DP to 'tell the truth at all times', otherwise it is shooting in the dark at a moving target.

[stubbsonic]

Just confirming this old thread. This bug happens on my system 8.07/10.10.5.

It's probably been like that, and I didn't zoom in enough to see. The amount it was off in my test was a little over one sample. I could understand if this was just a rounding error of less than a sample.

[Robert Randolph]

If someone can replicate this issue in DP 9.x, please file a report here: viewtopic.php?f=1&t=61937

Video or images would be appreciated, along with a concise step-by-step.

[Nibiru]

And I was just going to pose the question of whether it's better to use a bus to perform parallel compression or to duplicate the track to avoid phasing issues...oh dear.

I also noticed this in 2006-2007 when working on a project at that time. I thought it was probably a graphic issue and not audible...bummer it's still an issue. I have many many question, like dither, once again... for f**** sake...

[stubbsonic]

I'm not sure I'd be able to hear a track delayed by 1 sample (or in this case, something like 1.5 samples). But yea, the bigger point being that we're all trusting that quantizing and nudging are behaving as any reasonable person would expect them to.

This is especially bothersome since we've heard over the decades various claims that DP has be "redesigned" or "rebuilt" from THE GROUND UP. I would take that to mean that they've worked with all the code to make sure it is all working correctly and with precision. This and the nudge bug are important, not because the error is so huge-- or that a workaround can't be found, but that they happen at all. As an aside, if MOTU pledge that they would fix ALL these things, I would gladly pay for that update-- even if it meant that it might take a while. Their focus on new features is fine, but at the expense of languishing features & bugs--it's a little hard to defend.

[Nibiru]

Not trying to be a jerk at all but, has MOTU responded to these claims at any point? If DP is not sample accurate, as I mentioned before, wouldn't it also not have proper phasing? Sorry, again, not trying to cause a stir, just asking/sayin...

[Robert Randolph]

Not trying to be a jerk at all but, has MOTU responded to these claims at any point? If DP is not sample accurate, as I mentioned before, wouldn't it also not have proper phasing? Sorry, again, not trying to cause a stir, just asking/sayin...

No response from Motu yet, but I can replicate this pretty easily in every version of DP9. See the attached video.

I created a new techlink for this a few minutes ago. I'll update the community issues list with this if/when I've confirmed (or not!) it with Motu.



(Forgive my stuttering. I got sick of re-recording 20-30 times like I usually do to deal with my stutters. </irrational embarrassment>)

[mwilloam]

Just throwing this out there. I've seen something like this in versions of DP dating back ... for awhile. I wonder if it is simply a UI rendering(bug/rounding error) and the audio engine is actually handling the timing sample accurate. Just a thought...