ENUFF GRABASS!!! Sample-rounding BUG!!

[s2n]

Forget about ADC. Forget about the mix bus problem.

Digidesign, can you fix this GRABASS sample-rounding BUG?!!! It's a joke (and an embarrasment) having to spend hours deleting these 4-sample long regions.

[s2n]

I'm surprised nobody gives a [bleep] about this BUG.

[John McDaniel]

Elucidate.

[Jan Folkson]

Yeah...what John said! I think

If you explain your problem with some more detail (or any) you might get a better response.

[Rail Jon Rogut]

By using Command+Zero to quantize my regions I don't have any issues editing in Bars and Beats mode.. so I'm curious about what technique you're using in Chudderville which leaves you with the 4 sample long regions.

Rail

[Tweakhead]

so I'm curious about what technique you're using in Chudderville which leaves you with the 4 sample long regions.
Rail

LMAO !

[s2n]

Copy/pasting loops (and I'm not talking about drum loops) in bars/beat mode.

From the Pro Tools Reference Guide:
Pro Tools is a sample-based program with an internal
MIDI resolution of 960,000 pulses per
quarter note (ppq). However, when the Time
Scale is set to Bars:Beats, the display resolution
in Pro Tools is 960 ppq.

In Bars:Beats, Pro Tools is tick-based (960 ticks
to a quarter note), which means that some
amount of sample-rounding may occur when
placing events at certain locations.

It's also been a topic on the DUC here and here .

It's a bug. No other audio editing program that I have used has had this type of BUG.

Rail, do you think I should really have to quantize my audio regions every time after I've pasted them to the grid? This is nothing but a workaround (and extra step to make) to overcome this BUG.

In Chudderville, we don't have time to waste while sitting there chudding on Pro Tools all day in a small room.

[Rail Jon Rogut]

Pro Tools is sample based.. and not tempo based like most other apps... I don't think that having to hit Command+Zero is too much of a hardship (and doesn't slow me down).. but that's just me.

Rail

[Philthy]

I think that there are other glitches that relate to this problem... spots in the timeline where it's impossible to get a midi note to stick; little pieces of audio ending up stuck between regions which make group fades fail; meter changes in italics insisting that you're working with partial measures even when you're not, etc. etc. In general the tempo/meter region in ProTools feels really iffy to me, and there are still no controls over tempo and meter anywhere near the power and flexibility of the controls in Digital Performer, Logic, or Studio Vision Pro. It seems like Digi might need to figure out a method of dealing with the samples/tempos issue before we can start to see any of the modern conductor track/midi features that you find in other sequencing programs. Face it; by now it's a lame excuse to claim that ProTools is just for audio. It's marketed as a full-fledged production tool and the MIDI was first implemented a long time ago now. This stuff is beyond overdue for some major improvements.

[ctmartin]

This sample-rounding thing goes back to the very beginning, doesn't it? There was a time I thought they "fixed" it, but... umm... no.