sysex dump and loading of patchs is the way to go

On 29/04/2011, at 10:13 AM, kiwitechnics wrote:

 

Tape backup is not operational in the upgrade. I couldn't see the point. I have coded but have yet to test sysex dump and loading of patches. But as patch layout changes this will also change so it is not very useful yet. I will investigate the possibility of fitting a larger SRam chip in the 3P as the current one is pretty limited. This will require some hardware mods though.
Murray

--- In kiwitechnics@yahoogroups.com , Robert Stickles <rob.ocelot@...> wrote:
>
> Would it be possible to increase memory storage, or are we bound by the 3P's
> bank switching scheme to keep some backwards compatibility with the original
> 3P patches (I haven't checked this -- is tape saving/loading still working
> with the KT upgrade? Is there even a need for this nowadays?)
>
> On Thu, Apr 28, 2011 at 5:54 PM, kiwitechnics
> <yahoogroups@...>wrote:
>
> >
> >
> > I too think the uniqueness of the 3P Upgrade is with the major sections not
> > all the mods that can be made. I am a little concerned too that the patch
> > storage size is going to increase with the proposed changes as storage space
> > is pretty tight. I am being fairly efficient so far but things like adding a
> > level for every destination of a mod with ruin that pretty fast. What this
> > will mean is the number of editable patches will have to drop as patch size
> > increases and in the worst case it would end up like the original 3P where
> > you can only edit bank C & D. I have tried to keep a balance between
> > features and memory usage and this will need to be maintained. I realise
> > that this will not satisfy everyone but there are practical limits to what
> > can be achieved. Once there is a consensus on the most desired parameters I
> > can then look at the practicalities of implimenting these.
> >
> > Regards
> > Murray
> >
> >
> >
>