#11

Right. I’m going to have to pass this one up the food chain. Sorry, I don’t have a clue.

@tehn any idea why on this?

#12

we’re missing the top of the stack trace so can’t see why banging the parameter set is failing - probably while calling a param update func.

@samule.edmoon it would be good if you could post more of the matron output, preferably as text instead of a screen photo.

one possible (likely) reason is that you don’t have PolyPerc installed. (it’s installed by awake now.) the stack trace would be consistent:

### SCRIPT ERROR: init
/home/we/dust/code/strum/strum_pp.lua:632: attempt to call a nil value (field 'pw')
stack traceback:
	/home/we/norns/lua/core/norns.lua:185: in field 'pw'
	/home/we/dust/code/strum/strum_pp.lua:632: in field 'action'
	/home/we/norns/lua/core/params/control.lua:76: in function 'core/params/control.bang'
	/home/we/norns/lua/core/paramset.lua:272: in function 'core/paramset.bang'
	/home/we/dust/code/strum/strum_pp.lua:646: in function 'init'
	/home/we/norns/lua/core/script.lua:71: in function 'core/script.init'
	[C]: in function 'xpcall'
	/home/we/norns/lua/core/norns.lua:186: in field 'try'
	/home/we/norns/lua/core/engine.lua:83: in function </home/we/norns/lua/core/engine.lua:82>
>> reading PMAP /home/we/dust/data/strum/strum_pp/strum_pp.pmap
#13

The PolyPerc version of Strum works for him. It’s the KarplusRings version that throws the error.

#14

ah right, sorry. in that case maybe KarplusRings is missing (it lives in we/lib, since its author has not claimed it) - the stack trace would be similar. both versions work fine for me with the engines installed.

2 Likes
#15

Both versions are working fine for me.

This happens for me as well, but pressing key3 loads the script…

#16

oh right: ‘no script information’ is due to the leading whitespace (typo) in the first comment line of the scripts.

2 Likes
#17

Ok. Will fix this in repo.

Edit: updated.

#18

I think I may have deleted the we/lib by accident. Is there any way to reinstall it?

Norns: help
#19

Not sure. Ask in the help thread.

#20

@carvingcode, strum is super fun! can’t believe I waited so long to play with it :slight_smile:

Edit: realized that this was solved in another thread :slight_smile:

2 Likes
#21

Glad to hear it. Sometimes, simple things work.

2 Likes
#22

On the params page for both strum scripts the amp value doesn’t raise or lower the volume of the engine for me. Anyone else? Also if I set midi out and set the channel to any value it always sends out on channel one

#23

I really don’t know why that is. I’m using the same code for setting up parameters as Awake. The AMP param works in Awake, but not in the PolyPerc version of Strum. Same with the KarplusRings version.

Mysteries of norns…

#24

Enjoying strum kr… I love the way it runs extremely fast and has great staccato sounds.

Can I ask how one accesses the reverb - or turns it off? though it is very nice i want to go much dryer into my DAW. I am confused about this over a few of the dust apps. is it just a question of whether the coder has brought these controls through to the parameters page?

#25

Try the SYSTEM > AUDIO menu

#26

THANKS! I hadnt twigged there was another menu there…a whole other world of controls. Half suspected i was missing something obvious.

1 Like
#27

neato script!

running it with both MIDI and Audio.
MIDI into the Deluge and also clocking a Little Deformer 3.

1 Like
#28

Sequencing the endorphin.es shuttle system with strum this morning. Really love the simplicity of this sequencer, thanks @carvingcode

3 Likes
#29

This may be some issue on my end (running the Karplus Strum on a Fates, rather than a Norns), but I find consistently that when I map the last of the parameters to a MIDI controller (I’ve tried several, mostly a Launch Control, the small one), after fiddling with that specific controller briefly, the audio always cuts out entirely. If I only map the others, I can play with them to my heart’s content (and my heart is content, as Strum is a pleasure to use).

The issue has no equivalent in the PolyPerc Strum.

#30

it looks to me like there are several parameters in the KarplusRings engine that are not clamped to safe values and could easily blow the thing up.

in particular, the last parameter looks like “bpf_res”, which if “res” means “resonance” is a misnomer - it is mapped to the rq parameter of the BPF UGen, so controls the reciprocal of its Q/resonance.

in other words, the rq value specifies bandwidth in proportion to center frequency.

setting rq=0 makes an infinitely resonant biquad; noise is fed through this into the input of a Pluck karplus-strong resonator. this could certainly blow up the resonator.

RQ should be clamped to, i dunno, 0.00166666 or something. (that’s a bandwidth of 1 cent if my math is right)

4 Likes