#3

d’oh! very good question! live audio.

I’ll update the above.

2 Likes
#4

Can this take the internal tape loop as input?

#5

Woah!
Is it syncable to external MIDI clock ?
Many thanks!

1 Like
#6

Currently, it takes live audio only. Let me iron out some bugs and I’ll add “tape loop as input” on the feature roadmap.

@KthulhTriokus I can’t test whether setting the clock with midi works (I have limited gear at the moment) but I can confirm that Ableton link works.

5 Likes
#7

Got an odd big earlier when I when to clock settings. It wouldn’t allow me to scroll over it. Kept forcing me to bottom of the page. I’m going to reinstall and check my end again.

#8

Yeah, there’s something going on with settings. @okyeron had something similar with the Softcut menu. I’m going to dig into the issue tonight. Thanks everyone for reporting these things!

1 Like
#9

I tracked down the menu bug and fixed it.

If anyone else runs into the same bug:
/home/we/norns/lua/core/screen.lua:215: bad argument #1 to 'screen_text_extents' (string expected, got table) read on

Summary

The bug was caused by the way I was setting options for params:add_option. My options object wasn’t just a simple array e.g. foo = {1, 2, 3, 4}, but rather a complex object such as foo = {bar: {1, 2}, baz: {3, 4}} and Norns did not like it. So always use simple arrays for options!

I pushed this params bug fix as well as some additional tidying, noted above in the Changelog. I’ll work on tape input and on-going bug squashing.

4 Likes
#10

Thanks for the script! I just tried it!

4 Likes
#11

The menu goes crazy when i’m increasing the glitch amount. It jitters around.
I’m on FATES latest firmware.
I test it further tomorrow. But hey, nice work !!!

#12

It’s supposed to (seriously). It’s glitching, ha! If that’s annoying to more folks I can remove it, or in the meantime you can edit the script and replace the glitch_shift_px() function with the following:

local function glitch_shift_px()
  return 1
end
4 Likes
#13

I think it’s pretty cool !

2 Likes
#14

I love it, it looks so realistic! :sweat_smile:

1 Like
#15

I’ve had a chance to make some significant updates and getting even closer to 1.0.0 release. You can get the latest build from Maiden look for commit hash (f54cae6), be sure to refresh the community list!

Bildschirmfoto 2020-08-21 um 23.58.02
Bildschirmfoto 2020-08-21 um 23.58.021238×122 3.26 KB

Overall I’ve squashed some bugs (I hope!) related to audio passthrough and improved performance/accuracy (separating clock and redraw coroutines). Also the UI is looking much better.

I’m looking into implementing loading samples from tape but I’m honestly not sure where to start, any tips would be welcome! Please report any bugs you all find. Onward!

2 Likes
#16

happy to help with any sample loading q’s that the softcut studies don’t cover! lmk where there’s grey :slight_smile:

1 Like
#17

:+1: thanks! now that I have time I’ll dig into the studies with more rigor.

1 Like
#18

Installed this (via maiden) for the first time this morning and it doesn’t seem to do anything? Lots of graphic smearing when turning the knobs. I also noticed that it added beat, beat core/grid, and beat /core ui to the select menu?

Edit/update: the graphics do randomly clear and audio sporadically passes/repeats, but it also does this:

FullSizeRender

#19

Turning off the “glitch ui” setting fixes it, sometimes.

#20

The glitchy UI is actually intended and occurs more frequently and “violently” as the Glitch param gets closer to 100. The Glitch UI param disables this effect. Perhaps in future revisions, I’ll disable this effect by default.

As for the functionality, the Beat Repeater plugin from Ableton is notoriously confusing, so I am working on a guide and accompanying demo to demistify things.

All that said, I’m sure there are still bugs, a longer video with sound would be helpful for me to better understand the issues you’re having (and or clarify what is happening).

4 Likes
#21

Yeah :sweat_smile:

It occurred to me later, having some experience with the notorious Ableton Beat Repeater, that most likely I was just doing it wrong.

Looking forward to that guide/demo! hahaha

2 Likes
#22

small suggestion; you may want to skip setting softcut.rec(voice, 0) at runtime, like here:
[ https://github.com/frederickk/b-b-b-b-beat/blob/primary/b-b-b-b-beat.lua#L119 ]

rec(0) will immediately disable the write heads for a voice, usually causing a click in the buffer, and rendering the following call to rec_level irrelevant. (whereas rec_level(voice, 0) applies smoothing, but should probably be accompanied by pre_level(voice, 1).)

using rec_level and pre_level alone during runtime is usually sufficient and produces less artifacts

(use rec() as a set-and-forget flag indicating to softcut that you do or do not want to use the voice for writing during the lifetime of the script or when transitioning to some mode where potential write-discontinuities are not a problem. i should obviously have named these functions better and softcut 2.0 will break the API to be less surprising.)

1 Like