Difference between revisions of "Talk:BRSAR (File Format)"

From Custom Mario Kart
Jump to navigation Jump to search
Line 14: Line 14:
 
I noticed while observing the collection table, the section doesn't seem to start until 8 bytes after the offset defined in the INFO header. Is there a reason for that?
 
I noticed while observing the collection table, the section doesn't seem to start until 8 bytes after the offset defined in the INFO header. Is there a reason for that?
 
[[User:TheZACAtac]] ([[User talk:TheZACAtac|talk]]) 7:00, 9 April 2020 (UTC)
 
[[User:TheZACAtac]] ([[User talk:TheZACAtac|talk]]) 7:00, 9 April 2020 (UTC)
 +
:I also noticed the offset to the first section in INFO (sound data) is 0x00000030. However, the header of INFO is 0x38 bytes long. Based on rough observation, it seems the sound data section doesn't start until 0x00000038, which is also 8 bytes after the specified offset. So maybe for each section in INFO, the offset should be determined by taking the offset specified in the INFO header and adding 8. [[User:TheZACAtac]] ([[User talk:TheZACAtac|talk]]) 7:20, 9 April 2020 (UTC)

Revision as of 07:19, 9 April 2020

Documentation from elsewhere

This contains some documentation on the BRSAR. It isn't complete, but it contains some info on the SYMB header, which I don't know much about. Aplumafreak500 (talk) 04:53, 20 June 2016 (UTC)

Related: This is BrawlBox's handler for saving BRSAR files. It's C# code, but it seems well organized. Aplumafreak500 (talk) 16:16, 14 June 2017 (UTC)

Other types

there is at least one other type of brsar that is usedn inside a .carc file and it has different header RÿSARþÿ in ASCII and i have a screenshot of it in here:https://drive.google.com/file/d/1_AG8qVbLCX2T4-9UvoQzOZxK8fdpV48K/view?usp=sharing

James Potkukelkka (talk) 18:14, 19 December 2017 (UTC)

It isn't a different type of BRSAR. CARC files are compressed formats, so that's why it does look like that in hex. —Atlas (talk) – CT/MK8 Wiki Admin 19:15, 19 December 2017 (UTC)

Collection Table

I noticed while observing the collection table, the section doesn't seem to start until 8 bytes after the offset defined in the INFO header. Is there a reason for that? User:TheZACAtac (talk) 7:00, 9 April 2020 (UTC)

I also noticed the offset to the first section in INFO (sound data) is 0x00000030. However, the header of INFO is 0x38 bytes long. Based on rough observation, it seems the sound data section doesn't start until 0x00000038, which is also 8 bytes after the specified offset. So maybe for each section in INFO, the offset should be determined by taking the offset specified in the INFO header and adding 8. User:TheZACAtac (talk) 7:20, 9 April 2020 (UTC)