Yahoo Groups archive

Analogue-sequencer

Index last updated: 2026-04-28 23:15 UTC

Thread

Re: [analogue-sequencer] New directions

Re: [analogue-sequencer] New directions

2003-10-14 by Colin f

> Why not support both? Many arpeggatiors have both options.
> Pendulum- and Pendulum+?

I most probably will. I was thinking of changing the current mode to the
non-repeating mode, since GBar can be used to keep the length sensible. I
thought I didn't have much space to store the direction settings per
pattern, but now I've found plenty space so it's not a problem to add lots
of options, except if it makes the UI too complicated.

> What's brownian direction, btw?

A random number is generated at the end of each step. There are weighted
probabilities that the sequence position will either stay the same, move
forward one step or move backward one step.
The name brownian was originally coined to describe the motion of particles
of pollen in a liquid by Robert Brown, a Scottish botanist. Google it, and
you'll find plenty of nice little Java applets that demonstrate the
phenomenon.

Cheers,
Colin f




________________________________________________
Message sent using UebiMiau 2.7.2

Re: [analogue-sequencer] New directions

2003-10-14 by Robert van der Kamp

On Tuesday 14 October 2003 09:57, Colin f wrote:

> I thought I didn't have
> much space to store the direction settings per pattern,
> but now I've found plenty space so it's not a problem to
> add lots of options, except if it makes the UI too
> complicated.

Will upgrading to a newer OS using these new pattern options 
invalidate currently stored patterns? Just curious. I still 
don't own a P3, I was waiting for the random direction mode 
to show up. So how's the state of that complete P3 kit, 
Colin?

> A random number is generated at the end of each step.
> There are weighted probabilities that the sequence
> position will either stay the same, move forward one step
> or move backward one step.

So brownian random mode is a random mode with different 
statistics?

- Robert

Re: New directions

2003-10-14 by ch.³l

hi Colin,
> thought I didn't have much space to store the direction settings per
> pattern, but now I've found plenty space so it's not a problem to 
> add lots of options, except if it makes the UI too complicated.

are you talking about lots of options for the direction settings or 
lots of options in general? because i'm finding that the 'quick mute 
access' from playlist edit mode is getting pretty high on my 'most 
wanted' list...as well as the user config option for 'keep 
destination mutes on part copy'..if they're at all possible of course.

oh and count me in for at least one 'MIDI CPU Experimentor'. 

grtz, Chiel

RE: [analogue-sequencer] Re: New directions

2003-10-14 by Colin f

> are you talking about lots of options for the direction settings or 
> lots of options in general?

I'm talking about being able to store more settings that apply
separately to every pattern.
Each pattern has 16 steps * 4 bytes plus a single byte for timebase and
length, and 4 bytes for aux config.
Each per pattern value needs 384 bytes, which is more than is left in P3
RAM.
But now I've realised half the 'length' byte is unused, there are 8
bytes per pattern extra to store settings in.
So I've used half a byte for direction. I can't really think of any
other per pattern settings I might add at the moment, but I'm sure Paul
Nagle can ;-)

> because i'm finding that the 'quick mute 
> access' from playlist edit mode is getting pretty high on my 'most 
> wanted' list...as well as the user config option for 'keep 
> destination mutes on part copy'..if they're at all possible of course.

The current list I'm working on is as follows (in the order I plan to do
them)

- direction: random, brownian, modified pendulum, reverse from step 1
- playlist edit record mode
- playlist edit quick mute access (but what keys to use... possibly the
step function switch ?)
- 'keep mutes on pc' user config option
- bank init
- access to playlist hold flags from play mode (could use step function
switch too)
- midi thru note to PXPos
- modified PXPos range

There were a couple of things I've been stuck with due to lack of RAM
space, but if I move the pattern aux config settings into the 'length'
space, I'll free up enough space to have more than 4 bits per part to
hold the PXPos setting, for example.
A couple of people have been wanting more range on that one...
That will need a backup and restore before upgrading though - as it
involves changing the location of data in RAM.

Cheers,
Colin f

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.