Pattern storage in sequencer

[sonomute]

Just like in drum machines... it will be nice to store patterns and recall it inside of module...i know i can sore the whole stack in preset change melody for example and store it again...but what if i want to build complicated melody line withe several parts and to parts parts randomly?

i was trying to put in stack several similar modules program parts of melodies in them and then with help of modulation sequencers stop and start them in different times but it not work, looks like if i`m changing runstate of one module i`m changing it for all song...

Thank you.

[jim]

Just like in drum machines... it will be nice to store patterns and recall it inside of module...i know i can sore the whole stack in preset change melody for example and store it again...but what if i want to build complicated melody line withe several parts and to parts parts randomly?


You can kinda do that now with module import/export, but it is a bit slow,
and there is no way to load settings into an existing module. Support for full-on 'module presets' with a dedicated browser is high on the 2.1 list...

i was trying to put in stack several similar modules program parts of melodies in them and then with help of modulation sequencers stop and start them in different times but it not work, looks like if i`m changing runstate of one module i`m changing it for all song...
.

Review the 'run mode' parameters in the doc (http://www.five12.com/doc/MonoNote.html), You probably just need to change the run mode to manual -- or switch to one of the triggered modes.

Cheers,
Jim

[ToniSpeck]

Just like in drum machines... it will be nice to store patterns and recall it inside of module...i know i can sore the whole stack in preset change melody for example and store it again...but what if i want to build complicated melody line withe several parts and to parts parts randomly?


+1

The idea of having stored hundreds of patterns, all organized in the browser is awesome. I could load a Kick, HiHat or Percursion sample in the Drum Kit and in the DrumSeq browse through gazillions of pre-made patterns until i find one the suits what i want. And also the ability to load midi files and save them as patterns would be great too.
That in conjunction with the DrumKit next/previous sample button as requested in other thread would be killer.

[steff3]

So, if you can store multiple patterns in a module how would you do that with a timeline?
I mean, I know what you mean - I always often thought about that but I think it is many useful for 'composing' and not really for playing back.
It is less convenient but functionally the same to use multiple stacks and split up your line over multiple stacks - that also works then with the timeline etc.

maybe it would be great to stack stacks (uuups) on top of each other as a display option which would make things easier ...

best

[jue]

Hello,

for me it makes more sense to have a seperate PatternGenerator
( Euclidean, chaos or something like that ) because then it could be
possible to use this patterns on all other Seqs.
Thinking of a ModulationSeq that is triggered by a PatternGenerator sending its
modulationvalues only at the generated times. This could be fully integrated to the timeline possibilities.
The second for me could be a GateSeq with a PatternStorage for save and load of let say preset patterns. With the same possibility to use it were you want not only with the DrumKit.

best
jue

[jim]

So, if you can store multiple patterns in a module how would you do that with a timeline?


There would still only be one pattern per preset in a module, so it doesn't affect timeline operation. Think of module presets as the Numerology equivalent of AU Presets: all the parameters for a single module, stored in a file. This is actually what is contained in a module export file is. The problem is that currently you have to import those settings as a new module-- you can't load those settings into an existing module. But if I make three changes, all of a sudden the export/import feature becomes much more powerful:

- Allow modules to load settings (parameters, samples, etc) from a ".nmod" module export file.
- Create a specific location for you to save all your module export files, grouped by module type
(just like /Library/Audio/Presets works for AU preset files).
- Create an easy-to-use browser for those files.

With those 3 things in place, you could have a sequence running, then open the module preset browser for that sequencer, see a list of all the presets available, and click through them until you find what you want. The same goes for DrumKits: start a pattern, then click through your kits until you find what you need. You could perhaps even keep multiple browser windows open, mixing and matching presets until you find the combination you like.

Cheers,
Jim

[jim]

for me it makes more sense to have a seperate PatternGenerator
( Euclidean, chaos or something like that ) because then it could be
possible to use this patterns on all other Seqs.
Thinking of a ModulationSeq that is triggered by a PatternGenerator sending its
modulationvalues only at the generated times. This could be fully integrated to the timeline possibilities.
The second for me could be a GateSeq with a PatternStorage for save and load of let say preset patterns. With the same possibility to use it were you want not only with the DrumKit.

I see this as being a related but separate function: the ability to bring up a window that lets you run some sort of algorithm (the Euclidean generator is the obvious choice) to generate a pattern, that you can then load into the module, possibly saving later as a preset. This could work well for algorithms that generate a pattern that you are then likely to tweak. It would not be appropriate for algorithms that need to run continuously, such as a finite automata simulation.

Jim

[jue]

Hello,
sorry not to be clear enough!

For shure I was thinking the same way as Jim, just generate one set of gates
up to 128 steps by a button and then let this pattern run.
If you like you can make changes/corrections and then save your new pattern.

best
jue

PS:Again sorry but now I am thinking about sending a gate to the generate butten to make a new pattern on the fly every 4/5/6/7 beats..........
I could not stopp thinking this way....

[adamj]

I see this as being a related but separate function: the ability to bring up a window that lets you run some sort of algorithm (the Euclidean generator is the obvious choice) to generate a pattern, that you can then load into the module, possibly saving later as a preset. This could work well for algorithms that generate a pattern that you are then likely to tweak.


This would be awesome! Perhaps Numerology could have some sort of embedded scripting language like python, ruby, or lua.

Or maybe there would be a way to provide some hooks so that power users could use the programming language of their choice from outside of Numerology. Perhaps if the right things were exposed via OSC. In fact, that might be the best approach. I could see every slider having an address that would be accessible over UDP. Like /stack1/mononote1/slider1 or something like that. Maybe the addresses could be somewhat configurable or based on the names entered by the user.

If you go the OSC route, I will gladly provide a Ruby Numerology library for people to use.