Regarding numbers already avaiable, maybe following implementation strategy could be interesting:
1- keeping all numbers as it is now (trigger numbers 1 or 0)
2- adding probability numbers as smaller red number in right bottom corner (Example: 0.78, or shorter saving some space .78, two decimals after comma should be enough for the probability precision I guess)
3- if probability is set to 1, this small number should not be displayed
4- implementation could use a multiplicative form current number (current_number: 1 or 0 only I guess, current_number * probability, if probability is not 1)
5- for saving strategy of those numbers, I am sure master saike, you will find best way (some multi-dimensional state-array maybe?)
Christmas has come early for you TonE. I just implemented probabilistic triggering in both SEQS and MIDI Arp.
In MIDI arp it's bound under scrollwheel (since there the blocks have no "settings" anyhow).
In SEQS it's bound to ctrl + scrollwheel. Note that I've also added a more informative tooltip if you forget.
Because there's not that much space and I didn't want to crowd the blocks unnecessarily, you can see the probability at a glance from how "full" the block is.
Please let me know if you find any bugs. I had to encode it in a bit of a funky way (bitmask yay), because I didn't want to add an additional array of data.
Wow, friend saike, thanks a lot! Have to test quickly. If all works nicely, as I am expecting from all your great tools and additions friend, this just adds another dimension to the probabilistic options available in Reaper.
1- probalocity (velocity used as probability value)
2- random note gate (note triggers passing by set probability value, added another output slider when notes are passed or blocked, using this slider for mapping to any fx parameter of any fx, so this is most general concept, can be applied anywhere)
3- now this above, saike SEQS and saike MIDI Arp. (I have to experiment here much more, seeing how this can sound cool, bringing more variety into a "static 1 bar or 0.5 bar loop")
4- gaussian humanizer (velocity and note onsets / timing)
?- maybe there are a few more probabilistic options, you can add below if you know some more
Added SEQS to a test project, increasing CPU from 1.8% to 48% (as a first quick comment)
Added Midi ARP to same project, crashed Reaper. (will test later more)
Midi ARP, second try did not crash, sounding very cool. Most left, bottom square could not be adjusted via mousewheel, other slots working nicely. Cool sound.
Added SEQS to a test project, increasing CPU from 1.8% to 48% (as a first quick comment)
Added Midi ARP to same project, crashed Reaper. (will test later more)
Midi ARP, second try did not crash, sounding very cool. Most left, bottom square could not be adjusted via mousewheel, other slots working nicely. Cool sound.
Yikes! Just adding it did that? o_o
I wonder wheter bitwise operations are really slow on Linux for some reason.
Any other JSFX plugins that have this effect on your system?
Trying again (in train all seems to be fine. Before it was a project with some stuff there, so the cpu problem source might be something else as well, audio inputs, other fx, was also experimenting with low latency mode, which is quite cool, if you want to play live, a guitar for example. More fun with less or almost no latency, making a big difference in terms of fun factor.
So all fine, experimentation can continue. Thanks a lot my friend.
Trying again (in train all seems to be fine. Before it was a project with some stuff there, so the cpu problem source might be something else as well, audio inputs, other fx, was also experimenting with low latency mode, which is quite cool, if you want to play live, a guitar for example. More fun with less or almost no latency, making a big difference in terms of fun factor.
So all fine, experimentation can continue. Thanks a lot my friend.
Awesome. I'll still have a look at the bottom left issue this weekend. Nevermind, found and fixed it already.
Quote:
Originally Posted by rafa1981
I will just randomly throw SEQS ideas to the bottom of your backlog. In order of personal preference, if that matters...
Cool.
Quote:
Originally Posted by rafa1981
- Pattern Swing/Shuffle.
Do you mean a toggle to have the sequence advance columns in a swing or shuffle manner? Or one that moves the blocks around in that manner?
Quote:
Originally Posted by rafa1981
- Comb filter (this one was pretty funny on CamelSpace).
Anything in particular about the comb filter in CamelSpace?
SEQS has a Karplus feedback with which you should be able to make combs.
I hadn't seen the Karplus. I don't remember exactly how the comb was, I assume a tuned delay line. It was useful for total sound transformations.
WRT to the swing, basically the same functionality that drum machines with step sequencers have. I think that under the hood they shift forward/backward the timing of every even time division. So of e.g. 1,2,3,4 2 and 4 get closer to the next division.
I don't know if you have Atlas2 or the Electribe plugin. Both do it.
Just added swing to SEQS and MIDI Arp. It's the last numeric control.
Thanks a lot for swing addition. -50 to +50 the value can be changed. If you load MIDI Rhythm Trainer (be careful, this disturbing the timing, should be last in chain maybe, after synths) jsfx after it you can see visually how the timing shifting is happening, for analysis and comparison purposes with other midi timing tools. Probability, yes, swing, yes, what else we can want? Not much left. Thanks a lot friend!
Now next question which is optimum value at which bpm for closed hihat for example? Is there any rule? Just by ear or is there a secret technique for typical working values?
For example: Metronome running here at 105 bpm, closed hihat sound, increased speed to 8, saike midi arp, swing amount 17 sounds good to me. In a different bpm same value would sound different I guess, so one needs to experiment blindly, or there is a secret technique which sounds always good? If there would be such a technique this could be built into the js maybe, as a next step... let us wait for user inputs and experiences. Very cool sounding swing now, great. Speed 4, at 105 bpm, swing amount 30, closed hihat sound.
Speed of saike ARP could go even further down a bit, if one would want to generate long notes with it. Ok this is not typical use case scenario.
Example: Hold some chord, e.g. using k-board smart keyboard hardware, via its toggle note feature, which means you hold 4 notes for example, any chord you like. That's it. But now, saike arp would help in following way, instead of playing constantly this exact same chord, it would do certain variations, based on its programming, adding or removing notes, switching octaves... just bringing a bit more variation, even what you did was entering a simple chord. This would be one use case of this slower arp feature.
speed 1 (what we have now) is 1 beats long. (can be useful for slower guitar picking like style, speed 2 a bit faster guitar picking arpeggio style)
speed 1/2 (not available yet) would be 2 beats long.
speed 1/4 (not available yet) would be 1 bar long.
speed 1/8 (not available yet) would be 2 bars long.
2 bars as maximum length (or minimum speed) should be enough, as we can connect anyway two cells to get longer durations, like 4 bars for example.
Another idea for saike arp: Would it make sense adding retrigger function of SEQS into saike arp, but for midi, not audio? Would be cool. Mostly I am splitting notes into two or three equal lengths, for which I set two key bindings already for midi editor (x splitting selected notes into two parts, c splitting selected notes into three parts). Retrigger function inside saike arp would do basically same, but now directly inside the arp, just another way of doing more or less same. For quick Tangerine Dream sequence pattern designs (Berlin School) this could be useful.
And yes, swing in saike arp, sounds magic! Thanks a lot.
One more thing. In saike SEQs, in Pitched Delay, having automation access to parameter "Pitch" would be cool. As manipulating this parameter sounds cool. Or did you publish "Pitched Delay" as separate jsfx as well?
UPDATE: Answering my question. SEQS is crazier and cooler than I though, Modulator A and B can be any parameter of any available fx, ooooo, magic. Thanks saike for another magic dimension. Unlimited craziness in one package. All filthers included.
Having modulator A and B in random mode, brings even more craziness. Where will this craziness dimension stop? Thanks a lot! Nobody can complain about same repetitive patterns any more. Using SEQS with lower speed values (when randomizing enabled on modulator A and B) like 1 (current minimum) seems to bring more interesting results. So same as with arpeggiator above, slower speeds also here could be interesting.
Last edited by TonE; 12-27-2022 at 04:28 AM.
Reason: added idea for Pitched Delay, pitch parameter automation, saike SEQs is craziness pure
The use case for lower speeds never occurred to me. I've added support for them now. They go down to 1/8 now on both SEQS and MIDI Arp.
I think retrigger would be cool for midi arp, but it's a relatively big feature because of the way midi arp is written. I'll think about it.
I've also extended the tooltip for modulators a bit for SEQS, to hopefully make more people aware that you can in fact automate nearly all parameters with the modulator section
No problem regarding retrigger in arp, if too complicated. There is x and c key bindings anyway for me in midi editor.
Thanks a lot for slower speeds addition. Regarding my story in slow speeds. I knew from somewhere a program called Wizard Master Control Program, tiny program with great step sequencing capabilities, logarithmic bpm, and going up to 99999 bpm, and going down very low as well. Then I asked if Phil (Tipping), developer of Sequetron, can add logarithmic bpm also to Sequetron, which he did, thanks to Phil again from here, which goes also up to 99999 bpm, he made a youtube demonstration even with such speeds , so I knew logarithmic bpm can be interesting. Then I wanted to have this in Reaper as well. Put together a logarithmic bpm table and shared in this forum somewhere, which takes as input midi program change events, going to oscii-bot, converting to osc, going to Reaper, changing tempo based on incoming osc events. So we have such speeds in Reaper as well. However first time I tried with Reaper it could go up to around 4000 bpm, then it went down to around 999 bpm, not sure what is the current max bpm value in Reaper. Anyway, you can go slower and slower as well, like stopping time. Then what is happening is, you are changing the relationship between midi based programming / changes in sound and synth patch based changes in sound, so you hear more and more only the synth based programming in the sound, as the other notes are almost non-existent, coming from time to time, at 2 bpm, for example. If you want to experiment with ambient style very long notes, this can be useful. Then you can design more slow envelope transitions, going up, down, fade in, fade out, layering... pitchbending slowly up and down, but holding the pitchbend value, not releasing again...
What I also discovered while using logarithmic bpm's, at certain bpm values you find some optimum tempo for a given rhythm, or melody, so changing bpm in such "bigger" steps can be useful for such unexpected optimal tempo discoveries.
As a related note, developer of airwindows did a plugin which deals with pi based bpm values, up to three decimal precision, so those can be interesting as well regarding bpm experiments.
As a summary:
- logarithmic bpm and
- pi based bpm (3 demical precision)
- higher speeds up to 99999 bpm
- lower speeds down to 2 bpm
can be interesting for experiments. Maybe not in Reaper, but in Wizard Master Control Program and Sequetron by Phil Tipping. Have fun friends, thanks for reading.
Anyway, slower tempos, with random activated on modulater A and B, probability down on certain longer steps (2-3 steps), then automation drawing on SEQS "Current speed" parameter more dancing around slow tempo ranges, occasionally getting faster, can lead to good fx modulation results. Assigning of modulator A,B parameters to taste targets. Tape stop, Retrigger, Pitched Delay, for example.
Last edited by TonE; 12-27-2022 at 11:10 AM.
Reason: added last paragraph
We could start composition competitions , only allowed tools:
- Surge XT vst
- RS5k, with 1 sample of your choice
- saike arp
- saike SEQS
- 1 chord allowed, up to 5 notes
- nothing more allowed
The idea is, what can you do from 1 chord, using saike arp and SEQS, using Surge XT (because of its variety in sound capabilities) plus 1 sample in RS5k.
1 chord, 1 synth (Surge XT), 1 sample + saike arp and SEQS.
I wanted to quickly program with saike arp each 4 bars a CC 123, just to discover it has same midi cc limitation as Reaper midi editor has, stopping at cc 119, rather than going up to 127.
Let me check megababy then. Would be cool if saike arp could do it as well.
Another idea for saike ARP. Having randomize feature of SEQS for saike ARP's cc lanes would be cool. Current randomize feature of saike ARP can be kept, additionally the SEQS style randomization, where it changes permanently, without requiring any clicks.
Another idea for saike ARP: It could have a MIDI output channel parameter. Values: As incoming (this is what we have now, only), but then additionally selecting one specifici midi output channel 1..16. Same for midi input channel. Any input midi channel (what we have now), or selecting a specific one. More advanced would be clickable free combination of input midi channels (if led is on, input from this input midi channel is accepted and processed, else blocked, meaning passed through without any processing)
Why this can be useful? If you load multiple saike ARP, sequentially into same track, or sequential chain, by specifying those midi input and output channels you could use all together.
Typical use case would be:
- first saike arp would accept midi from any midi channel.
- next saike arps would be based on what is output by first (or previous) arp(s). Or any, if it should depend on previous arps. Or instead, a specific one, selected orthogonally, outside the output range of previous arps, so it behaves independently, so different speed for example.
Its advantages would be you can generate slow, fast, high, low, all with different probabilities, all triggered from same midi input source. Even with swing. Thanks saike again, for this and all the other great tools you develop and share!
Important for this feature is saike arp should be usable in a sequential form. Most advanced implementation would be something like:
17 buttons for midi input channel activation (16 channels + any + rest (passed through non-processed))
17 buttons for midi output channel activation (16 channels + as incoming)
If you would select midi output channels 1 and 3 for example, saike arp would get a midi multiplipier in this case, the processed midi events would be copied to both midi channel outputs. Or at least output should be as input midi channel. I hope you get the idea...
Hmm, still thinking, maybe the midi routing should be done simply via tracks and multi-channel routing, then it is later much easier remapping the items, just move to another track. More flexible and you see what item is going where. From visual point of view more flexible. So above features are not really required, if you learned saike arp is always outputting on midi channel 1, and you need to do your midi channel routings yourself elsewhere, e.g. as mentioned in this paragraph via new tracks with multi-routing.
I wanted to quickly program with saike arp each 4 bars a CC 123, just to discover it has same midi cc limitation as Reaper midi editor has, stopping at cc 119, rather than going up to 127.
Let me check megababy then. Would be cool if saike arp could do it as well.
Another idea for saike ARP. Having randomize feature of SEQS for saike ARP's cc lanes would be cool. Current randomize feature of saike ARP can be kept, additionally the SEQS style randomization, where it changes permanently, without requiring any clicks.
There's a good reason for this. CCs above 119 are reserved for special meanings (things like all sounds off, all controllers off etc). I don't really think it's a good idea to use those for programming.
Quote:
Originally Posted by TonE
Another idea for saike ARP. Having randomize feature of SEQS for saike ARP's cc lanes would be cool. Current randomize feature of saike ARP can be kept, additionally the SEQS style randomization, where it changes permanently, without requiring any clicks.
Right mouse click on the label of that row and enable "Randomize after bar". Also supported for mod and vel now.
Quote:
Originally Posted by TonE
Another idea for saike ARP: It could have a MIDI output channel parameter. Values: As incoming (this is what we have now, only), but then additionally selecting one specifici midi output channel 1..16. Same for midi input channel. Any input midi channel (what we have now), or selecting a specific one. More advanced would be clickable free combination of input midi channels (if led is on, input from this input midi channel is accepted and processed, else blocked, meaning passed through without any processing)
You can now set the input/output channel. Right mouse button on the top row will give you a list to choose from. Note that you have to click to the left of CC (because there the right mouse button has a meaning).
Dear saike, thanks a lot, will test soon. Regarding CC, yes I know their meaning, and exactly for this meaning I want to use those, but can not, no problem, megababy step sequencer can do it. This is an acceptable workaroud. Imo we should construct our solutions, systems, anyway using multiple tools, like unix command line philosophy, not depending too much on a single tool. jsfx design is great for this purpose. If most important parameters could be mapping via a buzz like interface would be much cooler, I should check your hackey machines more in depth. Most important parameters, in terms of midi are filters for: midi channel, from, to, pitchclass, program change, from, to, bank select, from, to, octave, from, to, force to notes, force to scale, force to chords, midi port = midi output port in Reaper. Like pure data patching those could look, having gates for above parameters, connecting and manipulating from there. Having one big overview for those parameters. The main midi cockpit for Starship Saike.
Wow you added even this into hackey trackey, octave preserving, thanks a lot my friend, will test this as well!
Quote:
+ Add mode to preserve octave to "advance by note"-mode.
Currently this special mode is only accessible via the keyboard shortcut and will be indicated by Adv[O].
In this mode the playhead goes to the next note when entering a note.
When a new note is entered, the octave that was there s preserved rather than overwritten.
Yutani, and 'Nord Modular mode'. Quote from another forum post:
Quote:
Didn't try it, but the paper linked in the article stated a pretty
shocking fact: Nord's oscillators are NOT anti-aliased but are running
at 96k! So that was interesting. So that's where the character comes
from! Aliasing but at a higher sample rate, hehe.
Does Yutani have a mode with 96k sample rate, with two options maybe (a) with aliasing, (b) without aliasing.
Yutani, 96k sampling rate with option (a) with aliasing would be kind of Yutani 'Nord Modular mode'. Not sure is this was tried already? Just to see/hear how it will sound? Different? Much better? New sound sytle? Or already available if doing ... ?
Yutani, and 'Nord Modular mode'. Quote from another forum post:
Does Yutani have a mode with 96k sample rate, with two options maybe (a) with aliasing, (b) without aliasing.
Yutani, 96k sampling rate with option (a) with aliasing would be kind of Yutani 'Nord Modular mode'. Not sure is this was tried already? Just to see/hear how it will sound? Different? Much better? New sound sytle? Or already available if doing ... ?
Nope, not supported by Yutani. I quickly tried it (by just muting the anti aliasing contributions and turning REAPERs built in oversampling on for the effect) but to me, it doesn't sound particularly good. Sounds mostly like a higher noise floor to me.
I could expose this option in the future, but I don't want to pull the oscillator into the oversampling function (since that's not free for users that use Yutani in regular mode), so to do it, you'd have to rely on REAPER's built in FX instance oversampling.
Hey Sai'ke! I'm really loving Amaranth (and other FX you've made of course)! Was just wondering if the "freeze" function could be added so that I can MIDI map it? I don't know if it's possible but I would love to use Amaranth as a guitar or a synth pedal with the "freeze" function but currently it seems like it can't be MIDI mapped. If not, well okay. If yes, HURRAH!
Hey Sai'ke! I'm really loving Amaranth (and other FX you've made of course)! Was just wondering if the "freeze" function could be added so that I can MIDI map it? I don't know if it's possible but I would love to use Amaranth as a guitar or a synth pedal with the "freeze" function but currently it seems like it can't be MIDI mapped. If not, well okay. If yes, HURRAH!
Thanks for all the nice FX's!
Yours,
PW
Ah interesting. Yeah, we can probably make this work somehow.
So some questions from my side first though (to make sure I don't add the wrong thing). Would you like to:
A. Toggle freeze with a CC message (if so, which one).
B. Enable freeze with one CC message and disable it with a different CC message?
C. Toggle freeze by playing a particular note?
D. Enable freeze for as long as a particular note is held?
Ah interesting. Yeah, we can probably make this work somehow.
So some questions from my side first though (to make sure I don't add the wrong thing). Would you like to:
A. Toggle freeze with a CC message (if so, which one).
B. Enable freeze with one CC message and disable it with a different CC message?
C. Toggle freeze by playing a particular note?
D. Enable freeze for as long as a particular note is held?
Oh wow! Well, I have one controller at home but would love to use another in the practice space so is it possible to make A but leave the cc message open (so I can find it in Reaper's FX parameter list and assign it there with "learn"?
Oh wow! Well, I have one controller at home but would love to use another in the practice space so is it possible to make A but leave the cc message open (so I can find it in Reaper's FX parameter list and assign it there with "learn"?
Oh, you just want it as a parameter? It's already there. It just doesn't have a very good name. It's called Update Buffer. It's the opposite of freeze. I should probably rename that parameter. Any parameter name suggestion that would make the name more clear? Unfrozen? Not frozen?
Any parameter name suggestion that would make the name more clear? Unfrozen? Not frozen?
Parameter name suggestion: Unforgiven. (This parameter name might pull a lot more metal fans to Reaper), alone this would be a win. And because it would be cool. You need to find its story to understand the parameters meaning...
Another saike ARP question, can saike ARP be used or set in such a way, so it will only apply swing to incoming notes? Without changing the incoming note order. Without changing note durations! So long notes should still sound long. Only their starting times should be changed, from non-quantized, to swing-quantized positions. This would give mainly Reaper a "real-time variant" of groove quantization. You could apply it on anything. Also polyphonic chords for example.
Another variant could be: It would also quantize durations, beside swing onset times, but to closest step length, thus allowing variable step lengths, based on incoming notes.
Example with 2 notes:
- first note is 2*1beat long, but starting on even 16th position, second note is 1*16th note long, starting as well on another even 16th position. Now both notes would be shifted to a swing position for their starting time (onset), but both would keep their original durations, extending to set step length, if wanted so. Mainly I would find the starting time swinging interesting, with different note durations.
How this would be useful? Take a guitar, after it a pitch follower jsfx, converting incoming audio from guitar to midi, this midi you would send to saike ARP (with those new functions), and it would swingify it, but you could play freely, long and short notes, as you want on your guitar, saike ARP would "only" ensure the perfect timing, plus the swing amount you adjusted before. Would be cool, I guess. Maybe there are other swing jsfx as well, somehow, saike ARP sounded very good to me, swing wise, would need to compare other jsfx, why they do not sound that good or same. Or do they?
Parameter name suggestion: Unforgiven. (This parameter name might pull a lot more metal fans to Reaper), alone this would be a win. And because it would be cool. You need to find its story to understand the parameters meaning...
I'd prefer a name that would tell users what it is.
Quote:
Originally Posted by TonE
Another saike ARP question, can saike ARP be used or set in such a way, so it will only apply swing to incoming notes? Without changing the incoming note order. Without changing note durations! So long notes should still sound long. Only their starting times should be changed, from non-quantized, to swing-quantized positions. This would give mainly Reaper a "real-time variant" of groove quantization. You could apply it on anything. Also polyphonic chords for example.
I don't really think that should be part of the arp. Considering it acts on the incoming notes, it sounds like that would sooner be a separate plugin in itself.
Quote:
Originally Posted by Tone
Maybe there are other swing jsfx as well, somehow, saike ARP sounded very good to me, swing wise, would need to compare other jsfx, why they do not sound that good or same. Or do they?
I don't know. The swing is pretty straightforward. I wouldn't be surprised if someone has already done something like it.
Changelog
SEQS: Added 4 variants of the pillow filter. Added vowel filter.
SEQS: Added option to make cutoff settings samplerate independent (there's a legacy button to get the old behaviour back).
Yutani: Added option to turn oscillator anti-aliasing off.
Yutani: Added inharmonizer effect.
Oh, you just want it as a parameter? It's already there. It just doesn't have a very good name. It's called Update Buffer. It's the opposite of freeze. I should probably rename that parameter. Any parameter name suggestion that would make the name more clear? Unfrozen? Not frozen?
So that's why I didn't find it! For me the most sense would make naming the parameters the same as they are "on the panel". But whatever is your preference!
But thank you! Now I have a new tool to try out! Things are going to get FUNKY!
Hi, I'm newish to Reaper (a little under 2 years) and I feel so privileged to have found these wonderful scripts. I am playing around with them at a rate of about 1-3 per day. I can't believe they're not in the default ReaPack download!!!
I am committing myself to reading this entire thread, but before that I have a question -- I hope it's not contained somewhere within the thread already. It may be badly worded, so bear with me: How do we "print" things from SEQS? I suppose that's a question for sequencers more generally, but, say I've got a cool pattern that I like. How do I render/flatten/freeze/record that pattern so that I can move on to the next one?
You can record output, of audio and midi. If an fx outputs midi you can select between midi output or audio output recording. Else you have only audio output recording. Right click on write button, red button, there you can select write output... Good luck friend, have fun with Reaper.
Hi, I'm newish to Reaper (a little under 2 years) and I feel so privileged to have found these wonderful scripts. I am playing around with them at a rate of about 1-3 per day. I can't believe they're not in the default ReaPack download!!!
I am committing myself to reading this entire thread, but before that I have a question -- I hope it's not contained somewhere within the thread already. It may be badly worded, so bear with me: How do we "print" things from SEQS? I suppose that's a question for sequencers more generally, but, say I've got a cool pattern that I like. How do I render/flatten/freeze/record that pattern so that I can move on to the next one?
Hey, thank you for the nice comment
SEQS and the MIDI arp allow you to make 64 patterns. You can toggle between them with these buttons:
If you want to switch between patterns you made while sequencing your music, you have two options:
1. You can change the pattern with automation by automating the "Current pattern" parameter.
2. You can set a MIDI note that will trigger pattern changes by clicking the C-9 button in the image above. The plugin will then listen for an incoming MIDI note that will be the start of pattern changes. So for instance, if you play a C-7 then playing a C-7 after that will trigger a change to pattern 0. Playing a C#7 will change to pattern 1 etc. That way you can trigger patterns from a MIDI keyboard for instance.
If it's just about saving the patterns you made, you can save them as a preset. All 64 patterns will be stored in the preset you made.
For SEQS, "printing" off the effects into a MIDI item is unfortunately not really possible. You could record the audio coming out though, if it's just about freezing things. To do this, either do what TonE suggested, or if you just want stuff applied to a single take click with the right mouse button on the item and click "Apply track/take FX to items as new take". I hope this helps.
SEQS and the MIDI arp allow you to make 64 patterns. You can toggle between them with these buttons:
If you want to switch between patterns you made while sequencing your music, you have two options:
1. You can change the pattern with automation by automating the "Current pattern" parameter.
2. You can set a MIDI note that will trigger pattern changes by clicking the C-9 button in the image above. The plugin will then listen for an incoming MIDI note that will be the start of pattern changes. So for instance, if you play a C-7 then playing a C-7 after that will trigger a change to pattern 0. Playing a C#7 will change to pattern 1 etc. That way you can trigger patterns from a MIDI keyboard for instance.
If it's just about saving the patterns you made, you can save them as a preset. All 64 patterns will be stored in the preset you made.
For SEQS, "printing" off the effects into a MIDI item is unfortunately not really possible. You could record the audio coming out though, if it's just about freezing things. To do this, either do what TonE suggested, or if you just want stuff applied to a single take click with the right mouse button on the item and click "Apply track/take FX to items as new take". I hope this helps.
OMG! Take FX! It's the perfect solution!
Thanks for weighing in, y'all. I've gone through this thread and now realize I'm just scratching the surface of this package.
Yes, if you have takes in your arrange. There could be also cases where the arrange is completely empty, but having lots of tracks, sends and folders between tracks, sending midi and audio here and there, or deep folderified structures, like 20 levels of child tracks (giving on purpose extreme examples), each feeding / sending its midi output to its parent track. Now you might want to records outputs as well, especially if you designed lots of randomized, probablity parameters, where things change permanently. In such cases the output recording technique might help. You can record all track outputs all in one go, if you want.
Wondering if hackey trackey sample player can be used without midi input as well? Need to check what I am doing wrong, maybe it requires a special form of loading? Whenever I tried, without midi input, normal opening of hackey trackey, then inputting qwerty notes, playing never played loaded samples inside hackey trackey sample player. Need to test more, was thinking always, usage of midi is a requirement for it maybe, but that would be an artificial limitation.
Wondering if hackey trackey sample player can be used without midi input as well? Need to check what I am doing wrong, maybe it requires a special form of loading? Whenever I tried, without midi input, normal opening of hackey trackey, then inputting qwerty notes, playing never played loaded samples inside hackey trackey sample player. Need to test more, was thinking always, usage of midi is a requirement for it maybe, but that would be an artificial limitation.
You can play within HTS, but only the currently selected sample. Playing from the plugin itself is more intended for previewing edits you're doing to the samples.
The intended use case is to play through hackey trackey (record needs to be armed) and/or MIDI.
all seems to be fine. Before it was a project with some stuff there, so the cpu problem source might be something else as well, audio inputs, other fx, was also experimenting with low latency mode, which is quite cool, if you want to play live, a guitar for example. More fun with less or almost no latency, making a big difference in terms of fun factor.
Thanks a lot! Nobody can complain about same repetitive patterns any more. 
Linear Mode
