Sorry to mingle in, but could it be because of your are using wrong table for storing the presets? I am not 100% sure, but you should probably be using a 32 bit table, if you are not all ready using it.
SirSickSik Contributions
mtyas
#843
Ahhh, Silly me 
Thanks a lot @jaffasplaffa it was exactly that ! Seems obvious now. Need a new brain I think !
Thanks again, and back to beat making 
blaerg
#845
Finger-Tonnetz.axp (35.4 KB)
Here is a patch I've put some time into developing, it is using a very old Novation Launchpad to trigger notes and generate logic for chord transformations. Why? Because I got one free. Alternately I have used TidalMIDI to generate sequences that are time-based.
Yes, there are probably more efficient ways to arrange some of the elements of the patch, however my delight is not in being efficient but rather arriving at a melodious and functional result as rapidly as possible.
Thanks for making this object, @SirSickSik it's fucking awesome.
Makrotulpa
#846
Just wanted to say thanks for you inventive work! 
I've made a bunch of Glitch Beast / Factotum combinations using a single QuNeo setup that works really well for standalone jams and processing.
SirSickSik
#847
let's hit "sync library"..... "click"
NEW MODULES
SAMPLER
"loadtrain1", "loadtrain2", "sampleplayer1", "sampleplayer2"
first of all:
-please read.. they're complex enough. Also, first check the info of inputs/outputs/parameters/attributes on the module if you're not sure what to do. Most should be explained.
-loading modules can be used together in a, what I call, a "loading train", by connecting them in a row (connect out&inputs between modules).
-able to load .tab, .raw, . wav files, though only 1 format per module, but each module may load it's own format.
-2 tables are needed to save the samples themselves (16bit) as well as the array-starting/end-point for each sample (32bit).
-you can use either a single table to save all your samples to or use seperate tables for each sample-instrument. (remember, it's 2 tables per set! So using two sets requires 2 sample-tables and 2 start-tables!).
-The size of these tables is up to yourself. I mostly use 2091752bits (about 43 seconds) for 64 drum samples, some of which may be fairly long (up to 3 sec, but most are way smaller). If the selected samples don't fit in the buffer, it just stops loading new samples (a bug should be fixed, but not entirely sure, let me know if this might still cause errors!).
As each module has readouts for array-start/end, (last loaded) samplesize and sample positions, you can check whether the load was within the bounds.
The "first" sample-index and amount of samples being loaded by the module are also send as outputs of the module. These can be used to bound the sampleplayers to the right sample-start indexes (eg. only the part with the snares).
These values could also be saved into an extra table, that's saved together with the samples and samplestarts. This way you can save and load sampletables that use different setups and order of samples!
well, the modules themselves:
-loadtrain1:
loads up to 16 files from your SDcard. Names can be entered manually. This is used to load a predefined set of samples that are not necessarilly in consecutive order, have different file naming/suffix or belong to different folders. Names are set at startup and cannot be changed while being live. Mostly used for "fixed" samples of which you are sure you're always wanting to use them.
-loadtrain2:
loads an indexed-named set of samples from your SDcard set with a prefix and suffix, like BD003.raw. Samples can either be loaded in consecutive order (BD001,BD002,BD003,etc) with a sample-index-start and sample-index-end control OR
be loaded using a randomisation process. The latter is controlled by two controls for setting maximum and minimum sample index and the amount of samples that should be randomly loaded.
Both loadtrain modules can be used in any order, for example:
- two kick samples, loaded by name (loadtrain1),
- 6 random kick samples (loadtrain2 in random mode),
- 2 'fixed/preset' snares (loadtrain2 in consecutive order and using index-input to offset the name-index to select next 2 snare samples with each new sample-library-build)
- 5 modules to randomly load a bunch of snares/hihats/cymbals/glitch/instrument samples from different folders for the remaining samples.
Each time the "load" is triggered, it will load the same two kicks, the snares that are selected and a bunch of random other samples.
As for the sampleplayers:
-sampleplayer1 is a "complex" one. Two samples can be played together with an internal decay-envelope mixing from one to the other (direction can be both swapped and tilted and rate can be externally controlled). Sample 1 only plays once, but sample 2 can be looped using the loopstart and end points. Play can be pitchshifted and reversed and looping can also be set to alternating.
The module has "first" sample and "samples" range inputs to keep it only playing samples within the desired reach of the sample bank (eg. only the part where the snares are loaded).(If multiple loading-modules are creating a combined set (eg. all snares), the "samples" outputs of the loading-modules should be added together and the "first" output of the first loading-module should be used as the "first" input of the sampleplayer.)
An extra feature is the Swalk (sample-walk) that selects a different sample each time the sample loops. The number send to this input sets the stepsize to use for stepping through the sampleset (only the samples within "first" and "first+samples" index)
-loadtrain2:
this is a simple sampleplayer that's able to independently play 4 samples from the samplebank. Each sample has it's own pitch control, sample selection and gate-trigger. Only has one audio-output. Useful for quickly adding a bit more polyphony next to the heavier sampleplayer1 (of which I use only 3 in a patch).
and a little demo: https://soundcloud.com/sirsicksik/broken-axoloti-sampling
Module requests
SirSickSik
#848
NEW MODULES
LOGIC
"rndLGC"
4 inputs, 16-multi-logic stages and 4 outputs that can select any of them and a randomisation trigger and chance.
Turn any 4 gate-patterns into something completely different. (eg. the track of the audio-link in the former message is made by 4 unchanged gate-patterns that are mangled by 2 slowely randomised rndLGC modules.)
SAMPLER
"liveRecord" and "livePlayer"
These modules are set up in the same way as the sampler (using a table for the samples and a table for the start-positions), but are used to live-record and play samples. Could very well be used a live granular sampler in conjunction with the samplers to further mangle up samples. Ehm, actual sharing of the tables between the samplers and the live-sampling hasn't been tried and might not work... So you probably need to use an extra set of table-allocators for this duo.
Rbrt Contributions
SirSickSik
#849
could anyone tell me whether the new modules are present or there are any errors, as my axoloti patcher suddenly can't find my library anyore and I'm trying to figure out what the heck has happened..
mtyas
#850
Just quickly played around with liveRecord and livePlayer, they work a treat, Fantastic job
servandisco
#851
All Objects show up but I get errors, probably due to something missing or with the wrong table name, etc.. It would be great if you could provide a "help" patch working for the samplers and specifying that if you put X samples in Y folder it should work .. Btw, I have many kits with 24 percussive samples in a single sample file of 12 secs (op-1 format) It would be totally rad to be able to reuse this kits in axoloti since there are tons of them in the internet... (https://op1.fun/). definitely, Axoloti has maaany more ways of having fun with the sound than an op-1
mtyas
#852
Very late answer for the donation question.
I think a simple donation page link (PayPal.me or the likes) on our profile page could be a reasonable solution. I sometimes want to put a few euros in a tip jar for some people in this forum (or elsewhere) and I find this solution the easiest.
SirSickSik
#854
NEW MODULES
HARMONY
"scalebankLIVE"
records the notes being played and remembers their "priority" order
all external controls:
-gate: when it goes high, adds the note-value present at the note-input to the scale, except when the "delete" input is high. In that case, it will remove the note value from the scale.
-note: sets the note value to be added/deleted to/from the scale. (octave-offset will be removed)
-clear: after pressing clear, the next note being added will reset the scale with only the new note being active.
-notes: sets the maximum amount of notes to be recorded into the scale. If it is lowered below the amount of notes in the scale, it will look at priority to remove the extra notes from the scale: last played is first gone. Though, the extra notes are still remembered to allow them to come back when the notes-input goes higher again.
"scaleLIVE"
This module is used to actually quantize your note-data. Just has an note in&output and an object reference to refer to the scalebankLIVE module. This way you can quantize multiple oscillators using just the single array of the scalebankLIVE module (or any combination of scalebankLIVE and scaleLIVE modules to allow different parts to play different notes).
SirSickSik
#856
Lots of thanks to Matthew and Jeremy for their donations!
I'm going to use this for my next axoloti + controls that I'm going to use in my eurorack to control my doepfer CV16 and have myself a 16-channel CV-recorder/pattern-generator/clock-source.
SirSickSik
#857
NEW MODULES
(and updated)
"repeater", "repeater2" and "repeater2St"
-repeater is bug-fixed and has an added option of reverse-play (former did forward and reverse at the same time) and input-duck on/off while repeating.
-repeater2 is a variant on repeater that doesn't duck the audio, but just repeats the audio. Next to this, it has a swing-setting for time-offsetting every even numbered repetition. You can also set the wet mix and add feedback.
-repeater2St is the stereo variant of the repeater2 module. It has extra panning controls for start-panning, spread-panning (every next repetition will have this offset added to the former one) and panning-swell (sets a slope to either start from the center and pan outwards at the last repetitions (negative numbers) or start outwards and go to center with every next repetition (positive numbers)). 2 panning modes: triangle and saw shape.
Next to the panning, it also has individual dampening for each tap with a main dampen cutoff as well as a dampSwell control which either adds to the main cutoff (positive values) or subtracts from it (negative values)
SirSickSik
#858
a control module for a new upcoming fx module
NEW MODULE
CTRL
"permuList"
Combination module based on permutation:
Creates a full list of 4-number-combinations from the available options.
No repetition, no importance of order.
eg:
1,2,3,4
1,2,3,5
or
3,6,8,11 (any increasing order)
BUT NOT:
1,1,3,3,6 (no repetition of numbers)
AND NOT:
3,1,6,5 (not smaller then any value left of itself)
"select" knob is scaled to the amount of possible combinations
"fine" knob can be used when using a high option count->otherwise the stepsize would be to big to select all possible combinations.
The 4 outputs give you the selected indices.
This module could be used for selecting any 4 out of up to 16 functions which may not be selected twice. (which is a hint for the upcoming module)
axoman
#859
Too skint to donate right now, but intend to when I can give you something decent. In the meantime I would just like to say that your new avatar looks totally 'SickSik', and I look forward to playing with those new sampler modules you released 
SirSickSik
#860
NEW MODULES
a lot of m.. a chain to be chained.
FX/CHAINER/......... (all modules that can work together are in the same folder)
main module:
"chainFX"
Main effect chaining module.
Uses the fx modules contained in the same folder (sss/fx/chainer/...) (or if other developers jump in to make their own chainable effects, there might be more fx folders later on)
Loads up to 12 different effects of which 4 are used.
The "routing" input can order the selected effects in all possible combination (using each effect only once).
Each effect has a dry/wet-mix, mixing the output of the effect with the input of the effect. This could be used to layer effects on top of the original signal.
Effect 2,3 and 4 also have a mix control to mix between the former effect output and the former effect input.
This could be used for parallel effects fx1->(fx2&fx3)->fx4
Each effect in the chain has two CV inputs that alter the fx that is currently loaded at that position in the chain. The effects themselves (modules containing the effect functions) can also have their own parameter inputs for fx-dedicated control (eg. tempo synced delay/lfo)
All effects are stereo for lots of spatial effects.
if you don't need 12 effects, just load a single "cempty" module and refer to that one with the remaining object references that you don't use.
"cFXselector" (same module as listed in my former "new module" message, but now saved to the same folder for easy and quick loading of modules). Set "options" to the amount of modules that you've loaded (currently max=12).
Well... the effects (all seperate modules that contain the "effect functions"):
-1 stage phaser (load multiple module for more stages)
-pingpong delay
-simple vca (envelope/gapper)
-panner
-SV-filter
-(noise-)gate
-sustain
-amplitude modulation (ringmod)
-samplerate reduction
-soft distortion
-peak distortion
-pitch-tremelo
New additions:
-shuffler (random delayed signal shuffle)
-empty module: can be used for empty sockets OR to write your own fx code to be used by the chainFX module.
Lot's of different modules can still be made and added to the list.. If you think of a new nice one.. let me know. Just keep it simple. 4 layers of simple effects are often enough modulation.
To say it simple:
You've got up to 12 effects of which you can combine any 4 of them in any order with serial/parallel/dry/wet mixing.
And of course.. it can all be driven by ((semi-)random) pattern generators/sequencers/envelopes/LFO's 
The "chainFX" module shouldn't be too hard to mod to remove unnecessary object references if you want to get memory usage down (eg. by only allowing 4 effects and deleting the other attributes and the part of the code mentioning them in local, K-rate and S-rate). This way you can just use 4 effects in any order for your synth (eg. filter,phaser,delay and pitch-tremelo for spherical stuff or the sustain, gate, softdist and peakdist for a distortion).
ps. if anyone else makes modules that can be used with the chainFX, let me know and I'll add the name of your folder to the chainFX overview, so people know where to look for other modules.
Cannonball
#861
Sic,
Is there a help file to show how this is set up properly? If not could you add one to show an example?