hihi! hope all’s well 
thought this might be a good way to share steps for modifying the script at home!
finding the functions
since the record enable + clear all buffers actions are both tied to keypresses, start by finding where keypresses are defined by searching function key in the script. the key function is standard for all norns scripts – it’s how the system layer reports to the script that a keypress/release has occurred.
key 2 (record)
reading through, here’s key 2’s action:
-- KEY 2
if n == 2 and z == 1 then
record()
end
rad! this means that record() is the function which handles all the recording.
clear all buffers (hold K3 then hold K1)
reading through, here’s the key combo which clears all the buffers:
-- KEY 1
-- hold key 1 + key 3 to clear the buffers
if n == 1 and z == 1 and KEY3_hold == true then
clear_all()
KEY1_hold = false
-- Proposed fix to allow clear and re-record
softcut.buffer_clear()
for i = 1, TRACKS do
softcut.loop_start(i, 0)
softcut.position(i, 0)
end
softcut.event_phase(phase)
note: if i was writing this script now, i’d put all that stuff inside of the clear_all() function – i learned a lot in 4 years! but we’ll work with this
make these parameters!
since norns offers MIDI mapping through the stock parameters system, let’s build some parameters to trigger these functions. i think the trigger style binary parameter will probably be best.
if we search for params:add in the script, we can see where parameters are built.
let’s put our two new parameters at the top of our script’s parameters:
-- format: params:add_binary('scripting_id', 'display name', 'behavior')
params:add_binary('rec_flag', 'rec', 'trigger')
params:set_action('rec_flag', function() record() end)
params:add_binary('clear_all', 'clear buffers', 'trigger')
params:set_action('clear_all',
function()
-- this is just copied/pasted from our k3+k1 action:
clear_all()
KEY1_hold = false
-- Proposed fix to allow clear and re-record
softcut.buffer_clear()
for i = 1, TRACKS do
softcut.loop_start(i, 0)
softcut.position(i, 0)
end
softcut.event_phase(phase)
end
)
closing
and that should do it! a quick re-run of the script should add these parameters and allow you to MIDI map to 'em. while learning how to script can be daunting, learning how to read and search through a script is often a more-approachable first huge win. lmk if you run into any trouble, though – totally happy to help chat through these types of modifications.
