#115

…had similar issues on 1, much better now but still quite slow (filezilla)

#116

FWIW - I get these errors when the data buffer fills up because the grid/arc refresh rate is too fast.

In the case of my DIY grid and DIY arc - this is about 30 frame per second (fps). Anything faster will throw libmonome errors (with certain scripts). Real Grids/Arcs seem to do ok up to 40/60 fps from what I understand.

However, step is checking to see if the grid is dirty before refreshing, so I think that means its not actually calling grid:refresh() every 1/60th of a second, right?

EDIT - for example - Glut (line 287) will throw these errors for me at 1/40, but not at 1/30. Crank that number up (down?) and you can probably reproduce the error.

1 Like
#117

Use the hotspot. It’s much faster in my experience.

1 Like
#118

I just stared at the update filename for 15 mins before realizing that you have to selected it with button 3 to start updating. :sweat_smile:

I would love a UI for dummies or people that don’t use norns daily. Like, the docs show the ‘pages’ levels/tape/home/params, but the ui on norns is just blank. Its a trap I fall into consistently throughout the norns interface. blabla I’m bad at this! :smiley:

Ok back to it!

edit:
I see 2.0 does have some tabs for the pages in the UI :smiling_face_with_three_hearts:

edit2:
all working, so cool!

1 Like
#119

If hotspot is much faster than using a normal WIFI connection then that most likely indicates signal strength issues since I’d assume that when using hotspot mode norns and one’s computer are in close proximity.

If one is pushing large amounts of data back and forth other options include:

  • if comfortable using ssh and the command line, using ssh to jump onto norns then copy the file to a usb stick
  • use a wired USB-to-gigabit ethernet adapter (this is what I normally use because I have an ethernet switch under my desk)
3 Likes
#120

3 posts were merged into an existing topic: Norns: scripting

#123

@karst e-mail info@monome.org to make sure your arc is ok. there were issues with the first short batch of aluminum arcs a few years ago.

1 Like
#124

I’m happy about the addition of a library category, but is there a standard for where documents should live on norns itself? Having a utility to add docs (images, and text files) to the documents directory when a script repository is cloned might be useful if scripts are intended to be ala carte in 2.0. I’ll probably just write a few lines to move the files directly on the first run of my scripts.

#125

you can put them in a docs folder within your project, and this folder won’t show up in SELECT.

there is presently not a solution for “serving” these files locally, but if they are present they can be displayed via a github link.

1 Like
#126

After a fair amount of trial and error, I was able to get the update applied by copying 190405.tgz to the directory root of my thumb drive (not norns190405.tgz as described in the documentation).

#127

thanks

odd but this trick worked for me

#128

Not really odd, because when you use the hotspot norns and the computer are usually close to each other (as @ngwese noted) and it’s a dedicated connection, so whatever other people or devices are doing with your home wifi you’ll always get good transfer speeds.

I’d need an usb-ethernet adapter for norns and another for the computer (mine has no ethernet port), with an ethernet cable in the middle, right? Would it be possible to fake ethernet over usb someway?

#129

That’s correct, there are dirty checks before update of arc, grid and screen. This is something I aim to do for all my scripts. Before, I had similar íssues when updating the grid in my scripts based on ultra-fast sequencer metros. Instantenous update of leds is not needed, and, to be honest, 60fps is probably quicker than what is needed too. I’m going to experiment with refresh rate.

1 Like
#130

image
608C56E8-BB76-4CFE-BE0E-73488F71BC71.jpeg4032×3024 2.43 MB

never did figure out the midi connect bug and the script has definitely crossed over into “too big to be manageable” territory and needs to be junked and largely rebuilt again… but i have to say for clueless people like me with like ~15 hours of code time a month, to be able to sit down and randomly add new interface support in a couple of hours without having to look anything up is seriously amazing. wanted to send thanks to everyone who contributed to v2!

11 Likes
#131

Manual update worked fine and everything seem to be back to normal. Thanks!

THough i’m noticing a bug in MLR where the pad lights don’t match when you hit them. (there seem to be a lag or offset)

#132

Quick question re. wifi connection: does Norns support both 2.4 and 5 GHz? My network (even with Norns in close proximity to the router) has never appeared, and I’m wondering if my 5 GHz setup has anything to do with it.

#133

I think the wifi nub is 2.4 GHz only. I have a dual-band router and only the 2.4 GHz version of my network shows up on Norns.

1 Like
#134

I’m having trouble re-naming files in maiden. This are fine if I leave the file as a default ‘untitled1.lua’ for example but as soon as I rename it - I keep getting file not found?

norns.script.load("code/Arigs/xyz")
# script load: /home/we/dust/code/Arigs/xyz
file not found: /home/we/dust/code/Arigs/xyz
<ok>
#135

I’ve noticed this too. it should be good if you either (a) restart norns or (b) select the script from norns (not maiden)

#136

yeah. I thought I fixed that bug but apparently something else is still broken. If you refresh the page (after having saved anything you have edited) and attempt the rename again it works.

I will investigate that as soon as possible.

UPDATE: I’ve created a GH issue for this https://github.com/monome/maiden/issues/155

2 Likes