I believe I posted this earlier but it outlines points better than I can express (or understand from a development point of view)
The two founders of Samplitude who still head up development state:
This is not something that was written back in the early 90's when development was still ropey, this was written a year or two ago.Herberger is sceptical about the notion that there are no sonic differences between audio programs.
"I think the big thing about the sound quality is to make no mistakes. You must not do mistakes in the DSP. It's a big goal, and a lot of errors and not-clever routines are done by a lot of parties on the market, and people who are trained to hear audio will discover these immediately. Six or seven years ago, we had a patch for a new Samplitude version, and one day an American guy called us and said 'Hey, you did something wrong in your program. It sounds bad now.' We measured, and did tests, and after a long time we found out that in the 24th bit of the audio in going from floating-point arithmetic that we do internally down to the sample level through a 24-bit converter, we forgot the dithering. I personally could not hear this, to be honest — but you can measure it, and in a program as huge as Samplitude, you have a thousand points where you can make a mistake of this sort.”
From the very beginning, two hallmarks have defined the philosophy behind Samplitude: the 'object oriented' approach to editing and processing, and an obsessive commitment to purity of sound quality.
"Especially with small waves in the area of the zero crossing,” adds Titus Tost. "As you switch from negative to positive, there are some problems with rounding. It takes a lot of experience to put this together so that it sounds good.”
I'd like to think this kind of commitment, dedication and experience in programming for such focus on purity of sound quality should have tangible results in audible output. My ears agree with me and the above statements (even before I had read them.)