Android resampling

Feb 24, 2022 at 3:51 PM Post #106 of 124
I still don't understand your point, but this is something other than why I joined the thread,
You asked for "proof that it's possible for a dac to differentiate a sawtooth wave from a sine wave from a couple samples", which is exactly what I posted. If this is not why you joined the thread, then why did you make the false assertion that it's not possible AND then asked for proof that it was?
so I'm disengaging from the discussion for an open time period.
OK, you're disengaging because you got the proof you asked for, which falsifies your assertion.

G
 
Last edited:
Feb 24, 2022 at 6:26 PM Post #107 of 124
You asked for "proof that it's possible for a dac to differentiate a sawtooth wave from a sine wave from a couple samples", which is exactly what I posted. If this is not why you joined the thread, then why did you make the false assertion that it's not possible AND then asked for proof that it was?
Thank you for your service and intent to make me better understand these things.

I asked because I didn't know and I thought your proof may change my mind or give me insight into your own thought process.

I made the assertion because it made sense to me, I didn't know it was false.

This animation may help you visualise this sine wave combination, "N" is the number of sine waves added together.

If a function x(t) contains no frequencies higher than B hertz...

you're disengaging because...
I have my particular reasons. For now I'm just interested in practicalities of how to make my gear perform as I want it.

I am completely disinterested in the detailed discussion that we were having previously. I don't believe it will be disrespectful of me to not answer your further questions in regards to it for the reasons of not knowing much anyway (so not having much to offer) and not caring to learn it better at this time either. Please allow me to disengage 🙏🏻
 
Last edited:
Feb 24, 2022 at 6:55 PM Post #108 of 124
I have my reasons.
I like the discussion, although most goes over my head. Maybe the issue between players is an effect that is getting applied by one software or the other.

A DSP is especially noticeable when playing something like a podcast where added reverb etc is easily noticed. Hopefully such effects could be turned off.

the other testing you can do is bring In another bitperfect source feeding your dac, ie PC and see which one it sounds closest to.
 
Feb 24, 2022 at 7:52 PM Post #109 of 124
Yep, we're like that in this sub-forum; We tend to ignore aspects of resampling which are not actually aspects of resampling! For example:


What "in and out clocks"?
An ASRC, by its nature, has a clock going in, in this case 44.1kHz word/frame clock and the associated Bit clock, and the outgoing clock, at 48kHz and the different Bit clock
No they won't, they'll have the same clock.
If an ASYNCHROUS sample rate converter has the same clocks, it is not converting anything. A SYNCHROUS sample rate converter is converting multiples of teh same clock, like 48kHz to 96kHz, then is can work from the same master clock, and derive the bit clocks, but this is not what we are talking about. ASRC: Its entire purpose is to change to the different clock speed.
There is no different in and out clocks, there's only one clock. So, what jitter is there between one clock and why does it need to be compensated for? Reminds me of a bad old joke: What's the difference between a duck? Answer: One leg is both the same.
See above
1. Not sophisticated asynchronous sample rate converter! They may have been relatively sophisticated about 30 ago but these days they're completely standard and relatively basic/simple.
2. ~30 years ago when they were first released, they cost about $20 but today (and for many years) they cost peanuts, in fact they cost less than a packet of peanuts!
Show me where they are peanuts for a stand alone ASRC:

https://www.digikey.com/en/products...EKikjKy8iBO0CBiACYCALTwngGpIHa8AJ7cuALo2CjZQA

Cheapest is $8. I buy in bulk so i can get around $2

Cheapest standalone DSP I know which has built in ASRC is $2.83 in tens of thousands quanitity. I use them daily.

2a. Again, 30 year old ASRCs probably weren't very power efficient but then they didn't need to be, there were no smartphones in the early 1990's!

It's true that jitter is turned directly into distortion, so where is all this distortion then? The earliest ASRC chip I'm aware of is the AD1890 from 1993: "Note that all distortion components are less than -115dB" - So, completely inaudible even then! (Analog Devices catalogue - AD1890 explantation and measurements)
That is without jitter. The datasheet says -102dB THD at 1kHz, but this is just the arithmetic errors. The datasheet also says a loss of 1dB of degradation at 10nS jitter. Still fine, but the new ones do better.
1. I haven't seen such information either and I'd be willing to change my position given reliable evidence to the contrary but until then, it's more than reasonable to assume that it performs as well or better than a 1st generation, 20bit ASRC from 1993!
2. I'd take that bet! Because you can bet that they are designed for BOTH battery conservation AND time domain resolution.

