Quantizing of Audio causing region corruption?

Question

I have noticed that when I quantize, then de-quantize audio regions numerous times (trying to learn what works best in a given instance), the note placement eventually becomes way off, even with no quantize is selected. Why is this and what can be done to prevent it? Is there a way to restore an audio region back to the original file's condition?
This problem makes me not want to experiment until I know there is a way to get back to 'square one'!
Thanks!

Answer 1

I need to do that {turn flex off} per track, no?
Not exactly. Flex can be controlled (i.e., turned on and off) on a per track basis, and also on a per region basis (except that it must be on at the track level if you want it to be on at the region level). So you can turn Flex off per track, but you're not required to turn Flex off per track, if all you really want to accomplish is turn Flex off for one region.
The Track Inspector has a menu for selecting Flex modes, and one choice on that menu is "Off." And this is the exact same menu that appears in the track header when you press ⌘F. That keystroke is the equivalent of this command in the Arrange window local menu: View > Flex View. It's also the equivalent of the Flex button in the toolbar. It's important to understand that showing and hiding Flex information is a separate matter from turning Flex on and off.
The Region Inspector has a checkbox called Flex. This checkbox only appears if Flex is turned on for the track hosting this region. The point of this checkbox is that you can turn Flex on for a track, and then make one or more regions on that track exempt from Flex.
The Flex button at the top of Arrange only turns on the flex View, correct?
Exactly. This has to do with what I said about the difference between enabling Flex and making Flex visible. Two different things.
Is it possible that although the original file is not changed, the Region being quantized could get messed up to the point of becoming unusable?
I don't think so.
I think there is a chance that I am getting this problem and the varispeed/autopunch problems mixed up/mixed together
That could be. These features tend to overlap each other somewhat, so it's easy to get confused, especially if you're trying to use a bunch of new, powerful features all at the same time. But there's nothing wrong with that, as long as you're willing to tolerate the confusion. Then you can take a step back and examine each feature separately, to figure out what's causing what.
There might be less confusion if you learn one feature first, before you jump into another one. Some people might prefer that approach. But it's perfectly fine to take some chances and jump right into the deep end, as long as you realize that every now and then you'll be a little bit over your head. No harm done! It's just different approaches to learning, and you should take whatever approach suits you.
sometimes one problem is confused for another because we're just not sharp enough to make the distinction
This is what happens when you try to learn multiple advanced features at once, but there's nothing wrong with doing it that way, if you like to do it that way.
Sorry for all the questions
Don't be sorry, that's what this place is for. And you're asking good questions that are also probably on the minds of lots of other present and future readers.