You are not logged in. Your edit will be placed in a queue until it is peer reviewed.
We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.
Required fields*
- $\begingroup$ Thanks for this very thorough answer. It was helpful in several ways already. I'm willing to accept, though still working through stuff. I added some additional info to my question in response to this answer. Not sure if you have thoughts. Thank you! $\endgroup$John Chrysostom– John Chrysostom2021-05-25 15:06:52 +00:00Commented May 25, 2021 at 15:06
- $\begingroup$ Oh... wow. I wonder if that "stuff" leading up to the beginning of the main signal is an audio compression artifact... That would explain so much. $\endgroup$John Chrysostom– John Chrysostom2021-05-25 16:42:58 +00:00Commented May 25, 2021 at 16:42
- $\begingroup$ @John Good that was of some use. I've added a few more notes to my original answer. $\endgroup$telemeister– telemeister2021-05-27 05:12:39 +00:00Commented May 27, 2021 at 5:12
- $\begingroup$ Thanks again! The use case here is measuring distance. Unfortunately, there is unavoidable, randomly varying delay in the audio stack - there's no way to know when sound arrives, even if clocks were synced. So I have both devices play a sound and record. The difference between A hearing A and B hearing A is clock offset + time of flight, the difference between A hearing B and B hearing B is clock offset - ToF. Two equations, two variables, solve for time of flight. I've seen this be highly accurate in certain conditions, so I know the math is right, but echos and reverb often kill it. $\endgroup$John Chrysostom– John Chrysostom2021-05-27 12:30:12 +00:00Commented May 27, 2021 at 12:30
- $\begingroup$ Went ahead and accepted this answer. It didn't magically solve all my problems, but it DID give me a ton of helpful information that's moved my project forward. Thank you. Also, thank you for your kindness in responding helpfully to this question. On many SE sites, I'm afraid this question would have been met with lots of downvoting and complaints that it was "too vague" or "didn't have one right answer." Thanks for the assistance and the warm welcome to somebody who's new to Signal Processing SE! $\endgroup$John Chrysostom– John Chrysostom2021-06-01 12:40:11 +00:00Commented Jun 1, 2021 at 12:40
| Show 1 more comment
How to Edit
- Correct minor typos or mistakes
- Clarify meaning without changing it
- Add related resources or links
- Always respect the author’s intent
- Don’t use edits to reply to the author
How to Format
- create code fences with backticks ` or tildes ~ ```
like so
``` - add language identifier to highlight code ```python
def function(foo):
print(foo)
``` - put returns between paragraphs
- for linebreak add 2 spaces at end
- _italic_ or **bold**
- indent code by 4 spaces
- backtick escapes
`like _so_` - quote by placing > at start of line
- to make links (use https whenever possible) <https://example.com>[example](https://example.com)<a href="https://example.com">example</a>
- MathJax equations
$\sin^2 \theta$
How to Tag
A tag is a keyword or label that categorizes your question with other, similar questions. Choose one or more (up to 5) tags that will help answerers to find and interpret your question.
- complete the sentence: my question is about...
- use tags that describe things or concepts that are essential, not incidental to your question
- favor using existing popular tags
- read the descriptions that appear below the tag
If your question is primarily about a topic for which you can't find a tag:
- combine multiple words into single-words with hyphens (e.g. image-processing), up to a maximum of 35 characters
- creating new tags is a privilege; if you can't yet create a tag you need, then post this question without it, then ask the community to create it for you