Again, a modern Snapdragon is hundreds of times more powerful than processors in 1993, plus the SRC algorithms are more efficient. High quality sample rate conversion simply isn't that demanding and hasn't been an issue for years.
It is. However they don't care very much. How do I know? A world class DSP engineer I have know for 30 years worked at CSR when tehy were bought by Qualcomm. I trust him over someone who has to be right all the time on the internet.

Here's a different example of a major corporation doing audio: Apple's so called lossless Airplay & Airplay 2 skips samples. Why, because they couldn't be bothered to get it right. That is from a a VERY knowledgable source.
J
 
Feb 25, 2022 at 11:45 AM Post #110 of 124
Clocking and related digital signal processing are specialist fields, in which I don't profess to have expertise. So I'm open to modifying my layman's understanding given reliable evidence. According to my (current) understanding:
If an ASYNCHROUS sample rate converter has the same clocks, it is not converting anything.
Why can't we convert the sample rate with the same clock? For example, let's say we have an input sample rate of 48kHz and an output sample rate of 44.1kHz. We get a clock that oscillates at 7,056kHz (or from which we can derive 7,056kHz) then divide that by 147 to get the 48kHz sample rate and by 160 to get the 44.1kHz sample rate. Same clock, two different sample rates. This is just an illustrative example of course, even old clocks operate at far higher frequencies.
A SYNCHROUS sample rate converter is converting multiples of teh same clock, like 48kHz to 96kHz, then is can work from the same master clock, and derive the bit clocks, but this is not what we are talking about. ASRC: Its entire purpose is to change to the different clock speed.
But the purpose is not to change to a different clock speed, we want the clock to be the same speed, the purpose is to change the number of samples per (the same) second.
Cheapest standalone DSP I know which has built in ASRC is $2.83 in tens of thousands quanitity. I use them daily.
Firstly, we're not talking about a standalone chip but a SOC and more importantly, we're not talking about hardware SRC but software SRC (Android). So most of the above is irrelevant anyway, because there is no clock, there's just data and processing, time is irrelevant.
However they don't care very much. How do I know? A world class DSP engineer I have know for 30 years worked at CSR when tehy were bought by Qualcomm. I trust him over someone who has to be right all the time on the internet.
That's just an "appeal to authority", an unacceptable fallacy in this sub-forum. Likewise, your relative level of trust between me and your friend is both unimportant to me personally and again, irrelevant in this subforum.

Again, unless you have some reliable evidence to the contrary, there's no reason to assume that Android can't do SRC as well as a PC could easily do 20 years ago.

G
 
Feb 25, 2022 at 7:27 PM Post #112 of 124
I’ve always wondered why audio folks go to the mat over things that can’t be heard in normal use. It’s as prevalent in science circles as it is among subjectivists. I guess it’s a human instinct to double down just to be safe… but people do it over and over all the way down the rabbit hole.
 
Feb 25, 2022 at 11:26 PM Post #113 of 124
Clocking and related digital signal processing are specialist fields, in which I don't profess to have expertise. So I'm open to modifying my layman's understanding given reliable evidence. According to my (current) understanding:

Why can't we convert the sample rate with the same clock? For example, let's say we have an input sample rate of 48kHz and an output sample rate of 44.1kHz. We get a clock that oscillates at 7,056kHz (or from which we can derive 7,056kHz) then divide that by 147 to get the 48kHz sample rate and by 160 to get the 44.1kHz sample rate. Same clock, two different sample rates. This is just an illustrative example of course, even old clocks operate at far higher frequencies.
You are also forgetting: There is latency, so the jitter affects different samples.
But the purpose is not to change to a different clock speed, we want the clock to be the same speed, the purpose is to change the number of samples per (the same) second.

Firstly, we're not talking about a standalone chip but a SOC and more importantly, we're not talking about hardware SRC but software SRC (Android). So most of the above is irrelevant anyway, because there is no clock, there's just data and processing, time is irrelevant.

That's just an "appeal to authority", an unacceptable fallacy in this sub-forum. Likewise, your relative level of trust between me and your friend is both unimportant to me personally and again, irrelevant in this subforum.

