Analogue-sequencer

I would LOVE to see preset chords implemented even if it used all of  
the available codespace remaining.
Or even a cut down 'demo' OS of this feature.

s

On 8/05/2008, at 10:50 AM, Colin Fraser wrote:

>
> > 3P is already polyphonic sequencer, why do I need to spend
> > memory and tiiiimmmeee for 3 auxes, to get one chord (how for
> > 5-7 note chord)?
> > I would rather use auxes for midi delays, echoes, than just for  
> chord.
> > It was the same with drone in the begining, p3 didnt have 13
> > lenght nither.
>
> In order to send a chord, P3 has to store all the notes that make up  
> the
> chord somewhere.
> The data structure for a pattern has eight numeric rows - note,  
> velocity,
> length, delay, aux A, B, C and D.
> To play chords, the auxes have to be used, otherwise the data  
> structure has
> to change.
> Changing the data structure means there would be fewer patterns in  
> total.
> Remember P3 is a pattern based sequencer, not an event based one.
>
> There is a possibility I have considered to allow 'preset' chords to  
> be
> entered using only a single aux, and a 'chord' event.
> That would take a single value to select the type of chord to play,  
> with the
> main note value setting the root note.
> But adding any significant number of chords, or a user interface for
> user-defind chords would quickly use up the last of the code space.
> I might experimentally add the event, and a few chords, such as  
> major triad,
> minor triad, major/minor 7th, and see how much code it does use.
>
> Best regards,
> Colin Fraser
> Sequentix Music Systems Ltd
> http://www.sequentix.com
>
>
> 



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