#1626

Ok so, the issue has been identified.

Case-sensitivity.

When inputting the password into the norns, I failed to realize that there was an entire different alphabet off-screen for lowercase. It’s all good, I put in the password with the correct characters and the update ran all fine and dandy.

If I could make a recommendation, however, perhaps there could be a notice in the manual alerting people to make sure they take note of the case-sensitivity of their password and the alternate keyboard? Or maybe make a character at the beginning of the alphabet to toggle between uppercase and lowercase, to make things more intuitive? Idk, it was probably dumb of me to not think of this sooner, but I feel like it could be helpful to at least point that out somewhere. Thank you!

2 Likes
#1628

I got my Norns last week, and had the same problem with FM7. Norns works fine after removing the script, but does this mean that FM7 doesn’t work anymore?

#1629

FM7 still works. Just make sure that you have the current version, and that dust/code/we/lib doesn’t contain an Engine_FM7 file. The problem is that the FM7 lib used to live in we, now it lives in the project folder. It can’t be in both places, or norns will complain.

#1630

I have been having some trouble using Norns trough the wifi nub and a hotspot.
Connection will switch on and off randomly, pain if transferring audio files.
Any reason not to use a ethernet usb dongle (like the apple one)
I just set it up and its running reliable and at ethernet speed for transferring files.

#1631

nope, that’s a great option

1 Like
#1632

Sorry if this has been asked before. Is norns friendly to powered usb hubs? Could i increase the number of usb devices connected to norns with a usb hub?
I have thought of a midi merger and then roland um one as a work around.
Thanks!

2 Likes
#1633

yes a powered USB hub will work fine

curious to hear what you’re doing!

1 Like
#1634

Would it be acceptable to use a bus powered hub rather than a wall powered one with norns charging, or is that putting too much strain on the norns battery? I’m thinking of typically using norns with the included WiFi nub, Grid, Arc, Qunexus, Midi Fighter Twister and Seville Soft Midi host to host.

#1635

sounds a little excessive

1 Like
#1636

Hi Tehn,

Thanks for the reply and info.

I have the studio wired up trough a bome Bomebox.

The bomebox is connected to a usb hub and i can make midi connections between different computers using the bomebox as a kind of data hub.

I can use wifi or ethernet for midi data; I have the computers synced with Ableton link trough Ethernet and im thinking of being able to control norns from different devices of the studio, specially since there can be midi assignments im thinking of midi mapping controls and creating some lemur templates (via osc or midi)

Lots of options!

Thanks :slight_smile:

#1637

you definitely need a powered hub. the norns battery is not huge and does not deliver high capacity current, especially if you’re using most of that current for CPU.

1 Like
#1638

Unfortunately no luck with midi twister trough powered usb hub, fine if plugged into iconnectivity midi 4 or directly into norns.

This machine rocks!

#1639

Do the lights come on? I’ve noticed that the midi fighter can be occasionally weird like that where - if it receives power before it’s able to initiate a data connection, then it has trouble with the data connection… even though it is powered on.

For example, I use my midi fighter twister with a powered hub… but I actually have to connect the hub to the computer and then the midi fighter twister gets connected to the hub after the hub has been connected to the running computer, otherwise it exhibits this issue.

#1640

Hi,
Thanks for the tip!
Yes lights come on when i plug it to the usb hub, but then when ever i touch one of the knobs it resets it self every time.
Im going to try your approach, Thanks!

1 Like
#1641

I was wondering if the folder names inside the dust/code can be renamed as to have some indication of what the app does, so i could have something like:

dust/code/loopers/…
dust/code/sequencers/…

or maybe just change the names of the actual folders like:

seq_isoseq
seq_kria

What is the best approach for not breaking anything? Is there a should or shouldn’t to be considered?

Im kind of lost at the moment with so many apps and woulds be great if i could have some idea of what it does before loading it.

Thanks!

#1642

Scripts can “include” code from other scripts, and they do this by referencing the path. If you rename a folder you could potentially break another script that references that path. You would have to check for those references and update them as well, but then you’d have to maintain your own custom version of those scripts. It would all probably be more trouble than it’s worth.

#1643

as @crim says, there are a lot of instances of scripts including lua from other folders in code, in particular engine interface libs, like this: https://github.com/dndrks/less_concepts/blob/master/less_concepts.lua#L109

in the above, this will still work if less_concepts is moved to a subfolder, but include 'passerby/...' will not work if passerby isn’t in the top level of ~/dust/code.

(i’ve even committed the sin of usin direct paths relative to .../code in local includes: https://github.com/catfact/zebra/blob/master/crowns.lua#L272)

anyways you could certainly move things around and edit include paths appropriately; up to you if this is a worthwhile task.

(also fwiw, i am personally ambivalent about the convention of gnomic and whimsical single-word names for everything. it’s fine in moderation. but if i ever take time to “release” norns libraries i will probable opt for more boring and descriptive titles.)

i think we would also welcome any technical ideas / assistance implementing better script organization tools in future norns versions.

1 Like
#1644

Thanks for the heads up, i thought it would not be as easy as renaming the files. Roger that
Can the opposite be done, meaning just keeping a few apps that you use the most?
Or that would also mean deleting some engines or scripts that are not being used?
I think i better get used to the current folder structure so i dont end up breaking things.
Thanks for the help!

#1645

yes, absolutely. i have ~/dust/code and ~/dust/code_no. their contents are respectively visible and invisible to both the norns menu, and to the include mechanism. i move things between them, no need to delete.

one current limitation is that there is not a way to make something visiable to include, but invisible on the menu.

1 Like
#1646

Wow thats a great tip! I might just move the majority of the scripts to a dust/code_no folder and slowly start moving them to the dust/code folder as i get to know my way around.
Thanks!

1 Like