HelixBackupFiles

KO | EN

gitlite — search

#hacktoberfest #react #typescript #llm #android #rust #macos #java #windows #awesome #cli #kubernetes #awesome-list #open-source

HelixBackupFiles

(★ 8)

Parsing Line6 Helix Backup Files

HelixBackupFiles 최신버젼 다운로드

최종 버전 다운로드 (.zip)

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

# HelixBackupFiles
Parsing Line6 Helix Backup Files

The project parses a Line 6 Helix Backup file (*.hxb).

I am using firmware 2.81 but I expect the format of the hxb file hasn't changed much in recent times.

The file starts with a non-compressed header with a proprietary file signature "AF6L" which I'm guessing may stand for for "Line6 Full Archive" (little-endian byte ordering). The header also contains some text including the backup description and names of the set lists and is immediately followed by the first of several zlib sections. The first section contains the global settings. This is followed by a section for each of the IRs and a section for each of the 8 setlists. The sections use the standard zlib Deflate algorithm, and when inflated the global settings and setlist sections are in json, and the IRs are in wav (with "RIFF" signature at the head and embedded metadata for IR name, etc).

Finally there's a non-compressed "footer" section at the end of the file (straight after the last zlib section) that describes the various parts of the archive and provides offsets into the file and the lengths of each section. This info can be used if you want to inflate a particular section rather than process the whole file. The footer contains several sections of 36 bytes. The first 4 bytes of each section describe the data. The sections are "IDXH" (stands for HeliX ??), "CSED" (which stands for DESCription), "MNLS" (Set List NaMes), "BOLG" (GLOBal settings). Then there are sections for each of your IRs ("000I", "100I", "200I", etc, where "I" denotes IR), then a section for each of the 8 setlists - "00LS", "10LS", etc. After the initial 4 bytes of each section there are 8 x 32 bit integers (little-endian). The 1st is the starting offset of the section, the 3rd is the length of the data, the 5th indicates if the data is deflated (1) or not (0), and the 6th is the size of the data once inflated. Note that the address of the footer can be found at offset 0x08 in the file (32-bit unsigned).

I created this in order to extract and analyse preset data. You must be very careful if you decide to modify data and write back to the hxb file! Use at your own risk.

# Instructions

There are 2 versions available as follows:

## Portable

HelixBackupFileConsole.zip - This is a portable release in a zip archive. You must have .NET 7 installed on your system.

1. Download the zip file
2. Unzip it to a new folder.
3. Copy your Helix backup file into the folder.
4. Open a command prompt window.
4. Run HelixBackupFileConsole.exe placing the name of your backup file on the command-line.

## Windows

HelixBackupFileConsole.exe - This is a Windows-only release and does _not_ require NET 7 to be installed.

1. Download the exe file to a new folder.
2. Copy your Helix backup file into the folder.
3. Open a command prompt window.
4. Run HelixBackupFileConsole.exe placing the name of your backup file on the command-line.

The console application will extract all of the presets and IRs from the backup file and place them in a subfolder named "output"

HelixBackupFiles

HelixBackupFiles 최신버젼 다운로드

오늘의 추천 프로젝트

Was this content helpful?

Recent Feedback

HelixBackupFiles

HelixBackupFiles 최신버젼 다운로드

오늘의 추천 프로젝트

Was this content helpful?

Recent Feedback

Download README