JUKEBOX.SI - Revision history

MattKC: Reverted edit by PawPatroler (2025) (talk) to last revision by DmitriLeon2000

2026-03-06T05:49:13Z

Reverted edit by PawPatroler (2025) (talk) to last revision by DmitriLeon2000

← Older revision		Revision as of 05:49, 6 March 2026
(No difference)

PawPatroler (2025): PawPatroler (2025) changed the content model of the page JUKEBOX.SI from "wikitext" to "JavaScript"

2026-03-05T19:14:27Z

PawPatroler (2025) changed the content model of the page JUKEBOX.SI from "wikitext" to "JavaScript"

← Older revision		Revision as of 19:14, 5 March 2026
(No difference)

DmitriLeon2000 at 11:43, 17 April 2024

2024-04-17T11:43:33Z

← Older revision		Revision as of 11:43, 17 April 2024
Line 7:		Line 7:
	As an Interleaf file, JUKEBOX.SI is a container for a large number of asset files. Most of these files are background and radio music (including the radio voices) in Microsoft {{Wikipedia\|WAV}} audio, however there are also 4 [[FLIC]] video files for each of the building rooms (dune buggy, jetski, helicopter, and race car). These FLC files are the small instructional videos played in the screen and are interleaved together as "movies" that are equal length (thus looping together).		As an Interleaf file, JUKEBOX.SI is a container for a large number of asset files. Most of these files are background and radio music (including the radio voices) in Microsoft {{Wikipedia\|WAV}} audio, however there are also 4 [[FLIC]] video files for each of the building rooms (dune buggy, jetski, helicopter, and race car). These FLC files are the small instructional videos played in the screen and are interleaved together as "movies" that are equal length (thus looping together).

	All audio in JUKEBOX.SI (like most of LEGO Island's audio assets) is mono uncompressed PCM. While the majority of tracks are sampled at 11025 Hz/16-bit, a handful are sampled at 22050 Hz/8-bit. These can be distinguished by each track's WAV header (the "fmt " section if you're familiar with WAV headers) left intact in the first [[MxCh\|chunk] of their respective streams.		All audio in JUKEBOX.SI (like most of LEGO Island's audio assets) is mono uncompressed PCM. While the majority of tracks are sampled at 11025 Hz/16-bit, a handful are sampled at 22050 Hz/8-bit. These can be distinguished by each track's WAV header (the "fmt " section if you're familiar with WAV headers) left intact in the first [[MxCh\|chunk]] of their respective streams.

	When replacing, the WAV "fmt " header can be directly transplanted over the existing data in said first chunk. All WAV formats are compatible. The PCM data can be transplanted too, but it must be interleaved into chunks.		When replacing, the WAV "fmt " header can be directly transplanted over the existing data in said first chunk. All WAV formats are compatible. The PCM data can be transplanted too, but it must be interleaved into chunks.

MattKC at 17:08, 21 December 2019

2019-12-21T17:08:54Z

← Older revision		Revision as of 17:08, 21 December 2019
Line 1:		Line 1:
			{{Confused\|JUKEBOXW.SI}}

	[[JUKEBOX.SI]] is an [[Interleaf File]] containing 60 audio tracks of music and radio dialogue. With a few exceptions{{Citation needed}}, all of [[LEGO Island]]'s music is stored in JUKEBOX.SI.		[[JUKEBOX.SI]] is an [[Interleaf File]] containing 60 audio tracks of music and radio dialogue. With a few exceptions{{Citation needed}}, all of [[LEGO Island]]'s music is stored in JUKEBOX.SI.

MattKC: /* Details */

2019-12-21T16:37:45Z

Details

