alef's bits released to library

the new module is basically a weird little noise-based oscillator idea i had while learning about oscillators using lookup tables.

essentially, you choose a ‘table size’ in the right click menu, and can generate a new sequence of random values to fill the table, and that table is used as a repeating waveform with the frequency controlled by knob/input. generating a new ‘table’ results in slightly different timbres of sound, and increasing the ‘table size’ results in noisier and noisier sounds.

i’m also adding a “simplex mode” to use simplex noise values to fill the table instead of RNG, including a ‘speed’ slider for the simplex noise source. simplex mode results in (usually) less harsh sounds.

unlikely to be popular with people who hate aliasing lol

So sounds an interesting oscillator so what sorta sounds will it produce or does that depend on the ‘table’?

it does depend on the values stored in the table. the available table sizes are 64, 128, 256, 512, and 1024. 64 leads to the closest to a ‘normal’ oscillator sound you’ll get, with higher table sizes resulting in more and more chaotic/noisy sounding waveforms (this is with the normal random number generation, that is - with simplex noise, the sounds are typically less harsh and ‘smoother’).

1 Like

Sounds worth waiting for then. Thanks for making these great modules.

1 Like

a few more tweaks and fixes to both slips and slipspander, and added what i have so far of the new module ‘nos’.

EDIT: as a note, and as i said in my previous post about it, ‘nos’ is a bit… chaotic by nature. filtering is recommended. if you’re looking for a ‘good’ or ‘normal’ oscillator - this ain’t it.

1 Like

i’ve been thinking about it a bit, and depending on how i feel down the line, i may or may not remove ‘nos’ from alef’s bits and stick it into a separate plugin i make for more ‘experimental’ modules. i really like the module even though it can sound harsh at times, but i don’t know yet if it’s something i want to include in the main plugin.

i am very curious to hear what other people think about it, though.

Love this, nice thinking.

1 Like

Any reason why the table sizes have to be a power of two? Seems like a continuous/exponential range could be interesting, especially if you develop other types of signal (or samples) to initialize the tables with.

it was honestly a pretty arbitrary choice. it just seemed like the most logical way to approach it to me.

i could certainly try setting up a more customizable size option, thanks for the suggestion :slight_smile:

1 Like

i just implemented an arbitrary table size slider in the context menu, in place of the static options. i’ve left the minimum and maximum at 64 and 1024 respectively, for now, mostly because i don’t yet know what a better min/max would be.

EDIT: also, i added an easter egg to one of the modules. :wink:


ok i was thinking about hiding nos for the next update, but i just added more functionality to it, so i decided ‘screw it’ and i’m keeping it in and visible.

changes this build:

  • added new module ‘lucc’ - clock divider, similar to ‘fibb’ but based on the “Lucas numbers/sequence”
  • nos: added new ‘worley noise’ mode option
  • nos: reorganized context menu a little bit
  • nos: included the new table size slider in the menu (min = 64, max = 1024, subject to change)
  • probably a couple other minor tweaks here and there
  • EDIT: nos: added perlin noise option, because why not

also, added in a recent build that i forgot to mention:

  • added a “speed” param and cv input to my ‘simplex and hold’ module, to control the speed of the internal simplex noise source

if i don’t get any new feedback or reported issues about the new modules in the next few days, i’ll probably submit an update to the library to fix ‘slips’ and include the new modules.

EDIT: updated release build link - Release Release 2.5.3-ef28cc2 · alefnull/alefsbits · GitHub


just submitted another update to the library to fix the issues i found with ‘slips’, and add the new modules ‘nos’ and ‘lucc’.

should come with the next library update. until then, current pre-release build is available as always: Releases · alefnull/alefsbits · GitHub

@alefnull tbh I didn’t notice any issues lol. I have to say Slips deserves a tagline my friend… like “Slips is your/my homeboy”. I’ve been playing the hell out of this module as of late! Thanks for this, cheers! oh and in conjunction with Oct Sclr :+1:

1 Like

wow, thanks so much for the kind words! i’m excited that you’re enjoying the module :smiley:

EDIT: as for the issues with slips, it had to do with the root note and quantization, and it wasn’t a particularly huge problem, but it did occasionally produce incorrect results. in any case, it’s been fixed and should be in the library soon, along with a couple new modules :stuck_out_tongue:

1 Like

new update available in the library.

  • added an end-of-cycle pulse output to ‘slips’
  • added light indicators to ‘slips’ and ‘slipspander’ to indicate when they are connected
  • added option to add ‘slipspander’ from ‘slips’ context menu
  • added ‘lucc’ and ‘nos’ modules (‘nos’ is also now polyphonic)
  • other minor tweaks/fixes here and there

haha that end of cycle is pretty slick for retriggering generate, aside from triggering anything else.

i’m honestly surprised at myself for not including it in the original release, and that i didn’t even think of it until it was suggested to me by Omri Cohen himself lol

1 Like

I’m having a lot of fun with slips. Of course I am using it to accompany my Meander module :wink: I have slips set up to a C chromatic scale and then either quantizing the seq out with Grande Quant to the Meander outout scale or with Chinenual Tint to the Meander chords. Both sound very good, but usually not together. Meander is playing a 12 bar blues chord progression in Am with bass. Just using 4 steps for now.

This one module gives a lot of variations for a generative piece.

Thanks for the module.


thanks so much for the kind words :smiley:

never get tired of hearing that someone enjoys something i made. it’s part of why i love developing for Rack so much these days. this community is very supportive and it makes the process of developing new ideas that much more enjoyable.