is there a way for timber keys to have a per-instrument send to the reverb? looking at a multi-timbral setup and would like to be able to send some sounds to the reverb while others remain dry. if this is possible with a simple LUA mod, i’d love to give it a shot…

a second send bus to a softcut based delay would be awesome, too.

finally - on the engine feature requests side, i’ve been thinking dj style filter would be super useful.


To answer a few questions etc from above…

@hallmar @FLORINS if you have changes that would make sense for a PR I’d be happy to approve it.

Go for it! I’m not working on any updates at the moment.

Should be very implementable without engine changes.

I don’t think this is possible using the global reverb with the way norns audio routing is. You could build your own reverb into the engine (some perf implications but possible for sure).

I think these would be relatively simple engine updates. Depending on exactly what you want from a DJ filter that might even be done just in a script.


I just proposed an update :slight_smile: (I hope I’m doing it correctly, I’ve never proposed any change to any other repository other than my own)


Thanks @hallmar and @markeats. I too am a bit github challenged tho i should probably learn…


Timber is working nicely for me now, when I last posted I had a somehow messed up Norns install. Anyway… am I missing something or is there no way to globally set parameters (ADSR etc rather than per sample!?) in Timber Player?

EDIT: all i needed to do right now is extend the release times for every sample in my set, so I hacked it by just opening the preset and search+replacing “0.003” with my desired release time :smiley: but that’s not ideal.

Would love global control over the params for an entire set of samples rather than only individual editing per sample! I’m much more likely to find use cases where I’d want to do pretty much the same thing to each sample in a kit, than to go in and tweak every one individually.

1 Like

Hey @markeats, I was wondering if there is any way to hack in a “sample preview” function when you’re selecting samples for a slot for Timber Player?
Edit: what i’m imagining is when you are at the select screen you can push the relevant grid button and it triggers the sample that is highlighted

I might be able to do something but I’m not sure where to start. Any tips?

I’ve also been thinking if there’s any way for the script to remember the last location where I selected a sample. So for example if I select a sample from /common/samples/kickdrums/bd1 and then go to another slot and select a sample the sample select menu starts at /common/samples/kickdrums instead of at root.

Ok looking at this further it appears that lib.fileselect is something that Monome provides with their own API. They say that the “remember previous filepath” is functional in firmware version 200712 of Norns but for some reason it doesn’t work with Timber(or atleast my version). See this thread: Norns: Sample load workflow improvement - #9 by csboling

And looking at all firmware releases for Norns it seems that the sample preview function is not implemented for fileselect at the moment, BUT it appears that Maiden 1.1.4 (Norns firmware 210927)has a sample preview function which is a good solution for now


Not much I can add to what you already found. :slight_smile: Expanding fileselect would I’m sure be appreciated by many!


How can I switch between apps and send clock to external midi out? In my app I use params:set(“clock_tempo”) but when I switch back to timber tempo is doubled in time and I have to set PARAMETERS / CLOCK to 1 to make timber clock out right. What is the correct combination for sending external clock and keep global clock setting?

That + pattern record alla earthsea that would be to die for.

Allready kind of thinking i would be better of with ansible running Earthsea and have timber as a standalone Cv reciving module instead norns. But the soft implementation would be much less hassle i am sure.

1 Like

I just noticed the 7-voice limitation that Timber has. Do you think an increase to 16 would have too negative of performance implications? Maybe I should just try it on my Norns and see what happens?


Please let me know how it goes?

so, it doesn’t appear to cause my script to slow down or crash or anything. I’ll keep playing around with it and report back if I discover something untoward.


Very very cool to know!! Thanks for checking it out!

Fwiw 7 voices is the max I could get running without audio dropouts when I made this engine - most noticeable when rapidly triggering sounds.


is there the possibility of having the LFO also command the “sample start” and “sample end”? :nerd_face:


I can’t recall any reason it wouldn’t be possible to add that to the engine – I probably just left it out because of the limited number of LFOs.

1 Like

I understand, thanks.
I have a problem with the sample change, I can only play the one loaded in slot 0, what can I do?

On Timber Keys the samples are triggered by different MIDI channels, is that where you’re having problems?

ah ok, I thought you could also choose the preloaded sample with some key combination. It would be nice to be able to choose the sample in use also in Timber Keys for example through grid.

Good day! Long time lurker here, I’m looking to expand my Digitakt somewhat cheaply with polyphonic stereo sample playback for live sets, so far Timber (especially Timber Keys) looks like one of the best solutions for me (compact, looks like easy to use). I have few questions thou:

  1. atm I don’t own norns, can I map Timber parameters to midi controller? (let’s say filter frequency)
  2. is there a way to save/load a set/project (don’t know how it’s called in norns terminology) with all the settings?
    My whole idea marrying Digitakt with Timber would be like this: Digitakts 8 audio tracks for drums percussions and random samples, one midi channel plays up to 4 note chords on Timber, and additional three midi channels can play monophonic samples (that is total of 7 voices). Btw is it total 7 voices, or 7 voices per midi channel? Also how does voice allocation work?