splnkr

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?

DoS · 2022-02-05T13:05:50.827Z

ampism:

to access maiden I use a number 192.blah.blah in my browser - Can I do that in this context?

That should work too, I believe, if you can see the REPL.

jaseknighter · 2022-02-05T16:54:54.650Z

@ampism, i hope your gig is lots of fun! will it be recorded?

ampism · 2022-02-05T20:38:45.917Z

Thanks man!
Yes, it’ll be recorded. Gonna be processing Uilleann pipes samples that I triggered using the Initenere script. Sounds kinda chamber-ish when I start layering them in MLR. I’ll upload a snippet. Assuming I like it

H.K · 2022-02-16T04:44:08.639Z

I’ve been unable to touch Norns for a long time, so I’m late replying. I apologize for that.

I have to take care of my parents, so I can only enjoy Norns in my spare time. So, I really appreciate this update, which allows me to save my work frequently. Thank you very much.

I have one question about saving.

I understand that saving is “New Save”. This is fine for new work. When loading, editing, and saving saved data in the middle of work, is it possible to select from the saved data and overwrite it without entering a data name?

jaseknighter · 2022-02-16T08:00:43.775Z

@H.K, it shouldn’t be too difficult to put together a feature to overwrite existing data. i’ll work on this tomorrow. all the very best to you and your parents.

EDIT: a data overwrite feature has been added to the splnkr data params sub-menu. it appears to work for me but please do let me know if anything isn’t working as expected for you.

H.K · 2022-02-26T02:33:58.912Z

I apologize for the delay in replying again and again.

I have confirmed the loading of existing saves and the overwrite function. So far, it works fine.
Thanks to you, I can enjoy Splnkr in a short time.
Thank you very much for fulfilling my request.

One question: When I select LOAD SPLNKR DATA, there is a data “cancel.spl”, what is the purpose of this?

jaseknighter · 2022-02-26T21:10:05.307Z

hihi @H.K! I’m glad the new overwrite function is working for you. I’m not really sure why a data file called “cancel.spl” is showing up but I’m pretty sure you can ignore (or even delete) it.

0netwo0netwo · 2023-02-03T00:46:01.425Z

intro screen on my version of splnkr as well as the doc downloaded under the “v0.3.0 documentation” link up top says v0.2.0

just installed from maiden today, is there somewhere secret we have to go to get the v0.3.0??

thank you appreciate it

jaseknighter · 2023-02-03T02:35:16.203Z

@0netwo0netwo, erm…my file revision number updating team forgot to do its job. pretty certain you have the latest code already but the version number has been updated so if you do a fresh pull of the code you should see the right version number.

deepest apologies for the oversight.