ah thanks i was not familiar with the refresh button.

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?

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?

The problem is solved. :smiley:
the ā€œfm7ā€ update has created a duplicate of the engine. After eliminating the duplicate from ā€œweā€ folder i solved.

2 Likes

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)

2 Likes

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

1 Like

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

update failed: reference has changed concurrently

What does this error mean?

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.

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

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

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.

1 Like

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!

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)

1 Like

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