Upload a supported measurement export in your Showcase, identify what it measures and record how it was captured. Add the equipment used so readers can interpret the curves and compare frequency-response traces.
Before you start
Save your build, then open Measurements in the Showcase editor. Have the export and its capture settings available. For taking the measurement itself, read How to measure a speaker with REW and a UMIK-1.
Supported exports are .frd, .zma, .csv and .txt, including REW text exports. A REW .mdat project is not a supported chart upload. Export the data to a supported format first. Bassilisk keeps the original uploaded file and parses its data for display.
Steps
Under Equipment used, choose Add equipment. Select saved measurement gear, a part in this build or Unlisted equipment…. Check its role and calibration notes. Reusable gear is managed in measurement gear settings.
Choose Add measurement file and select an export. Give it a Title that distinguishes it from the other files, such as Final on-axis response. Add the Measurement date when known.
Check Type. Choices include Frequency Response, Impedance, Distortion, Impulse Response, Waterfall, Spectrogram and Custom. The file extension supplies an initial choice, and recognised REW text headers can identify impulse or distortion data. Check that the choice matches your file.
Set Measured item to Whole build or Selected parts. For selected parts, choose entries from this build's parts list. Add the parts first if the list is empty. Use Not specified when you have not identified a target.
Record Method and Software for this file. Methods include log sweeps, fixed or moving microphone RTA, near-field, ground-plane, transfer function and impedance sweeps. Choose the method you actually used.
Fill the capture fields shown for that method. Signal records the test signal. Copy FFT length and Averages from the measurement software when those controls appear. Use No averaging when applicable. The averages list also includes fixed counts and Forever, stopped by hand.
Set Export processing to describe processing already in the export. Choices include Raw / no smoothing, fractional-octave smoothing, variable smoothing, psychoacoustic smoothing, unknown and custom. Leave a field blank when you cannot supply it accurately.
Choose Upload measurement. Check that the file appears in the list with the right title, type and measured item. Repeat for other files, order them as intended and use Measurement notes for context shared by the set. Save your remaining build changes.
What happens next
Capture settings belong to each file. An RTA trace and an impedance sweep can therefore retain different methods and settings on the same build. Method selection changes which capture controls are shown; a log sweep does not expose the same fields as an RTA measurement.
Equipment describes what you measured with. The measured item describes what you measured. Adding a microphone to measurement gear does not add it to the bill of materials. Gear names and calibration details are copied into the build's equipment record, so later profile edits do not rewrite that record.
With at least two frequency-response measurements, the public build offers an overlay. Use its trace buttons to show or hide curves for comparison. Display smoothing changes the graph view; export processing records what was already applied to the uploaded data.
Saved measurement changes follow the build's publication review. Uploading a file to your working build does not immediately replace the approved public version.
Common mistakes
- Uploading a project file instead of a supported text export.
- Leaving the initial type unchanged when it does not describe the file.
- Selecting the measurement microphone as the measured item when the curve describes a speaker.
- Copying one file's capture settings onto files taken by a different method.
- Recording the graph's display smoothing as processing already in the export.
Related
Read Publish your build to make the saved measurements public, or Showcase and Build Guide for where the rest of your documentation belongs.