#31

Got the newest version and seem to be having an issue where the sample isn’t looping worked fine in the old version and latest firmware with fates. Also possible UI suggestion move the record to ALT + K2 it’s too easy to acidentaly clear your recording while messing around with the loop parameters.

1 Like
#32

I’ll take a look at it this morning.

re: UI, I agree. I made sam really quickly, and there is very little to the UI. Maybe I should add some indicators on screen for what key2/3 are doing.

edit: @Tim052, i’ve fixed the looping bug. starting working on a more informative UI now. should have something up tomorrow.

2 Likes
#33

update v1.1

  • various screen improvements
  • various bug fixes
7 Likes
#35

Sorry if this is a silly question, but in which way is this a slicer? Can I create slices from a recorded audio?

#36

Yep! You can load up a long audio file, select start/end points, then save that smaller selection as a new sample/file.

#37

Oh that’s what you mean by slicing! Still, I can totally see how this can be useful! Thanks a lot!

1 Like
#38

Was wondering the same and i think the best interaction on norns for now is sampling with sam, and then loading up a folder of those at timber player where you can actually slice non destructive.

1 Like
#39

An update to choose save location would be cool to make/fill folders for timber!

1 Like
#40

Just pushed a small update that changes the way files are named. We’re now using the same text entry system that the params menu uses. I think this is way better :slight_smile:

2 Likes
#41

I got an error in maiden when I tried to update, but unfortunately, I didn’t take note of it. Tried updating again and maiden says it’s already up to date. But when I save a file, it just gives it the 000x.wav name. What am I doing wrong? Thanks for the ongoing work on this!

#42

Hmmmm, I removed the file that keeps track of the sample count, so it definitely shouldn’t be using that naming scheme.

Maybe try deleting the script and reinstalling? I have definitely had the error, then already up to date situation happen in maiden. Not sure what the cause is.

#43

Ah, yes. Deleting and reinstalling worked. Great update, thanks!

1 Like
#44

Hey @Justmat I just love the straight forward no nonsense approach to this script. Using it to sample and slice stuff all the time. I feel like Dilla. Or Dilla’s cousin, the guy who never got Dilla’s skills but kind of pretended that he had.

How messy would it be to get synchronized recording into this, given the new clock updates? I was thinking something along the lines of this -

  • norns sends clock out to let’s say my awesome MFB Tanzmaus - for the sake of example, I’m at 139bpm today

  • I can, before recording, set number of bars I want to record, or not if I want to just stop the recording myself when I feel like it. The bar count can be quantized, say 1 bar, 2, 4, 8, 16, 32, 64, 128 and 256.

  • I start recording in Sam, which also send start to the Tanzmaus. Boom. Tanzmaus starts playing, Sam starts recording. If I’d set the bar count to something, Sam stops recording when that bar count has been reached.

And I now have a perfectly recorded loop with spot on start and end points, which I can use in whatever other script I enjoy.

And yes, I’m into the Blackbox if the approach seems familiar (though it’s currently gathering dust since the norns showed up with his pal the grid :slight_smile: )

4 Likes
#45

To elaborate - couple of use cases where this would be useful when timed stuff is of some relevance, without wanting to leave the norns system or just manually trim samples in Sam or other scripts (timing’s tricky as soon as a sample goes beyond a few bars, milliseconds count and can be hard to get right) -

So I could record a few loops. Move them straight into @markeats awesome Timber without bothering about the time stretch algoritms and take it to town, clip launch style, by help of Timber’s quantize feature.

I could take my loops, go into @dan_derks lovely cheat codes (known locally here as the Octatrack’s funky cousin) and have them loop in perfect sync, then using the pattern editor and meta sequencer to do all kinds of crazy stuff, but in time.

I could record one bar loops and use them in @mattbiddulph Beets, the one script that made me finally stop missing my Tempest and its beat fx. Might require me to file transfer between sessions, but hey - it’d be worth it.

To mention just a few.

4 Likes
#46

This is a great idea! :partying_face:

I’ll see what I can do. :sunglasses:

5 Likes
#47

You, sir, are amazing for even considering it.

If it helps, I could send you vids from my Blackbox workflow. I think they nailed it on this one. It’s flawless. If you ask me, that is :slight_smile: :innocent:

2 Likes
#48

This is not a feature request :upside_down_face:, but in the nineties, on akaï samplers, starting a record with just a threshold level was pure magic.

2 Likes
#50

What do you think about a fast autonaming algo, maybe naming the first sample of a session and after that its auto-completed with digits? Just a quick save yes/no and automatically being in record mode again. For intense sample sessions this would be such a help.

#51

I can see how that’d be useful. Let me think on it and I’ll try to implement something :slight_smile:

1 Like
#52

My samba is inconsistent and i think its time to use norns more like a true sampler thanks to your script. Nothing like an evening with needles on wax time traveling and collecting artifacts from another era.

1 Like