#43

mmmmm ok, yeah, i have an idea. thanks marcus!

2 Likes
#44

You should be able to queue up slew and level changes to make envelopes?

2 Likes
#45

exactly what iā€™m thinking ā€“ queuing using a metro, right? wouldnā€™t work just by stacking like this:

if enveloped then
     softcut.level_slew_time = 0.3
     softcut.level(2,0)
     softcut.level(2,1)
end

ā€¦which makes sense, but just wanted to confirm. running low on metroā€™s :sweat_smile:

#46

I was about to install it, but I canā€™t find it in the library right now. Is it my problem or is it something server-side?

#47

did you refresh community catalog with the icon? should show as cheat_codes:

image
image2768Ɨ1104 169 KB

#48

Yes, Iā€™ve even tried with a browser I had never used with norns and I canā€™t see it :confused:

#49

weird, i see it with two different norns. perhaps reboot both norns and your computer?

#50

Iā€™ve tried on both my norns (both rebooted), and on two computers, and I canā€™t see it in the ā€œAvailableā€ tab in the library. I will try again later!

#51

super strange ā€“ please keep me updated!

oo, can you use maiden to navigate to data > catalogs > community.json and let me know if cheat_codes shows up on line 83? that would determine if your refresh is actually downloading the new catalog

also, ditto what @Justmat posted below

1 Like
#52

when you say you refreshed the list, just to be sure, you do mean that you used the icon next to community on the available page, and not just refreshed the browser tab?

2 Likes
#53

I thought clearing the cache and reloading the page was enough, thanks @Justmat, this solved it! I just didnā€™t think about it, sorry :smiley:

2 Likes
#55

yeah, sorryā€¦ i guess the idea is that the construct you show should work, but in practice i see why it would not.

we can address it in a couple ways, maybe this thread is not best context for that discussion

i will say that i donā€™t see any reason not to increase the metro count to something larger if itā€™s needed. change needs to be in two places, matron source and lua module

1 Like
#56

i feel like the answer is right under my nose but whenever i try recording a sample to chop it disappears (within seconds)

initially i thought this was cause the default feedback setting is erasing it but the problem still occurs when feedback is set to 0

is my loop hiding somewhere and i have to press play some how? iā€™m sure this is user error

any help would be greatly appreciated

#57

oh man, stoked for @glia jams

0 = full overwrite, try 100?

also, if you want to keep a recorded bufferā€™s content static you can do one of two other things with the keys on the bottom row:

A 1 2 3 | p p p p

  1. A(LT) + rec buffer number 1 / 2 / 3 (the three buttons to the right of ALT) will disable recording (and dim the key). hold ALT and press the bufferā€™s key again to re-enable recording.
  2. after recording into a rec buffer 1 / 2 / 3, just switch to one of the other buffers by selecting it (with no ALT). this will bring the record head into a different buffer and you wonā€™t be overwriting the contents of the other two.

please lmk if this helps! :slight_smile:

3 Likes
#58


(if someone knows how to fix the linkā€™s imageā€¦ :thinking: )

2 Likes
#59

it helped
thanks

hereā€™s a mono clip of my 1st session

7 Likes
#60

WOW! Amazing! Thank you so much!

1 Like
#61

Spent some time with Cheat codes tonight, really fun to play!

6 Likes
#62

Trying to get Cheat Codes up and running and maybe hereā€™s a bugā€¦?

Mapped 16n faders to some delay params. If I look at the params page I can see the values change, but if Iā€™m looking at the Cheat Codes delays page, the numbers do not change, unless some other interaction - like encoder turns - happens.

Soā€¦ looks like I can add a redraw() on line 199 and get that working:

clk_midi.event = function(data) clk:process_midi(data) redraw() end

:grin:

1 Like
#63

sounds right, thank you so much for investigating! i honestly threw in all the midi-controllable stuff last minute to help folks get started, but havenā€™t actually spent much time using a 16n or similar to test extensively. thank you(!!) for the report, will add that fix and explore midi interactions today to make sure itā€™s all groovy!

also excited to hear the sounds you make with it!

anything else getting in the way?

iā€™ve already gone through and fixed:

  • screen redraw with param adjustments
  • params write to a pad rather than perform momentary adjustments
  • swapped the option-style params to a midi-mappable control style (labeled (RAW))

this dev branch is up to date, if youā€™re able to test :slight_smile:

1 Like