Again, unless you have some reliable evidence to the contrary, there's no reason to assume that Android can't do SRC as well as a PC could easily do 20 years ago.

G
There is no reason to assume they have done the job properly. There are multiple citations that they haven't, and like you I want proof. Having worked with Qualcomm, and measured in detail their attempts at audio (have you seen what they do to AAC? 14kHz brickwall bandwidth in many cases. Definately not transparent.) I side with them not being able to do a good job, or being bothered.
 
Feb 26, 2022 at 7:35 AM Post #114 of 124
I’ve always wondered why audio folks go to the mat over things that can’t be heard in normal use. It’s as prevalent in science circles as it is among subjectivists.
There's two serious issues with this assertion:
Firstly, it's false. Or rather it was false. SRC artefacts could be heard in normal use and it's because of science that it isn't (or shouldn't) be audible today.
Secondly, what is "normal use" and who gets to define it? For example, the digital audio to which you're listening could have anything from just 2 sample rate conversions up to dozens. So we have to consider the possibility of cumulative SRC artefacts being audible, not just of a single SRC process being inaudible. Science has to account for all of this, not just what you personally believe "normal use" to be.
You are also forgetting: There is latency, so the jitter affects different samples.
I'm not forgetting latency but maybe you're forgetting that latency doesn't affect jitter? Latency is the period of time required for (SRC) processing, which can be up to 30ms or so. However, that (say) 30ms processing delay is applied to all the samples, so there is no added jitter.
There is no reason to assume they have done the job properly.
Yes, there is. SRC is a common, widely used process that's accomplished transparently as standard by everyone else with modern processors and even free off-the-shelf algorithms/libraries. The freely available MatLab resampler code for example has artefacts down at around the -170dB level! So, it's not so much about having "done the job properly", they'd pretty much have to deliberately screw it up to get audible artefacts. But again, my understanding does not go deep enough to be absolutely certain.
[1] There are multiple citations that they haven't, and [2] like you I want proof.
1. There are also multiple citations that silver cables sound brighter than copper cables, doesn't make it true though. There are numerous similar examples, which is why anecdotal evidence is considered amongst the very least reliable types of evidence. Even if the anecdotal evidence is correct, we still have to ask "when?". The probability of Android not performing audibly transparent SRC is far higher in early devices and early versions of Android.
2. Even if there is proof, it might not tell us very much. Android provides built-in default options for SRC but AFAIK, OEMs can override/replace that and provide their own SRC code. So proof that one model of smartphone running Android does or doesn't perform SRC transparently doesn't necessarily tell us if other models do. I suspect this is one of the reasons why we don't see any proof.
Having worked with Qualcomm, and measured in detail their attempts at audio (have you seen what they do to AAC? 14kHz brickwall bandwidth in many cases. Definately not transparent.) I side with them not being able to do a good job, or being bothered.
But the AAC format is supposed to have a low pass filter set at about 14kHz (below a certain bit rate). Additionally, as I'm sure you know, Android is developed by a consortium of dozens of companies. So how do you know that it was Qualcomm who developed the SRC code in Android? Even if it was Qualcomm AND they screwed it up big time, how is it that none of the other companies in the consortium noticed or did anything about it?

G
 
Feb 26, 2022 at 1:08 PM Post #115 of 124
Normal use is listening to music in the home.

Science is great. Don't get me wrong. It's just that people sometimes think that crossing every t and dotting every i when it comes to numbers on a sheet of paper is life or death for the purposes of listening to music for pleasure. They'll worry about numbers they can't hear just to be safe. They spend more energy thinking up rare exceptions to the rule than just following it.
 
Last edited:
Feb 27, 2022 at 5:01 AM Post #116 of 124
It's just that people sometimes think that crossing every t and dotting every i when it comes to numbers on a sheet of paper is life or death for the purposes of listening to music for pleasure. They'll worry about numbers they can't hear just to be safe.
Again, ALL of that is false (or can be false), because you don't get to define "normal use" for the whole of science. Even your assertion about "life or death" is false, it CAN be a matter of life or death because most of the digital signal processes used to record and reproduce "music for pleasure" are not designed specifically for "music for pleasure", they're designed for digital audio in general or for other A-D-A applications. For example, a wearable heart monitor can be a matter of life or death and medical scans/images certainly can.

