ASAsense Binary Table (ABT) format - Revision history

Thomas: Marked this version for translation

2026-10-14T10:23:00Z

Marked this version for translation

← Older revision		Revision as of 10:23, 14 October 2026
Line 1:		Line 1:
	<languages/>		<languages/>
	<translate>		<translate>
			<!--T:1-->
	The ASAsense Binary Table (ABT) format is an alternative to the CSV format, but for binary data with fixed row lengths. The structure is as follows:		The ASAsense Binary Table (ABT) format is an alternative to the CSV format, but for binary data with fixed row lengths. The structure is as follows:

			<!--T:2-->
	{\| class="wikitable"		{\| class="wikitable"
	! name		! name
Line 47:		Line 49:
	\|}		\|}

			<!--T:3-->
	The JSON metadata should be an object with the following structure:		The JSON metadata should be an object with the following structure:

			<!--T:4-->
	{\| class="wikitable"		{\| class="wikitable"
	! field		! field
Line 76:		Line 80:
	\|}		\|}

			<!--T:5-->
	A "column definition object" should have the following format:		A "column definition object" should have the following format:

			<!--T:6-->
	{\| class="wikitable"		{\| class="wikitable"
	! field		! field
Line 100:		Line 106:
	\|}		\|}

			<!--T:7-->
	The datatype identifiers can be anything, but the reader should support at least the following:		The datatype identifiers can be anything, but the reader should support at least the following:

			<!--T:8-->
	{\| class="wikitable"		{\| class="wikitable"
	! identifier		! identifier
Line 128:		Line 136:
	\|}		\|}

			<!--T:9-->
	Other, unknown datatype identifiers should be treated by the reader as opaque binary data (bytes).		Other, unknown datatype identifiers should be treated by the reader as opaque binary data (bytes).

	== Common extra metadata fields ==		== Common extra metadata fields == <!--T:10-->

			<!--T:11-->
	In many ABT files used by ASAsense, the following extra metadata fields will be found:		In many ABT files used by ASAsense, the following extra metadata fields will be found:

			<!--T:12-->
	{\| class="wikitable"		{\| class="wikitable"
	! Field name		! Field name
Line 151:		Line 162:
	\|}		\|}

	== CLI tool for ABT handling ==		== CLI tool for ABT handling == <!--T:13-->

			<!--T:14-->
	To make the ABT format easier to use, a few precompiled binaries are available:		To make the ABT format easier to use, a few precompiled binaries are available:
	</translate>		</translate>
