Skip to content

Releases: QuantAsylum/QA401

Release 1.913

24 Jun 02:02
1ab5ab9
Compare
Choose a tag to compare
Release 1.913 Pre-release
Pre-release

Release 1.913 (June 2020)

  • Restored RMS button (got lost in yesterday's release)
  • Changed N+D measurement window so that bandwith is clamped at 0.9 * fundamental frequency. This means N+D bandwidth now reduces as measured frequency drops below about 225 Hz. Thus, at 300 Hz, you'll see the RMS bandwidth will be computed in the region +/- 200 Hz from the 300 Hz fundamental (thus, 100 to 500 Hz will not be considered). However, the 2H was correctly picked up even with the old algorithm. At 100 Hz, the window will be +/- 90 Hz, which means the region from 10 Hz to 190 Hz will be excluded from the noise calc (in practice, 20 Hz is the lower bound unless the user has specified otherwise). But this ensures the 2H will be correctly measured with a fundamental of 100 Hz. Note that as frequencies get lower and FFT sizes get smaller, the uncertainty will grow. It's important to manually sanity check measurements when using very low frequencies.
  • Inverted time domain display for input. This means that external signals with positive going slope will display correctly, but generated
    signals will display as inverted even though they are still being generated with the same phase. This might go back to 1.912 behavior based on feedback. Generally, this doesn't mean anything to the measurements you are making--everything measures the same. But it does correct the polarity you see for externally applied signals when in the time domain. See issue here: #2

Release 1.912

22 Jun 18:05
1ab5ab9
Compare
Choose a tag to compare
Release 1.912 Pre-release
Pre-release

Release 1.912 (June 2020)

  • Enabled phase on AMP FreqResponseChirp. This used a centered-IR approach to display the phase, but in environments with lots of delay you may still see errant results.
  • Added autodoc generation. This has touched every plugin, so be on the lookout for changed behavior. Some field names have changed to unify them across plugins, and as a result you might see a one-time error on the first time a plugin is used. The autodoc allows the plugin documentation to be updated by running the QA401 application with a -h command line option. This will emit a *.md file in the QA401 data directory. That file has been placed in the wiki located here
  • Plugin menu has a option at the bottom to go directly to the wiki so you can readily reference field names.
  • Added ability to re-run last plugin via F3 key. This should save a bit of time navigating menus when building graphs with many traces.
  • removed a change introduced a few months back where user state was preserved across plugin use. For example, if the main screen had 0dB of input offset, and you ran a plugin that had -6 dB of input offset, the plugin offset didn't persist. But this was causing problems with errant state. And it's not clear what is really the expected/preferred way here. So, for now, the ability to preserve state across plugin runs has been removed.
  • The state issue above has hopefully fixed the need to press buttons twice sometimes. A lot of logic was cleaned up.
  • There is now the ability to export a chirp WAV. This is for an upcoming feature where you'll be able to play a chirp wav from a DAC and capture it in the analyzer. This will allow measuring devices that don't have an analog input once it is ready.

Release 1.909

02 Jun 22:50
1ab5ab9
Compare
Choose a tag to compare

** Release 1.909 **

This is a bit of a rushed release as DigiCert has finished the cert issuance. But a lot has changed on the build machine and so some things might be missing and/or not working. Over the next few days that will get tightend up. If you don't need the new features, please install 1.907.

  • Fixed a bug related to PC Mirror settings not getting applied, ensured plug-in freq settings were getting rounded to nearest bin, and cleaned up code used for PC Mirroring and consolidated PC Mirror delay logic.
  • Darken marker color for Dark-On-Light color scheme
  • Added ability to import WAV file. WAV must be stereo, 24b int or 32b (float)
  • Changed WAV audition so that gain is now effectively 2X previous value. This is to better align with WAV import. If you have been using WAV audition, expect playback to now be twice as loud. WAV audition also picked up 32b (float) support
  • Output cal data was not being applied correctly.

The API for loading the WAV file appears as follows. Note you Import the WAV (stereo, 24b int or 32b single at the current sample rate) and after you've imported it you can then do whatever operations you wish (THD, SNR, etc).

image

From the GUI, the Import Data menu has been expanded and you can now import a wav from that menu item for analysis.

image

For the stepped improvements, the comparison between stepped and chirped is shown below. The matching improvements here have largely come from forcing the points submitted by the plug-ins to the center of each frequency bin.

image

(Edited 3-Jun-2020 to correct trace name in image)

Release 1.908

13 May 23:05
1ab5ab9
Compare
Choose a tag to compare
Release 1.908 Pre-release
Pre-release

Release 1.908 (May 2020)

IMPORTANT: This release is not signed. The build machine is being re-built after an upgrade, and the folks at DigiCert cannot re-issue the cert until the end of May due internal issues as they migrate Thawte certs over to DigiCert.

1.908

  • Averaging indicator will now show X of Y in upper left. If averaging is off, the '---' will be shown. This allows you to see when the specified number of averages has been met.
  • Added ability for Tractor to remotely set the traces that are being tested.

Release 1.907

01 Apr 23:09
1ab5ab9
Compare
Choose a tag to compare

Release 1.907 (March 2020)

  • Added half-octave step interval in Gen settings
  • Fixed bug where PC audio mirror wasn't correctly following QA401 sample rate settings.
  • Changes to THD versus Level plugin (see https://forum.quantasylum.com/t/plugin-requests-modifications/58/3)
  • Added tips dlg. This will explain scrolling when you first start the app. If you want to restore tips, just delete the file in the QA401 data directory

Release 1.906

12 Mar 23:35
1ab5ab9
Compare
Choose a tag to compare

Release 1.906 (March 2020)

  • Fixed bug where activating user weighting while running would cause unhandled exception
  • When FFT size is too small for selected chirp, a warning message will appear on screen and nothing will be displayed. Previously, if the FFT size was too small, the generated signal more closely resembled an impulse. This ensures you are still operation in a region that makes sense. Also, if the FFT size was too small, then strange artifacts could appear at upper frequencies
  • Display trace width increased to improve legibility
  • Changed FR window on chirp IR from rect to halfhann.
  • Rub and buzz plug-in adapted so that it can run stereo concurrently (versus sequentially). This is for IEM test.
  • Added ability to snapshot left trace data via "L" key press, and right channel with "R" key press. These are toggles.
  • Added HEAD Impedance plug-in. This requires QA490 hardware (which isn't shipping yet, but if you work for a company that is shipping headphones and would like to eval, contact sales). But it's a very fast way of making an impedance measurement on headphones from 4 to >600 ohms:

image

Release 1.905

26 Feb 20:57
1ab5ab9
Compare
Choose a tag to compare
Release 1.905 Pre-release
Pre-release

Release 1.905 (Feb 2020)

  • Removed ComputePowerDb() and ComputePeakPowerDb() API calls. These should be replaced with ComputeRmsDb() and GetPeakDb() calls. This moves closer to future API change that resembles QA401H approach where data is left on the application and maths (SNR, THD) are computed in place VERSUS the old way where all data was pulled to the remote app and then pushed back to the QA401 app for processing.
  • Fixed bug in "PWR THD versus Power" related to deprecated APIs. The bug was that incorrect power levels were shown when attenuator was engaged.
  • Fixed bug where User Weighting indicated it was applied, but it wasn't.

Release 1.904

24 Feb 18:40
1ab5ab9
Compare
Choose a tag to compare
Release 1.904 Pre-release
Pre-release

Release 1.904 (February 2020)

  • Changes to speaker compression plugin. This includes distance calculation
  • Min FFT moved to 1k. This helps with peak testing for speakers
  • Changes for Tractor version 0.994.
  • Fixed bug that failed to load user weighting via option menu (Thanks TJ)
  • Improvements to Wow and Flutter plugin (thanks DS)
  • Updates to user manual

Release 1.901

14 Feb 01:06
1ab5ab9
Compare
Choose a tag to compare
Release 1.901 Pre-release
Pre-release

Release 1.901 (February 2020)

  • Fixed SigGen1 settings dlg so it correctly reparses 0.1 mHz (millihertz)
  • Added ability to completely turn off filtering on sweeps to better characterize super deep and narrow notches
  • Updated splash to include year in copyright
  • Added ability to specify a distance on SPRK ChirpCompression plugin. Distance must be 1-10m. Amplitude will be adjusted assuming 6dB/doubling fall off from 1m
  • cleaned up details on status display for FR (eg 0 mS reported as "none" and FR gen level now shown)

Release 1.900

12 Feb 00:08
1ab5ab9
Compare
Choose a tag to compare
Release 1.900 Pre-release
Pre-release

Release 1.900 (February 2020)

  • Overlay data will not dissappear as easily when settings are changed.
  • Output Z calc gets a close button (X in upper right)
  • Restored ability to add/edit title
  • Restored ability to delete all markers
  • Added option indicator on SNR button
  • Updated NAudio to version 1.10
  • Settings will be restored when Tests have completed. That is, if you are at 1 kHz for Gen1, and you run stepped tests that end at 20K, when you run again the generator will be back at 1 kHz
  • RemotingGetPeak and other level APIs now takes remotely-assigned user offsets into account
  • Changed capitalization of some remote interface names. This should be obvious when trying to link against.
  • Updated RemotingTest zip in API directory to take into account offsets that can be applied
  • Remoting GetTimeData will now adjust returned values based on atten settings
  • Fixed (hopefully) bug where exports weren't always in CultureInvariant. This caused problems for DE/FR/etc users
  • Test plugins (DLLs) have had a lot of changes to better align with Tractor. Please use caution when making measurements with Analyzer Input Gains specified in the various plugins and double check the answer makes sense.