In my main patch I'm working on a quantization mechanism that can be freely set to 1/4, 1/2 1bar 2 bar etc. so that you can be really free with how long the loops should be.
I think I posted a version here. But it was worked around the quantization phasor and multiplying the the frequency input.
Rbrt Contributions
Cool!
What I've done in mine is to have a master loop that is also the master clock for midi out, but the slave loop is synced directly to the master, from one fourth to any integer multiple of the master length, set on the fly depending on when you press the button, using range scaling and rounding... I would really love to avoid midi clock sync completely, but to do that across boards I guess I'll have to wait until @johannes implements a stable object to communicate digitally through gpios... well, my live setup became nearly 10x smaller thanks to axoloti, so I can already be satisfied!
2 more objects, stransport and ktransport
...take kticks ore samples as input and drive a phasor and a 16-step clock.
divide and multiply the tempo as you please!
'mode' selects whether to divide or multiply, 'factor' sets the multiplikation/division factor.
also,there's some new stuff in /testing
looks great will test it later!
just from looking:
maybe an inlet for max value for the counter could be great
Junge!
Thx to your objects I built a syncable and subdividable delay with tables.
Check this out:
Reason why I did this I want to have a delay and looper on one board and have the max looping time, leaving me no space more for the delay. so my idea was using part of the table for the delay. To be precise the first loop slot, leaving me still 3 tracks for looping. (wich is for the travel setup I'm working on still enough)
If you have any concerns about this let me know, theoretically it should work...
btw you can also to the drooney stuff you sent me but all synced to a clock.
P.S. Now I'm busy building user interfaces using your midi and seq objects. I find still a bit hard to do what I want to do with your blocks:
With my Launchcontrol I want to have different layers of button rows that I can shift with some other buttons.
Each row should either:
1. Have and off toggles or momentary behaviour
2. give me an integer, so notes 0-3 should give me i 0-3
I want to get this as efficient as possible since I'm limited on ram. The 1. is easy with your objects but I can't manage to get both.
My aproach is using tables for this, wich has the advantage that I can store default values. You have any Ideas how to do this with your objects?
right now I'm using step toggle and table sent note.
...just updated 'stransport' and 'ktransport'...
..now with a selection of max counts and a 24-ppq-outlet
as 'steps' defaults to '8' , you might have to change this in already existing patches to '16'
tcopy V2
...useful for copying data around in between tables.
v2:
it's now possible to copy data faster than audio-processing-rate (up to 16 x !)
this has a lot of potential regarding sample-mangling.
of course 16 x has quite an impact on CPU-usage...
'splat' == the contents of the destination table will not be overwritten,but added to.
'clear' == the contents of the destination table will be cleared (overrides 'splat')
the lmangle mod pitch control is a bit iffy. the audio stops at 3 o'clock in a simple patch i made.
and i can't seem to get the inlet startpoint to work
i should expand... the pitch seems to work if you move the parameter continuously, but if you leave it static it goes off.
also, the startpoint does work... my bad.
really enjoying this object btw, lots of potential as a nice sampler
..yeah the concept is nice ,but it doesn't work as it's supposed to...
thanks for pointing this out,e-hem...
something connected to 'speed' is really messed up,I'll fix it ASAP
and let you know...
waveshaping
just did some really quick and dirty lookup-table style waveshaping objects.
nothing fancy,basically just an adaption of existing objects.
I think they're fun anyway,check out the help-patches (especially for 'shaper 8 mod')
HEAVY aliasing,gritty sound.
I'm beginning an effort to document all objects with help - patches.
here's the first, for 'rbrt/fx'.because there's not much there,yet
more wavetable stuff
here's WAVE CREATOR
to create lofi-32-bit waveforms directly in axoloti UI.
BIG HACK: if you press 'saw' , 'sine' or 'square', the sliders will re-set to the respective waveform!
you can acces the waveform you've created by entering the object's name (in this example, 'wave1' ) into
'table/read interp' or such....
I will post an approach to multi-waveform-wavetables and morphing when I've gotten around some interesting difficulties...
Does this have a name?
this is really nice! I'm using this now as quantization phasor and transport. the only problem I have is the external input for factor doesn't really work. I divide my smps now with factory objects but its somehting the stransport should do right?
For the rest, really great and useful object!
Heyho!
Is the internal parameter factor working?
I guess its just one line of code I forgot...
I'll check it tomorrow...
The internal one works perfectly well!
btw I'm having a really great time with my looper here, things really start to come together musically
I was just wondering, I really like the fade option of the lrec object. Would it be possible to add this to the ldub too?