splnkr

jaseknighter · 2022-01-17T23:34:54.241Z

splnkr v0.2.0 has been published. it includes some minor bug fixes and new live sampling capabilities requested by @marcus_fischer.

here is a video demonstrating the new live sampling code, with tape saturation and distortion added by @infinitedigits new tapedeck script.

glia · 2022-01-18T16:40:30.203Z

this is such a beautiful performance!

jaseknighter · 2022-01-18T17:26:31.012Z

thank you @glia. i really struggled making this recording and the equal mixture of sequenced sounds made to a beat with sounds occurring at random. it makes me really happy to hear you liked it.

today, i’m going to see if i can setup an option to sync the live voices to the script’s beats and to one another.

dondelion · 2022-01-18T20:10:30.433Z

This looks amazing but I’m having issues loading samples on my Shield. Whichever sample I load I never get any cutters showing and I am unable to add any from the autogenerate screen. I’ve tried rebooting, restarting and reinstalling but it’s always the same. I’m using midigrid if that makes a difference and the samples work on other scripts. Maiden repeatedly gives me this error

lua: /home/we/dust/code/splnkr/lib/sample_player.lua:333: attempt to index a nil value (field '?')

stack traceback:

/home/we/dust/code/splnkr/lib/sample_player.lua:333: in function </home/we/dust/code/splnkr/lib/sample_player.lua:302>

Any ideas?

jaseknighter · 2022-01-18T20:46:29.965Z

@dondelion, ooops…i’m sorry about that.

i think i fixed these issues. if you update the script, the cutters should appear and autogenerating cutters should now work.

dondelion · 2022-01-21T16:27:02.459Z

I had a bit of time watching the videos and getting acquainted with this deeep script. We’re not best friends yet as it keeps spiralling out of control as I lose track of its actions but I am really enjoying its company.

Things I noticed -

recsamp->voice->cutter only ever has the option to select 1 cutter
when adding additional cutters you lose the position of your existing cutters. grrr it took me ages to find that loop point!
k2 on the adjust screen and on the move screen deletes cutters (undocumented?) and I keep hitting it accidentally and it also resets your existing cutters.
rates of voices 2 and 3 change to that of voice 1 unpredictably.

Thanks for your gift of this monster!

jaseknighter · 2022-01-21T20:47:06.759Z

thank you so much for this great feedback!

i keep thinking there’s a way, (perhaps on a different screen) of visualizing outputs that have been sequenced so you don’t have to keep everything in your head.

i’ll work on investigating addressing the things you noticed. probably, i’ll start with the issue that resulted in grrr.

in terms of k2 deleting cutters, i think i added this to the documentation in the last release, but i can change it so it requres k1+k2 to delete (so it doesn’t happen as easily by accident).

jaseknighter · 2022-01-28T00:15:17.290Z

splnkr v0.3.0 has been released with updates requested by @dondelion and @H.K, including:

the save sequence params submenu has been replaced with a new data management submenu, which now allows the following to be saved:
- sequence data
- recorded sampler settings (norns page 1)
- live sampler settings (norns page 2)
recsamp->voice->cutter now has the option of selecting multiple cutters
delete cutters with k1 + k2 to prevent deletions by inadvertently pressing k2 by itself
if a cutter has been modified on norns pages 1 & 2, adding and deleting new cutters will not change the modified cutter.
- important note: a modified cutter may be still be deleted with k1+k2

i haven’t been able to replicate rates of voices 2 and 3 changing to voice 1 unpredictably but if i can get a more predictable set of steps to replicate this i’ll investigate further.

ampism · 2022-01-31T12:11:40.039Z

Hi,

I’m getting an “error:load fail” message when I try to open splnkr.

Have got the latest version. Tried shutting down the shield and booting up again, same deal.

Any thoughts?

Cheers!

jaseknighter · 2022-01-31T15:48:03.211Z

@ampism, are there any error messages showing up in maiden?

ampism · 2022-01-31T16:37:20.721Z

says this in maiden:

script load: /home/we/dust/code/splnkr/splnkr.lua

cleanup

script clear

including /home/we/dust/code/splnkr/lib/includes.lua

SCRIPT ERROR: load fail

/home/we/dust/code/splnkr/lib/includes.lua:10: module ‘sequins’ not found:

no field package.preload[‘sequins’]

no file ‘/home/we/norns/lua/sequins.lua’

no file ‘/home/we/norns/lua/core/sequins.lua’

no file ‘/home/we/norns/lua/core/params/sequins.lua’

no file ‘/home/we/norns/lua/lib/sequins.lua’

no file ‘/home/we/norns/lua/softcut/sequins.lua’

no file ‘/home/we/dust/code/sequins.lua’

no file ‘/usr/local/share/lua/5.3/sequins.lua’

no file ‘/usr/local/share/lua/5.3/sequins/init.lua’

no file ‘/usr/local/lib/lua/5.3/sequins.lua’

no file ‘/usr/local/lib/lua/5.3/sequins/init.lua’

no file ‘/usr/share/lua/5.3/sequins.lua’

no file ‘/usr/share/lua/5.3/sequins/init.lua’

no file ‘./sequins.lua’

no file ‘./sequins/init.lua’

