Analogue-sequencer

"The 'note rng' settings allow you to set the base note and range covered by
the NOTE knobs when you are editing a pattern.
These are stored separately for each track.
How about a user config option that allows the note range for input to also
be enforced as a limit for randomised and accumulated notes ?"

could be a good work around - it certainly makes sense to do this on a track by track basis - of course it may be confusing if I forget it and wonder why the accumaltors aren't doing what I expect

Richard


  ----- Original Message ----- 
  From: Colin Fraser 
  To: analogue-sequencer@yahoogroups.com 
  Sent: Friday, September 15, 2006 10:14 AM
  Subject: RE: [analogue-sequencer] random limiters



  > What I would really like is to be able to set a high and low 
  > note limit for the random aux settings, so I could set 
  > velocity and pitch not to stray beyond a certain limit - I 
  > use the random features for all my work on the P3 but at the 
  > moment too many things can jump out in an out of control way. 
  > I could also for example set a cello part to be played on a 
  > sampler so it didn't stretch beyond the natural range of 
  > cello... I could compose a playable string quartet on the P3!!
  > 
  > I made various suggestions a few months ago about controlling 
  > randomness - most of which were judged too CPU or memory 
  > intensive - Surely this abilty to limit randomness just 
  > using two numbers would not be too expensive and it could be 
  > useful addition to other users than myself too? If so - do speak up

  Thinking about this, there is a relatively simple solution for note limiting
  that wouldn't take too much code space.
  The 'note rng' settings allow you to set the base note and range covered by
  the NOTE knobs when you are editing a pattern.
  These are stored separately for each track.
  How about a user config option that allows the note range for input to also
  be enforced as a limit for randomised and accumulated notes ?
  It would probably need a little finer control over the span than at present,
  but that wouldn't be too hard.

  > I also wonder of RNPNs are still in the pipeline?

  It's on the possible TBI list, but there are other things before it that are
  higher priority use of code space.

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



   

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