Hi i do not know if this means something, maybe not 😱
but i heard a very good sound from Pioneer cd players with stable platter mechanism that reminds me of a Turntable ...
i like this solution very much indeed. I would buy one if i had a definitive situation at home. Very nice.
but i heard a very good sound from Pioneer cd players with stable platter mechanism that reminds me of a Turntable ...
i like this solution very much indeed. I would buy one if i had a definitive situation at home. Very nice.
Actually it would, especially if you calibrate your monitor... Look at PDFs opened in many different PDF readers, or Pictures...
Ginetto, it looks nice, but it is a bogus solution to a non-problem, which only makes matters worse.
CD's don't spin at a constant RPM, but go from 210 at the rim to 480 RPM on the inside. You want to have as little rotational momentum as you can so the player can adjust its speed as quickly as possible. This stage of the process only gets the bits off the CD. Playback timing is done separately from this stage and is not impacted by speed variations in reading the bits.
CD's don't spin at a constant RPM, but go from 210 at the rim to 480 RPM on the inside. You want to have as little rotational momentum as you can so the player can adjust its speed as quickly as possible. This stage of the process only gets the bits off the CD. Playback timing is done separately from this stage and is not impacted by speed variations in reading the bits.
In multi-threading environment, CPU-time and memory is "shared" among software. If free memory or CPU is not sufficient, as often caused by virus, of course no process will run perfectly.
This cannot be a reason why Foobar is different. Virus is complicated as it can disguise itself in the form of whatever system's filename. WINAMPA is another file that often causes problem in memory usage.
A relevant issue with audio players is the buffering, i.e. putting some encoded file in a buffer and then decode the file in the buffer. I have seen in a simple MP3 player where buffer size is defaulted to a constant. If a decoded file already "played" and buffer cannot provide "fresh" frames then a GLITCH may be heard.
But the glitch is so short that it may be inaudible for most people. When the glitch is so serious, then even the cloth ears audiophile can hear it 😉
So you actually meant to write: This cannot be a reason why Foobar is claimed to be different.
Your analogy is inapt. "Pretty" has nothing to do with whether person A is distinguishable from person B. It assumes that the person referred to can be distinguished.
Your analogy is inapt. "Pretty" has nothing to do with whether person A is distinguishable from person B. It assumes that the person referred to can be distinguished.
Possible but unlikely, Richard - a lot to do with the inflexibility of altering the output module, I suspect, under Vista. I've just done a quick round going the next step with foobar on the laptop, which entailed as much as possible matching the output options with those I'm using for Media Monkey, and in an initial test, in a non-optimum stage of warm-up it's close, very close. Which is to be expected, the output module is doing virtually everything, foobar registers 0% usage while playing.
Tomorrow I'll get the machine fully up to optimum, and throw my worst at it, in terms of difficult tracks, and see what shows up. Unfortunately, even if they remain at par it still doesn't solve the ABX issue, because the latter module wants to churn CPU cycles while playing, and I've already seen this slug the SQ.
Amir mentioned its the ABX module which kicks the 'audiodg.exe.' into its incontinent state - but there's a fix which he said he's so far been unable to apply.
Regarding highs, my experience with different tweeters all baffled in the same manner will subjectively produce different amounts of treble energy. One tweeter can be down 4-5 db from the other and sound brighter than the one that has a flat FR.. If mounted in waveguides, another issue altogether..
If not electronically.. I have to wonder then.. I guess it's a secret for now..😉
Last edited:
I'll go a step at a time, and see what he says once I'm happy with foobar straight. The other, huge downside is that the ABX copies and resamples the test tracks into a uniform format, in a work folder, before running! Well, duhhh ... that's bloody useful for doing fine comparisons, in related areas!!
Okay, just did a simple test regarding "audiodg.exe". In Windows 8.1 it definitely is used, it gets started if not running, when replay starts for both by Media Monkey and foobar - but appears to be benign, at least in regard to how I've specified the output processing: no apparent CPU cycles used, and the initial memory allocation doesn't budge.
No it would't. Not if I use Open Office with Linux and a different screen resolution.
But in this analogy if the output pdf prints the same then they are equivalent.
How did we get from a doc file to a pdf? The point is that there is all kinds of processing going on by different programs. Take something simple like the volume level will mean bits loaded to a register and shifted or other processor function and sent out on its way. I am trying to look at this in a very low programming/machine level
Last edited:
because we are talking about the OUTPUT of the package. The output from a word processor is a printed document. The output from a music player is music. If the waveform visualisations look different who cares as long as same bits are fed to ASIO.
- Status
- Not open for further replies.