DP 10-11Bug!!!

[oshtakuta]

https://drive.google.com/file/d/1ySSWsM ... YwuzB/view

https://drive.google.com/drive/folders/ ... zhY72Va8Ke

[mikehalloran]

It opened once for me. Unfortunately, you can't stroll a gif back to look at something again, only reload — which this wouldn't do for me.

YouTube is a much better vehicle. Take the screen recording and upload.

I see the offset but without being able to look again and see exactly what you were doing, I haven't a clue and don't know what questions to ask except what plugins you may have on the track. Some cause offset delays even when bypassed.

[sockmonkey]

Looks like you've found a few off-by-one errors. Have you submitted TechLinks for these things?

Also, please write some text so that we know what we're looking at and how you're set up / whether your setup has any special features (weird sample rates, etc.). Same goes for submitting bugs at MOTU. If the issues are as straightforward as your videos indicate, seems like this stuff ought to get fixed.

[bayswater]

I can't reproduce the error in DP 10. But this definitely needs to be posted as tech link to see if MOTU can reproduce it.
Difficult to tell from the gif, but it looks like there is something not quite right with the wave dragged into the Tracks window right from the start. The shading looks odd, as if the soundbite borders are not conforming to the actual start and end of the audio file. Can this be reproduced with other audio files?

[oshtakuta]

This occurs at tempos not equal to 120 beats per minute. In this example, the tempo is 135 bpm.
You can try it yourself. Import the audio sample and copy it to the beginning of a new measure (mind you, tempo is 135 bpm, not 120!). You can copy with the keyboard shortcut Option Shift D, or using the Cmd R, or just drag and copy. Then place the wiper at the beginning of the new measure with the copied audio and zoom in to the maximum. See where the audio is and were is the wiper.

This happens on both the Mac and Windows.

[Drumwizard]

One of these bugs in all versions since DP 8. One extra sample appears all the time.
By the way, if you drag and drop an audio file from Finder somewhere on the 57th bar, for example, it will also be shifted by one sample.
A mathematical error in the program engine.

[mikehalloran]

This occurs at tempos not equal to 120 beats per minute. In this example, the tempo is 135 bpm.
You can try it yourself. Import the audio sample and copy it to the beginning of a new measure (mind you, tempo is 135 bpm, not 120!). You can copy with the keyboard shortcut Option Shift D, or using the Cmd R, or just drag and copy. Then place the wiper at the beginning of the new measure with the copied audio and zoom in to the maximum. See where the audio is and were is the wiper.

This happens on both the Mac and Windows.

So is it quantizing to the next beat? If so, that's not a bug; it's in your setup.

[sockmonkey]

One of these bugs in all versions since DP 8. One extra sample appears all the time.
By the way, if you drag and drop an audio file from Finder somewhere on the 57th bar, for example, it will also be shifted by one sample.
A mathematical error in the program engine.

This seems like something which really ought to be fixed, have you filed a TechLink with MOTU?

[Phil O]

If I did the math right-

at a 48K sample rate and a tempo of 135 bpb, 1 measure should be 85,333.3333 samples. That would explain why when snapping to a measure it would be off (0, .3333, or .6666 samples) and we can't split samples, can we? One would expect it to be dead on every three measures right? Well maybe. I've found that it is in fact 1 sample to the right (at least in the case of 135 bpm). In playing with this I've found it's always placed to the right. Maybe MOTU decided to always round up or somethin. Anyway...

At 48k 1 sample is roughly 20.8 microseconds. So, everything we do will be quantized to that anyway, right? Am I missing something?

BTW 20.8 microseconds is the amount of time it takes sound to travel 0.28 inches or about 7.1mm (depending on temp, presure, etc.) I suppose if you have two tracks that require perfect phase correlation (like doing parrallel compression or something) this MIGHT make an audible difference, but other than that no one can hear it. So on that rare occasion when splitting hairs (or samples) is needed, don't rely on "snap to" to be better than one sample. Instead zoom way the F in and move it manually.

Your friendly neighborhood Phil

p.s., Did I do the math right?

[Drumwizard]

So is it quantizing to the next beat? If so, that's not a bug; it's in your setup.

Dear, Mike Halloran, I respect your venerable age and understand your attitude to your favorite program. But... This is a software error.
Try copying the soundbite to the beginning of a new measure. Set the tempo to 135 bpm (there is no error in 120 bpm). Place the cursor at the beginning of the measure in which you copied the audio file. Zoom in to the maximum. Maximum! And now look. The soundbite is shifted one sample to the right. This shouldn't be! If you copy a selection using the Command R keyboard shortcut, the last copied soundbite will be shifted by as many samples as the copies were made.

[Drumwizard]

p.s., Did I do the math right?
[/quote]

Nice job, Phil! Now calculate it for 44100

[bayswater]

This occurs at tempos not equal to 120 beats per minute. In this example, the tempo is 135 bpm.
You can try it yourself. Import the audio sample and copy it to the beginning of a new measure (mind you, tempo is 135 bpm, not 120!). You can copy with the keyboard shortcut Option Shift D, or using the Cmd R, or just drag and copy. Then place the wiper at the beginning of the new measure with the copied audio and zoom in to the maximum. See where the audio is and were is the wiper.

This happens on both the Mac and Windows.

So is it quantizing to the next beat? If so, that's not a bug; it's in your setup.

Not the next beat. The next sample. It's always one sample late and it compounds over multiple copies.

[HCMarkus]

Just sent a link to this Thread to MOTU.

[oshtakuta]

is there any feedback?

[HCMarkus]

is there any feedback?

I'm using in-ears, so no.

If you mean from MOTU... Travis responded that he will notify DP Development Team.