Analogue-sequencer

v3.974 adds some basic events that grab the current values from the 
knobs.
So far we have:
	knob n to velo
	knob n to leng
	knob n to auxC
	knob n to auxD

Knob numbers are from 1 to 32 - 1 to 16 are the bottom row, 17 to 32 
are the top.
These are very likely not to be the final list or implementation...
But have a play and see what you think.

Cheers,
Colin f

Please indulge my stupidity ... I'm trying to play around with this, and
read Paul's post about the Notron, etc, but I'm just not sure how this is
supposed to work.

Can someone supply some additional explanation?

Thanks,
Gene (how many brain cells have died? Dunno, can't figure it out)

> v3.974 adds some basic events that grab the current values from the
> knobs.
> So far we have:
> knob n to velo
> knob n to leng
> knob n to auxC
> knob n to auxD
> 
> Knob numbers are from 1 to 32 - 1 to 16 are the bottom row, 17 to 32
> are the top.
> These are very likely not to be the final list or implementation...
> But have a play and see what you think.
> 
> Cheers,
> Colin f
> 
> 
> 
> 
> 
> 
> 
> 
> Yahoo! Groups Links
> 
> 
> 
> 
>

hi Colin,

> v3.974 adds some basic events that grab the current values from the 
> knobs.

i've had a quick play around with it and it's way cool! assign the 
velocity of half the notes in a pattern to a knob, and play around 
with them;...one hell of a cool performance feature! i find the knob 
layout a bit weird though; i'd expect the top left knob to be #1 and 
the bottom right to be #32. also, the knob values are grabbed when in 
playlist edit as well as in play mode, which is annoying if you're 
setting transpose & repeats for a playlist step. i'd also like to see 
a definable range on the knobs, but i guess that's gonna be a hard 
one..but it would open up the possiblity of adding a 'grab note-value 
from knob N' event, which i can also see as being pretty cool; 
transposing a pattern up an octave on the fly...
another weirdness going on with these functions is that in playlist 
mode the knob values also appear to be scanned & translated to 
transpose & repeat values. not quite what's supposed to happen i 
assume?
about the rep*N thing; to be honest i've never tried in with tbase 
16. i'll give it a try tonight and let you know how i get on..
and i got the BAD DATA/BAD BLOCK messages during sysex transfers 
thing sorted; turns out i had an extra virtual midi port looping back 
in midi-OX. removed it and it all works fine now.

grtz Chiel

> i find the knob 
> layout a bit weird though; i'd expect the top left knob to be #1 and 
> the bottom right to be #32.

The knob numbering is what's used internally by P3.
Paul N suggested the events could be hard-coded to use the upper and lower
knobs for the track the pattern is on.
That makes sense, although it means you only get two knobs, or 4, if I
included the upper and lower knobs above the parts.
It would mean that the event value could be used for other things though -
such as a scale factor or offset, or even another event - so you could
configure multiple different events to happen, all grabbing their value from
the current knob position.
Too many possibilities...

> also, the knob values are grabbed when in 
> playlist edit as well as in play mode, which is annoying if you're 
> setting transpose & repeats for a playlist step.

Indeed. I'll need to add some code so the events are only active in playmode
- not hard.

> i'd also like to see 
> a definable range on the knobs, but i guess that's gonna be a hard 
> one..but it would open up the possiblity of adding a 'grab note-value 
> from knob N' event, which i can also see as being pretty cool; 
> transposing a pattern up an octave on the fly...

Grabbing the note accumulator value from a knob will allow this - you could
already grab aux C from a knob and assign aux C to offsel note abs. I'll add
a direct event for this though.

> another weirdness going on with these functions is that in playlist 
> mode the knob values also appear to be scanned & translated to 
> transpose & repeat values. not quite what's supposed to happen i 
> assume?

It is just a test build Chiel - thrown together quickly just to generate
ideas.
I'll slickify it in the next builds ;-)

Cheers,
Colin f

On Sat, 11 Sep 2004 17:52:56 +0100, "Colin f" <colin@colinfraser.com>
wrote:

>The knob numbering is what's used internally by P3.
>Paul N suggested the events could be hard-coded to use the upper and lower
>knobs for the track the pattern is on.
>That makes sense, although it means you only get two knobs, or 4, if I
>included the upper and lower knobs above the parts.

Oh yes. I though four per track rather than 32 to be used by any or
multiple tracks would be less confusing. Would love to hear
alternatives though. Anyone got any thoughts on this?

I just made a pattern where the top row of knobs selected event types
and the bottom row selected their amounts. Of course you turn them and
have no idea what event you selected nor the amount. And you could
program multiple tracks to use the same knobs too.. uhgggg
All of which was why I looked for something a little more simplistic
but still giving the knobs a useful purpose in play mode. Even if a
config default set them to control the four Auxes directly it might
still be cool - so you have a kind of "live sculpt" for them - perhaps
you could hit Record and sculpt them into the track? 

Seems like with just a little space left, we should think carefully
about how the knobs are used in this way. I have several competing
ideas of my own but there must be others?

And no, this wasn't a deliberate attempt to start a mass discussion
just prior to Colin going on hols.. 8)

