Yahoo Groups archive
Thread
2007-05-09 by jeromepacman
Hi Colin, My situation is that I have on aux B, a "Rep*3 note" & on aux C, a "Random mask aux B". So, normally, my aux B would be on or off depends of aux C, but it doesn't work.. Am I wrong? Can you reproduce this?. I'm on the last V4... (love the V4) peace Jerome
2007-05-09 by Colin Fraser
> My situation is that I have on aux B, a "Rep*3 note" & on > aux C, a "Random mask aux B". > So, normally, my aux B would be on or off depends of aux C, > but it doesn't work.. This is the expected behaviour. Events are processed in order - A, B, C, D So when your aux B is processed, the track is configured to repeat the current note 3 times with the desired offset. When aux C is processed, aux B has already been processed, so masking it has no effect. That's why there are no events to mask aux A - they would never take effect. It's good practice to start with aux C or D for events, then masks can be added 'in front' of them later if you want to. > Am I wrong? Can you reproduce this?. I'm on the last V4... > (love the V4) A new v4 build is imminent, which fixes a few things, and adds some more features. Anyone else using it ? I've not had much feedback... Best regards, Colin Fraser Sequentix Music Systems Ltd http://www.sequentix.com
2007-05-10 by DB
Colin Fraser wrote:
>
> A new v4 build is imminent, which fixes a few things, and adds some more
> features.
> Anyone else using it ?
> I've not had much feedback...
Hi Colin,
Sorry haven't posted up yet about it. I've been using the new v4 OS
since you posted it publicly and have been upgrading to each revision.,
as I see them on your site. I have to agree, I am very happy with it.
It took a second to get used to it, as I've been interfacing with the
older way for a while now and I actually really like the Playlist thing,
but now I'm really starting to like the
flexibility that it provides. I'm actually really wishing that you
would make that memory upgrade thing that you were talking about a
reality :)
Give me a bit more time with it and I'll post some more thoughts...
Dave2007-05-10 by ch.³l
--- In analogue-sequencer@yahoogroups.com, "Colin Fraser" <colin@...> wrote: > ... > A new v4 build is imminent, which fixes a few things, and adds some > more features. > Anyone else using it ? > I've not had much feedback... i'm interested in the v4, but as i'm preparing for a series of livesets at the moment i'm sticking to what I know, being the latest v3 build. I hope the continued work on the v4 doesn't mean you've abandoned the v3 build, i'm still hoping for a few adaptations to it, the sticky-keys in playlist edit mode for one.. When i'm done with the livesets I think i'm going to run v3 on one P3 and v4 on the other...curious to see how that's going to work out. grtz Chiel
2007-05-10 by Nick Rothwell
On 10 May 2007, at 11:11, ch.³l wrote: > i'm interested in the v4, but as i'm preparing for a series of > livesets at the moment i'm sticking to what I know, being the latest > v3 build. Same here. Also, I wasn't sure whether V4 supported sysex backups yet... -- N. Nick Rothwell / Cassiel.com Limited www.cassiel.com www.myspace.com/cassieldotcom www.loadbang.net
2007-05-10 by Colin Fraser
> > i'm interested in the v4, but as i'm preparing for a series of > > livesets at the moment i'm sticking to what I know, being the latest > > v3 build. > > Same here. Also, I wasn't sure whether V4 supported sysex > backups yet... v4 has got sysex, though there is no way as yet to convert a v3 dump to load in v4. You may well want to wait for that before trying it out. Dave is working on a new version of P3 Tools to do this. (Go Da-ave, go Da-ave...) I have uploaded the most recent build to http://www.sequentix.com/v4beta.htm This beta has an altered sysex format from the previous v4 builds, so sysex dumps from b16 and earlier will NOT load. But the contents of memory will be preserved during an upgrade, apart from any user FTS scales. The reason for the change in sysex format is that user defined FTS scales are now held at the bank level. If you transferred a bank between P3s before this, any user scales used would have to be manually copied between them, unless you also transferred all the configuration settings. Even then, there may have been conflicts between different banks using the same scale numbers. So now you get eight user-defined scales, unique to each bank. This build also adds bar copy and swap functions, that are designed to let you juggle the bars of a pattern around in much the same way as you might play with the order of patterns in a playlist. Best regards, Colin Fraser Sequentix Music Systems Ltd http://www.sequentix.com
2007-05-10 by Stuart Carroll
Just wanted to thank Colin for all of his hard work in updating the P3 software constantly. As a group we are incredibly fortunate to have continued development of the P3. My studio is packed up for a move in the next fortnight, but as soon as I'm set up again, I'll be diving into V4. Thanks Colin, for making the P3 a continually evolving platform. Stu
2007-05-10 by Colin Fraser
> I hope the continued work on the v4 doesn't mean you've abandoned the > v3 build, i'm still hoping for a few adaptations to it, the > sticky-keys in playlist edit mode for one.. I've made a few changes to the v3 code in parallel with the v4 code where I've found common issues, but haven't done anything new with v3 for a while. If there's still demand to polish some things in v3 once v4 is in a release state, I'll look at it again if time permits. From my point of view as a user, I can't see me going back to v3 - it's been so long since I used playlist edit, it's somewhat baffling. My aim is to enable anything that could be done with playlists possible using pattern and bar level properties. Best regards, Colin Fraser Sequentix Music Systems Ltd http://www.sequentix.com
2007-05-10 by josh!
Colin said: > > From my point of view as a user, I can't see me going back to v3 - it's > been > so long since I used playlist edit, it's somewhat baffling. > My aim is to enable anything that could be done with playlists possible > using pattern and bar level properties. > I too have been holding off a bit on V4, but have gotten to try it out on Swedish Christ's P3. 1 minor thing I'd like V4 to do in a way that V3 does (at least we couldn't find a way): LIVE transposition of whatever bar (playlist step) you're editing... the only thing we found was to change the transpose for said bar and then APPLY it. Am I missing it? Is it on the way? And yes, thank you SO much for keeping the developement alive and exciting! [Non-text portions of this message have been removed]
2007-05-26 by DB
Colin Fraser wrote: > > > > > I hope the continued work on the v4 doesn't mean you've abandoned the > > v3 build, i'm still hoping for a few adaptations to it, the > > sticky-keys in playlist edit mode for one.. > > I've made a few changes to the v3 code in parallel with the v4 code where > I've found common issues, but haven't done anything new with v3 for a while. > If there's still demand to polish some things in v3 once v4 is in a release > state, I'll look at it again if time permits. Colin, If v3 is pretty much frozen code, would you be able to document the Remote Control options that are available for it? I know that you are actively working on v4 and will probably be working on enableing all the funtions of playlist into v4 before worrying about remote control, but I am hoping that you are planning on implementing some remote control at some point with v4. But with v3, there were several changes that you've done to the remote control code over time, and I wanted to know what I can and can't control remotely. No hurry with this, but would be useful for me when you do get a chance to visit this, as I usually use another sequencer with the P3. Cheers, Dave
2007-06-13 by colinfraser_com
--- In analogue-sequencer@yahoogroups.com, DB <dave@...> wrote: > Colin, If v3 is pretty much frozen code, would you be able to document > the Remote Control options that are available for it? Took me a while to get round to it, but there's a summary of remote control functions in the file 'P3 remcon.pdf', in Yahoo files. These are currently the same for both v3 and v4. Best regards, Colin Fraser Sequentix Music Systems Ltd http://www.sequentix.com
2007-06-14 by DB
Excellent!!!! Thx. This is very useful. Any chance on getting Midi CC #19 to be Part Select 0-7 ??? :) I'd take it for both v3 and v4... Dave colinfraser_com wrote:
> > > --- In analogue-sequencer@yahoogroups.com > <mailto:analogue-sequencer%40yahoogroups.com>, DB <dave@...> wrote: > > > Colin, If v3 is pretty much frozen code, would you be able to > document > > the Remote Control options that are available for it? > > Took me a while to get round to it, but there's a summary of remote > control functions in the file 'P3 remcon.pdf', in Yahoo files. > These are currently the same for both v3 and v4. > > Best regards, > Colin Fraser > Sequentix Music Systems Ltd > http://www.sequentix.com <http://www.sequentix.com>
2007-06-14 by jeromepacman
I'm definitly ok. We all buy the memory expansion then you boost the Os with new features. Is it the way? --- In analogue-sequencer@yahoogroups.com, "Colin Fraser" <colin@...> wrote:
> > 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 >
2007-06-14 by Colin Fraser
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
2007-06-14 by ch.³l
--- In analogue-sequencer@yahoogroups.com, "Colin Fraser" <colin@...> wrote: > 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. Hi Colin, do you think you could already give an estimate as to the cost of the daughterboard or are you still heavily in development? grtz, Chiel
2007-06-14 by Steve
This is pretty nifty. I'd be up for one, I think. I do have three questions, though... 1) How much will the PCB cost? 2) Will it be just a bare PCB, or will components be included (kit)? 3) Would you be willing to release the schematic and/or layout files so those of us who are capable of making our own boards could etch and assemble one? Thanks. :) -Steve --- In analogue-sequencer@yahoogroups.com, "Colin Fraser" <colin@...> wrote: > > 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 >
2007-06-15 by Stuart Carroll
Count me in on buying a memory expansion board for sure... Thanks, Stu On 15/06/2007, at 10:11 AM, Colin Fraser wrote: > 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]
2007-06-15 by Julian
>>We all buy the memory expansion then you boost the Os with new features. >>Is it the way? I think its a different type of memory. Julian (someone please correct me if im wrong...)
2007-06-15 by Wheaton, Simon
I'd like one. Thanks, Simon Canberra AUSTRALIA ________________________________
From: analogue-sequencer@yahoogroups.com [mailto:analogue-sequencer@yahoogroups.com] On Behalf Of Colin Fraser Sent: Friday, 15 June 2007 8:12 AM To: analogue-sequencer@yahoogroups.com 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 <http://www.sequentix.com/p3-half-meg-memex.jpg> Best regards, Colin Fraser Sequentix Music Systems Ltd http://www.sequentix.com <http://www.sequentix.com> ----------------------------------------------------------------------- This email, and any attachments, may be confidential and also privileged. If you are not the intended recipient, please notify the sender and delete all copies of this transmission along with any attachments immediately. You should not copy or use it for any purpose, nor disclose its contents to any other person. ----------------------------------------------------------------------- [Non-text portions of this message have been removed]
2007-06-15 by DB
I'm in for 1 for my production unit. Depending on the price, I might want another for my soon to be built P3. Thanks, Dave Colin Fraser wrote:
> > > 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 > <http://www.sequentix.com/p3-half-meg-memex.jpg> > > Best regards, > Colin Fraser > Sequentix Music Systems Ltd > http://www.sequentix.com <http://www.sequentix.com>
2007-06-15 by otison
plus one ! --- In analogue-sequencer@yahoogroups.com, "Colin Fraser" <colin@...> wrote: > > Folks, > > One of the things that became clear from developing the v3 to v4 conversion
2007-06-15 by Bas De Jong
If its just a action of liting the lid of the P3 and plugging in a new ramboard, why not? Yeah I want one also. Bas On 15-jun-2007, at 0:11, Colin Fraser wrote: > 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]
2007-06-15 by Jez Creek [Modulator ESP]
I've not got round to using V4 yet, but it's on the list of things to do So I'd be interested in a memory expansion Cheers Jez
-----Original Message----- From: analogue-sequencer@yahoogroups.com [mailto:analogue-sequencer@yahoogroups.com]On Behalf Of Colin Fraser Sent: 14 June 2007 23:12 To: analogue-sequencer@yahoogroups.com 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]
2007-06-15 by Colin Fraser
> We all buy the memory expansion then you boost the Os with > new features. > > Is it the way? There is only a very slight change required to the OS to enable the memory expansion board. I will just add some test code to identify if the expansion board is fitted, and have the OS reconfigure automatically. So there should be a single build of v4 that will run on either standard or expanded P3s. But to be clear, the expansion board only increases the memory capacity for pattern storage - it can't increase the available code space. v4 is still slightly smaller than v3, so there is room for a few more features yet. Best regards, Colin Fraser Sequentix Music Systems Ltd http://www.sequentix.com
2007-06-15 by duncan
me two, too. :-) d.
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]
2007-06-15 by privat_joy
What a question.... Sure, i need this expansion, by the way, i like the layout of the the proto very much... Thanks a< lot, stefan
2007-06-15 by Jim Combs
--- In analogue-sequencer@yahoogroups.com, "Colin Fraser" <colin@...> wrote: > If you've been using v4, and would like to buy a memory expansion board, let > me know. Two for me, please! -Jim
2007-06-15 by eas
1 for me please
2007-06-15 by Jesse
I am an unconcerned about transferring my data from V3 to V4, is there any reason I woudl benefit from the expansion board?
----- Original Message ----- From: Colin Fraser To: analogue-sequencer@yahoogroups.com Sent: Friday, June 15, 2007 5:32 AM Subject: RE: [analogue-sequencer] Re: P3 v4 memory expansion > We all buy the memory expansion then you boost the Os with > new features. > > Is it the way? There is only a very slight change required to the OS to enable the memory expansion board. I will just add some test code to identify if the expansion board is fitted, and have the OS reconfigure automatically. So there should be a single build of v4 that will run on either standard or expanded P3s. But to be clear, the expansion board only increases the memory capacity for pattern storage - it can't increase the available code space. v4 is still slightly smaller than v3, so there is room for a few more features yet. Best regards, Colin Fraser Sequentix Music Systems Ltd http://www.sequentix.com [Non-text portions of this message have been removed]
2007-06-15 by Mark Pulver
I'm in for one! THANK YOU COLIN! ----------- Colin Fraser (03:11 PM 6/14/2007) wrote: >If you've been using v4, and would like to buy a memory expansion board, let >me know.
2007-06-15 by Colin Fraser
> I am an unconcerned about transferring my data from V3 to V4, > is there any reason I woudl benefit from the expansion board? It would give you more storage space for creating patterns in v4. If you don't find you ever run out of room, you can probably live without one. Best regards, Colin Fraser Sequentix Music Systems Ltd http://www.sequentix.com
2007-06-15 by Zahir Manek
i'll take one.
Colin Fraser <colin@sequentix.com> wrote: 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
---------------------------------
Shape Yahoo! in your own image. Join our Network Research Panel today!
[Non-text portions of this message have been removed]2007-06-15 by Jesse
Oh well since you said the word "more" I MUST have one...
----- Original Message ----- From: Colin Fraser To: analogue-sequencer@yahoogroups.com Sent: Friday, June 15, 2007 11:01 AM Subject: RE: [analogue-sequencer] Re: P3 v4 memory expansion > I am an unconcerned about transferring my data from V3 to V4, > is there any reason I woudl benefit from the expansion board? It would give you more storage space for creating patterns in v4. If you don't find you ever run out of room, you can probably live without one. Best regards, Colin Fraser Sequentix Music Systems Ltd http://www.sequentix.com [Non-text portions of this message have been removed]
2007-06-15 by James R. Coplin
put me down for one... James R. Coplin
2007-06-15 by Stoffel
Also I'm still using v3 I'd liked to have one. So please put me on the List. Thank you Colin!
2007-06-15 by hal_414
count me for one also :)
2007-06-15 by Tom Adam
Just wondering... How long will a sysex dump take? ToAd Colin Fraser wrote: > > 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 > <http://www.sequentix.com/p3-half-meg-memex.jpg> > > Best regards, > Colin Fraser > Sequentix Music Systems Ltd > http://www.sequentix.com <http://www.sequentix.com> > > > ------------------------------------------------------------------------ > > No virus found in this incoming message. > Checked by AVG Free Edition. > Version: 7.5.472 / Virus Database: 269.8.16/849 - Release Date: 14/06/2007 12:44 > -- Tom Adam The Big Ear http://users.pandora.be/the-big-ear/ Check out the download section!
2007-06-15 by Colin Fraser
> Just wondering... > How long will a sysex dump take? That depends on how many bars you have allocated, and whether you use handshaking for the transfer. v4 does automatic handshaking, with a fail over to single ended transmission if the sender doesn't get an ACK or NACK. When Dave sends me the beta of P3 Tools 2, I'll be able to test how long the maximum possible dump takes. Best regards, Colin Fraser Sequentix Music Systems Ltd http://www.sequentix.com
2007-06-16 by waveformer74
I´m in for two :) Thank you Colin. --- In analogue-sequencer@yahoogroups.com, "Colin Fraser" <colin@...> wrote: > > 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 >
2007-06-16 by em_dkj
Colin I want one .. But you already knew that. PS A first beta version of P3Tools2 with V4 support draws ever closer Dave
2007-06-18 by josh
I'll take 1 please sire. On 6/16/07, em_dkj <david@davekj.f2s.com> wrote: > > Colin > > I want one .. > But you already knew that. > > PS > A first beta version of P3Tools2 with V4 support draws ever closer > > Dave > > > -- http://superuntitled.com/josh [Non-text portions of this message have been removed]
2007-06-19 by legozone23
Hi Colin, Please count 2 Board for me too. cheers o3
2007-06-19 by Mancuniman
Please count me i for a expansion board too Colin. Have bee using V4 the last few weeks in the studio now and i'm very impressed with the changes even if i do burn up memory quicker than before... As suggested by Paul that maybe points to focusing on the essential patterns for any bank or tune and a more streamlined way of working but the extra memory will be most welcome. BTW, i was sporting the Sequentix-P3 colours @ Sonar last week and off to Glastonbury tomorrow for more adventures. Maybe some eager girl will ask me the relative merits of V4 versus V3, ghost patterns v playlists, or maybe even just to fiddle with my lower knobs and see what the accumulators do... Kev.
2007-06-20 by Nick Rothwell
On 14 Jun 2007, at 23:11, Colin Fraser wrote: > 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. Definitely interested. Sign me up... A couple of questions: How well secured would the expansion board be? (Digital instrument history is littered with examples of unreliable daughterboards and connections coming loose, the D-50 MEX being a prime example.) With the board in place, will the P3 boot up and operate with the V3 software at all (with the old bank structure), or does it make the V4 jump permanent? (I'm still on V3, and need to figure out a non-Windows way to decant my V3 banks to V4 before upgrading.) -- N. Nick Rothwell / Cassiel.com Limited www.cassiel.com www.myspace.com/cassieldotcom www.loadbang.net
2007-06-20 by Doug Wellington
> If you've been using v4, and would like to buy a memory expansion board, let > me know. I'd like one too... -- -Doug http://www.analognotes.com http://www.stoogepanels.com http://www.dougwellington.com
2007-06-20 by Colin Fraser
> A couple of questions: > > How well secured would the expansion board be? (Digital instrument > history is littered with examples of unreliable daughterboards and > connections coming loose, the D-50 MEX being a prime example.) I use turned pin PCB headers in turned pin PCB sockets. They are hard to get in, and hard to get out. DIYed P3s with cheaper sockets may not grip as hard. > With the board in place, will the P3 boot up and operate with the V3 > software at all (with the old bank structure), or does it > make the V4 > jump permanent? The v3 OS could be patched to run with memory board without opening up the expanded space. The memory expansion decodes a single address (top byte of the bottom 32k of RAM) to a page select register, which selects one of sixteen pages of 32k RAM. So long as the page select register is forced to a fixed value at every boot, and the pattern byte that would normally be stored there is held somewhere else, v3 would run happily with the board in place. > (I'm still on V3, and need to figure out a non-Windows way to decant > my V3 banks to V4 before upgrading.) If you have v3 dumps in .syx format, I could run a few through the conversion utility. Unless I get fifty people all asking me to do a dozen dumps each... Best regards, Colin Fraser Sequentix Music Systems Ltd http://www.sequentix.com
2007-06-21 by Gene Schwartz
I¹m sure that as soon as I ask this I¹ll figure out that I¹m overlooking something simple, but I¹m puzzled right now. I¹m hoping that someone can spend the considerable effort to try to figure out what¹s going wrong here, or what I¹m misunderstanding. I¹ve narrowed this down to the interaction of 2 tracks. Basically the issue is that somehow the p3 is sending controller #24, which is modulating the filter envelope of my mfb synth 2, which I definitely don¹t want at the moment. But I don¹t see that I¹m telling the p3 to send this controller. I¹m also perhaps not understanding how the push aux to track n works.....as explained below. Currently, only track 1 and track 6 are activated. When track 1 is mute, track 6 (which sends the controllers) does NOT send controller #24 and sends only controllers #22 and #29, which is to be expected. Track 6 has: Aux 1: push. Only 1 step selected, which is pushing aux b to track 1. So, there is no controller explicitly sent on this aux event. Aux 2: rep*n by length. Only the same step as above is selected. Again no controller. Aux 3: cc#29 Aux 4: cc#22 Track 1 has: Aux 1: Grab all steps are grabbing velocity from another track Aux 2: xpose by trak n Aux 3 and 4: nothing set The midi monitor program I¹m running is showing that the controller #24 is coming from the p3 port on my midi timepiece av. Again when port 1 is muted, Now this is interesting I just edited things so that track one sends on channel 2 (track 6 is sending on channel 1). Sometimes the controller events are being sent on channel 2 and sometimes they are being sent on channel 1. So, it kind of looks like the push event is actually pushing aux b, c, and d, to track 1. This can¹t be the way the push event works?! (if so, why not have a push all subsequent aux events choice instead? And I¹m still confused as to where controller 24 is coming from. 20:12:24.439 From MIDI Timepiece AV Port 7 Control 2 Controller 22 87 20:12:24.554 From MIDI Timepiece AV Port 7 Control 1 Controller 29 82 20:12:24.555 From MIDI Timepiece AV Port 7 Control 1 Controller 22 13 20:12:24.671 From MIDI Timepiece AV Port 7 Control 1 Controller 29 23 20:12:24.672 From MIDI Timepiece AV Port 7 Control 1 Controller 22 19 20:12:24.789 From MIDI Timepiece AV Port 7 Control 1 Controller 22 13 20:12:24.906 From MIDI Timepiece AV Port 7 Control 1 Controller 29 53 20:12:24.906 From MIDI Timepiece AV Port 7 Control 1 Controller 22 107 20:12:25.023 From MIDI Timepiece AV Port 7 Control 1 Controller 29 102 20:12:25.024 From MIDI Timepiece AV Port 7 Control 1 Controller 22 13 20:12:25.140 From MIDI Timepiece AV Port 7 Control 1 Controller 29 14 20:12:25.141 From MIDI Timepiece AV Port 7 Control 1 Controller 22 13 20:12:25.257 From MIDI Timepiece AV Port 7 Control 1 Controller 29 1 20:12:25.258 From MIDI Timepiece AV Port 7 Control 1 Controller 22 13 20:12:25.374 From MIDI Timepiece AV Port 7 Control 1 Controller 29 108 20:12:25.375 From MIDI Timepiece AV Port 7 Control 1 Controller 22 13 20:12:25.492 From MIDI Timepiece AV Port 7 Control 1 Controller 29 31 20:12:25.493 From MIDI Timepiece AV Port 7 Control 1 Controller 22 58 20:12:25.609 From MIDI Timepiece AV Port 7 Control 1 Controller 29 113 20:12:25.610 From MIDI Timepiece AV Port 7 Control 1 Controller 22 13 20:12:25.726 From MIDI Timepiece AV Port 7 Control 1 Controller 22 20 20:12:25.843 From MIDI Timepiece AV Port 7 Control 1 Controller 29 13 20:12:25.844 From MIDI Timepiece AV Port 7 Control 1 Controller 22 13 20:12:25.961 From MIDI Timepiece AV Port 7 Control 1 Controller 22 13 20:12:26.077 From MIDI Timepiece AV Port 7 Control 1 Controller 29 85 20:12:26.078 From MIDI Timepiece AV Port 7 Control 1 Controller 22 13 20:12:26.194 From MIDI Timepiece AV Port 7 Control 2 Controller 24 52 20:12:26.196 From MIDI Timepiece AV Port 7 Control 2 Controller 29 7 20:12:26.196 From MIDI Timepiece AV Port 7 Control 2 Controller 22 87 20:12:26.312 From MIDI Timepiece AV Port 7 Control 1 Controller 29 82 20:12:26.313 From MIDI Timepiece AV Port 7 Control 1 Controller 22 13 20:12:26.429 From MIDI Timepiece AV Port 7 Control 1 Controller 29 23 20:12:26.430 From MIDI Timepiece AV Port 7 Control 1 Controller 22 19 20:12:26.546 From MIDI Timepiece AV Port 7 Control 1 Controller 22 13 20:12:26.664 From MIDI Timepiece AV Port 7 Control 1 Controller 29 53 20:12:26.664 From MIDI Timepiece AV Port 7 Control 1 Controller 22 107 20:12:26.781 From MIDI Timepiece AV Port 7 Control 1 Controller 29 102 20:12:26.782 From MIDI Timepiece AV Port 7 Control 1 Controller 22 13 20:12:26.898 From MIDI Timepiece AV Port 7 Control 1 Controller 29 14 20:12:26.899 From MIDI Timepiece AV Port 7 Control 1 Controller 22 13 20:12:27.015 From MIDI Timepiece AV Port 7 Control 1 Controller 29 1 20:12:27.016 From MIDI Timepiece AV Port 7 Control 1 Controller 22 13 20:12:27.133 From MIDI Timepiece AV Port 7 Control 1 Controller 29 108 20:12:27.133 From MIDI Timepiece AV Port 7 Control 1 Controller 22 13 20:12:27.250 From MIDI Timepiece AV Port 7 Control 1 Controller 29 31 20:12:27.251 From MIDI Timepiece AV Port 7 Control 1 Controller 22 58 20:12:27.367 From MIDI Timepiece AV Port 7 Control 1 Controller 29 113 20:12:27.368 From MIDI Timepiece AV Port 7 Control 1 Controller 22 13 20:12:27.484 From MIDI Timepiece AV Port 7 Control 1 Controller 22 20 20:12:27.601 From MIDI Timepiece AV Port 7 Control 1 Controller 29 13 20:12:27.602 From MIDI Timepiece AV Port 7 Control 1 Controller 22 13 20:12:27.718 From MIDI Timepiece AV Port 7 Control 1 Controller 22 13 20:12:27.836 From MIDI Timepiece AV Port 7 Control 1 Controller 29 85 20:12:27.836 From MIDI Timepiece AV Port 7 Control 1 Controller 22 13 20:12:27.952 From MIDI Timepiece AV Port 7 Control 2 Controller 24 52 20:12:27.954 From MIDI Timepiece AV Port 7 Control 2 Controller 29 7 20:12:27.954 From MIDI Timepiece AV Port 7 Control 2 Controller 22 87 20:12:28.070 From MIDI Timepiece AV Port 7 Control 1 Controller 29 82 20:12:28.071 From MIDI Timepiece AV Port 7 Control 1 Controller 22 13 20:12:28.187 From MIDI Timepiece AV Port 7 Control 1 Controller 29 23 20:12:28.188 From MIDI Timepiece AV Port 7 Control 1 Controller 22 19 20:12:28.305 From MIDI Timepiece AV Port 7 Control 1 Controller 22 13 20:12:28.422 From MIDI Timepiece AV Port 7 Control 1 Controller 29 53 20:12:28.422 From MIDI Timepiece AV Port 7 Control 1 Controller 22 107 20:12:28.539 From MIDI Timepiece AV Port 7 Control 1 Controller 29 102 20:12:28.540 From MIDI Timepiece AV Port 7 Control 1 Controller 22 13 20:12:28.656 From MIDI Timepiece AV Port 7 Control 1 Controller 29 14 20:12:28.657 From MIDI Timepiece AV Port 7 Control 1 Controller 22 13 20:12:28.773 From MIDI Timepiece AV Port 7 Control 1 Controller 29 1 [Non-text portions of this message have been removed]
2007-06-21 by Colin f
Gene, Any chance you could send me a dump of the bank doing this ? I could try to set it up myself, but if I either miss something, or it is peculiar to some other track in the bank, it might not behave the same way. A single bank dump can be done from play mode page 7 using FUNC+'send'. Best regards, Colin Fraser Sequentix Music Systems Ltd http://www.sequentix.com
> -----Original Message----- > From: analogue-sequencer@yahoogroups.com > [mailto:analogue-sequencer@yahoogroups.com] On Behalf Of Gene Schwartz > Sent: 21 June 2007 04:21 > To: analogue-sequencer@yahoogroups.com > Subject: [analogue-sequencer] p3 v4 controller weirdness > > I¹m sure that as soon as I ask this I¹ll figure out that I¹m > overlooking > something simple, but I¹m puzzled right now. I¹m hoping that > someone can > spend the considerable effort to try to figure out what¹s > going wrong here, > or what I¹m misunderstanding. > > I¹ve narrowed this down to the interaction of 2 tracks. > Basically the issue > is that somehow the p3 is sending controller #24, which is > modulating the > filter envelope of my mfb synth 2, which I definitely don¹t > want at the > moment. But I don¹t see that I¹m telling the p3 to send this > controller. I¹m > also perhaps not understanding how the push aux to track n > works.....as > explained below. > > Currently, only track 1 and track 6 are activated. When track > 1 is mute, > track 6 (which sends the controllers) does NOT send > controller #24 and > sends only controllers #22 and #29, which is to be expected. > Track 6 has: > Aux 1: push. Only 1 step selected, which is pushing aux b to > track 1. So, > there is no controller explicitly sent on this aux event. > Aux 2: rep*n by length. Only the same step as above is > selected. Again no > controller. > Aux 3: cc#29 > Aux 4: cc#22 > > Track 1 has: > Aux 1: Grab all steps are grabbing velocity from another track > Aux 2: xpose by trak n > Aux 3 and 4: nothing set > > The midi monitor program I¹m running is showing that the > controller #24 is > coming from the p3 port on my midi timepiece av. Again > when port 1 is > muted, > > Now this is interesting I just edited things so that track > one sends on > channel 2 (track 6 is sending on channel 1). > Sometimes the controller events are being sent on channel 2 > and sometimes > they are being sent on channel 1. So, it kind of looks like > the push event > is actually pushing aux b, c, and d, to track 1. This can¹t > be the way the > push event works?! (if so, why not have a push all subsequent > aux events > choice instead? > > And I¹m still confused as to where controller 24 is coming from. > > 20:12:24.439 From MIDI Timepiece AV Port 7 Control 2 > Controller > 22 87 > 20:12:24.554 From MIDI Timepiece AV Port 7 Control 1 > Controller > 29 82 > 20:12:24.555 From MIDI Timepiece AV Port 7 Control 1 > Controller > 22 13 > 20:12:24.671 From MIDI Timepiece AV Port 7 Control 1 > Controller > 29 23 > 20:12:24.672 From MIDI Timepiece AV Port 7 Control 1 > Controller > 22 19 > 20:12:24.789 From MIDI Timepiece AV Port 7 Control 1 > Controller > 22 13 > 20:12:24.906 From MIDI Timepiece AV Port 7 Control 1 > Controller > 29 53 > 20:12:24.906 From MIDI Timepiece AV Port 7 Control 1 > Controller > 22 107 > 20:12:25.023 From MIDI Timepiece AV Port 7 Control 1 > Controller > 29 102 > 20:12:25.024 From MIDI Timepiece AV Port 7 Control 1 > Controller > 22 13 > 20:12:25.140 From MIDI Timepiece AV Port 7 Control 1 > Controller > 29 14 > 20:12:25.141 From MIDI Timepiece AV Port 7 Control 1 > Controller > 22 13 > 20:12:25.257 From MIDI Timepiece AV Port 7 Control 1 > Controller > 29 1 > 20:12:25.258 From MIDI Timepiece AV Port 7 Control 1 > Controller > 22 13 > 20:12:25.374 From MIDI Timepiece AV Port 7 Control 1 > Controller > 29 108 > 20:12:25.375 From MIDI Timepiece AV Port 7 Control 1 > Controller > 22 13 > 20:12:25.492 From MIDI Timepiece AV Port 7 Control 1 > Controller > 29 31 > 20:12:25.493 From MIDI Timepiece AV Port 7 Control 1 > Controller > 22 58 > 20:12:25.609 From MIDI Timepiece AV Port 7 Control 1 > Controller > 29 113 > 20:12:25.610 From MIDI Timepiece AV Port 7 Control 1 > Controller > 22 13 > 20:12:25.726 From MIDI Timepiece AV Port 7 Control 1 > Controller > 22 20 > 20:12:25.843 From MIDI Timepiece AV Port 7 Control 1 > Controller > 29 13 > 20:12:25.844 From MIDI Timepiece AV Port 7 Control 1 > Controller > 22 13 > 20:12:25.961 From MIDI Timepiece AV Port 7 Control 1 > Controller > 22 13 > 20:12:26.077 From MIDI Timepiece AV Port 7 Control 1 > Controller > 29 85 > 20:12:26.078 From MIDI Timepiece AV Port 7 Control 1 > Controller > 22 13 > 20:12:26.194 From MIDI Timepiece AV Port 7 Control 2 > Controller > 24 52 > 20:12:26.196 From MIDI Timepiece AV Port 7 Control 2 > Controller > 29 7 > 20:12:26.196 From MIDI Timepiece AV Port 7 Control 2 > Controller > 22 87 > 20:12:26.312 From MIDI Timepiece AV Port 7 Control 1 > Controller > 29 82 > 20:12:26.313 From MIDI Timepiece AV Port 7 Control 1 > Controller > 22 13 > 20:12:26.429 From MIDI Timepiece AV Port 7 Control 1 > Controller > 29 23 > 20:12:26.430 From MIDI Timepiece AV Port 7 Control 1 > Controller > 22 19 > 20:12:26.546 From MIDI Timepiece AV Port 7 Control 1 > Controller > 22 13 > 20:12:26.664 From MIDI Timepiece AV Port 7 Control 1 > Controller > 29 53 > 20:12:26.664 From MIDI Timepiece AV Port 7 Control 1 > Controller > 22 107 > 20:12:26.781 From MIDI Timepiece AV Port 7 Control 1 > Controller > 29 102 > 20:12:26.782 From MIDI Timepiece AV Port 7 Control 1 > Controller > 22 13 > 20:12:26.898 From MIDI Timepiece AV Port 7 Control 1 > Controller > 29 14 > 20:12:26.899 From MIDI Timepiece AV Port 7 Control 1 > Controller > 22 13 > 20:12:27.015 From MIDI Timepiece AV Port 7 Control 1 > Controller > 29 1 > 20:12:27.016 From MIDI Timepiece AV Port 7 Control 1 > Controller > 22 13 > 20:12:27.133 From MIDI Timepiece AV Port 7 Control 1 > Controller > 29 108 > 20:12:27.133 From MIDI Timepiece AV Port 7 Control 1 > Controller > 22 13 > 20:12:27.250 From MIDI Timepiece AV Port 7 Control 1 > Controller > 29 31 > 20:12:27.251 From MIDI Timepiece AV Port 7 Control 1 > Controller > 22 58 > 20:12:27.367 From MIDI Timepiece AV Port 7 Control 1 > Controller > 29 113 > 20:12:27.368 From MIDI Timepiece AV Port 7 Control 1 > Controller > 22 13 > 20:12:27.484 From MIDI Timepiece AV Port 7 Control 1 > Controller > 22 20 > 20:12:27.601 From MIDI Timepiece AV Port 7 Control 1 > Controller > 29 13 > 20:12:27.602 From MIDI Timepiece AV Port 7 Control 1 > Controller > 22 13 > 20:12:27.718 From MIDI Timepiece AV Port 7 Control 1 > Controller > 22 13 > 20:12:27.836 From MIDI Timepiece AV Port 7 Control 1 > Controller > 29 85 > 20:12:27.836 From MIDI Timepiece AV Port 7 Control 1 > Controller > 22 13 > 20:12:27.952 From MIDI Timepiece AV Port 7 Control 2 > Controller > 24 52 > 20:12:27.954 From MIDI Timepiece AV Port 7 Control 2 > Controller > 29 7 > 20:12:27.954 From MIDI Timepiece AV Port 7 Control 2 > Controller > 22 87 > 20:12:28.070 From MIDI Timepiece AV Port 7 Control 1 > Controller > 29 82 > 20:12:28.071 From MIDI Timepiece AV Port 7 Control 1 > Controller > 22 13 > 20:12:28.187 From MIDI Timepiece AV Port 7 Control 1 > Controller > 29 23 > 20:12:28.188 From MIDI Timepiece AV Port 7 Control 1 > Controller > 22 19 > 20:12:28.305 From MIDI Timepiece AV Port 7 Control 1 > Controller > 22 13 > 20:12:28.422 From MIDI Timepiece AV Port 7 Control 1 > Controller > 29 53 > 20:12:28.422 From MIDI Timepiece AV Port 7 Control 1 > Controller > 22 107 > 20:12:28.539 From MIDI Timepiece AV Port 7 Control 1 > Controller > 29 102 > 20:12:28.540 From MIDI Timepiece AV Port 7 Control 1 > Controller > 22 13 > 20:12:28.656 From MIDI Timepiece AV Port 7 Control 1 > Controller > 29 14 > 20:12:28.657 From MIDI Timepiece AV Port 7 Control 1 > Controller > 22 13 > 20:12:28.773 From MIDI Timepiece AV Port 7 Control 1 > Controller > 29 1 > > > > [Non-text portions of this message have been removed] > > > > > Yahoo! Groups Links > > >
2007-06-22 by Colin Fraser
Hi Gene, > I¹m sure that as soon as I ask this I¹ll figure out that I¹m > overlooking > something simple, but I¹m puzzled right now. You were overlooking something simple - a bug ;-) Well, mostly. When you use the push, swap or grab events, you need to remember two things - the tracks are processed in numerical order, and push/swap/grab only changes the values, not the aux assignments (though you maybe knew that already) So when you were pushing a value for aux B from track 6 to track 1, it was already too late - track 1's events had been processed, so the change of value made by the event on track 6 should have not had any effect. The bug (which has probably been around for a long time...) is that the change of value did have an effect - it fooled the CC generating code into thinking there was a valid CC value in aux B on track 1. There's an enable bit in the value for an aux on a given step that is cleared when the event assigned to that aux is processed. If the active bit is still set once event handling is complete, the value is treated as a CC instead. The 'push' of the value from a later track was making the value for the step in track 1 active again after it had been cleared when the event was processed, so it was treated as a CC. Internally, 'xpose by track n' is event number 24, which is where CC #24 came from. I'll look at fixing this, though it shouldn't really be a problem, since pushing/grabbing/swapping from a higher track number does not have any effect. Best regards, Colin Fraser Sequentix Music Systems Ltd http://www.sequentix.com
2007-06-25 by bambam4236
I'd love one too colin....big thumbs up for continuing to work with the P3 ;) cheers Brett --- In analogue-sequencer@yahoogroups.com, "Wheaton, Simon" <simon.wheaton@...> wrote: > > I'd like one. > > > > Thanks, > > Simon > Canberra > AUSTRALIA > > > > ________________________________ > > From: analogue-sequencer@yahoogroups.com > [mailto:analogue-sequencer@yahoogroups.com] On Behalf Of Colin Fraser > Sent: Friday, 15 June 2007 8:12 AM > To: analogue-sequencer@yahoogroups.com > 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 > <http://www.sequentix.com/p3-half-meg-memex.jpg> > > Best regards, > Colin Fraser > Sequentix Music Systems Ltd > http://www.sequentix.com <http://www.sequentix.com> > > > > ----------------------------------------------------------------------- > This email, and any attachments, may be confidential and also privileged. If you are not the intended recipient, please notify the sender and delete all copies of this transmission along with any attachments immediately. You should not copy or use it for any purpose, nor disclose its contents to any other person.
> ----------------------------------------------------------------------- > > > [Non-text portions of this message have been removed] >
2007-06-25 by sascha.matzke@gmail.com
Count me in... [Non-text portions of this message have been removed]
2007-07-17 by skylab001
I would be in for 1 expansion for my P3.