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 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.
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
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.
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:
atm I don’t own norns, can I map Timber parameters to midi controller? (let’s say filter frequency)
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?
EDIT: After having slept on it (and not seeing any similar specific issues anywhere), it occurred to me that maybe some recent changes on my system may have been causing the troubles below… which led me to suspect mods. After I disabled toolkit, matrix, nb, nice-tapes, and emplaitress—all seems well with presets now. When I have more time, I will see if I can find out which is in conflict, but for now, I am super happy! (I plan to use Timber Player at the center of a performance next weekend, so I was experiencing some anxiety).
Thanks, again, markeats for such an amazingly flexible and legible instrument!
@markeats I am greatly enjoying working with your Timber Player; it is exactly the instrument I’ve wanted with the greatly customizable envelopes and LFOs—it’s really lovely.
Unfortunately, I hit a bit of a snag today and have been trying to work through it. I could use some help. I’m on a norns shield running 221214 if that helps.
PSET saves and loads presets just fine within one norns session, but all the presets seem to get clobbered after a system restart or sleep…by which I mean the presets are still visible in the PSET menu, but none of them will load.
In the course of troubleshooting, I have found that if I delete all the presets, save a new scratch preset, and then overwrite that new preset (via smb) with the files from a previously saved one (player-01.pset and player-01.pset.matrix in this case) then I can load the old preset normally. Unfortunately, when I restart or sleep norns again, the new (old) preset will no longer load.
Is there something about this description of this behavior that might lead to a solution?Or can anyone think of a better workaround than I’ve discovered?