Paul

---
Paul Nagle / Soft Room Music
Email: paul@softroom.co.uk www.softroom.co.uk
                           www.BogusFocus.com

> Oh yes. I though four per track rather than 32 to be used by any or
> multiple tracks would be less confusing. Would love to hear
> alternatives though. Anyone got any thoughts on this?

I can see reasons for both, and there are plenty slots in the event list
left, so I'll leave the events that can grab any knob, add a couple more of
those for note setting etc., but also add some that use the knobs above the
track keys.
 
> so you have a kind of "live sculpt" for them - perhaps
> you could hit Record and sculpt them into the track? 

An interesting idea - it would be simple enough to add a record option where
the upper and lower knobs above the track are recorded to auxes A and B, and
the knobs above the part keys recorded to C and D.
This would let you capture auxes over multiple patterns as you can do with
play mode record for notes...

> Seems like with just a little space left, we should think carefully
> about how the knobs are used in this way. I have several competing
> ideas of my own but there must be others?

I can't tell you how glad I'll be when the code space is finally full...
It'll be nice to able to say, "it's finished" ;-)

> And no, this wasn't a deliberate attempt to start a mass discussion
> just prior to Colin going on hols.. 8)

The hotel should have net access, so I'll still be 'around'. Just don't
expect any updates, I'll be drinking cocktails.

Cheers,
Colin f

On Mon, 13 Sep 2004 20:37:58 +0100, "Colin f" <colin@colinfraser.com>
wrote:

>I can see reasons for both, and there are plenty slots in the event list
>left, so I'll leave the events that can grab any knob, add a couple more of
>those for note setting etc., but also add some that use the knobs above the
>track keys.

Lovely - and some composites? I guard my auxes carefully and am always
greedy for more.. 8)
An event to turn off the results of the knob twiddling afterwards
would be ace if you can think of a way to do it. I think I thought of
one but... maybe I forgot now....
 
>> so you have a kind of "live sculpt" for them - perhaps
>> you could hit Record and sculpt them into the track? 
>An interesting idea - it would be simple enough to add a record option where
>the upper and lower knobs above the track are recorded to auxes A and B, and
>the knobs above the part keys recorded to C and D.
>This would let you capture auxes over multiple patterns as you can do with
>play mode record for notes...

Mmmmmm

>I can't tell you how glad I'll be when the code space is finally full...
>It'll be nice to able to say, "it's finished" ;-)

It's weird but once it's finished in this way, I'll feel I can really
start pushing it. At the moment I poke about with each new feature as
it comes - rather like when you get your first few modules of a
modular synth and use them to death until you get more. When the P3 is
complete it will be like the architecture is finalised and you can
then really work the system as a whole, if that makes sense.

>The hotel should have net access, so I'll still be 'around'. Just don't
>expect any updates, I'll be drinking cocktails.

8-)

Enjoy - you deserve it man,

Paul
---
Paul Nagle / Soft Room Music
Email: paul@softroom.co.uk www.softroom.co.uk
                           www.BogusFocus.com