Line 160:		Line 172:
	* [http://asasense.com/abt-binaries/abt-cli-win11-x64.zip Windows 11 x64]		* [http://asasense.com/abt-binaries/abt-cli-win11-x64.zip Windows 11 x64]
	<translate>		<translate>
			<!--T:15-->
	The MD5 sums of the ZIP files are as follows:		The MD5 sums of the ZIP files are as follows:
	</translate>		</translate>

Thomas: English source text for translation

2026-10-14T10:23:00Z

English source text for translation

Show changes

Thomas: /* Cli tool for ABT handling */

2025-08-07T09:26:06Z

Cli tool for ABT handling

← Older revision		Revision as of 09:26, 7 August 2025
Line 152:		Line 152:

	* Linux		* Linux
	** [http://asasense.com/abt-binaries/abt-cli-ubuntu-22.04-x86_64.gz Ubuntu 22.04 x86_64]		** [http://asasense.com/abt-binaries/abt-cli-ubuntu-22.04-x86_64.zip Ubuntu 22.04 x86_64]
	** [http://asasense.com/abt-binaries/abt-cli-ubuntu-20.04-x86_64.gz Ubuntu 20.04 x86_64]		** [http://asasense.com/abt-binaries/abt-cli-ubuntu-20.04-x86_64.zip Ubuntu 20.04 x86_64]
	* [http://asasense.com/abt-binaries/abt-win11-x64.zip Windows 11 x64]		* [http://asasense.com/abt-binaries/abt-cli-win11-x64.zip Windows 11 x64]
			The MD5sums of the zipfiles is as follows.
			adcd6a227861bb6b188ef8c5748faae8 abt-cli-ubuntu-20.04-x86_64.zip
			6f4c63cbd7416ead026f170c97b3ab89 abt-cli-ubuntu-22.04-x86_64.zip
			39db54827d2634262d9d666b4262b212 abt-cli-win11-x64.zip

Thomas: /* Cli tool for ABT handling */

2025-08-05T22:55:22Z

Cli tool for ABT handling

← Older revision		Revision as of 22:55, 5 August 2025
Line 150:		Line 150:
	== Cli tool for ABT handling ==		== Cli tool for ABT handling ==
	To ease the use of the ABT format, a few precompiled binaries are available.		To ease the use of the ABT format, a few precompiled binaries are available.

			* Linux
			** [http://asasense.com/abt-binaries/abt-cli-ubuntu-22.04-x86_64.gz Ubuntu 22.04 x86_64]
			** [http://asasense.com/abt-binaries/abt-cli-ubuntu-20.04-x86_64.gz Ubuntu 20.04 x86_64]
			* [http://asasense.com/abt-binaries/abt-win11-x64.zip Windows 11 x64]

Thomas at 22:26, 5 August 2025

2025-08-05T22:26:24Z

← Older revision		Revision as of 22:26, 5 August 2025
Line 123:		Line 123:
	Other, unknown datatype identifiers, should be treated as opaque binary data (bytes) by the reader.		Other, unknown datatype identifiers, should be treated as opaque binary data (bytes) by the reader.

	=== Common Extra Metadata fields ===		== Common Extra Metadata fields ==
	In many ABT files ASAsense uses, the following extra matadata fields will be found		In many ABT files ASAsense uses, the following extra matadata fields will be found
	{\| class="wikitable"		{\| class="wikitable"
Line 147:		Line 147:
	\|		\|
	\|}		\|}

			== Cli tool for ABT handling ==
			To ease the use of the ABT format, a few precompiled binaries are available.

Thomas: /* Common Extra Metadata fields */

2025-08-01T12:40:44Z

Common Extra Metadata fields

← Older revision		Revision as of 12:40, 1 August 2025
Line 137:		Line 137:
	\|Indicates whether the data in the ABT file is sorted by timestamp (column 1)		\|Indicates whether the data in the ABT file is sorted by timestamp (column 1)
	\|-		\|-
	\|		\|frame_width_s
	\|		\|float
	\|		\|NaN
	\|		\|Used to indicate the frame width of one sample (for example the sampling period or spectrogram frame width)
	\|-		\|-
	\|		\|

Thomas at 14:51, 31 July 2025

2025-07-31T14:51:09Z

← Older revision		Revision as of 14:51, 31 July 2025
Line 122:		Line 122:
	\|}		\|}
	Other, unknown datatype identifiers, should be treated as opaque binary data (bytes) by the reader.		Other, unknown datatype identifiers, should be treated as opaque binary data (bytes) by the reader.

			=== Common Extra Metadata fields ===
			In many ABT files ASAsense uses, the following extra matadata fields will be found
			{\| class="wikitable"
			\|+
			!Field name
			!Field type
			!Default value
			!Description
			\|-
			\|sorted_by_timestamp
			\|bool
			\|true
			\|Indicates whether the data in the ABT file is sorted by timestamp (column 1)
			\|-
			\|
			\|
			\|
			\|
			\|-
			\|
			\|
			\|
			\|
			\|}

Thomas at 15:37, 12 May 2025

2025-05-12T15:37:55Z

← Older revision		Revision as of 15:37, 12 May 2025
Line 18:		Line 18:
	\|u32		\|u32
	\|1-u32::max		\|1-u32::max
	\|the amount of ~~headers~~		\|the amount of columns
	\|-		\|-
	\|col_widths		\|col_widths

Thomas at 12:55, 5 February 2025

2025-02-05T12:55:54Z

← Older revision		Revision as of 12:55, 5 February 2025
Line 30:		Line 30:
	\|u32		\|u32
	\|0-u32::max		\|0-u32::max
	\|the length of the metadata field (can be 0 is it needs to be skipped)		\|the length of the metadata field (can be 0 if it needs to be skipped)
	\|-		\|-
	\|metadata		\|metadata

Thomas at 07:37, 5 October 2024

2024-10-05T07:37:10Z

← Older revision		Revision as of 07:37, 5 October 2024
Line 118:		Line 118:
	\|"div" should be replaced by any floating point number. The data is then first interpreted as "numtype" (int, uint or float) and then divided by "div". This is mainly useful for storing decimal numbers in integer fields.		\|"div" should be replaced by any floating point number. The data is then first interpreted as "numtype" (int, uint or float) and then divided by "div". This is mainly useful for storing decimal numbers in integer fields.
	\|-		\|-
	\|unix_timestamp		\|unix_timestamp(numtype/div)
	\|Interprets the data as ~~"uint"~~ , but takes into account that it is a unix_timestamp (offset seconds since the Unix Epoch on January 1st, 1970 at UTC)		\|Interprets the data as specified within brackets (so any numtype, with optional divider), but takes into account that it is a unix_timestamp (offset seconds since the Unix Epoch on January 1st, 1970 at UTC)
	\|}		\|}
	Other, unknown datatype identifiers, should be treated as opaque binary data (bytes) by the reader.		Other, unknown datatype identifiers, should be treated as opaque binary data (bytes) by the reader.