Norns update: 191028 -- maiden 1.0!

robotboot · 2019-11-01T14:30:56.281Z

When Kira_Midi is installed via madien it’s adding extra folders and scripts and “engines?” In it’s folder and then makes Norns not happy. If you just instal via SFTP it well “works but the actual script isn’t fully functional” works as expected. I don’t know enough about how to see errors and or monitor on madien.

ngwese · 2019-11-01T15:26:55.420Z

I took a quick look and the GitHub repository for Kria_Midi is setup differently than most/all other projects. I just updated the catalog to point directly at the zip file which is referenced in the discussion thread: Kria MIDI

If you remove the previously installed kria_midi, refresh the community catalog, and then install kria_midi again you should (hopefully) be working.

LLK · 2019-11-01T15:44:17.329Z

As someone who spent a few hours 2 days ago, re-updating my entire norns library, this update is amazing, I keep being impressed by how streamlined and elegant the experience is becoming with each new code addition, it’s unvaluable, I loved Norns at reception, I love it so much more a year later.

robotboot · 2019-11-01T15:47:26.773Z

Yeah i feel exactly the same way.

robotboot · 2019-11-03T21:27:14.198Z

It’s still installing extra things(a data folder and info, a super colider folder and info) into the Kria folder that messing up Norns not sure why this one is getting messed up via madien. If you download it from glit it does not have all the extra stuff and installs fine. Everything else’s I have installed is working just great and the new flow is otherwise great compared to doing it all manually.

ngwese · 2019-11-03T21:51:51.841Z

Have you hit the refresh button on the community catalog? Currently the catalogs are only downloaded when the refresh button is clicked.

I was able to test on my norns that as of about 12 hours ago things were working (one more pass at getting the URL correct!)

robotboot · 2019-11-05T03:55:31.870Z

ah thanks i was not familiar with the refresh button.

gwpt · 2019-11-06T08:39:53.761Z

Im getting the duplicate engine error after installing kira_midi via the maiden app manager.

DUPLICATE ENGINES:
/home/we/dust/code/kria_midi/dust/code/BowMPE/Engine_MPEBow.sc Engine_MPEBow.sc
/home/we/dust/code/kria_midi/dust/lib/sc/Engine_MPEBow.sc Engine_MPEBow.sc
### SCRIPT ERROR: DUPLICATE ENGINES

I’ve tried deleting both (one at a time) and in both cases I then get a Super Collider error.
Anyone know a fix?

elia · 2019-11-06T11:39:38.043Z

Hi guys! Yesterday I updated to the latest version and I installed and updated the app through the new maiden, everything was fine. Today when I reboot Norns nothing works anymore and it tells me error: Duplicate engines. What can I do?

elia · 2019-11-06T11:51:16.217Z

The problem is solved.
the “fm7” update has created a duplicate of the engine. After eliminating the duplicate from “we” folder i solved.

jlmitch5 · 2019-11-06T12:49:02.224Z

Delete kria_midi, click the refresh icon on the available packages and reinstall.

There was an update to the git url used. New one works (had the same issue as you)

riggar · 2019-11-11T16:30:20.204Z

Installed - so quick! Thanks to everyone efforts. All fine but noticed temp permanently at 0c?

Oxbown · 2019-11-12T22:08:13.984Z

I´ve a endless Refreshing catalog… (norns are connected to internet) so… what’s the deal?

image1184×231 4.18 KB

okyeron · 2019-11-23T17:41:04.979Z

update failed: reference has changed concurrently

What does this error mean?

ngwese · 2019-11-23T21:30:49.817Z

I’m away from the device/code right now but I believe that is the underlying git library cryptically saying that the “project” has local changes which the git lib doesn’t know what do do with ahead of pulling an update down. If you don’t have any local changes you want to keep the most expedient way to get around this is to delete the project and reinstall it.

The git implementation currently in use is not the standard git command line tool and I’ve since discovered that it is limited in certain areas. Moving forward the hope would be to be more accommodating in situations like this - offering to blow away local changes or attempt a merge.

okyeron · 2019-11-23T21:32:17.069Z

FWIW - if I tried to update a second time, it seemed to work OK.

ngwese · 2019-11-23T21:43:00.768Z

Oxbown:

I´ve a endless Refreshing catalog… (norns are connected to internet) so… what’s the deal?

Did this ever resolve itself? Refreshing the catalog is nothing more than downloading the catalog from GitHub, specifically:

github.com

monome/norns-community/blob/master/community.json

{
  "file_info": {
    "version": 1,
    "kind": "script_catalog"
  },
  "catalog_name": "community",
  "date": "0001-01-01T00:00:00Z",
  "entries": [
    {
      "project_name": "ack",
      "project_url": "https://github.com/antonhornquist/ack",
      "project_author": "Anton Hörnquist (jah)",
      "description": "sample player engine"
    },
    {
      "project_name": "arcify",
      "project_url": "https://github.com/mimetaur/arcify",
      "author": "Nathan (mimetaur)",
      "description": "map arc encoders to up to four parameters (eight with a shift key)",
      "discussion_url": "https://llllllll.co/t/arcify/22133",

This file has been truncated. show original

I have noticed occasional sluggish response from GitHub over the last few months. If you see this behavior again I’d try accessing that file from your computer to in order to rule out problems related to DNS or the network itself.

Oxbown · 2019-11-24T15:26:26.260Z

You are right, my local internet vendor (spain pepehone) has blocked github raw content… the solution is to use a different dns or use other network to refresh the catalog.
Thanks!

ngwese · 2019-11-24T15:35:08.773Z

As a side note the catalog files themselves live in ~we/dust/data/catalogs on the device so it is also possible to download them a different way then transfer them to norns via sftp (for example)

Oxbown · 2019-11-24T15:39:53.201Z

Ok, thanks for the information, i’ll test it.