Golden Sun Hacking Community
July 27, 2017, 10:47:08 PM *
Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
News:
 
  Home   Forum   DC Wiki Help Search Calendar Downloads Login Register  
Pages: [1]   Go Down
  Print  
Author Topic: LSDJ RAM Dump stuff  (Read 12592 times)
0 Members and 1 Guest are viewing this topic.
Seto Kaiba
the blind-oriented developer
Jupiter Clan

Regular Member
*

Coins: 3
Offline Offline

Gender: Male
I am: chillin'
Posts: 179

« on: June 30, 2015, 06:21:25 PM »

LSDJ is a tracker for the Gameboy that allows players to create their own chiptunes with it. I've done quite a bit of music with this nifty piece of software and I can say it's pretty dang awesome. Unfortunately, being a Gameboy game, it's completely inaccessible outside of memorization. So I may be writing a specific GB emulator that will allow blind musicians to explore this pretty awesome tool.

I may just make it so that you can write your own files and then just load it into VBA but whatever, I found these, so have fun.

Anyways, I'm dumping my findings here, so hopefully someone else finds it useful.

LSDJ Memory Values:

0xB290-0xB68F

On the SONG screen, these values include the values of the various Chains.

These values do NOT reflect the actual values on any other screen. This should only be referenced when SONG is the active screen.

Each 4 bytes indicates a row of Chains. For example, the first byte in a set of 4 is PU1, then PU2, then WAV, then NOISE. Then it repeats until reaching FF.

These values seem to be stored elsewhere when not on the SONG screen, but I can't find them.

Idea: Extract these values when SONG is first loaded and place them in an array for quick access while on this screen, and flush the array when the screen changes.

0xA080-0xA87F

On the CHAIN screen, these values include references to various phrases.

These values do not reflect the actual values on any other screen. This should only be references when CHAIN is the active screen.

Each 16 bytes reflects a single chain. Chain 00 starts at A080, chain 01 starts at A090 ect.

These values are stored elsewhere but I can't find them.

Idea: Extract these values when CHAIN is first loaded and place them in an array for quick access while on this screen, and flush the array when the screen changes. Only reference the CURRENTLY SELECTED CHAIN.

0xA880-0xB07F

On the CHAIN screen, these values are the pitch offset for each individual phrase.

Similar to the references to the phrases, each 16 bytes corresponds with each chain. So A880 is chain 00, A890 is chain 1 ect.

0xA000-0xAFEF

On the PHRASE screen, represents the various notes. C3 (the lowest note) is represented with 01 while the highest note, B8, is represented by 48.

This has a weird update format. When deleting a note, it completely erases all the notes. This also occurs if you insert the same note. Adding the same instrument clears the memory as well. The list is resorted when you change the current note.

Each 16 bytes represents a single phrase. A000 is Phrase 00, A010 is phrase 01, ect.

0xC0AD

Current screen. Values correspond to:

01 - PHRASE screen
02 - GROOVE screen
03 - CHAIN screen
04 - SONG screen
05 - TABLE screen
06 - INSTRUMENT Screen
08 - FRAME screen
09 - PROJECT screen
0A - BANK screen

I might be missing a few, it's always tricky to go and figure this one out. lol

0xC1EF

5 character string representing currently selected instrument's name. Only applicable on INSTRUMENT screen.

The following are values that monitor the cursor. They stay the same when switching screens unless otherwise specified.

0xC1CC

PHRASE screen:

Horizontal cursor position. Starts at 1. 1 is note, 2 is instrument, 3 is type of modulation and 4 is modulation modifier.

0xC1CD

PHRASE screen:

Vertical cursor position.

0xC1D2

CHAIN screen:

Horizontal cursor position. 0 is chain, 1 is transpose.

0xC1D3

CHAIN screen:

Vertical cursor position.

0xC1D7

SONG screen:

Horizontal cursor position.

0xC1D8

SONG screen:

Vertical cursor position.
« Last Edit: June 30, 2015, 07:23:15 PM by Seto Kaiba » Logged

View Profile WWW
Pages: [1]   Go Up
  Print  
 
Jump to:  

Cbox
Today at 04:39:37 PM
Fox: Yep. And they better change it fast, because once people have settled somewhere else, it'll be too much work to move back. (And there's the fool me once/fool me twice thing.)
Today at 04:31:28 PM
Seto Kaiba: its gonna die real quick lol. apparently they have made some sales but I don't think it's going to last unless they drastically change their business model.
Today at 03:21:00 PM
Fox: I think it is safe to guess that no one will remember photobucket five years from now... after it closes down, hahahaha!
Today at 02:45:50 PM
Fox: Yes, that would be a huge factor too... Will need to look into that. ; Also, I love how imgur basically has no ads, and photobucket has a bunch.
Today at 01:51:35 PM
Seto Kaiba: pretty sure it's also the fact that photobucket expects you to pay $400 to host your images if you want to link them on other sites
Today at 12:27:23 PM
Fox: Because there are better image hosting sites... Such as imgur.... it's a bonus when they don't resize photos if they are large.
Today at 11:31:56 AM
Seto Kaiba: also photobucket: Why is everyone leaving my site?
Today at 11:31:44 AM
Seto Kaiba: photobucket: hey wanna spend $400 so you can have your pics appear on other websites?
Yesterday at 08:29:05 PM
Fox: Hmm... Kind of curious if I should convert my Height tile table function thingy to a get height (by pixel) function, and then use that as necessary.... Well, I'll need to give it some thought.
Yesterday at 04:22:38 PM
Fox: script.google.com = Well, since this is the site, I mean. Still looks like the same script window you can get from a SpreadSheet Script, though.
Yesterday at 04:20:52 PM
Fox: Actually, I think Google Scripts is separate from Google Spreadsheets... I never really bothered to look into it befor,e but.... er.... well, I guess we see what can be done with it in the future. (If I ever find out we can access something like binary files or whatever, then that might also be interesting. :P)
Yesterday at 03:54:51 PM
Fox: Well, that being I could just look at this: https://developers.google.com/apps-script/reference/gmail/gmail-app
Yesterday at 03:53:12 PM
Fox: Like what program? If it's something like futureme, It's just date/time.... I am kinda curious what Google Spreadsheets can do with things like GmailApp, which is another reason I linked it. 
Yesterday at 01:11:03 PM
Luna_blade: was there not a program already supporting delayed messages?
July 25, 2017, 06:42:07 PM
Fox: Depends on what you're up to... But on the surface, it's not likely you'd need it... I love it when things can be versatile.
July 25, 2017, 08:41:08 AM
Crystal Sonata: I don't much see a purpose for it, but interesting.
July 24, 2017, 02:53:28 AM
Fox: I'm Teawater, by the way... Hi!
July 24, 2017, 02:52:34 AM
Fox: Who?
July 24, 2017, 02:40:42 AM
Takumi: GUESS WHO'S BACK BITCHES \o/

Affiliates
Temple of Kraden Golden Sunrise
Powered by MySQL Powered by PHP Powered by SMF 1.1.21 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!
Page created in 0.079 seconds with 22 queries.