Idea for a Trigger Pattern Sequencer/Generator

Dieses Thema im Forum "mit Sequencer" wurde erstellt von MvKeinen, 28. Januar 2008.

  1. MvKeinen

    MvKeinen Tach

    Posted this on

    because translating into german would take me a while i post it in ENGLISH: Synth + Music. Dont know if i will take the time to translate it into german.


    I hope my english is good enough to describe what i got in mind...(i have to use a translationsite and my school english.. so some expressions might be "cyptic") every expression im not sure is italic. Correction wanted!

    imagine as a basis a 4 Track Step sequenzer with patternmemory. 4 triggerouts and 4 cv outs without soundgeneration. So thats nothing new. What would be new is a "non chaotic" random generator that is based on some legalities. These legalities can "take over" the playing pattern seamlessly by the turn of a knob.

    its an idea im carring with me for some years now:

    the figure/number 16 seems to be quite general in the digital world :cool:
    so is it in the musical world

    How about having 4 16bit bytes describing 4 16Step patterns. The value of these bytes will be calculated by a Generator described below

    byte1 1 0 0 1 0 0 1 0 1 0 1 0 0 1 0 0 = Bd
    byte2 0 0 0 0 1 0 0 1 0 1 0 0 1 0 0 0 = Sn1
    byte3 0 1 0 0 0 1 0 0 0 0 0 1 0 0 1 1 = Sn2
    byte4 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 = HiHat

    In this example the decimal value of the BD is

    Bd = bit1=32768+bit4=16384+bit7=512+bit9=128+bit11=32+bit14=4 = 49828

    One (of many) Question would be: Is there a chance to implement and apply certain musical legalities or possibilities in algorythmic form so that the relations between the bits can be etablished not only horizontally but also vertically among the tracks?

    every legality should have 3 Parameters to play live:
    X = case sensitive
    Y = case sensitive
    Z = number of legality priority

    legalities (vertically) like: (relations between the Tracks)
    - Sn & Bd never ON simultanously
    - Bd & HiHat only in X% of all cases simultanously ON
    - never more than X instruments simultanously ON
    - ..... (your idea in here:) )
    - ..... (your idea in here:) )

    legalities (horizontally) like: (relations between the steps of one Track)
    - X% propabillity StepY = ON. example: (Bd) step(1) = (80)% This legalities should be applyable on every Step (bit)
    - general propabillity X% of ON
    - ON every XSteps
    - having editable 3bit and 4bit bytes repeating
    - mirror every Xsteps
    - negative of Track NoX
    - delayed copy of Track NoX (Delay=Ysteps)
    - ..... (your idea in here:) )
    - ..... (your idea in here:) )

    competing legalities: its possible that one legality can not be combined with the other one.
    Setting up a priority hierarchy in every storeable set of legalities

    This priority hierarchy would be a powerful feature because it will be a very musical parameter.

    You tell the Bd to be ON every 3Steps with legalitiy (horizontally) NO3 X=3/Z(prio)=2
    You tell the Bd to be ON on Step1 with legalitiy (horizontally) NO1 X=1/Z(prio)=1
    You tell the Bd to be ON on Step13 with legalitiy (horizontally) NO1 X=12/Z(prio)=1

    X00X|00X0|0X0X|X00X|X0X0|0X00|X00X|00X0|XX00|X00X|00XX|0X00| Then repeating.
    by telling the Sn to be the negative of that and by telling the "Set of legalities" to restart after 64 Steps you got a simple Breakbeat.

    next Step: 2-dimensional legalities which is a combination of horizontal and vertical relationships. (haven't really worked that out completely ;-) )

    you define recurring Squares by the sidelenghts a x b
    b=instruments that are taking part in this operation
    for example a=3 & b=byte1/byte2/byte4

    byte1|* * * |* * * * * * * * * * * * *
    byte2|* * * |* * * * * * * * * * * * *
    byte3 * * * * * * * * * * * * * * * *
    byte4|* * * |* * * * * * * * * * * * *

    in this resulting square you can bring in preprogrammed or random patterns:

    100 001 101
    100 010 111
    100 001 101


    1001 0010 1011
    0001 0101 1110
    1000 0011 1010

    other possible 2-dimensional legalities:
    - diagonal lines of ON
    - treating the bits of a square (according to a*b) as one byte of a*b bits and apply 1-dimensional legalities (see above)
    - switching on and off every single bit of a square in the 16*4 padfield of the hardware. LIVE!!
    - your idea welcome here...


    every bit beeing ON (and thus sending a trigger to one of the 4 trigger outputs) should have an other value sent as cv on the 4 cv outputs.

    this is a value you can use for volume or other things.

    The legalities could be here:
    - cv voltage according to priority of the trigger-producing legality
    ( "important" triggers trigger louder sounds)
    - cv voltage according to the frequency of occurence of the trigger (also negated) (if you have 3 Bds one after one they can be turned down in the volume ( or having a hi pass filter cutoff a little bit higher so that there is less rumble)

    General Thoungts:
    - must be hardware!
    - legality (I start to hate this word I hope you can find me nother one ;-) ) -setups editable at the computer
    - possibility to program custom legalities.

    while legality setupping will be quiet extensive the playing of the machine will be fun by having a display showing the Name of (I begin to say "operation" <--- better word) name of the operation and turning the propability or the priority knob located below this name. Also the LEDed 4*16 buttons always showing the state of their corresponding bits. Manually switching of these buttons will be priority No 0 which is the most important. Also you should have the ability to record whats happening into the memory. After you recorded, every probability should be set to 0% so that you hear the recorded pattern. then you can begin with new operations ;-) to go forth.

    Memory structure:
    1024 Patterns
    256 operationcombinations :D

    hardware layout:

    4*16 Stepswitches (electribe kind) steps are stored within patterns
    4*16 knobs (endless pots) values are stored within patterns

    One might think:" how can that be musical?"
    I believe (and know) that it can be musical if you really know what you are doing.

    puh it took me really long to write this posting.
    I hope some of you take their time read it. I know that in programming this would probably a monster project. And about that i know nothing.

    Ideas, discussions, smilies ar destroying of my dream highly apreciated

    :D :D
  2. ACA

    ACA bin angekommen

    I'm not sure if i really get it.

    Should this be a sequencer with 4 standart lines, but with the ability to do some "random" sequences and this "random" Sequences can be set in in different relations to the 4 standard lines?

    Jedenfalls glaube ich das du dieses Thema besser im deutschen Teil des Forums unterbringst. Ins deutsch übersetzt wäre es auch verständlicher. Hier geht das unter.
  3. Moogulator

    Moogulator Admin

  4. jane doe

    jane doe Tach


    so im großen und ganzen verstehe ich es so, daß regelbasierend eine neubelegung der einzelnen schritte erfolgen soll.

    die regeln werden sowohl auf einzelne schritte bei einem instument [bd, sd, sd (warum zwei?), hh] angewendet, als auch ein- und ausschlüsse bei unterschiedlichen instrumenten beachtet.

    ich würde bei der programmierung nicht mit bytes oder bitwerten arbeiten für mich wären das für einzelne instumente jeweils skalare mit der länge 16.

    insgesammt habe ich das mit dem X und O noch nicht verstanden, vll wäre die deutsche originalbeschreibung zielführender.

Diese Seite empfehlen