#177

Hey @markeats! Is there a way to make “start” one of the params that the LFO can affect?

Edit: I’m referring to the chosen sample’s start position, just for the record.

#178

Technically possible in the SC lib yes. It would only effect the start when a sample is triggered, not the progress of playback though, is that the intent? You could achieve similar by making a few copies of the sample with different start times and triggering them randomly for now.

#179

That’s the intent, yes. I ended up connecting my phone to norns with the an iConnect midi, and mapping the “start” param of two samples to different LFOs. Worked great! With a longish sample (these were chord progressions), it’s fun to just kind of mash buttons, not knowing which chord will come out!

Would be cool to be able to do this internally, but this worked great for today!

2 Likes
#180

Very nice! Thx for sharing

1 Like
#181

For sure! Hadn’t played in Timbre since the params system overhaul. Had so much fun!

1 Like
#182

I have a question about midi mapping timber to a 16n faderbank.

I imagine i can map each fader to a global function like sample start, sample end etc and have the fader active to the sample presently played/pressed on a grid.

Is that the way its set up or will the mapping always be individual per sample?

1 Like
#183

Good question, I asked that myself recently. Did not have the time to check this yet, but it would be great for the a smoother workflow if it would change with the sample presently played/pressed… and save a lot of work and mapping options with my EC4.

Timber is so deep and amazing.

I had a few crashes with norns though, when I wanted to change individual samples after I loaded a full folder in the beginning. Sometimes I was just scrolling through my (larger) sample folder). Otherwise it runs really stable.

Crash issue thread: Norns: crash reports with large sample holding

#184

I see what you both mean with the mapping. I guess I always just use the norns UI but will add that to the backlog.

Regarding crashes, it’s all going to be in the details:

  • Ensure you’re on the latest version of Timber (several fixes for large samples etc).
  • What exactly crashes - ie, is sound still playing via MIDI? Is the UI locked but no sound?
  • Exactly when does the crash occur? Is it while scrolling the list or when you press K3 to select a sample or later? What is on screen?
  • What is shown in Maiden when the crash happens (both matron and sc tabs)?
  • Is it repeatable? And, if so, would you be able to send me the samples that cause the issue?

If you’re up for digging into it then perhaps you could DM me with some details and we can investigate :slight_smile:

1 Like
#185

Mark, thanks for the fast reply.

Regarding the midi mapping I mixed something up, because I personally find the use of the Norns UI for most functions very pleasant to use.
For me, I wished that mainly pitch, scale by, percentage, but also Launch mode, quantization (2nd page UI Norns) would be mappable as described above since this always takes a bit longer to scroll down, etc…
Pitch and percentage play an important role in all my sessions in Timber and it would be cool to get quicker results here. On the other hand an additional, extra page on the Norns UI with pitch, etc. would probably do the job just as good, not sure if that is easier to do, or possible at all though.

Also, if I may wish and dream ;), a LFO for sample start would be extremely useful since I mostly do not use common one shots to trigger with my Polyend Seq., but more random recordings of old film music (appr. 3 sec. - 3 minutes samples) I collected over the years… and imagine having here a LFO on sample start :partying_face:

Regarding the crashes, I will collect a few infos and message them to you, if I understood you correctly. I am sure you read the Norns: crash reports with large sample holding already, It seems to be more a SC related problem, less a app related.

1 Like
#186

Making a cross post weaving kind of move to this topic about porting earthsea and midi-out into timber. Probably a good thing if interest is expressed:

2 Likes
#187

Earthsea and timber I would be very interested in.

1 Like
#188

I am enjoying the quick flexibility of timber. I think timber keys could use a per sample monophonic option with portamento/slide.

1 Like
#189

Wow you refined that scale parameter for good, my ct5 blushes. Very fine grained, quite tape-like. Really the tool i ever dreamt of! Thanks so much again.

#190

EDIT: actually figured out how to use this thing :smiley:

#191

One thing that’s so cool with Timber is that it seems obvious at first. Like oh, okay, a sample trigger. Always useful.

Then, the more you use it, the more you realise, there’s nothing quite like it. I can see a case where one would get norns for Timber alone, cause nothing really compares to it once you dig in.

9 Likes
#192

Just throwing this out there… I would love some arc functionality but I have limited (0) coding skills.
I’m day dreaming of:
For currently selected sample

  1. sample start
  2. sample end
  3. note repeat (a la mpc)
    4)??? Maybe quality or delay send
1 Like
#193

Probably easy enough to do with Arcify – even starting from square one, it won’t take more than a few hours. Give it a go :sparkles:

2 Likes
#194

@markeats just wanted to thank you for this excellent sampler engine! I’ve integrated it into a 16 track step sequencer called gridstep https://llllllll.co/t/gridstep/ which is based around an isomorphic grid keyboard. Timber works incredibly well and sounds fantastic!

4 Likes
#195

Thanks, great to hear you’re getting good usage out of it :smiley:

2 Likes
#196

Besides still hoping to see this mate up with earthsea i just thought how fun it d be to have a way to sample to it within the script. Like sampl to grid buttons and save as set when done.

2 Likes