Analogue-sequencer

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.

Melodic part of all my music that I do, is from chords and drones and I love using P3, just piss me off big time, to set chords from auxes all the time.
My old QY70 trigers some fat chords and riffs so good that I had to take it back from my little brother that I gave for present lont time ago. 
I also use sx chorader for chords because setting an auxes for chords is just nightmare.

P3 needs chords step pattern and chords scale menu because it can do it easily.

Regards,
Zed.

----- Original Message ----
From: DB <dave@RenegadeRhythms.com>
To: analogue-sequencer@yahoogroups.com
Sent: Monday, May 5, 2008 7:10:52 PM
Subject: Re: [analogue-sequencer] Chords on P3


Zed,
Hopefully, the P4 will take what the P3 has done with Chords and 
runs with it :)
Until then, we have what we have, which isn't too bad compared to most 
Step Sequencers. 

Are you aware that Colin's created a "Quick Config" for Aux Chord Mode. 
Here's the steps.

1. In Pattern Edit Mode, hit Func --> Upper Mode
2. Change the Mode to how many Aux's you want configured and if you want 
them absolute or relative.
3. Hit Save. 
4. Now your set to input a 2-5 note chord, depening on what you set with 
Quick Config

Now your Aux are configured.  You can now enter them the long way via 
the P3's knobs themselves,
or you can enter them via an External Keyboard (hit Record for external 
keyboard input)
which is fairly  easy to do.   A quick solution to the the P3 running 
faster then you can input the correct
chords at the correct time (I"m not a keyboard player myself),
is to turn the BPM down on the P3, or slowing the Tbase during the 
inputting of the chords.

Hope that helps,

Dave

Zed Velkovich wrote:

> Hi,
> It is complicated to program chords on P3 with 3 auxes spend.
> Why not set Xd button to enter in chord mode and to get a chord just 
> with one button selected like gate or tie.
> Upper row can be used to select a type of the chord.
> 
> Chords are important.
> 
> Regards,
> Zed. 
>
>
> .
>
> .
>
> 

    


      ____________________________________________________________________________________
Be a better friend, newshound, and 
know-it-all with Yahoo! Mobile.  Try it now.  http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ

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

I agree!

Hans
________________________________
> To: analogue-sequencer@yahoogroups.com
> From: zedhok@yahoo.com
> Date: Tue, 6 May 2008 04:12:55 -0700
> Subject: Re: [analogue-sequencer] Chords on P3
> 
> 
> 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.
> 
> Melodic part of all my music that I do, is from chords and drones and I love using P3, just piss me off big time, to set chords from auxes all the time.
> My old QY70 trigers some fat chords and riffs so good that I had to take it back from my little brother that I gave for present lont time ago.
> I also use sx chorader for chords because setting an auxes for chords is just nightmare.
> 
> P3 needs chords step pattern and chords scale menu because it can do it easily.
> 
> Regards,
> Zed.
> 
> ----- Original Message ----
> From: DB 
_________________________________________________________________
MSN Video. 
http://video.msn.com/?mkt=es-es

Hi Zed,
     Comments inline:

Zed Velkovich wrote:

 >>3P is already polyphonic sequencer,
I'm not sure if you are aware or not, but the P3 didn't start as a 
Polyphonic Step Sequencer.  It started as
a Monophonic Step Sequencer.  Polyphony was added later. I remember when 
it was added and I remember
my exitement when hearing about it.   I myself, several years ago 
requested for
an improvement in utilizing the Chords with the P3 similar to what you 
have requested and it was shot down
then due to code space.  I'm sure there is even less code space now then 
2 years ago.


 >>why do I need to spend memory and tiiiimmmeee for 3 auxes, to get one 
chord (how for 5-7 note chord)?
Because that is how the P3 stores it's information.  As indicated above, 
the P3 was originally designed for Monophonic
use and then it was determined that if one used the Aux parts  to hold 
other Notes that one could create Chords and
hence P3 Polyphony was created.   The other reason is because with the 
limited code space, that is how it is.  He would
have to restructure they way the P3 stores its information and uses it.  
Sometimes things are very easy to say in words
but when it gets to actual coding around the current design, they can be 
very difficult.
If you want chords/polyphony on a track with the P3,
then these are steps to achieve it.  If you don't want to spend the 
memory or tiiiimmmmmeeeee then
you can stick to monophonic sequences?   For a 6-8 note chord, you need 
to redirect your Auxes from another Track
to the Track that you want the additional Polyphony from for notes 6, 7, 
& 8 ( I believe Aux A will be Redirect
to Track and then Aux B, C, D are for your chords.).  1 -5 can be done 
on the original track.

 >>I would rather use auxes for midi delays, echoes, than just for chord.
I as well.   Thank goodness that Colin added the ability to redirect Aux 
to other Tracks.  So for example,
you can use Track 1 to create a 5 note chord, Track 2 to create add  3 
more  notes to Tracks1's  Chord, and Track 3 to have
it's Aux' redirected to Track 1 to do their funky goodness.      I think 
now you can start to understand why I have
2 P3's (as soon as I build my 2nd one).   There's more then I want to do 
than is available on a track. So you
double up or tripple up your Aux's and just Sequence less Synths from 
each P3.  So instead of sequencing 8 synths
from my P3, I'll be Sequencing 4 synths from each P3.  Would I like to 
do all of this on 1 P3, yep!  But I don't think
CPU and ROM upgrades is something he's going to do.

 >>It was the same with drone in the begining, p3 didnt have 13 lenght 
nither.
Same with Polyphony.  And to be honest, i'm fairly confident the code to 
add length of 13/drone is MUCH smaller then adding the Chord inputting
method that you detailed.  Somewhere, the P3 will have to store the type 
of chords you want. That will eat away RAM and/or ROM depending on
how it's implemented.

 >>Melodic part of all my music that I do, is from chords and drones and 
I love using P3, just piss me off big time, to set chords from auxes all 
the time.
 >>My old QY70 trigers some fat chords and riffs so good that I had to 
take it back from my little brother that I gave for present lont time ago.
 >>I also use sx chorader for chords because setting an auxes for chords 
is just nightmare.

Whew.. at least you have some work arounds.  The rest of us just sit 
down at our P3 and program them in or input them with a keyboard,
as I described them in the earlier keyboard..
I also think you can do something similiar with the MC-909 if you are 
looking for another method as well.

 >>P3 needs chords step pattern and chords scale menu because it can do 
it easily.
I'm guessing this statement is incorrect.  If there isn't enough code 
space to put this, it is very difficult to add it.  Try adding
water to a full glass and see what happens.  Something has to come 
out.    I'm guessing that what you want will be delayed
to the P4.

I would love it on the P3 as well, but I'm just trying to be realistic 
as to what will most likely come out.    Definitely count me as
a Plus 5 (for the 5 that we've got here between the heads) for this 
feature, but it doesn't look like it going to be something that could
be implmented until the P4.


Cheers,
Dave

To me is the only feature to  have the ultimate minimal machine and  say bye to computers forever.


If there only a remaining code , If Colin agree it coul be a last update for us,lovers of that feature sacrifing all upcoming ones leaving
other people right to choose delay etc.


I could  firm rigt now, I don´t need any other feature that chord mode. We five could even pay Colin for his effort to achieve that,agree?

It just come to my mind early house and G force,Robert Hood records and I´ll it again with just a P3!

Hans
________________________________
> To: analogue-sequencer@yahoogroups.com
> From: dave@RenegadeRhythms.com
> Date: Tue, 6 May 2008 13:37:20 -0700
> Subject: Re: [analogue-sequencer] Chords on P3
> 
> 
> Hi Zed,
> Comments inline:
> 
> Zed Velkovich wrote:
> 
>>>3P is already polyphonic sequencer,
> I'm not sure if you are aware or not, but the P3 didn't start as a
> Polyphonic Step Sequencer. It started as
> a Monophonic Step Sequencer. Polyphony was added later. I remember when
> it was added and I remember
> my exitement when hearing about it. I myself, several years ago
> requested for
> an improvement in utilizing the Chords with the P3 similar to what you
> have requested and it was shot down
> then due to code space. I'm sure there is even less code space now then
> 2 years ago.
> 
>>>why do I need to spend memory and tiiiimmmeee for 3 auxes, to get one
> chord (how for 5-7 note chord)?
> Because that is how the P3 stores it's information. As indicated above,
> the P3 was originally designed for Monophonic
> use and then it was determined that if one used the Aux parts to hold
> other Notes that one could create Chords and
> hence P3 Polyphony was created. The other reason is because with the
> limited code space, that is how it is. He would
> have to restructure they way the P3 stores its information and uses it.
> Sometimes things are very easy to say in words
> but when it gets to actual coding around the current design, they can be
> very difficult.
> If you want chords/polyphony on a track with the P3,
> then these are steps to achieve it. If you don't want to spend the
> memory or tiiiimmmmmeeeee then
> you can stick to monophonic sequences? For a 6-8 note chord, you need
> to redirect your Auxes from another Track
> to the Track that you want the additional Polyphony from for notes 6, 7,
> & 8 ( I believe Aux A will be Redirect
> to Track and then Aux B, C, D are for your chords.). 1 -5 can be done
> on the original track.
> 
>>>I would rather use auxes for midi delays, echoes, than just for chord.
> I as well. Thank goodness that Colin added the ability to redirect Aux
> to other Tracks. So for example,
> you can use Track 1 to create a 5 note chord, Track 2 to create add 3
> more notes to Tracks1's Chord, and Track 3 to have
> it's Aux' redirected to Track 1 to do their funky goodness. I think
> now you can start to understand why I have
> 2 P3's (as soon as I build my 2nd one). There's more then I want to do
> than is available on a track. So you
> double up or tripple up your Aux's and just Sequence less Synths from
> each P3. So instead of sequencing 8 synths
> from my P3, I'll be Sequencing 4 synths from each P3. Would I like to
> do all of this on 1 P3, yep! But I don't think
> CPU and ROM upgrades is something he's going to do.
> 
>>>It was the same with drone in the begining, p3 didnt have 13 lenght
> nither.
> Same with Polyphony. And to be honest, i'm fairly confident the code to
> add length of 13/drone is MUCH smaller then adding the Chord inputting
> method that you detailed. Somewhere, the P3 will have to store the type
> of chords you want. That will eat away RAM and/or ROM depending on
> how it's implemented.
> 
>>>Melodic part of all my music that I do, is from chords and drones and
> I love using P3, just piss me off big time, to set chords from auxes all
> the time.
>>>My old QY70 trigers some fat chords and riffs so good that I had to
> take it back from my little brother that I gave for present lont time ago.
>>>I also use sx chorader for chords because setting an auxes for chords
> is just nightmare.
> 
> Whew.. at least you have some work arounds. The rest of us just sit
> down at our P3 and program them in or input them with a keyboard,
> as I described them in the earlier keyboard..
> I also think you can do something similiar with the MC-909 if you are
> looking for another method as well.
> 
>>>P3 needs chords step pattern and chords scale menu because it can do
> it easily.
> I'm guessing this statement is incorrect. If there isn't enough code
> space to put this, it is very difficult to add it. Try adding
> water to a full glass and see what happens. Something has to come
> out. I'm guessing that what you want will be delayed
> to the P4.
> 
> I would love it on the P3 as well, but I'm just trying to be realistic
> as to what will most likely come out. Definitely count me as
> a Plus 5 (for the 5 that we've got here between the heads) for this
> feature, but it doesn't look like it going to be something that could
> be implmented until the P4.
> 
> Cheers,
> Dave
> 
> 
> Messages in this topic 
_________________________________________________________________
Tecnología, moda, motor, viajes,…suscríbete a nuestros boletines para estar siempre a la última
http://newsletters.msn.com/hm/maintenanceeses.asp?L=ES&C=ES&P=WCMaintenance&Brand=WL&RU=http%3a%2f%2fmail.live.com

Sorry about my indian english folks, I forgot a lot!
----------------------------------------
> To: analogue-sequencer@yahoogroups.com
> From: turbotron69@hotmail.com
> Date: Wed, 7 May 2008 05:15:48 +0200
> Subject: RE: [analogue-sequencer] Chords on P3
> 
> 
> To me is the only feature to  have the ultimate minimal machine and  say bye to computers forever.
> 
> 
> If there only a remaining code , If Colin agree it coul be a last update for us,lovers of that feature sacrifing all upcoming ones leaving
> other people right to choose delay etc.
> 
> 
> I could  firm rigt now, I don´t need any other feature that chord mode. We five could even pay Colin for his effort to achieve that,agree?
> 
> It just come to my mind early house and G force,Robert Hood records and I´ll it again with just a P3!
> 
> Hans
> ________________________________
>> To: analogue-sequencer@yahoogroups.com
>> From: dave@RenegadeRhythms.com
>> Date: Tue, 6 May 2008 13:37:20 -0700
>> Subject: Re: [analogue-sequencer] Chords on P3
>> 
>> 
>> Hi Zed,
>> Comments inline:
>> 
>> Zed Velkovich wrote:
>> 
>>>>3P is already polyphonic sequencer,
>> I'm not sure if you are aware or not, but the P3 didn't start as a
>> Polyphonic Step Sequencer. It started as
>> a Monophonic Step Sequencer. Polyphony was added later. I remember when
>> it was added and I remember
>> my exitement when hearing about it. I myself, several years ago
>> requested for
>> an improvement in utilizing the Chords with the P3 similar to what you
>> have requested and it was shot down
>> then due to code space. I'm sure there is even less code space now then
>> 2 years ago.
>> 
>>>>why do I need to spend memory and tiiiimmmeee for 3 auxes, to get one
>> chord (how for 5-7 note chord)?
>> Because that is how the P3 stores it's information. As indicated above,
>> the P3 was originally designed for Monophonic
>> use and then it was determined that if one used the Aux parts to hold
>> other Notes that one could create Chords and
>> hence P3 Polyphony was created. The other reason is because with the
>> limited code space, that is how it is. He would
>> have to restructure they way the P3 stores its information and uses it.
>> Sometimes things are very easy to say in words
>> but when it gets to actual coding around the current design, they can be
>> very difficult.
>> If you want chords/polyphony on a track with the P3,
>> then these are steps to achieve it. If you don't want to spend the
>> memory or tiiiimmmmmeeeee then
>> you can stick to monophonic sequences? For a 6-8 note chord, you need
>> to redirect your Auxes from another Track
>> to the Track that you want the additional Polyphony from for notes 6, 7,
>> & 8 ( I believe Aux A will be Redirect
>> to Track and then Aux B, C, D are for your chords.). 1 -5 can be done
>> on the original track.
>> 
>>>>I would rather use auxes for midi delays, echoes, than just for chord.
>> I as well. Thank goodness that Colin added the ability to redirect Aux
>> to other Tracks. So for example,
>> you can use Track 1 to create a 5 note chord, Track 2 to create add 3
>> more notes to Tracks1's Chord, and Track 3 to have
>> it's Aux' redirected to Track 1 to do their funky goodness. I think
>> now you can start to understand why I have
>> 2 P3's (as soon as I build my 2nd one). There's more then I want to do
>> than is available on a track. So you
>> double up or tripple up your Aux's and just Sequence less Synths from
>> each P3. So instead of sequencing 8 synths
>> from my P3, I'll be Sequencing 4 synths from each P3. Would I like to
>> do all of this on 1 P3, yep! But I don't think
>> CPU and ROM upgrades is something he's going to do.
>> 
>>>>It was the same with drone in the begining, p3 didnt have 13 lenght
>> nither.
>> Same with Polyphony. And to be honest, i'm fairly confident the code to
>> add length of 13/drone is MUCH smaller then adding the Chord inputting
>> method that you detailed. Somewhere, the P3 will have to store the type
>> of chords you want. That will eat away RAM and/or ROM depending on
>> how it's implemented.
>> 
>>>>Melodic part of all my music that I do, is from chords and drones and
>> I love using P3, just piss me off big time, to set chords from auxes all
>> the time.
>>>>My old QY70 trigers some fat chords and riffs so good that I had to
>> take it back from my little brother that I gave for present lont time ago.
>>>>I also use sx chorader for chords because setting an auxes for chords
>> is just nightmare.
>> 
>> Whew.. at least you have some work arounds. The rest of us just sit
>> down at our P3 and program them in or input them with a keyboard,
>> as I described them in the earlier keyboard..
>> I also think you can do something similiar with the MC-909 if you are
>> looking for another method as well.
>> 
>>>>P3 needs chords step pattern and chords scale menu because it can do
>> it easily.
>> I'm guessing this statement is incorrect. If there isn't enough code
>> space to put this, it is very difficult to add it. Try adding
>> water to a full glass and see what happens. Something has to come
>> out. I'm guessing that what you want will be delayed
>> to the P4.
>> 
>> I would love it on the P3 as well, but I'm just trying to be realistic
>> as to what will most likely come out. Definitely count me as
>> a Plus 5 (for the 5 that we've got here between the heads) for this
>> feature, but it doesn't look like it going to be something that could
>> be implmented until the P4.
>> 
>> Cheers,
>> Dave
>> 
>> 
>> Messages in this topic 
> _________________________________________________________________
> Tecnología, moda, motor, viajes,…suscríbete a nuestros boletines para estar siempre a la última
> http://newsletters.msn.com/hm/maintenanceeses.asp?L=ES&C=ES&P=WCMaintenance&Brand=WL&RU=http%3a%2f%2fmail.live.com
> ------------------------------------
> 
> Yahoo! Groups Links
> 
>  To visit your group on the web, go to:
>     http://groups.yahoo.com/group/analogue-sequencer/
> 
>  Your email settings:
>     Individual Email | Traditional
> 
>  To change settings online go to:
>     http://groups.yahoo.com/group/analogue-sequencer/join
>     (Yahoo! ID required)
> 
>  To change settings via email:
>     mailto:analogue-sequencer-digest@yahoogroups.com 
>     mailto:analogue-sequencer-fullfeatured@yahoogroups.com
> 
>  To unsubscribe from this group, send an email to:
>     analogue-sequencer-unsubscribe@yahoogroups.com
> 
>  Your use of Yahoo! Groups is subject to:
>     http://docs.yahoo.com/info/terms/
> 

_________________________________________________________________
La vida de los famosos al desnudo en MSN Entretenimiento
http://entretenimiento.es.msn.com/

> 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

________________________________
> To: analogue-sequencer@yahoogroups.com
> From: colin@sequentix.com
> Date: Wed, 7 May 2008 23:50:04 +0100
> Subject: RE: [analogue-sequencer] Chords on P3
> 
> 
>> 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
> 
> 
> 
> Messages in this topic 



Thanks Colin,

 I appreciate that. I case it doesn´t fit.. just two thinks. The way it´s been implemented already works for me,but as non keyboardist,note chords are not triggered on time quantized but a rookie player sound.

If not either Could I suggest a custom OS for 5 demanding ones with chords as other user suggested that nice knob mode?

In order to get enough space I´ll choose some features I never use or will use insted and those would be deleted( example I own 4 different dedicated delay machines Why should I need a terrible sounding midi delay? I know if is not implemented yet..
. I could wire you some money for your time and effort as I always wanted the " ultimate minimal detroit step one box sequencer" and I would like to come back to producing.

Best;

Hans
_________________________________________________________________
MSN Noticias
http://noticias.msn.es/comunidad.aspx

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]

I agree, I just need two or 3 user definable chords, that´s minimal house.Don´t need to sequence an Angelo  Baladamenti soundtrack with a P3 LOL

Hans
________________________________
> To: analogue-sequencer@yahoogroups.com
> From: lists@ericsmits.nl
> Date: Fri, 9 May 2008 12:45:39 -0700
> Subject: Re: [analogue-sequencer] Chords on P3 - idea
> 
> 
> Hi,
> I would be VERY happy with a number of preset chords too! Howmany presets do you think would fit?
> If there is space for 1 user defined chord per track that would be perfect of course...
> 
> I've not tried this yet: On the RM1X there are ghost tracks if I recall correctly. These play the same pattern only transposed by a number of notes +/-. Could this be done with the auxes? Global for a track and later individually set per step?? We could then do 5-note chords (root + 4 auxes).
> Maybe this could be a solution too?
> 
> Hope it helps. Good luck with the garage --> workshop/studio conversion... :-)
> Eric
> 
> ----- Original Message -----
> From: Colin Fraser
> To: analogue-sequencer@yahoogroups.com
_________________________________________________________________
MSN Noticias
http://noticias.msn.es/comunidad.aspx

----------------------------------------
> From: turbotron69@hotmail.com
> To: analogue-sequencer@yahoogroups.com
> Subject: RE: [analogue-sequencer] Chords on P3 - idea
> Date: Fri, 9 May 2008 18:42:46 +0200
> 
> 
> I agree, I just need two or 3 user definable chords, that´s minimal house.Don´t need to sequence an Angelo  Baladamenti soundtrack with a P3 LOL
> 
> Hans
> ________________________________
>> To: analogue-sequencer@yahoogroups.com
>> From: lists@ericsmits.nl
>> Date: Fri, 9 May 2008 12:45:39 -0700
>> Subject: Re: [analogue-sequencer] Chords on P3 - idea
>> 
>> 
>> Hi,
>> I would be VERY happy with a number of preset chords too! Howmany presets do you think would fit?
>> If there is space for 1 user defined chord per track that would be perfect of course...
>> 
>> I've not tried this yet: On the RM1X there are ghost tracks if I recall correctly. These play the same pattern only transposed by a number of notes +/-. Could this be done with the auxes? Global for a track and later individually set per step?? We could then do 5-note chords (root + 4 auxes).
>> Maybe this could be a solution too?
>> 
>> Hope it helps. Good luck with the garage --> workshop/studio conversion... :-)
>> Eric
>> 
>> ----- Original Message -----
>> From: Colin Fraser
>> To: analogue-sequencer@yahoogroups.com
> _________________________________________________________________
> MSN Noticias
> http://noticias.msn.es/comunidad.aspx

_________________________________________________________________
MSN Video. 
http://video.msn.com/?mkt=es-es

Hi,
I would be VERY happy with a number of preset chords too! Howmany presets do you think would fit?
If there is space for 1 user defined chord per track that would be perfect of course...

I've not tried this yet: On the RM1X there are ghost tracks if I recall correctly. These play the same pattern only transposed by a number of notes +/-. Could this be done with the auxes? Global for a track and later individually set per step?? We could then do 5-note chords (root + 4 auxes).
Maybe this could be a solution too?

Hope it helps. Good luck with the garage --> workshop/studio conversion... :-)
Eric

  ----- Original Message ----- 
  From: Colin Fraser 
  To: analogue-sequencer@yahoogroups.com 
  Sent: Wednesday, May 07, 2008 3:50 PM
  Subject: RE: [analogue-sequencer] Chords on P3



  > 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]