← Older revision		Revision as of 16:37, 21 December 2019
Line 3:		Line 3:
	== Details ==		== Details ==

	As an Interleaf file, JUKEBOX.SI is a container for a large number of asset files. Most of these files are background and radio music (including the radio voices) in Microsoft {{Wikipedia\|WAV}} audio, however there are also 4 [[~~FLC~~]] video files for each of the building rooms (dune buggy, jetski, helicopter, and race car). These FLC files are the small instructional videos played in the screen and are interleaved together as "movies" that are equal length (thus looping together).		As an Interleaf file, JUKEBOX.SI is a container for a large number of asset files. Most of these files are background and radio music (including the radio voices) in Microsoft {{Wikipedia\|WAV}} audio, however there are also 4 [[FLIC]] video files for each of the building rooms (dune buggy, jetski, helicopter, and race car). These FLC files are the small instructional videos played in the screen and are interleaved together as "movies" that are equal length (thus looping together).

	All audio in JUKEBOX.SI (like most of LEGO Island's audio assets) is mono uncompressed PCM. While the majority of tracks are sampled at 11025 Hz/16-bit, a handful are sampled at 22050 Hz/8-bit. These can be distinguished by each track's WAV header (the "fmt " section if you're familiar with WAV headers) left intact in the first [[MxCh\|chunk] of their respective streams.		All audio in JUKEBOX.SI (like most of LEGO Island's audio assets) is mono uncompressed PCM. While the majority of tracks are sampled at 11025 Hz/16-bit, a handful are sampled at 22050 Hz/8-bit. These can be distinguished by each track's WAV header (the "fmt " section if you're familiar with WAV headers) left intact in the first [[MxCh\|chunk] of their respective streams.

MattKC: Rewrote details section based on new information (more of this page will need rewriting)

2019-11-24T06:45:09Z

Rewrote details section based on new information (more of this page will need rewriting)

← Older revision		Revision as of 06:45, 24 November 2019
Line 1:		Line 1:
	[[JUKEBOX.SI]] is an [[~~SI Files\|SI file~~]] containing 60 audio tracks of music and radio dialogue. With a few exceptions{{Citation needed}}, all of [[~~Lego~~ Island]]'s music is stored in JUKEBOX.SI.		[[JUKEBOX.SI]] is an [[Interleaf File]] containing 60 audio tracks of music and radio dialogue. With a few exceptions{{Citation needed}}, all of [[LEGO Island]]'s music is stored in JUKEBOX.SI.

	== Details ==		== Details ==

	~~All audio in~~ JUKEBOX.SI is ~~uncompressed mono PCM~~. Most of the ~~tracks are~~ in ~~11025 Hz and 16-bit~~, ~~but a handful~~ are ~~22050 Hz and 8-bit. Each track starts with a header specifying its format~~ (~~sample rate~~, ~~sample size~~, ~~byte rate~~, ~~etc~~.)		As an Interleaf file, JUKEBOX.SI is a container for a large number of asset files. Most of these files are background and radio music (including the radio voices) in Microsoft {{Wikipedia\|WAV}} audio, however there are also 4 [[FLC]] video files for each of the building rooms (dune buggy, jetski, helicopter, and race car). These FLC files are the small instructional videos played in the screen and are interleaved together as "movies" that are equal length (thus looping together).

	~~Due to~~ SI ~~files~~' ~~standardization with RIFF~~, each track's ~~header is Microsoft {{Wikipedia\|~~WAV~~}} compatible and can be transplanted directly into a WAV file's~~ header~~. However due to SI files~~' ~~chunked/interleaved nature, the PCM data cannot be directly transplanted without noticeable clicks and glitches~~ in the ~~output~~.		All audio in JUKEBOX.SI (like most of LEGO Island's audio assets) is mono uncompressed PCM. While the majority of tracks are sampled at 11025 Hz/16-bit, a handful are sampled at 22050 Hz/8-bit. These can be distinguished by each track's WAV header (the "fmt " section if you're familiar with WAV headers) left intact in the first [[MxCh\|chunk] of their respective streams.

	~~JUKEBOX.SI does not actually interleave its audio with any other data~~, ~~making extraction easier than most SI files. However~~ the ~~audio is still separated into chunks and each chunk's 22-byte~~ header ~~(which is naturally not PCM data) is what causes the aforementioned clicks/glitches when trying to extract~~ the data ~~directly~~. ~~These chunk headers will need to~~ be ~~removed to extract a clean copy of the audio~~.		When replacing, the WAV "fmt " header can be directly transplanted over the existing data in said first chunk. All WAV formats are compatible. The PCM data can be transplanted too, but it must be interleaved into chunks.

	== Technical Information ==		== Technical Information ==

MattKC at 14:06, 18 April 2019

2019-04-18T14:06:20Z

← Older revision		Revision as of 14:06, 18 April 2019
Line 7:		Line 7:
	Due to SI files' standardization with RIFF, each track's header is Microsoft {{Wikipedia\|WAV}} compatible and can be transplanted directly into a WAV file's header. However due to SI files' chunked/interleaved nature, the PCM data cannot be directly transplanted without noticeable clicks and glitches in the output.		Due to SI files' standardization with RIFF, each track's header is Microsoft {{Wikipedia\|WAV}} compatible and can be transplanted directly into a WAV file's header. However due to SI files' chunked/interleaved nature, the PCM data cannot be directly transplanted without noticeable clicks and glitches in the output.

	JUKEBOX.SI does not actually interleave its audio with any other data, making extraction easier than most SI files. However the audio is still separated into chunks and each chunk's 20-byte header (which is naturally not PCM data) is what causes the aforementioned clicks/glitches when trying to extract the data directly. These chunk headers will need to be removed to extract a clean copy of the audio.		JUKEBOX.SI does not actually interleave its audio with any other data, making extraction easier than most SI files. However the audio is still separated into chunks and each chunk's 22-byte header (which is naturally not PCM data) is what causes the aforementioned clicks/glitches when trying to extract the data directly. These chunk headers will need to be removed to extract a clean copy of the audio.

	== Technical Information ==		== Technical Information ==

MattKC at 13:32, 18 April 2019

2019-04-18T13:32:16Z

← Older revision		Revision as of 13:32, 18 April 2019
Line 55:		Line 55:
	\|}		\|}

	Use this [http://archive.is/XXc3O WAV File Format Header Specification] and you'll be able to determine ~~the ordering and size of~~ the 16 bytes from "Audio Format" to "Bits per Sample per Channel" are identical. This makes up most of the WAV header data (apart from file and chunk size which cannot be determined from here) and can be directly transplanted to make extraction easier. Note that the MxCh header contains a few more bytes after ~~this~~ and therefore its "Sub-Chunk Size" is larger than the average WAV file's. These extra bytes should be ignored and not transplanted, though if they are the "Sub-Chunk Size" should be translated too (or at least increased to accommodate for them).		==== Transplanting the Header ====

			Use this [http://archive.is/XXc3O WAV File Format Header Specification] and you'll be able to determine the 16 bytes from "Audio Format" to "Bits per Sample per Channel" are identical. This makes up most of the WAV header data (apart from file and chunk size which cannot be determined from here) and can be directly transplanted to make extraction easier and ensure the sample rate and sample size are correct in the extraction.

			Note that the MxCh header contains a few more bytes after "Bits per Sample per Channel" and therefore its "Sub-Chunk Size" is larger than the average WAV file's. These extra bytes should be ignored and not transplanted, though if they are the "Sub-Chunk Size" should be translated too (or at least increased to accommodate for them).

MattKC at 13:30, 18 April 2019

2019-04-18T13:30:37Z

@@ Line 15: / Line 15: @@
 All bytes are little endian as is normal for RIFF-based files.
-'''MxDa Header Specification'''
+=== Extracting Audio ===
 {| class="wikitable"
 |-
@@ Line 41: / Line 55: @@
 |}
-'''MxCh Specification'''
+Use this [http://archive.is/XXc3O WAV File Format Header Specification] and you'll be able to determine the ordering and size of the 16 bytes from "Audio Format" to "Bits per Sample per Channel" are identical. This makes up most of the WAV header data (apart from file and chunk size which cannot be determined from here) and can be directly transplanted to make extraction easier. Note that the MxCh header contains a few more bytes after this and therefore its "Sub-Chunk Size" is larger than the average WAV file's. These extra bytes should be ignored and not transplanted, though if they are the "Sub-Chunk Size" should be translated too (or at least increased to accommodate for them).

MattKC at 12:51, 18 April 2019

2019-04-18T12:51:17Z

← Older revision		Revision as of 12:51, 18 April 2019
Line 1:		Line 1:
	[[JUKEBOX.SI]] is an [[SI Files\|SI file]] containing 60 audio tracks of music and radio dialogue. With a few exceptions{{Citation needed}}, all of [[Lego Island]]'s music is stored in JUKEBOX.SI.		[[JUKEBOX.SI]] is an [[SI Files\|SI file]] containing 60 audio tracks of music and radio dialogue. With a few exceptions{{Citation needed}}, all of [[Lego Island]]'s music is stored in JUKEBOX.SI.

			== Details ==

			All audio in JUKEBOX.SI is uncompressed mono PCM. Most of the tracks are in 11025 Hz and 16-bit, but a handful are 22050 Hz and 8-bit. Each track starts with a header specifying its format (sample rate, sample size, byte rate, etc.)

			Due to SI files' standardization with RIFF, each track's header is Microsoft {{Wikipedia\|WAV}} compatible and can be transplanted directly into a WAV file's header. However due to SI files' chunked/interleaved nature, the PCM data cannot be directly transplanted without noticeable clicks and glitches in the output.

			JUKEBOX.SI does not actually interleave its audio with any other data, making extraction easier than most SI files. However the audio is still separated into chunks and each chunk's 20-byte header (which is naturally not PCM data) is what causes the aforementioned clicks/glitches when trying to extract the data directly. These chunk headers will need to be removed to extract a clean copy of the audio.

	== Technical Information ==		== Technical Information ==
	~~All audio in JUKEBOX.SI is uncompressed mono PCM. Most of the tracks are in 11025 Hz and 16-bit, but a handful are 22050 Hz and 8-bit. Each track starts with a header specifying its format.~~

	Due to SI files' standardization with RIFF, each track's header (containing information about the sample rate, format, etc.) can be transplanted directly into a WAV file, however due to their chunked/interleaved nature, the PCM data cannot be directly transplanted without noticeable clicks and glitches in the output.

	Music appears to begin with a <code>MxDa</code> and is split into chunks of <code>MxCh</code>. The <code>MxDa</code> header contains information about the PCM audio in the <code>MxCh</code> chunks. The first <code>MxCh</code> appears to be information about the remainder of the chunks in the <code>MxDa</code> structure.		Music appears to begin with a <code>MxDa</code> and is split into chunks of <code>MxCh</code>. The <code>MxDa</code> header contains information about the PCM audio in the <code>MxCh</code> chunks. The first <code>MxCh</code> appears to be information about the remainder of the chunks in the <code>MxDa</code> structure.

	All bytes are little endian.		All bytes are little endian as is normal for RIFF-based files.

	'''MxDa Header Specification'''		'''MxDa Header Specification'''