Even considering only your personal definition, what you assert is still false: For example, can you hear SRC artefacts down at say -90dB in your "normal use"? No, from what I know of your normal use, that's a long way from being audible and it's probably inaudible all the way up to the most extreme music listening scenario achievable. However, what happens if we apply say 20 or more SRC operations? Those cumulative SRC artefacts could now be audible, even to you. And before you say: "but I don't perform 20 or more SRC operations" - if your "normal use" includes reproducing commercial music releases made in the last 15 years or so, there's a good chance that 20 or more SRC operations have already been applied to those recordings before you even try to reproduce them. You still won't be able to hear those SRC artefacts though but ONLY because every "t" has been crossed, every "i" has been dotted and the artefacts are now so far beyond inaudible that they're still inaudible when applied numerous times.

20 years or so ago, we had to be careful of the number and type of SRC operations we performed when producing and mastering music and this type of fact is typically abused by audiophiles/marketers: Take something that in the past could be an audible issue, fail to mention that it was solved years ago, and provide a now unnecessary solution. Jitter is another typical example of this type.
They spend more energy thinking up rare exceptions to the rule than just following it.
Of course they do, that's largely what science is! Didn't you know that? For example, the science of physics (inc. Sound and audio) is based on theories and laws; "rules" that are true within a set of conditions. Finding an exception within those conditions invalidates that "rule", it's what stops a hypothesis becoming a theory or proves that an existing theory is wrong (or at least incomplete) and of course vice versa; the lack of an exception is what allows a hypothesis to become a theory.

G
 
Last edited:
Mar 1, 2022 at 3:39 AM Post #117 of 124
I'm not defining normal use for all of science. I'm defining normal use for home audio. I buy stereo equipment to listen to my music in my living room or on the go played on my phone. I don't need laboratory quality, and I would venture to say that the vast majority of the rest of this forum is the same as me. You are an exception because you don't have a full system at home because you have a professional one at work. That is an exception.

We're in a forum here full of people who are hobbyists, not professionals. If you consider our audience, you'll understand what I'm saying better.

In this post you understand...
https://www.head-fi.org/threads/how-does-unison-usb-produce-better-sound.938228/page-5#post-16839558
 
Last edited:
Mar 1, 2022 at 7:46 AM Post #118 of 124
I'm not defining normal use for all of science.
Yes you are in a Science forum if you reference "people" in general and even more so if you specifically reference science! (quote: "It’s as prevalent in science circles as it is among subjectivists.")
I'm defining normal use for home audio.
No you're not, because ....
I buy stereo equipment to listen to my music in my living room or on the go played on my phone. I don't need laboratory quality, and I would venture to say that the vast majority of the rest of this forum is the same as me.
As already explained; "laboratory quality" is required because without it the multiple SRC processes on some/many of the recordings you probably play in your living room would have audible artefacts and "I would venture to say that the vast majority of the rest of this forum" would also be able to hear them!
You are an exception because you don't have a full system at home because you have a professional one at work. That is an exception.
No, I'm not an exception in this case, because: Firstly, I have had various consumer systems at home over the years and Secondly, you wouldn't need a professional system to hear the artefacts of cumulative multiple SRC processes performed by an SRC that was only just inaudible, it could/would be audible in normal home use.
We're in a forum here full of people who are hobbyists, not professionals. If you consider our audience, you'll understand what I'm saying better.
I do consider the audience of hobbyists (and the general public), that's what I do for a living!
And in this thread too. Clearly you don't know the difference between a hardware DAC and a software SRC process or the difference in their application?

G
 
Mar 1, 2022 at 9:04 AM Post #119 of 124
This is a home audio forum. I’m not a scientist. Neither are most people on head-Fi. We’re talking about the science behind home audio, but that doesn’t make us scientists. If I talk about how I deal with lower back pain, does that make me a doctor?
 
Last edited:
Mar 1, 2022 at 10:11 AM Post #120 of 124
We’re talking about the science behind home audio, but that doesn’t make us scientists.

No, "we're" not talking about the science behind home audio and that's the problem! I'm talking about that but you're talking about something entirely different: What you think is important, based on an apparent lack of understanding of how SRC is employed.

The nonsense about not being a scientist is just a red herring to deflect from that fact, something you're highly intolerant of when others do it to you!

G
 

Users who are viewing this thread

Back
Top