#30

this is a pretty minor vulnerability that would only present itself when changing from one network to another (which is pretty uncommon), i’ll comment it out anyway

can you clarify what you’re doing? how can i replicate this?

#31

It occurred constantly (repeatedly) ever since I updated to 191126. I tried loading other scripts and disabling Wi-Fi but that didn’t seem to change anything. I decided to disconnect the powered USB hub, which finally made that message stop appearing.

Attached to that hub is a walnut 128 Grid, the latest Arc and a Mio MIDI interface. I’m assuming this has something to do with the MIDI interface, not the Grid or Arc.

Edit: Sorry, my hub isn’t very easy to get to - it is stored under the stand for my Grid & Arc, which is surrounded by others. Seriously limited desk space over here! I decided to check anyway (for science) and am able to confirm now that the error doesn’t appear after disconnecting the Mio. I don’t think the Mio is defective, so it may be something that changed with this update.

#32

spotted to bug. fixing now.

2 Likes
#33

That’s great!! I just wanted to add that I appreciate this update very much. These all appear to be some pretty exciting changes and I love seeing the wonderful progress being made all the time! :smiley:

Just wondering now, how do I change the overall grid intensity? Is it per script, or global? Is the option already available somewhere that I’m not seeing, or does it need to be coded into a given script?

Finally - the list of changes in the original post says “FIX wif menu indication”. That should read “wifi” I’m assuming?

1 Like
#34

fixed. files updated again. thank you all for your patience and bug spotting.

grid intensity is per-grid, per-script. i’m planning to add a menu option for intensity and rotation.

in the meantime most scripts can have g:intensity(10) (or whatever brightness you prefer) added after g = grid.connect()

4 Likes
Cheat codes (v1.1.1)
#35

A bit more info after additional troubleshooting:

I am able to connect to the device using WebDAV via HTTP using Cyberduck, but the drive mapping in Windows file explorer still doesn’t work. In Cyberduck, it appears that both the IP address as well as using norns.local for the server name are functioning properly.

I am rolling through my network settings to see if anything else would be preventing me from mapping the drive.

#36

FYI - my webdav problem was user error. :man_facepalming:
Not enough 3’s! (was trying port 3333 instead of 33333)

1 Like
#37

I wish it were that simple of a fix! :slightly_smiling_face:

1 Like
#38

thanks for your patience— hoping i’ll figure this one out soon— it’s a little more fiddly then the norns software fixes up-thread (which were mostly typos on my part) :grimacing:

#39

does this help at all?
https://support.netdocuments.com/hc/en-us/articles/205212850-WebDAV-as-a-Mapped-Drive

1 Like
#40

I did see this and tried a few things in regedit, and it doesn’t seem to make a difference. Are there others who have gotten WebDAV working on the Norns and Windows 10?

#41

with @okyeron’s link i did just get it to work on win10. you need to specify the IP and port ie http://192.168.0.111:33333 and check the extra boxes for “other credentials”

but doing regedit etc is not a great requirement for people. windows users i’d suggest continuing to use SFTP until there’s a solution worked out (though the regedit method works.)

2 Likes
#42

If I understand your question, this isn’t a per-LED compatibility fix. I think it’s just adding support for the global brightness value, which was all we had for variable brightness back in the day.

I leveraged that here:
https://vimeo.com/12192331
…but can’t think of other examples which made use of it dynamically.

(Which is weird. Bumping it as a metronome seems such an obvious use case.)

4 Likes
#43

this would be a handy to have I think I’ll look into it & PR : )

something like lvl = lvl < 8 ? 0 : 15 ?

2 Likes
#44

Yah! That would be awesome!

It would be a nice way to put my legacy grid to use if my vari-bright is in use with something else. If that function could be added to the norns functionality, like a simple way to globally account for a legacy grid, that would rock.

#45

there’s no way to account for all variations in how brightness is used in scripts but there might be something that’s better than the current situation

a better option could be easier tools for script authors to design for legacy rather than a global toggle

any particular script / use pattern that’s not useable on non-varibright rn ?

1 Like
#46

Hmm, that’s actually a good question. I think something like mlr would be one that comes to mind, since there isn’t a ton of layering with that one. But I don’t have anything else really in mind. I haven’t done too much with this legacy grid, just was thinking about it. I’ll give the other scripts a look.

#48

Also for maximum hardcore, I can confirm that Tramp Mode in Emacs works fine to edit Norns files transparently over SSH. WebDAV is welcome, but is there a reason to prefer it over SMB?

1 Like
#49

honestly I thought WebDAV was the new easy modern thing, but windows somewhat thwarted that initial optimism. so perhaps we will switch.

#50

Options are good. What works well on one platform might not on another. And sometimes it just amounts to preferences.