Gigabytes of sequences with Prop-1 and uMP3 ?

[BigRez]

I was just wondering if this is possible...

Was working on a sequencing program (a modified version of Jon's sequencer) and am far short of EEPROM area.  I was thinking though, since I'm already using a uMP3 device for the prop, couldn't I store all of the sequence information in a file on the uMP3 and then read the sequence info from the file rather than EEPROM? 

The uMP3's    FC R fh ###   command could be used to read the sequence data from a file and then SERIN would be used (similar to the READ command with a pointer) to obtain the returned data.  (Although we could use a pointer to tell it where to start reading from, we wouldn't need to because the uMP# would keep track of that for us.)

So, I imagine it would go something like:

Play_Show:
   SEROUT 6, Baud, ("FC R 1 16", 32 )   ' read 16 bytes from handle 1, assumes already opened
   SERIN 5, Baud, showBits, timer       ' store data into showBits (B0) and timer (B2)

   PINS = showBits & %01111111


Similar to the original sequencer program, the last bits of showBits would be used to indicate the end of the show.

So, could this work?  Are there any concerns with doing this?

Thanks,

[JonnyMac]

If it will let you open the file and read one byte at a time you might be able to pull it off.  The problem you face with the Prop-1 is the small RAM footprint.  I just picked up a new SD card for my uMP3; as time permits I'll see if I can make this work (things are crazy, though, so please don't push).  BTW, how are you writing the data to the SD card?

[BigRez]

Oops, just realized (with the help of your question) that I was mixing bits and bytes...  So I originally thought to just move the EEPROM lines into the file.  It could work that way but would make the routine to read in the data larger.

A hex/binary editor on the PC could be used to make the file work as needed, or a small conversion utility could be written.

[JonnyMac]

I think you're going to need to save the values as raw binary so that you can treat the reads just like pulling data from an EEPROM.