jimknopf:
Funkybot:
I suspect what’s happening is that there are some types of audio where it’s worse, or some particular use-cases. I don’t think the people who say it’s terrible are lying, I just think it’s not working for them in their particular use-cases or with the types of audio files they’re using. That’s why I think it makes the most sense for these people to start offering some details (sample rate, system), example audio files, screen prints, and maybe even project files so the powers that be can properly analyze the issue.
Completely agree, and would never assume any lying or badmouthing from anyone. And I’m ready to check audio files, where the present detection fails, to find out more about possible reasons.
But from my own experience, I can’t buy generalising claims and over-excited, aggressive follower statements above any more. Something like a generally broken hitpoint detection simply does NOT exist in my general use 0f 10.0.20 here so far. Just the contrary: the new tools really seem to work quite well here, and offer much smarter solutions for different material, than any previous version has ever offered.
Normally I’d agree with that sentiment but if you refer to my original post with an example; it’s obvious that the detection algorithm wasn’t functioning correctly.