Arghhhhhhhhhhhh my f'ing ears!
Last post by Chibisteven -
On the subject of normal listening levels.
I can't tell the difference between these.
I do not deny and have never denied that the noise can be inaudible with normal listening levels. That is the whole point of getting a new soundcard or DAC over one's existing solution. Many motherboard integrated sound devices for example do not offer such luxury.
Digital devices also have noise as long as they're dithered properly, so they're equivalent to analog in this regard.
So what are the circumstances when it becomes audible? This is hardly a new question. The sensitivity of human hearing has been under investigation for generations, and we have some hard data available that allows us to talk numbers.
Example: If you have a DAC whose noise floor is at, say, -94dBFS, and your average playback level is around -14dBFS (this is material-dependent, of course), which you play with an amplifier gain that results in 86dB(SPL) at your ears, would you consider this a typical use case? If not, what would your definition of a typical use case be?
If you accept it, you will have a noise floor at 6dB(SPL), assuming the noise from other sources (for example the amplifier) is negligible. You're not suggesting that you hear this in a normal environment, even with closed headphones, are you?
Now, noise floor at -94dBFS is a very modest example of a DAC. It is the type of performance you can expect from chips costing less than a dollar, consuming a few milliwatts. It is the type of chip you find nearly everywhere these days. At somewhat greater expense and power consumption, chips delivering this kind of performance were commonplace more than 25 years ago.
If you do hear hiss from such DACs, I suggest it may be because of something else than the actual DAC. The noise may come from elsewhere, perhaps the amplifier, or perhaps it may be due to interference. Or you are working with an inappropriate gain structure that doesn't make good use of the DACs capabilities. None of this would be the DACs fault, and basing a rating on it would be unfair.
Granted, the complexity of actual soundcard hardware and the associated software may make it difficult to even determine what the gain structure is, let alone control it purposefully. But if you want to make relevant statements that can be replicated by others, you will have to be explicit about it. If you hear hiss in a normal environment, something is wrong, or at least not adjusted optimally.
Last post by klaberte -
Hi again! I have been doing research since my last post. A few updates:
1. The clavinetjunkie youtube video double blind test is misleading. I have been corresponding with the poster with the hopes that he sets things straight, specifically that the non-aptx files he is sharing are almost certainly using the high quality profile of sbc, not the medium profile that most people actually experience.
2. I have found a bluetooth speaker that does both aptx and wireless pairing, the Beoplay S3. However, it has no battery, so must be plugged in via AC power. That is actually a plus for me. I just got a pair and will post once I got a chance to give a good listen.
Last post by Whoknew -
In the content tab of properties, only title is populated. Windows explorer (Details pane) isn't able to edit the tags without throwing an error, however, I can't get it to edit m4a files that are in the music library either.
Hi I'm Gustavo Woltmann and I work here in a publishers office. I want to ask regarding an app for converting mp3 recommended for android users? What is the best app so far?Did you ever try out MP3 Compressor? It is totally free and i have used it for months. I think the compression ratio is more than 50% as far as I have noticed.
I'd disable the network driver or turn off the network hardware just to narrow things down.
As was mentioned and if you haven't, explore setting foobar2000's buffering for more time.
If your audio hardware supports it, try using some other output driver in foobar2000, e.g. WASAPI, ASIO, Kernel Streaming. They each have their own options dealing with things like interrupt priority, hardware audio buffer size, etc. that may help.
It's up to the OP now to say whether such pedantry is what he's interested in.That would seem rather hopeless since he also tosses around the concept of audibility in a willy nilly fashion...
Only respond if you perceive/believe there is a difference
People who think that there is an audible difference between DACs is the only demographic which I am interested in for this poll.
Also, If I were trying to get an answer as to if there is a difference or not, asking random people on the internet is certainly not the way to go about it.Yet, that's exactly what he's doing.
As you all know there are far far better and objective ways of determining that.We all know?!? I wouldn't be so sure of that.
I am fully aware that looking at measurements there should be no difference between any reasonably designed (and they don't deliberately have high distortion) [...] Also, I am aware in ABX tests DACs do not fare well, as the measurements say they should.At least someone here begs to differ.
As part of what I am doing I will conduct an ABX test (a proper ABX, not just a blind test) with several people between DACs.I'm not holding my breath.
Here are the Latency tests (ran while the hard drive was under load).
Where should I go from here? My network drivers were up to date, so I've downgraded them just check the problem wasn't introduced by the newer drivers, but the problem persists.
I can't get the command prompt to run anything under "Sort" in the Edit menu -- I want to set Foobar to run the randomize command and it doesn't actually do what it's supposed to...
In console, this is the error I get:
runcmd: Resolving main menu command: Edit/Sort/Randomize
No available command found