#457

Use the search/replace function in your text editor to save time! sorry if you knew this already

1 Like
#458

replacing ‘g.’ with ‘g:’ will introduce hidden problems - ‘g’ is a poor choice for a name in this case although it saved me a lot of typing originally

something. becomes something:

(I mean I am going to automate it but I’m not just search and replacing blindly)

3 Likes
#459

Saw this on the norns 2.0 page on git hub

MIDI-CC MAPPING on and the param screen now shows cc channels. params with a dash are mappable. use ENC3 to scroll cc number. push KEY3 to toggle MIDI LEARN, where the next incoming midi cc will be assigned to the parameter.

is the channel setting implemented yet, or is that a typo?

#460

however - might be winning! think it works - bit of testing and I’ll post a link to my repo

3 Likes
#461

I believe these globals are not for use by scripts, but @tehn can probably tell more about this.

#462

yeah - i’m not really sure, but I saw at least 3-4 scripts that had previously used home_dir or data_dir and threw errors on run with the new build.

1 Like
#463

2.0 WiFi is great! I was able to connect to my iPad, via a hotspot from my phone, and successfully script, save and run from the tablet. Then, a nice little MLR jam with the Rode mic through the same iPad.

image
833CB42C-E472-48D4-BEB2-7869ECBB2467.jpeg3024×4032 2.48 MB

20 Likes
#464

Not sure if this is the right place for this, but one weird thing w/ MLR. When selecting the loop length, on the second page, for track one, the loop always extend one button to the left of the one I selected. The other three tracks are presice to my selection. It’s just track one that’s off.

#465

quick dust/we question:

library scripts - how do you stop those showing up on the main menu? I’ve got a few supporting scripts that aren’t top level and don’t want people to try loading them

3 Likes
#466

You make a folder with the name of your script to contain it all, then a lib folder inside to contain the hidden scripts:

See the section on libs here: https://github.com/monome/norns/wiki/dust-2.0

4 Likes
#467

cheers - knew it was in there somewhere but suffering from ‘too much to learn’ right this second.

3 Likes
#468

copy the Kria directory from here https://github.com/junklight/misc/tree/master/dust/code (the other stuff isn’t 2.0 compatible yet - working on those)

all seems to be working

edit: The BowMPE script works as well! - not tested with light block - presume that still has issues but is great with my seaboard

10 Likes
#469

There’s something funny going on for me - I haven’t been able to get it to find softcut scripts in any of the beta updates including this one. I’ve tried in the directory with the script; and in ./lib. Any ideas?

/home/we/dust/code/boingg/boingg.lua:13: module 'looper1' not found:
	no field package.preload['looper1']
	no file '/home/we/norns/lua/looper1.lua'
	no file '/home/we/norns/lua/core/looper1.lua'
	no file '/home/we/norns/lua/core/params/looper1.lua'
	no file '/home/we/norns/lua/lib/looper1.lua'
	no file '/home/we/norns/lua/softcut/looper1.lua'
	no file '/home/we/dust/code/looper1.lua'
	no file '/usr/local/share/lua/5.3/looper1.lua'
	no file '/usr/local/share/lua/5.3/looper1/init.lua'
	no file '/usr/local/lib/lua/5.3/looper1.lua'
	no file '/usr/local/lib/lua/5.3/looper1/init.lua'
	no file '/usr/share/lua/5.3/looper1.lua'
	no file '/usr/share/lua/5.3/looper1/init.lua'
	no file './looper1.lua'
	no file './looper1/init.lua'
	no file '/usr/local/lib/lua/5.3/looper1.so'
	no file '/usr/lib/arm-linux-gnueabihf/lua/5.3/looper1.so'
	no file '/usr/lib/lua/5.3/looper1.so'
	no file '/usr/local/lib/lua/5.3/loadall.so'
	no file './looper1.so'
#470

I’ll have to take a look again tonight at structure, but I realized I probably won’t want it in the same folder anyway because then it shows up in MENU > SELECT >

prior to the newest beta I was placing it in /norns/lua/softcut/, so you could do that for now.

1 Like
#471

Yes, that works - but obvs not ideal as the script can’t be edited in maiden. Hmm. Let me know if you discover what’s going on. Thanks!

#472

can you tell us the file locations and the require string that you are using?

ie

dust/code/ish/ish.lua
dust/code/ish/lib/thing.lua

and then in ish.lua (corrected!):

require `ish/lib/thing`

this should work! :grimacing:

1 Like
#473

I have fired up cyber duck, and want to connect with norns via serial cable. It cannot connect to any wifi since the last update however

How do you use cyberduck to connect with serial cable. cyberduck just hangs, spinning wheel etc

#474

To serial connect, use the USB A to USB mini cable that came with norns. Connect the USB A side to your computer.

Scroll back to the first message in this thread. Follow the steps listed there for upgrading. It will become clear.

1 Like
#475

I understand the cable connections. - i am looking for something even more explicit that just use smtf to transfer the file. For example what do i put in the server field? do i use we and sleep for user and password here too?

I connected via wifi using cyberduck previously and now norns is in poorer state. I want to connect with serial, get it back to working state, even 1.0 at this stage . although i believe i need osx 10.14 to do a full image transfer - not an option for me just now. Hopeful i can get the latest 2.0 and bring back some normality.

#476

Cyberduck is SFTP (or regular FTP) and will only work over a wired or wireless network connection.

The serial business will get you command line access, but not SFTP.