#173

thank you for your kind and insightful words, and quick response @ngwese!

#174

I’ve recently got a Norns Shield (from the Monome kit), which is all working great, and updated to the newest OS.

I can connect to Maiden fine, and install scripts. But after ‘refreshing’ available scripts, the most recent scripts don’t appear e.g. Kolor or Flora.

If anyone could shed any light on why this might be, that’d be great. Thanks

#175

Welcome to the world of Norns. :slight_smile:
Not all scripts are available in Maiden but there is ways to place these manually, the top entry of Kolor has directions listed under “download”.
For Flora there is a download link and you could use Cyberduck but shouldn’t and do this instead, to copy the contents to the correct place (dust/data). Remember to get rid of the “-master” in the folder name.
For Flora entering this into maiden might also work ;install https://github.com/jaseknighter/flora

1 Like
#176

Thanks for getting back to me. Yes very exciting to have it, just overwhelmed with the options currently!

I realise you can download them seperately, and I did manage to get Flora working this way.
I was just trying to workout why these scripts weren’t appearing, as the creator of Flora told me that both these scripts should definitely be on Maiden, and I most likley have an issue my end. Just trrying to figure out what the issue may be.

#177

Hm, I cannot check right now, but can you try a general update of your norns (system) first?
The thing is: Maiden should now automatically update (you used to have to press the update circles for community scripts before in Maiden) and then present you with a list of available scripts.

#178

I did already update my norns to the newest version, but I will try it again.

Having looked at the main community file at norns-community/community.json at master · monome/norns-community · GitHub, it appears my list it not matching this up-to-date list.

#179

Try in an incognito/private window, could be a cache issue ?

2 Likes
#180

please— everyone— the much easier way of transferring files is via samba, as indicated in the docs. please stop suggesting SFTP/cyberduck, it’s a total pain in comparison (if you don’t already have cyberduck/etc, which most people don’t).

for script downloading, ;install absolutely the best way if something is not in the catalog, please let this be the only recommendation onwards.

6 Likes
#181

Thanks. Tried that too. Plus tried on different computers. Feel like I’m missing something obvious.

#182

Are you refreshing the right part of maiden? There’s both ‘base’ and ‘community’ that can be refeshed, see screenshot attached.

maiden
maiden2421×663 25.8 KB

#183

Ok, edited my post above.

#184

Yes, tried refresh all. Then refreshed each parts separately.

I guess I might just reflash my SD card to see if that fix’s it.

#185

Out of curiosity are trying outside of North America? It is a long shot but if the catalogs don’t seem to be updating there have been reports of difficulty accessing GitHub.

Can you download this file in a browser on your computer?

Just to double check Is the shield connected to your WiFi network directly? For downloads, updates, etc to work, norns needs to be directly connected to the network as opposed to running in hotspot mode.

#186

Just tried to understand the issue and can confirm the same thing:
both scripts also do not show up in maiden for me.

I tried refreshing (all and each base community and again), my norns shield is up to date.
I emptied my cache and tried again, did a reset and tried again, no dice.
I have these scripts installed (manually).

#187

@doomglue, @Comoving_Observer Sorry. This one is one me - it looks like the latest update included the change to switch the norns-community repository to use more inclusive branch names. The new main branch was out of date so flora and kolor where not included (fixed now).

3 Likes
#188

Great. Nice one figuring it out so quickly!

I thought I was just making some fundamental error. All the scripts seem available now.

3 Likes
#189

@DoS - can you provide more information and a screen shot? Which browser are you using? Do you have any browser extensions installed (like Greasemonkey) which “add” functionality to web sites?

Other than updating the version of the underlying editor component which maiden uses the styling hasn’t been modified in the latest update and I haven’t noted any changes in font size.

1 Like
#190

I don’t have any extensions like that - see below for a screenshot and more details.

Right - I should have thought it probably wouldn’t be the same across every browser; but a quick check with Chromium, Firefox and Opera (the browser I use most), the font size seems quite a bit smaller than before - here’s Firefox, for example, on a screen with 1680 x 1050 resolution

image
image1680×1010 137 KB

It may of course be that a) I just got new varifocal glasses and everything seems smaller ; 2) I also recently had to switch to Linux Mint 19.3 from Manjaro 20, though on the same screens at the same resolutions, so I don’t think that would be the reason - and the font face change did happen immediately after updating the Norns Shield to the latest version.

Thanks for taking the time to look into this. Being able to make the font size for the code window larger would certainly be useful, given 1) above in particular, if it’s at all possible. Zooming in on the browser does work too though, so if it’s not possible at any point it’s liveable with for sure.

#191

I just checked to make sure nothing changed between the previous maiden release and the current maiden release - a side by side comparison of version 1.0.2 and version 1.1.0 is identical (when using the same browser on the same OS).

The maiden style sheet does not specify a particular font, only monospace. One consequence of that is that it uses whatever font is set in the browser preferences as the default to use as monospace. The rendering of maiden that I get with Firefox on Debian 10 looks like your screen shot, the text in the editor and in the file tree is slightly smaller (12px) than text used in the “matron” and “supercollider” repl tabs (which is computing to 14.66px for some reason). On macOS using Chrome the editor and file tree renders with a 12px font but the text used repl tabs is getting computed as 13 px.

The main takeaway:

  • …there are rendering differences between the platforms (not surprising)
  • …the loose CSS specifications around the REPL can give the impression (particularly on Linux) that editor font is smaller than intended when it looks like the reverse is true (the REPL is rendering larger than intended).
  • …the rendering hasn’t changed in the latest maiden release. If there is very noticeable shift then there is a strong possibility that any changes to the browser, OS font selection, and/or browser settings could could be the source of the difference.

I’ve created a ticket for adding font size control:

1 Like
#192

Thank you hugely for taking the time to research this @ngwese . It’s really appreciated. For now I will use the browser zoom on higher-resolution screens as that works OK.