#2327

the weird thing is I absolutely did not hear any of this. Like, the tape recording is nothing like what I heard at those points. (It happened on two tapes from two different scripts: mangl and cheatcodes.

#2328

Has anyone experienced screen banding when filling big shape with multiple curves with screen.level(1) & screen.aa(1) and text at level(15)?
I switched to using lines from curve and it improved, so I suspect this is a low level software issue?

(On fates hardware, not that is should matter as its the exact same new haven display module)

#2329

do you recall if your MONITOR level is turned up? ie is the audio input stage getting into the tape recording?

(side note: the shield audio circuitry is primitive compared to the actual norns (which has good isolation))

this is normal for the newhaven displays, and it’s annoying for sure. there might be some driver-level adjustment that could be made (though i’ve spent too long with NH tech support already, if someone wants to jump in on that).

#2330

ah, yes, MONITOR was all the way up, but nothing connected. so that’s not a good start, and might be related… and I had Wifi on as well. It was just the first time I looked at a TAPE recording on a computer, is all, hence flagging it. I’ll keep an eye on it and try something again in the near future.

#2331

Is there a general MIDI I/O and learning or does it change between engines?

#2332

midi learn works for most parameters. parameters are defined by the script, and are often associated with engine params. yes you have to remap midi mapping for each script— it generally doesn’t make sense to have persistent mappings as scripts differ drastically. you could theoretically write a script that have standard mappings, but i don’t think that’s what you were asking?

1 Like
#2333

Learning how to use my new Norns. I’ve manage to download a bunch of new apps from the Maiden library that all appear to be working, save for the one I want to use most: Otis. Initially I was getting an error saying it was missing Decimator, but after deleting and reinstalling it that problem was fixed.

Now I’m just getting an “error: init” message. Here’s the matron info:

SCRIPT ERROR: init

/home/we/norns/lua/core/softcut.lua:140: bad argument #3 to ‘cut_param’ (number expected, got nil)
stack traceback:
/home/we/norns/lua/core/norns.lua:126: in function </home/we/norns/lua/core/norns.lua:126>
[C]: in field ‘cut_param’
/home/we/norns/lua/core/softcut.lua:140: in function ‘core/softcut.pre_filter_fc_mod’
/home/we/dust/code/otis/lib/tlps.lua:88: in field ‘init’
/home/we/dust/code/otis/otis.lua:239: in global ‘init’
/home/we/norns/lua/core/script.lua:93: in function ‘core/script.init’
[C]: in function ‘xpcall’
/home/we/norns/lua/core/norns.lua:127: in field ‘try’
/home/we/norns/lua/core/engine.lua:91: in function </home/we/norns/lua/core/engine.lua:89>
reading PMAP /home/we/dust/data/otis/otis.pmap

Thanks!

#2334

Did you restart Norns after install? That’s when I typically get a error:init

#2335

there’s a bug in the last norns update that will be fixed momentarily

2 Likes
#2336

Ah got it! Thanks.

I did restart Norns after the update. That confused me at first, but I did it eventually!

#2337

Just updated Norns again, but still getting the error: init message on the main screen unfortunately. Again, appears to just be for Otis. Every other app seems to be working. Any ideas?

#2338

Hey friends. I can reproduce in Otis, and I posted my maiden readout over in that thread.

#2339

@CrookedWalking and @mattlowery, I am getting this here as well. Since nothing changed in Otis, I am wondering if it could be a softcut issue?

#2340

will check this out, sorry again

1 Like
#2341

No worries, appreciate you guys!

#2342

All good! This thing is complicated for me, but this forum (and you!) are so appreciated and make me feel like I’ll be able to wrap my head around it :joy:

#2343

this is in fact working.

what you need to do is re-run the 200129 update by holding K1 while executing SYSTEM > UPDATE

#2344

Odd, I re-ran the update this morning before testing. Will try again.

Edit: Re-ran the update, and I’m still getting the same error.

# script init
### SCRIPT ERROR: init
/home/we/dust/code/otis/lib/tlps.lua:97: attempt to call a nil value (field 'post_filter_fc_mod')
stack traceback:
	/home/we/norns/lua/core/norns.lua:126: in field 'post_filter_fc_mod'
	/home/we/dust/code/otis/lib/tlps.lua:97: in field 'init'
	/home/we/dust/code/otis/otis.lua:239: in global 'init'
	/home/we/norns/lua/core/script.lua:93: in function 'core/script.init'
	[C]: in function 'xpcall'
	/home/we/norns/lua/core/norns.lua:127: in field 'try'
	/home/we/norns/lua/core/engine.lua:91: in function </home/we/norns/lua/core/engine.lua:89>

Did softcut.post_filter_fc_mod get removed?

1 Like
#2345

will check and fix! weird that it was working for me

1 Like
#2346

Same here. Re ran the update this morning and still got the error.