I would love to see what ever you could try....

Dave

Colin Fraser wrote:

>
>
>
> 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 <http://www.sequentix.com>
>
> .
>
> .
>
>

> ----------------------------------------
> > From: turbotron69@...

> > I agree, I just need two or 3 user definable chords, that´s
minimal house.

Your house isn't quite minimal if your using big 3 note chords.
Pffft. There's 2 whole notes in there you don't need :)

I've used chords a lot on my P3s- I may have been one of the first to
ask for these particular aux events, & was certainly one of the first
to ask for them to be live-recordable.
so- I have a couple of ideas.

if it's possible to have an aux event that works in tandem with the
FTS settings to produce /on a single aux/ a choice of minor & major
triads, then this- along with the other aux(es) set to play aux notes
as usual, ought to take care of most requirements. probably plenty.

OR- I would like for there to be a way- let's call it an
"aux-setup-macro"- to quickly assign favourite groups of aux
functions. at the moment, one has to do this by copy/paste of empty
tracks. if there were enough code & a clever use of the UI to
implememnt it, the "user aux configs" could be stored in the same way
as the current aux configs, under a step button & in a scrolly list thing.

or we could have a poll on the most useful groupings of aux configs &
have all of them under a single step-key in a scrolly list.

personally, I'd like to hold the shift key & press the aux mode button
several times- it would work it's way through the four auxes, then  go
to A & B together, A & C together, A & D together, A, B & C together &
so on, with the aux assignment chosen thereafter being the same for
the thusly chosen auxes.

