swhic
536
Deleted cc the issue persists.
EDIT buzz tone is constant on norns outs
a script wouldn’t cause that, so there’s gotta be something else going on. i’ll dm!
1 Like
I always wondered what “distro” means. 
2 Likes
Blit
539
YES! Thanks a lot! This is super dope. I loved that feature on the oooooo. Its going to be much easier to record and correct those recordings 
Now both apps are starting to overlap. Maybe one day the will fusion to create Cheat Coooooodes
4 Likes
swhic
540
that comes on fates:
pset >> read: /home/we/dust/data/cheat_codes_2/cheat_codes_2-01.pset
pset :: /home/we/dust/data/cheat_codes_2/cheat_codes_2-01.pset not read.
SCRIPT ERROR: init
/home/we/dust/code/cheat_codes_2/lib/start_up.lua:125: attempt to call a nil value (field ‘rebuild_params’)
stack traceback:
/home/we/norns/lua/core/norns.lua:138: in field ‘rebuild_params’
/home/we/dust/code/cheat_codes_2/lib/start_up.lua:125: in field ‘action’
/home/we/norns/lua/core/params/option.lua:52: in function ‘core/params/option.bang’
/home/we/norns/lua/core/paramset.lua:437: in function ‘core/paramset.bang’
/home/we/dust/code/cheat_codes_2/cheat_codes_2.lua:1287: in global ‘init’
/home/we/norns/lua/core/script.lua:107: in function ‘core/script.init’
[C]: in function ‘xpcall’
/home/we/norns/lua/core/norns.lua:139: in field ‘try’
/home/we/norns/lua/core/engine.lua:91: in function </home/we/norns/lua/core/engine.lua:89>
Blit
541
Are you on the newest norns firmware? That happened to me a few minutes ago
1 Like
swhic
542
I am on fates… @okyeron ?
doesn’t look like fates has had an update yet – you’ll need to download the previous version. dang, hit after hit, hope you get up and running soon!
1 Like
@dani_derks so cool! and so glad that those bits of code helped. love your menu pop-down, brilliant! cheat codes is utterly amazing. not just saying that either. i know how awesome it is because… i’m a cheat-coder now! here’s my first cheat codes foray:
its really wild how fast cheat codes can take you into magical musical territory.
36 Likes
holy shit, zack, this is INCREDIBLE. what a fuckin’ entrance. thank you so much for your energy + for all of the special, embodied, and compelling instruments you’ve contributed to this ecosystem 
5 Likes
Cloud
546
If I may…which synth engine are you using on the OP-1 at the very beginning of the video?
1 Like
thats the sampler engine, with a sample of a piano: bechstein piano
the other patch is one of my favorite pads using the fm? engine: wobble pad
2 Likes
Cloud
548
Thank you so much. Guess it’s time to dust off my OP-1 after your inspiring video.
1 Like
Great update to an already wonderful script, thank you Dan!
Experiencing some strange behavior lately with norns running Cheat Codes 2…
Summary
The latest weirdness (maybe since the update?) is that I can no longer engage recording from my grid. When one of the record buttons is pressed, instead of engaging recording the looping buffer(if set to loop) will sort of freeze in place until pressed again. If mashed a few more times Norns itself will completely freeze up requiring a reset (k3+k2+k1).
I was getting this same behaviour last night, so this morning I did a fresh install>update>grab CC2, but still the behaviour is the same. The strange thing is that I CAN engage recording from the norns loop menu using K2+K3. I am on a Greyscale 64, and OG Norns.
It’s possible this is all user error, as about 50% of the time when using Norns I feel I am over my head 
… However this is coming off weeks of having crashing errors, where Norns would become unresponsive and make a constant buzzing sound until performing a hard reset. It got to a point last week where the audio output suddenly became very quiet and muffled(?) requiring a fresh install to get it back working.
I have done 3 fresh installs in the past few weeks but just can’t seem to shake these freezing issues. Sorta starting to wonder if maybe this 2nd hand Norns I picked up has some deeper issues…
Here are the last few lines in maiden before the latest crash:
[C]: in function ‘error’
/home/we/norns/lua/core/paramset.lua:357: in function ‘core/paramset.lookup_param’
/home/we/norns/lua/core/paramset.lua:301: in function ‘core/paramset.t’
/home/we/norns/lua/core/menu/params.lua:414: in function ‘core/menu/params.redraw’
/home/we/norns/lua/core/menu/params.lua:616: in field ‘event’
/home/we/norns/lua/core/metro.lua:165: in function </home/we/norns/lua/core/metro.lua:162>
lua: /home/we/norns/lua/core/paramset.lua:357: invalid paramset index: 82
stack traceback:
[C]: in function ‘error’
/home/we/norns/lua/core/paramset.lua:357: in function ‘core/paramset.lookup_param’
/home/we/norns/lua/core/paramset.lua:301: in function ‘core/paramset.t’
/home/we/norns/lua/core/menu/params.lua:414: in function ‘core/menu/params.redraw’
/home/we/norns/lua/core/menu/params.lua:616: in field ‘event’
/home/we/norns/lua/core/metro.lua:165: in function </home/we/norns/lua/core/metro.lua:162>
lua: /home/we/norns/lua/core/paramset.lua:357: invalid paramset index: 82
stack traceback:
[C]: in function ‘error’
/home/we/norns/lua/core/paramset.lua:357: in function ‘core/paramset.lookup_param’
/home/we/norns/lua/core/paramset.lua:301: in function ‘core/paramset.t’
/home/we/norns/lua/core/menu/params.lua:414: in function ‘core/menu/params.redraw’
/home/we/norns/lua/core/menu/params.lua:616: in field ‘event’
/home/we/norns/lua/core/metro.lua:165: in function </home/we/norns/lua/core/metro.lua:162>
lua: /home/we/norns/lua/core/paramset.lua:357: invalid paramset index: 82
stack traceback:
[C]: in function ‘error’
/home/we/norns/lua/core/paramset.lua:357: in function ‘core/paramset.lookup_param’
/home/we/norns/lua/core/paramset.lua:301: in function ‘core/paramset.t’
/home/we/norns/lua/core/menu/params.lua:414: in function ‘core/menu/params.redraw’
/home/we/norns/lua/core/menu/params.lua:616: in field ‘event’
/home/we/norns/lua/core/metro.lua:165: in function </home/we/norns/lua/core/metro.lua:162>
Apologies for the novel about my woes, would just love to get my Norns and CC2 into a more functional state, feeling like I’m in over my head trying to figure this out on my own tho…
hey hey! sorry to hear about the troubles.
the crashing and audio issues definitely point to some norns trouble, so please email help@monome.org and we can arrange further troubleshooting and potential repair.
not at my unit at the moment, but if you want to roll back to the previous script update it’s here: https://github.com/dndrks/cheat_codes_2/archive/ede8f49c0c277b491186bc6f50a6f4988975511f.zip. i’ll do some grayscale testing later today, but that version should get you running
Awesome, thanks so much @dani_derks. That’s actually super relieving to hear it might be something beyond my control… Will send an email that way!
1 Like
Could somebody please let me know on what line number I should add local grid = include(“midigrid/lib/mg_128”) in Cheat Codes? I can’t seem to find the g = grid.connect() line . . . .
Thanks in advance!
hey hey! the script handles all the connection, so you just need to modify line 25 of the main script and replace “midigrid/lib/midigrid” with “ midigrid/lib/mg_128”.
then:
- params > grid > midigrid set to yes
- params > grid > size set to 128
then turn your launchpads sideways and stack them cuz it’s a vertical interface on the 128
heads up: with launchpads, the 64 interface is much better — the line break between the two cuts thru the second bank and doesn’t feel as nice
1 Like
Thanks for the quick reply!
When you say “the main script,” are you referring to cheat_codes.lua? I don’t see midigrid/lib/midigrid there - here is what I see around that spot:
tau = math.pi * 2
arc_param = {}
arc_switcher = {}
for i = 1,3 do
arc_param[i] = 1
arc_switcher[i] = 0
end
arc_control = {}
for i = 1,3 do
arc_control[i] = i
end
Maybe I have an outdated version installed? I got mine from the project manager - should I install it directly from github?
Ideally, I would like to install two versions - one for when I am using a single LP, and another when I am using both as a 128.
Thanks again!
1 Like
