Perfect. Thank you so much for this,
I will dive into softcut!
Perfect. Thank you so much for this,
added #2 and #3.
these little sample scripts sound nice— #3 is sortof a mlr-ish auto-cutter. use them as a basis to make little things:
- change the soundfile
- change rates, panning, etc
I get how to play a sample and jump across various position, what I am most interested in, now that I am properly teased, is:
- How to change the pitch of the sample.
- How to use the filters, especially
- Start a new recording of what comes through audio L/R.
- How to replay that sample.
Where I want to go
What is a good way to make let say a sampler that can hold more than one sample at a time, a large number of samples, think Ableton Drum Rack. Let say I have a bank of 64 samples. Right now the buffer seems to always overwrite the previous sample.
change pitch with rate
the buffer is super super long, so use cut positions as storage points for clips. think about it like tape or RAM
recording is up next!
Oh that is clever!! Okay yes I think I know just how to make myself the perfect sampler.
in upcoming version (current
master branch), there are now two controllable filter stages: one before the write head, one after the playback head.
both have identical topologies: 2nd-order state variable. each filtering stage puts out an arbitrary blend of lowpass, highpass, bandpass, band-reject and dry signal.
the “mod” parameter is a little weird and deserves a special explanation. it applies only to the pre-filter. the
preFcMod parameter (normally in [0, 1]) allows the cutoff frequency to be affected by the rate parameter. this “modulation” can only decrease the filter FC, not increase it.
fcModValue = min(fcBase, fcBase * abs(rate)) fcValue = (fcModValue * fcModAmount) + (fcBase * (1 - fcModAmount))
there is a specific reason to have this: if you set the rate below 1.0 when writing to the buffer, you are effectively decreasing the sample rate of the material in the buffer.
at the extreme, when (say) sweeping the rate from positive to negative, rate ~=0 means effectively
sr ~=0, and any values written there will cause a nasty click when played back at higher speeds.
so, if you set up the pre-filter as follows:
- dry mix = 0
- lowpass mode = 1
- all other modes = 0
- base frequency at, say, 12k or 16k or something (well below nyquist, to accommodate shallow rolloff of 2nd-order SVF)
- rq = 1
- fcMod = 1
then the pre-filter acts as a fairly effective antialiasing device when changing the rate.
this isn’t “needed” in the post-filter.
also i should note that there’s no smoothing of filter parameters at the moment. this could be added… problem is the coefficient update method is rather heavy. so will take some work, like (a) profiling individual ops in coeff update on ARM (tan function) and making approximations / refactors as appropriate, and/or (b) downsampling the filter parameter signals (except when modulated, so… kinda tricky)… or maybe weirder things like smoothing the coefficients directly after calculation… i intend to try some of this stuff on the postfilter (no mod) and profile.
with this new version, does
halfsecond.lua need an update from
post_filter_dry (along with other
Yes indeed. But I suppose we could add aliases in lua
#4 record and overdub added.
During my vacation I can’t escape the voice in the back of my head, telling me it’s excited to get home to the Norns.
#5 filters, added. anyone making scripts?
Are the post filters currently available, or do I need to
git pull in
oh, good point. you’ll need to:
cd /home/we/norns git pull ./waf
we should have a formal update out very soon
I want to script an asyncronous 4 track looper in the vein of mlr. What is the max loop length if I want 4 loops? 2,5ish minutes?
anyone making scripts?
My 128 samples script is almost done, a should have the library up on here in a few more days.
I have a couple count to 5 inspired things, and something else that hasn’t quite taken shape yet. Softcut seems so endlessly scriptable.
edit: also adding filters to otis and bounds will be great!
I interpreted this to mean the loop length, which would also be cool
Am I wrong to think of (slowly) working on a softcut based script that emulates a tape delay ala RE-201? Or is this a bit too basic for softcut? Been thinking of some ideas for scripts to build (while attempting to learn Lua).
no, seems reasonable.
softcut isn’t a tape emulator exactly. but you could program some warbles on the lua side, use the filters, get somewhere in the territory rather easily.
Ah! Exactly what I was thinking. Not sure if its super exciting, but maybe a good exercise for myself to get a little familiar with the language etc. Cool