of course, being greedy & having an octopus here too, I'd like to be
able to "strum" the chords.... :-)

but I think the P3's pretty damn good already.

duncan.

Sure I mean three notes chord as maximun, other was for ambient soundscapes.!
> 
>> ----------------------------------------
>>> From: turbotron69@...
> 
>>> I agree, I just need two or 3 user definable chords, that´s
> minimal house.
> 
> Your house isn't quite minimal if your using big 3 note chords.
> Pffft. There's 2 whole notes in there you don't need :)
> 
> 
> 
> Messages in this topic 
_________________________________________________________________
MSN Noticias
http://noticias.msn.es/comunidad.aspx

> if it's possible to have an aux event that works in tandem with the
> FTS settings to produce /on a single aux/ a choice of minor & major
> triads, then this- along with the other aux(es) set to play aux notes
> as usual, ought to take care of most requirements. probably plenty.

This is sort of what I was thinking of.
Each aux has a 7 bit value range, so I was going to assign a particular
interval to each bit.
These might be minor third, major third, fourth, fifth, sixth, minor
seventh, and major seventh.
You'd be able to select any combination of those on top of the primary note.
That would certainly be the most code efficient way to do it.

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

Wouldn’t it be even more efficient just use each bit for a chord type?
Major, minor, augmented, diminished, etc. with some 4th, sixth, and
sevenths, thrown in and just use the note value as the root?  If you wanted
to get fancy one of the other auxs could set the voicing/inversion.  I have
a hard time believing that we really need completely user configurable
chords with the number of chord types you could easily pack into 7 bits. It
seems really clunky to have to enter the chord data individually for each
step.   I guess when I’m composing with chords, I’m thinking in terms of
the chord blocks themselves instead of the actual notes that make them up.
But, that’s just me…



