Yahoo Groups archive

Analogue-sequencer

Index last updated: 2026-04-28 23:15 UTC

Message

Re: [analogue-sequencer] P3 v4 memory expansion

2007-06-15 by Miguel Mendoza

Count on me also.
Cheers!

Miguel.

  ----- Original Message ----- 
  From: Colin Fraser 
  To: analogue-sequencer@yahoogroups.com 
  Sent: Friday, June 15, 2007 12:11 AM
  Subject: [analogue-sequencer] P3 v4 memory expansion


  Folks,

  One of the things that became clear from developing the v3 to v4 conversion
  utility (download coming soon), is that by re-using the patterns in
  different orders in many playlists, it's possible to create a bank in v3
  that uses quite a bit more storage space in v4.
  If every bank re-uses patterns in this way (now known as 'Nagling'), it can
  be impossible to fit a converted v3 dump in v4, even using ghosting where
  ever possible.

  Since v4 was developed as a test-bed for the P3 replacement hardware
  platform, it was designed for scalable memory.
  I've just completed a prototype memory expansion board for P3, which
  increases the internal RAM from 64k to 544k.
  Note that this board is only compatible with v4.
  It uses bank switching to give a dedicated 224 bars of pattern storage per
  v4 bank - still dynamically allocated between tracks and parts.
  This is rather more than the average 24 bars per bank in the stock P3 -
  3,200 extra bars in total, on top of the standard 384.

  If you've been using v4, and would like to buy a memory expansion board, let
  me know.
  I'll be finishing off a PCB layout shortly and ordering a run of boards.
  Installation will just be a case of unplugging the 32k SRAM in U2, and
  replacing it with a daughterboard.

  The prototype can be seen here:
  http://www.sequentix.com/p3-half-meg-memex.jpg

  Best regards,
  Colin Fraser
  Sequentix Music Systems Ltd
  http://www.sequentix.com



   

[Non-text portions of this message have been removed]

Attachments

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.