I was playing around with loading in samples today and found that I couldn’t get arps going. Monobright 64. The visual met was just “X.X” flashing to tempo. Which was actually kinda cool. I was using link, and the transport was running. Maybe I’m missing something. I also have to pick monobrightness everytime I load a fresh cheatcodes.
which transport? Live’s? or cheat codes? if you don’t have “send start/stop” set in Live then starting Live’s transport won’t auto-start cheat codes — you’ll need to hold k2 on the main/home screen and press k3. lmk!
re: monobright, are you loading from a default collection? if you save a default collection with monobright selected, it shouldn’t de-select, but lmk
FYI I’m currently patiently waiting for Okyeron to update the fates so that I can run Cheat Codes 2 myself.
Update: currently installing update
@dan_derks I suspect I will have some suggestions or maybe a PR once I get CC2 running and I can try a few things out.
That was it.
Wasn’t familiar with the addition of transport. Got it now.
Ah, CC2 looks for varibrightness by default. Saving a collection does indeed save my monobright selection.
Hi @dan_derks - one additional question, please. If I want to start off with a single LP, do I have to make any changes to the code first (other than setting the parameters as you mentioned)? I ask because when I plugged in my single LP and tried to run Cheat Codes 2, I got an error:init.
@Clashley1 – glad to hear it all worked out! arps + euclid rely on the transport, so just make sure it’s running and you should be good!
@bharris22 , single Launchpad midigrid support is fully integrated, so you don’t need to touch any of the code, it’ll just run. any shot you’re not on the latest norns software update? it came out this past week .
otherwise, seems like some folks have had the outdated midigrid library – the one you need is Midigrid: use launchpads and other midi grid controllers with Norns, which can be installed by executing
;install https://github.com/jaggednz/midigrid in the maiden repl after deleting the old one.
if it isn’t those two, could you please share the errors that print to maiden when you load the script? sounds like something local, but easy to overcome!
Hi @dan_derks - I am pretty sure I am not on the latest norns update, as I have not updated this week. I will try this in the morning (it’s past my bedtime now) and report back - thanks!!
Midigrid with two devices aka. mg_128 does not play nice with cheat codes 2 at the moment. Working on a fix as I am able…
For some reason, after the past two updates whenever I playback a pad on any bank from the live buffer I get a lot of aperiodic popping. I checked to make sure I wasn’t clipping when recording into the live buffer, and even if I recorded at a super low volume I still get popping. It seems to act up more the quicker I play a pad in succession. It never did this when I first installed cheat codes 2, and my cpu averages around 43% when using cheat codes 2. I was wondering what could be the cause. Here’s an example : Cheat Codes 2 Poppin' by China Club | Free Listening on SoundCloud
super strange – the last two updates, while including new features, have actually been minor in terms of the code and include some refinements which have reduced CPU utilization on my devices. though if you’re able to do some regression testing, here’s the last major version: Release rev 210208 · dndrks/cheat_codes_2 · GitHub.
let’s do some digging
so this only happens with the live buffer? pre-recorded clips are totally fine?
- are you using a stock norns, or a norns shield?
- if a shield, there’s been a bit of a rise in folks whose units are misbehaving due to their power supply and more importantly the cable which transfers power not being up to spec. monome highly recommends this one. the Pi3B has a micro-USB power port and requires at least 2A and 5.25V ideally supplied through a cable with 24AWG or less. lower AWG = lower noise & more stable voltage delivery for better performance. most consumer USB cables do not meet this spec.
- are you actively recording when this artifact occurs?
- if this occurs most often when you’re actively watching the waveform pages under [loops], is there any difference over time when you navigate to another page (like the main one)? screen drawing for those waveforms is one of the most processor-intensive function in the norns system, so i’m curious if that’s what’s throttling your CPU. typically, my CPU utilization drops 10% when i navigate away from watching the waveform drawing. (I also just figured out a way to avoid this entirely, so hopefully this is actually the root of your trouble!)
- if you’re able, please save a collection which exhibits this issue and DM me a zip of the corresponding folder which gets made under
data > cheat codes 2?
your audio clip sounds dope otherwise, stoked to get this sorted!
Hi @dan_derks - updated my Norns this morning, and everything seems to be working fine. Thanks again for all of your assistance!!
rev 210307: CPU optimization + 64/midigrid live buffer hotfix
@Placebo92: the recording issue you mentioned was actually being caused script-side, due to an over-exuberant 128-sized copy-paste. it’s now fixed! (all of the other stuff you mentioned is definitely repair-qualifying though, so we’ll [monome] be in touch tomorrow through email!)
@climatechanged: i was able to refine the waveform redraw during live recording to reduce CPU by about 10% when recording. lmk if you run into any additional troubles, but hopefully a combo of this and a beefier charge cable will help resolve any further trouble
What’s going on with the Rytm in this video?
summary: if you have
midigridinstalled on your norns, you can use a Launchpad to access the same controls as a monome 64 grid. for more information about the 64 grid controls, see this image .
Do you have a pdf version of this and what font style you’re using? Want to make a printable version of this, but OSR in Acrobat Pro is really not liking the png conversion and then recognition. Thought I was going crazy too re: live clip recording and glad there was a fix for it too!!
64: grid-64.pdf (23.6 KB)
font: 04b_03.zip (10.2 KB)
if you have access to Affinity Designer, all of the design files are here: cheat-codes-docs/assets/images/afdesign at main · dndrks/cheat-codes-docs · GitHub
fwiw: going to be migrating to an online docs platform with native printability in the next month, so don’t put in too much work!
Thank you Dan! Here’s a quick and dirty if anyone else wants it that’ll be a bit easier on your printer: grid64 CC2 printable.pdf (32.7 KB)
honestly, nothing too wild – in the video i’m mainly using the new
transport settings under parameters to sync an auto-start of the arps + patterns on the grid with a transport start message sent to the rytm. everything stays in sync thanks to the
send MIDI clock? section of those transport params.
@dan_derks Thank you so much! The issue was the power supply, I just switched it out with the one that came with my raspberry pi and the pops went away.
Please forgive me if this has been requested dan. I would love a ‘usb on side’ option in the grid settings. By the looks of it I think the space is there. not a huge deal at all just a desk space type of thing lol. hope all is well and can’t wait for Monday to hopefully snag those workshop vids! cheers
is it possible to feed the live buffer without hearing the input on Norns outs?