#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
#137

Yeah it’s been adressed in the “MLR (norns)” topic, I think it’s on @tehn 's (dramatically long?) to do list.

3 Likes
#138

Apologies if this is asking the obvious, but is there a list of the norns engines (and parameters) somewhere? Couldn’t find anything in http://norns.local/doc/
Currently trawling other scripts to find the engines used, but seems like I must be missing a trick here :wink:

1 Like
#139

unfortunately i don’t think so due to how the new library system is set up. the engines are now able to be shared the same way as scripts. the advantage is that engines and scripts can be freely added and updated without waiting for a norns update. the disadvantage is what you’re dealing with right now…

i am sure there is some command you can run to get a list of installed engines, but i don’t know it.

1 Like
#140

There is; but, I’m afraid it got broke somehow; I’ll fix in my next norns dev session. sorry about that.
[ https://github.com/monome/norns/issues/798 ]

3 Likes
#141

day 2 with 2.0 brought some more issues…

my grid does the little wake-up dance (or a sudden flash of some lights) when connected, but it otherwise unresponsive (no lights, no button-presses registered).

maiden shows

dev_list_add: error allocating device data

error: couldn't open monome device at /dev/ttyUSB1

dev_list_add: error allocating device data

error: couldn't open monome device at /dev/ttyUSB2

dev_list_add: error allocating device data

and so on and so forth

going into system/devices/grid locks the whole system up…

update - might just be a cable issue
update #2 - switched cables and now I get repeated disconnects and reconnects of the grid

#142

Try reassigning the grid. SYSTEM>DEVICES>GRID

#143

yeah, that was my thought, but SYSTEM>DEVICES>GRID causes norns to lock up entirely

#144

@karst this definitely sounds like a hardware problem; can you verify that same grid+cable work correctly with a different host (e.g. laptop)