#1258

No, by “connection looks ok” just means that the solder joints onto the PCB look good, and the physical connections in the jack piece are functioning correctly. I didn’t run any software trace (honestly don’t how to do that). I went ahead and sent a message to info@monome.org. The original seller has no clue what the problem is. He dumped it after just a few hours of use, because it was too complicated for him. So he’s not a good resource for help. I might push for a refund…but its probably easier to just get it fixed, than wait/try-to-find a new one.

2 Likes
#1259

Forgive me (in advance) for tossing out a few n00b norns questions. I recognize that this might not be the right forum for doing so.

Do components of the norns installation get updated in between the norns updates? If so what is the recommended method for updating those? Does a git pull accomplish this or should I be manually downloading zip files from gitlab and then updating them through maiden?

Thanks!

#1260

talking about the actual norns software— just wait for norns updates. 2.0 has an auto-fetch installer from the menu. it’s going to be so painless (once there is one available)

regarding individual scripts, you have to manage these yourself. SFTP is the suggested route, delete and replace script folders.

if you want to get into git, you can, and there’s been copious help posted here about that— but also command-line isn’t for everyone and don’t feel obligated.

we’re working on some friendlier library updating mechanisms as well.

#1261

Pressing key 1 to switch between the list of scripts and the currently loaded script causes the audio output to drop-out for a split second. This began to occur ever since I added more scripts. Is that a known issue with 2.0?

1 Like
#1262

yes, known issue: https://github.com/monome/norns/issues/815

will identify a fix soon.

1 Like
#1263

A post was merged into an existing topic: Norns: scripting

#1264

is there a way to set midi control over the levels screen from a bank of faders?

#1265

yes but not via the menu. you’d need to write it into your script to control the mix parameter set. see https://github.com/monome/norns/blob/master/lua/core/mix.lua

2 Likes
#1267

I’ve mucked up the file setup on norns mainly the dust folder so I thought I’d just reinstall 190405. However, when I selected update - cleverly norns knows and responds with ‘up to date’.

ok how can I just go back to a fresh 190405?

1 Like
#1268

edit: ignore, my bad.

I’m used to working via ftp and forgot it doesn’t exist in git like that anymore

#1270

Don’t do this :wink:
The dust repo is no longer used.
/home/we/dust is just a directory containing data, audio and code directories :slight_smile:

1 Like
#1271

Sorry if this is a noob question, but how is the perfect way to update scripts? Deleting the old one and uploading a new one via SFTP?
And how do I know which version of the script is already installed? This seems tricky…
thanks everyone!

1 Like
Norns 2.0.0
#1272

I just did the same, and would also love to know how to get back to a fresh Norns

1 Like
#1273

I am in a similar situation, since updating to 190405 my dust folders have come a mess. Not sure if there is a quick solution for this

22%20PM
Screen Shot 2019-04-19 at 10.14.22 PM.png1214×1038 193 KB

#1274

reset ~/dust manually

  • make backup copies of ~/dust, especially ~/dust/audio and ~/dust/data
  • delete the whole ~/dust folder
  • create ~/dust, ~/dust/audio, ~/dust/data, ~/dust/code
  • download we
  • move/copy we-master/ to ~/dust/code/we/ (<- rename important)
  • put other stuff (scripts) in ~/dust/code/THING
3 Likes
#1275

@Minimum @ptbarnum @riggar

Here’s what I do.

I keep 190405.tgz in my update folder on Norns and I don’t delete it. Because, I like to mess with stuff and I’ve been trying to teach myself Lua and it’s not an overnight thing at all haha. Also, I think the librarian script broke my Norns (duplicate engines? bad naming conventions? something…) so I stopped using it and things have been awesome again.

So since 190405 is already on my Norns, I actually use terminus on my iPad to login to norns via ssh, but you could also use terminal. Once you’ve logged in, simply navigate to the update folder by doing the following (I updated tehn’s comment):

(And if you’ve done this before, simply navigate to /update and just run the last line.)

…and don’t forget

sudo shutdown now

This update style makes a backup of your old dust and you can drag your audio back in for samples & tapes.

1 Like
#1276

I just followed @zebra instructions however my norns will no longer shut down on its own when I sleep and it appears that none of the scripts/engines are working although the WE master file is in code

01%20PM
Screen Shot 2019-04-19 at 10.55.01 PM.png1204×1032 135 KB

#1277

Should be lowercase ‘d’ in ‘dust’ and just ‘we’ not ‘we-master’. It’s important to match those paths exactly to zebra’s post.

1 Like
#1278

thank you that does appear to be the issue

2 Likes
#1279

So after updating to 2.0 and then uploading a few new scripts into the code folder over ssh, every single script became stuck on the ‘loading’ screen. After getting out of the frozen state and then deleting every newly added script I finally was able to load one of the pre-installed scripts. Is this just a case of a duplicated engine somewhere or did I install a script incorrectly?