idiot_savant

This is interesting - do they adjust the analogue filter for the various DSD rates? your friendly neighbourhood idiot

unless you put a signal in… Your friendly neighbourhood idiot

Nice review… for the slow filter impulse, what happens if you reduce the gain going in a bit? i.e. less than full scale? Looks like it’s wrapping round… your friendly neighbourhood idiot

@opus101 I’d have thought a general “sounds better” is falsifiable? ergo doesnt improve *anything* - isn’t that easier to prove? “The bass was improved but not treble” “the treble was improved, bass not” Serious question - when did becoming an audiophile equate to believing every piece of nonsense as a badge of honour? I’d always equated it with *caring* about the sound? Audio Love and all that? I’ll ask again - for subjectivist opinion, have you subjected yourself to this software? If not, why do you care? Your friendly neighbourhood idiot

Hi, just to clarify - there is no DSP here, and because it’s written in C# you can decompile it, not disassemble it which makes it much easier to read your friendly neighbourhood idiot

Because he made ridiculous claims, vowed to prove them and couldn’t. look, an outrageous claim has been made and not one other person can hear it your friendly neighbourhood idiot

This is an interesting point - who would you trust to design a rocket? People who do the sums, design, measure, test, repeat, looking into any anomalies - or people who iteratively do stuff because it "seems to make an improvement" without knowing why? your friendly neighbourhood idiot

OK, so I'll ask *again* Can anybody hear the "improvement"? As for the tedious repetitions about it doing "something" to the file, as has been stated ad nauseum, the file *is not being accessed whilst it is playing* it is read in it's *entirety* into RAM before playback starts. These are not conjectures or whatabouts. I have looked at the source code and that is what it does. The "optimising" involves reading the file into memory, then writing random numbers into the page file for 2 minutes, then writing it back to another file, with I'm guessing the (incorrect) assumption that there is "noise" in the data that is somehow reduced by magic. As for the "failed science" opinions, I'm afraid my irony meter is off the scale with people stating that *on the internet* your friendly neighbourhood idiot

Right, as entertaining as this topic has been, I think a prerequisite of “proving” something is having a supporter - I.e. someone that can hear the optimised file being better than the non-optimised file. since we have none, is it agreed that two files, with *identical* contents played back with *identical* software on the an *identical* system are, in fact indistinguishable from each other. if anyone disagrees with the above, please give us experiences *with this software*. I don’t really care you had wind in 1978 and could therefore hear previously hidden glockenspiels on an LP your friendly neighbourhood idiot

But the SSD isn’t being accessed during playback, as has been pointed out many, many, times. And before anybody talks about the OS, background processes - it’s only the audio file that has been “optimised” can *anybody* hear the difference? your friendly neighbourhood idiot

Whoah, getting a bit of ourselves here - who has ever said this does *anything*? My argument is it *can’t*, and even if by the magic of really, really believing something *any* change would be microscopic and over before the track started. We have had zero sensible explanations of how this software works, only one person who claims to have heard it working ( who has now left ) and several people explaining how it can’t work. now, we can wave our hands as much as we like but I’d prefer to stick to facts your friendly neighbourhood idiot

Erm, what? your friendly neighbourhood idiot

Now, I know I’m going to regret this, but… are we now claiming that after making the file “easier to read”, we bypass a cooling/charge effect that coincidentally lasts the length of the track that’s just been read? does this make sense to literally anybody? your friendly neighbourhood idiot

So there’s a bit of cross purposes here - there was a problem in early Samsung SSDs where the flash cells if they weren’t touched for a while began to discharge, so the drive would slow down over time. Utilities were written to basically rewrite the whole drive to refresh it - so a genuine problem, with a genuine fix that unfortunately doesn’t make the refreshed drive sound better, as all disk activity has stopped if we read the whole file into RAM. the other stuff is nonsense your friendly neighbourhood idiot

Nope - the example is it doesn’t matter how you store them, they are different representations of the same data. So sound the same as we can read them all and extract the same numbers at the same time your friendly neighbourhood idiot