Search Results
| Search type | Search syntax |
|---|---|
| Tags | [tag] |
| Exact | "words here" |
| Author |
user:1234 user:me (yours) |
| Score |
score:3 (3+) score:0 (none) |
| Answers |
answers:3 (3+) answers:0 (none) isaccepted:yes hasaccepted:no inquestion:1234 |
| Views | views:250 |
| Code | code:"if (foo != bar)" |
| Sections |
title:apples body:"apples oranges" |
| URL | url:"*.example.com" |
| Saves | in:saves |
| Status |
closed:yes duplicate:no migrated:no wiki:no |
| Types |
is:question is:answer |
| Exclude |
-[tag] -apples |
| For more details on advanced search visit our help page | |
Results tagged with amplitude
Search options questions only
not deleted
user 66622
6
votes
2
answers
440
views
What causes the mismatch between a calculated sine wave and a measured sine wave?
In Audacity, I generated a 700 Hz sine wave for 1 second, at amplitude 0.4. The bit rate is only 8000 samples per second. … expected to see when I opened the file:
$v(n)=aM \sin\left({\dfrac{n\pi f_\mathrm{data}}{f_\mathrm{Nyquist}}}\right)$
$v(n)$ is the value of the sample written out as a 16-bit signed integer
$a$ is the amplitude …
- 149