serko70
Member
More
- Preamp, Processor or Receiver
- Marantz SR6015
- Main Amp
- Rotel Michi X3
- DAC
- Oppo 205
- Computer Audio
- Intel NUC
- Universal / Blu-ray / CD Player
- Oppo 205
- Streaming Subscriptions
- TIDAL, ROON
- Front Speakers
- Focal Kanta 2
- Center Channel Speaker
- Linn Trikan
- Surround Speakers
- Focal Dome Flax
- Surround Back Speakers
- Focal Dome Flax
- Front Height Speakers
- Focal Dome Flax
- Rear Height Speakers
- Focal Dome Flax
- Subwoofers
- Focal Sub Air
- Video Display Device
- LG 65 3D OLED
Dear John,
Fetched Base64 frequency response (/frequency-response?smoothing=1%2F48&ppo=96) returns 1537 data values (6148 bytes) with 96 ppo and 1/48 smoothing (defaults to that when you use ppo) vs "Export as txt" with same settings returns 1536 values for a REW generated filter response. The startFreq is slightly different but not that different, 1536 frequencies still end just below 24kHz (23,827.34Hz vs 23,833.09Hz). Is this a floating point precision problem on my end? If not, what frequency the extra 1 data point is representing? 24,000 or 0?
Fetched Base64 frequency response (/frequency-response?smoothing=1%2F48&ppo=96) returns 1537 data values (6148 bytes) with 96 ppo and 1/48 smoothing (defaults to that when you use ppo) vs "Export as txt" with same settings returns 1536 values for a REW generated filter response. The startFreq is slightly different but not that different, 1536 frequencies still end just below 24kHz (23,827.34Hz vs 23,833.09Hz). Is this a floating point precision problem on my end? If not, what frequency the extra 1 data point is representing? 24,000 or 0?