no file ‘/usr/local/lib/lua/5.3/sequins.so’

no file ‘/usr/lib/arm-linux-gnueabihf/lua/5.3/sequins.so’

no file ‘/usr/lib/lua/5.3/sequins.so’

no file ‘/usr/local/lib/lua/5.3/loadall.so’

no file ‘./sequins.so’

stack traceback:

/home/we/norns/lua/core/norns.lua:144: in function </home/we/norns/lua/core/norns.lua:144>

[C]: in function ‘require’

/home/we/dust/code/splnkr/lib/includes.lua:10: in main chunk

[C]: in function ‘dofile’

/home/we/norns/lua/core/startup.lua:43: in function ‘include’

/home/we/dust/code/splnkr/splnkr.lua:7: in main chunk

[C]: in function ‘dofile’

/home/we/norns/lua/core/script.lua:186: in function </home/we/norns/lua/core/script.lua:186>

[C]: in function ‘xpcall’

/home/we/norns/lua/core/norns.lua:145: in field ‘try’

/home/we/norns/lua/core/script.lua:186: in function ‘core/script.load’

/home/we/norns/lua/core/menu/preview.lua:23: in function ‘core/menu/preview.key’

/home/we/norns/lua/core/menu.lua:140: in function </home/we/norns/lua/core/menu.lua:117>

script clear

lua: /home/we/norns/lua/core/clock.lua:59: bad argument #1 to ‘resume’ (thread expected)

stack traceback:

[C]: in function ‘coroutine.resume’

/home/we/norns/lua/core/clock.lua:59: in function ‘core/clock.resume’

jaseknighter · 2022-01-31T16:39:05.909Z

i think you need to upgrade to a newer version of norns so the script can use the sequins library.

ampism · 2022-01-31T17:21:31.441Z

Ah! ok.
I thought I had the latest version.
Sorry for dumb question but how do I upgrade?

DoS · 2022-01-31T17:26:27.977Z

ampism:

how do I upgrade?

Find your way to System > Update on the main Norns menu and if there is a new version of the OS, confirm that you would like to go ahead. Once that’s done, the system will ask to be shut down and restarted.

ampism · 2022-01-31T17:46:01.166Z

Ok, thanks @DoS . @jaseknighter
Did update, but then after restarting got “error: init”
?

DoS · 2022-01-31T18:01:03.181Z

ampism:

after restarting got “error: init”

Interesting; so did I, with the following results in Maiden:

### SCRIPT ERROR: init
/home/we/norns/lua/core/paramset.lua:122: paramset.add() error: id 'show_env_mod_params' is already used by another parameter
stack traceback:
	/home/we/norns/lua/core/norns.lua:145: in function </home/we/norns/lua/core/norns.lua:145>
	[C]: in function 'error'
	/home/we/norns/lua/core/paramset.lua:122: in function 'core/paramset.add'
	/home/we/dust/code/splnkr/lib/parameters.lua:1207: in field 'init_envelope_controls'
	/home/we/dust/code/splnkr/lib/parameters.lua:1249: in field 'init'
	/home/we/dust/code/splnkr/splnkr.lua:107: in global 'init'
	/home/we/norns/lua/core/script.lua:126: in function 'core/script.init'
	[C]: in function 'xpcall'
	/home/we/norns/lua/core/norns.lua:146: in field 'try'
	/home/we/norns/lua/core/engine.lua:91: in function </home/we/norns/lua/core/engine.lua:89>

Splnkr was working as far as I recall before the 220129 Norns update. I am using Midigrid too, but that seems to initiate before the error:init message occurs.

jaseknighter · 2022-01-31T19:44:00.938Z

it looks like we have two separate issues here.

the first is related to the lattice library requirement.

the second issue appears related to the latest norns update which i think will require some changes in the splnkr script (and flora too btw).

i have a laptop that is being repaired but i’ll be picking it up shortly so i should be able to look into this in the next few hours.

EDIT
a small fix has been posted to address issues uncovered by the latest norns: update 220129 that prevent the script from loading. thanks @ampism and @DoS for the assistance!

ampism · 2022-02-05T11:40:02.902Z

Thanks. I have a gig tomorrow and I’ll be using MLR, so I’ll wait until after that before I do this…

DoS · 2022-02-05T11:44:54.963Z

ampism:

I’ll wait until after that before I do this…

Since my post above, there’s been a hotfix issued to the latest Norns update for this problem, which is outlined here and in more detail in the full thread:

norns: update 220129 Monome

TL/DR: navigate to http://norns.local, enter these two lines in the matron REPL, and all scripts should work again: os.execute("cd ~/norns; git pull") ;restart [uhh caveat: this is assuming you haven’t done any “special” developer stuff with your norns. e.g. if you have cloned norns via ssh and your ssh key is passphrase-protected - mine is, of course - then this command will fail; you need to ssh in and pull from there.] in this update, we introduced a new error message to catch a potentia…

I just checked and splnkr loads fine now.

And good luck with the gig.

ampism · 2022-02-05T12:59:27.300Z

DoS:

And good luck with the gig.

Thanks!

Regarding the norns local thingy; I seem to recall that didn’t work for me, so to access maiden I use a number 192.blah.blah in my browser - Can I do that in this context?