| |
SIDWAVE
Account closed
Registered: Apr 2002
Posts: 2238 |
DE00-DFFF
I read just about everything I could find about this memory area, but I remembered something, perhaps from a chat on IRC or something..
This mem area contains the program-counter, the last accessed line nr, cycle-counter, well - just about everything the machine does.
Is this true ?
Who knows anything ?
I can dig that any expansions put into the machine must have some input data, so naturally there has to be some important info in this memblock - but which ones exactly ?
I also read that it don't nessecarily behave the same way on every C64.
So ?
Help!!
I am also looking for a way to read the read-only registers of the SID.
My friend Kaze/TST did it once, but that program is lost forever, and he didn't code since 1988 on C64. damn.
The program was running a modified KERNAL, and it enabled us to write the music while playing, out to disk as a D400+ dump - but it was way to slow and the disk just got filled up very fast.
But it worked!
|
|
... 23 posts hidden. Click here to view all posts....
|
| |
WVL
Registered: Mar 2002
Posts: 902 |
in case of a tricky music routine...
well... :)
maybe the easiest thing would be to find the pointers, and calling it twice.. or something ;)
you could also just have 1 buffer to catch the writes in, just put a very unusual value in there, and you should be alright in 99% of the cases, i think..
|
| |
Graham
Account closed
Registered: Dec 2002
Posts: 990 |
99.609375 actually :D and even more if you take into account that some values are more likely than others. |
| |
SIDWAVE
Account closed
Registered: Apr 2002
Posts: 2238 |
Quote: @rambones: Could you care to explain why you want the data of a whole tune for a post processing scenario? Since, I guess you're aiming for the c64 as target machine of your idea? I'm just curious and if you don't want to reveal your secrets I can surely wait..
Well, I want to attempt to make a universal player.
Just convert any tune to this dumpformat (crunched), and then play it using a STA d400,x
If I can crunch it enough that is...
|
| |
iopop
Registered: Dec 2001
Posts: 317 |
Quote: Well, I want to attempt to make a universal player.
Just convert any tune to this dumpformat (crunched), and then play it using a STA d400,x
If I can crunch it enough that is...
Ok, I thoguht you wanted to do some kind of tool that could filter selected parts of the tune etc. Though, the sampled data is not the amplitude but parameters creating the amplitude. So, that might not have been possible anyhow. |
| |
chatGPZ
Registered: Dec 2001
Posts: 11386 |
uhmz like i mentioned before.... this kind of tool already exists :o) its called "music cruncher" and works exactly like you say. |
| |
Hoogo
Registered: Jun 2002
Posts: 105 |
I'm thinking about an assembler-interpreter for the music-routine. That will surely detect any access to the sid. I have done such an interpreter ages ago, maybe I'll have a look at it again. |
| |
Clarence
Registered: Mar 2004
Posts: 121 |
Quote: uhmz like i mentioned before.... this kind of tool already exists :o) its called "music cruncher" and works exactly like you say.
Can you tell me who made this tool and where can I find it? If you refer to the Spiders Crews 'Music Rastertime Cruncher', that doesn't crunch the dumped data at all. |
| |
Vai
Registered: Mar 2002
Posts: 50 |
The Music rastertime cruncher wasn't supposed to crunch the music data but the amount of rasterlines used by the player.
Yeah, I know ... stupid tool I've made :) |
| |
Clarence
Registered: Mar 2004
Posts: 121 |
Quote: The Music rastertime cruncher wasn't supposed to crunch the music data but the amount of rasterlines used by the player.
Yeah, I know ... stupid tool I've made :)
I like your tool, but It could have been a bit improved. It uses too short dumps, and fe. doesn't detect simple things like if a register has a constant value for hte whole excerpt etc. So I had to do a routine of my own. |
| |
JackAsser
Registered: Jun 2002
Posts: 2014 |
Not that I know how the SID-chip works, but isn't there a chance that some registers only reacts to the actual write, not the value, like for instance reseting something. For example a write to register X causes something special despite the actual value. This would mean that by removing duplicate writes with the same value actually causes error in the playback.
Any comments? |
| Previous - 1 | 2 | 3 | 4 - Next |
