Re: Moving binary files to /RAM

[email@DELETE_THIS.luddite.no-ip.com (Simon Williams)]

Laine Houghton <laine@intergate.com> wrote:

>  I did a test saving  blocks of 1's 2's 3's......... 3072 bytes just as the
> program would do. The 12's representing the 12'th file ends right at $BFFF
> The 13'th to 16'th files would be contained in the bank 1 bank 2 and beyond
> memory.
> 
> I'm guessing that the bank switching overhead introduces an unavoidable
> delay that a program such as yours is sensative to.

I'm actually surprised it's that much of a delay, though I'll admit I
have no idea how memory actually works ;-)
Presumably then, this would still be an issue were I to write an
assembly routine to handle the file moving. 
 
> A good incentive to get down to the assy work. With a 1 meg card you could
> move 12 files worth of samples to successive 64k banks.
> 
> If I did my napkin math correctly that would be 180 files and it should work
> as smooth as the 12 alone.

...and I thought requiring 128K was pushing it! That definitely has
potential for a music sequencer where you could really use the added
range... loading the banks with 4 x 9K samples would give you a range of
5+ octaves and allow for notes that could sustain almost a full
second... actually I think this idea might be well worth pursuing.


-- 
._____.
|[LD8]! SIMON WILLIAMS :: LUDDITE ENTERPRISES UNLIMITED
| (O) | 68K MACINTOSH SERVER   http://luddite.no-ip.com
!__!__! FAILURE RECORDS http://failurerecords.no-ip.com