James R. Coplin
(郭杰明)

***************************************
Work is the Curse of the Drinking Class
***************************************

From: analogue-sequencer@yahoogroups.com
[mailto:analogue-sequencer@yahoogroups.com] On Behalf Of Colin Fraser
Sent: Saturday, May 10, 2008 1:25 PM
To: analogue-sequencer@yahoogroups.com
Subject: RE: [analogue-sequencer] Re: Chords on P3 - idea




> if it's possible to have an aux event that works in tandem with the
> FTS settings to produce /on a single aux/ a choice of minor & major
> triads, then this- along with the other aux(es) set to play aux notes
> as usual, ought to take care of most requirements. probably plenty.

This is sort of what I was thinking of.
Each aux has a 7 bit value range, so I was going to assign a particular
interval to each bit.
These might be minor third, major third, fourth, fifth, sixth, minor
seventh, and major seventh.
You'd be able to select any combination of those on top of the primary note.
That would certainly be the most code efficient way to do it.

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





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

Yes, user definable chords is the way not preset ones.

How difficult would be to implement this way?

You press the " chord comb/button" on the P3 then you press the chord on the keyboard  and voila!!
That in step mode recording

Hans
________________________________
> To: analogue-sequencer@yahoogroups.com
> From: james@ticalun.net
> Date: Sat, 10 May 2008 14:32:31 -0500
> Subject: RE: [analogue-sequencer] Re: Chords on P3 - idea
> 
> 
> Wouldn’t it be even more efficient just use each bit for a chord type?
> Major, minor, augmented, diminished, etc. with some 4th, sixth, and
> sevenths, thrown in and just use the note value as the root? If you wanted
> to get fancy one of the other auxs could set the voicing/inversion. I have
> a hard time believing that we really need completely user configurable
> chords with the number of chord types you could easily pack into 7 bits. It
> seems really clunky to have to enter the chord data individually for each
> step. I guess when I’m composing with chords, I’m thinking in terms of
> the chord blocks themselves instead of the actual notes that make them up.
> But, that’s just me…
> 
> James R. Coplin
> (郭杰明)
> 
> ***************************************
> Work is the Curse of the Drinking Class
> ***************************************
> 
> From: analogue-sequencer@yahoogroups.com
_________________________________________________________________
La vida de los famosos al desnudo en MSN Entretenimiento
http://entretenimiento.es.msn.com/

Hi list;

What features you don´t use on the P3?  Just to know whic ones could be sacrificed in order to achieve more space for chords,per example.

I never used playlist and some " advance" features for composing " tracks" or " songs".. but half a bar 6 sequences at the time triggering lots of analogues etc.


By the way,it´s been talked about using the P3 kinda 909 drum sequencer Can someone  resume me that? It could be impressive to sequence my midi 808 with this user programable shuffle per note!

Hans
_________________________________________________________________
La vida de los famosos al desnudo en MSN Entretenimiento
http://entretenimiento.es.msn.com/