JSON Datafile Definitions
Speakerbench does not save any data server side, instead data is handled in your browser and stored in a format named JSON. This section documents the content of the JSON containers for each application in Speakerbench. A normal user will not need to know. This documentaiton is for other applications and their programmers, who wish to exchange data with Speakerbench.
Measurements Collected JSON file format
Measurement data contains added masses m1 and m2 and frequency, magnitude and phase data for a total of three impedance measurements named z0, z1 and z2. All JSON data can be on a single line, or by choice on multiple lines. Here is a structured view of the content of such a JSON file (actual data are just for the example). The file name is by convention a Z_something.json.
{
"comments": "Write_something_here",
"volt": 0.242,
"m1": 8.017,
"m2": 16.048,
"z0": [
[10.0,7.1179,25.2241],
[10.199,7.1646,25.5729],
...
[19999.564,27.1911,48.1313],
[20000.0,27.1868,48.1256]
],
"z1": [
[10.0,7.1929,25.7824],
[10.199,7.2537,26.1631],
...
[19999.564,27.1904,48.1484],
[20000.0,27.1923,48.1576]
],
"z2": [
[10.0,7.3166,26.3593],
[10.2,7.3756,26.7591],
...
[19999.56,27.1579,48.1346],
[20000.0,27.1644,48.133]
]
}
Note: The frequency points for all three measurements must be the same.
Specifying a user comment is optional, but please consider inserting the name of the test object here; otherwise you may not have any way to identify the test object at a later time.
Specifying the applied voltage during measurements is optional, but it is nice (convenient) to register. Not all voltage levels will give you a good fit. Later you may compare fit results from measurements at different voltages.
All JSON files are ‘escaped’ such that a space (in the comment section) is replaced by an underscore.
Fitted Data JSON file format
The fitted data contains only the information identified by the fitting procedure plus the information you typed into the comment sections. All JSON data can be on a single line, or by choice on multiple lines. Here is a structured view of the content of such a JSON file (actual data are from the L16RNX just for the example). The file name is by convention an ADV_something.json.
{
"comments": "Sample_data_for_SEAS_woofer",
"volt": "0.242",
"git": "76ff186",
"date": "21/02/2020",
"re": 5.7212,
"leb": 0.1258,
"l3": 0.5255,
"le": 1.1774,
"rss": 562.405,
"ke": 0.0386,
"bl": 7.0089,
"mms": 14.8959,
"r0": 1.714,
"rms": 2.1101,
"c0": 0.7849,
"cms": 0.8403,
"beta": 0.1034,
"f0": 45.7839,
"fs": 44.985,
"error": "0.4251",
"score": "EXCELLENT"
}
String on the left side are keywords. All letters must be lower-case.
The ‘git’ hashtag is determined by the version of Speakerbench that was used for the fitting procedure and although you can write whatever here, please keep it unchanged. If you manipulate the file, please change the hashtag to zero (‘0’).
All JSON files are ‘escaped’ such that a space (in the comment section) is replaced by an underscore.
Datasheet JSON file format
The complete datasheet file contains all information necessary to describe a driver for Speakerbench simulations. All JSON data can be on a single line, or by choice on multiple lines. Here is a structured view of the content of such a JSON file (actual data are from the L16RNX just for the example). The file name is by convention a SBD_something.json.
{
"manufacturer": "SEAS_Fabrikker_AS",
"brand": "SEAS",
"model": "H1488-08_(L16RNX)",
"provider": "Claus_Futtrup",
"date": "14/03/2020",
"comments": "",
"volt": "0.24227",
"git": "f198998",
"re": "5.72125",
"leb": "0.125781",
"rss": "562.405",
"ke": "0.0386331",
"le": "1.17742",
"bl": "7.00892",
"mms": "14.8959",
"c0": "0.784866",
"r0": "1.71396",
"f0": "45.7839",
"beta": "0.10336",
"lambda": "0.57126",
"sd": "103.869",
"dd": "115.0",
"cms": "0.840309",
"rms": "2.11006",
"l3": "0.525458",
"qms": "1.99535",
"qes": "0.490346",
"qts": "0.393617",
"fs": "44.985",
"vas": "12.8604",
"temp": "21.0",
"pres": "1013.25",
"ah": "30.0",
"cs": "344.299",
"rho": "1.19667",
"xmax": "6.0",
"error": "0.425136",
"score": "EXCELLENT"
}
The ‘sd’ input is required and must be entered by the user. Brand and Model are also required and must be entered by the user, conveniently stored at the beginning of the file so that you can open a SBD file in a text editor and identify the test object. The listed temp, pres and ah (air temperature, air pressure and relative air humidity) are defaults but you can change this to reflect your actual measurement conditions.
Some inputs are optional, for example xmax is optional (set xmax = 0.0 if the information is not available). Specifying xmax adds additional functionality to Speakerbench. See below description for the Thiele/Small Datasheet for details. In the SBD-file all numbers are stored as strings.
The error value and the score are provided by the fit process and they are optional. Set error = 0.0 if the information is not available and score can be an empty string: “”.
Note the distinction between manufacturer and brand. For example brand name SB Acoustics are manufactured by Sinar Baja Electric Co. Ltd. Some brands have several manufacturing sites.
All JSON files are ‘escaped’ such that a space is replaced by an underscore.
Box Tuning JSON file format
Speakerbench allows you to download your box tuning parameters into a TUNE file and upload a TUNE file to configure the box simulator with saved settings. All JSON data can be on a single line, or by choice on multiple lines. Here is a structured view of the content of such a JSON file (actual data are just for the example). The file name is by convention a TUNE_something.json.
{
"eg": 2.83,
"fp": "43.1856",
"vb": "8.302388637830859",
"dp": 2,
"qp": "50.0",
"qa": "100.0",
"ql": "100.0",
"delta": "1.0",
"port": "classic",
"mybox": "Beranek",
"gain": 0,
"fmax": 10000,
"nfreq": 256,
"time": false,
"lxlz": 1,
"lylz": 1,
"ydrv": 0.5,
"yprt": 0.2
"filt": false,
"ls": "0",
"rs": "0",
"cp": 8.2,
"rcp": 12,
"tname": null
}
Thiele/Small Datasheet JSON file format
Speakerbench can work with standard Thiele/Small datasheets. The key is to set the ‘comments’ section to either ‘ts1’ or ‘ts2’ which implies there are two methods supported by Speakerbench. The first method is to accept the Q-values and other Thiele/Small parameters as input and calculate the mechanical parameters. The second method is to accept the mechanical parameters (Cms, Mms, Rms and so on) and calculate the Q-values, etc. The file contains the same keywords as a standard datasheet (see previous section) and the file name is unchanged; SBD_something.json. Here is a structured view of the content of such a JSON file, with comments (which should obviously not be typed into the JSON file).
{
"manufacturer": "", - optional
"brand": "Brand", - required
"model": "Model", - required
"provider": "Your_Name", - optional
"date": "", - optional, format: DD/MM/YYYY (consider at least a 'year' specification here, for some revision control)
"comments": "ts2", - ts1 or ts2 activates Thiele/Small simulations, as explained above
"volt": "", - optional, this is the voltage used for measuring the data (might be unknown)
"git": "0", - set to 0 when datasheet is not created by Speakerbench itself (through measurements, upload and fitting data)
"re": "3.1", - required in both cases (ts1 or ts2)
"leb": "0.0", - set to 0 when not using advanced parameters ... or set = l3 inductor, any value here is overwritten when activating ts1 or ts2
"rss": "0.0", - set to 0 when not using advanced parameters ... any value is overwritten
"ke": "0.0", - set to 0 when not using advanced parameters
"le": "0.0", - set to 0 when not using advanced parameters
"bl": "5.4", - required in both cases (ts1 or ts2)
"mms": "12.3", - required for ts2 (for ts1 this value is calculated, any value here is overwritten)
"c0": "0.0", - set to 0 when not using advanced parameters ... or set = cms, any value here is overwritten (by cms)
"r0": "0.0", - set to 0 when not using advanced parameters ... or set = rms, any value here is overwritten (by rms)
"f0": "0.0", - set to 0 when not using advanced parameters ... or set = fs, any value here is overwritten (by fs)
"beta": "0.0", - set to 0 when not using advanced parameters
"lambda": "0.0", - this field is calculated based on beta, any value here is overwritten
"sd": "104.0", - required in both cases (ts1 or ts2)
"dd": "0.0", - this field is calculated when sd is specified (push the APPLY button after data import)
"cms": "1.3", - required for ts2 (for ts1 this value is calculated, any value here is overwritten)
"rms": "1.54", - required for ts2 (for ts1 this value is calculated, any value here is overwritten)
"l3": "0.32", - required but can be zero - it is the classical voice coil inductance, Le, identified at the +3 dB point
"qms": "2.18357", - required for ts1 (for ts2 this value is calculated, any value here is overwritten)
"qes": "0.357488", - required for ts1 (for ts2 this value is calculated, any value here is overwritten)
"qts": "0.307195", - required for ts1 (for ts2 this value is calculated, any value here is overwritten)
"fs": "36.4074", - required for ts1
"vas": "0.0", - required for ts1 (for ts2 this value is calculated, any value here is overwritten)
"temp": "20.0", - required, this is ambient temperature for the input data and calculations
"pres": "1013.25", - required, this is air pressure for the input data and calculations
"ah": "30.0", - required, this is relative air humidity for the input data and calculations
"cs": "343.684", - required, this is the speed of sound for the input data and calculations
"rho": "1.20095", - required, this is the density of air for the input data and calculations
"xmax": "6.0", - optional
"error": "0", - optional, set to 0 when not using advanced parameters
"score": ""} - optional, set to "" (empty string) when not using advanced parameters
}
All JSON files are ‘escaped’ such that a space is replaced by an underscore.
An online internet database at Loudspeakerdatabase.com by Cristian Pop provides access to more than 4000 Thiele/Small datasheets and lets you download a JSON file for Speakerbench in the above mentioned format, which you can import directly into the Datasheet Creator app.