#778

for 12 buck is it worth future proofing it?

1 Like
#779

Audio seems to be all ok now, thanks for your patience with my Qs @okyeron

1 Like
#781

hi @okyeron, i just finished my fates built, everything went smooth. i managed to install the disk image.
however, when i want to continue to the next step (expand the system), it seems i can’t SSH into fates.
i tried few times : ssh we@norns.local, and also tried with IP address, and i got this message :
"
It is also possible that a host key has just been changed.

The fingerprint for the ECDSA key sent by the remote host is

SHA256:1JxXsCwJCm/uHIsU1IMFbMyGSdWj8nmtVE47CQRXhwU.

Please contact your system administrator.

Add correct host key in /Users/indraperkasa/.ssh/known_hosts to get rid of this message.

Offending ED25519 key in /Users/indraperkasa/.ssh/known_hosts:7

ECDSA host key for 192.168.1.9 has changed and you have requested strict checking.

Host key verification failed. "

do you know how to solve this?
i also have the original norns, is it because that the Fates using the same IP address like my norns?

EDIT:
also i noticed another problem, when i go to SYSTEM - SLEEP. Fates didn’t go off, it stays on with the ‘sleep.’ dim light, just hang in there. any idea why this is happen?

#782

just put sudo nano /Users/indraperkasa/.ssh/known_hosts into your terminal…enter pw … and put a #
in front of the line which starts with 192.168.1.9

1 Like
#783

thank you for your response. i did manage to put # on the IP address, but i how do i proceed after thatScreen Shot 2019-12-14 at 17.05.45 ?
sorry i don’t know anything about Terminal stuff…

#784

uh sorry…

you have to save the file by

ctrl + x (this closes the file and you are asked if you want to save) -> Y and return

1 Like
#785

it worked! thank you so much!

2 Likes
#786

Is that a slowgrowth (http://johannesneumann.net) arc clone? working with Norns?

For some reason mine appears as a grid device under norns !(but enumerates itself correctly as an arc with ansible or max/msp etc) Odd - Having no luck as yet to understanding norns code where the enumeration occurs.

#787

This is “normal”. SLEEP is actually sudo shutdown now so the pi is actually shut off at this point, but power is still going to the display so it continues to show the last thing on screen.

When you use SLEEP - Make sure you have a solid red indicator light on the pi (no flashing green) and then disconnect from power.

(I’ll add this to the docs/readme)

I use an inline usb power switch from canakit so I can switch power off after shutdown.

1 Like
#788

2 possible issues:

  • Not enough juice

i was wondering whether the source of the problem was power, so i tried to plug in the arc powered via offworld, and now the arc seems to work fine with norns

  • Wrong product identifier string from the arc clone.

I’ll update this with a thing for you to check here in a minute

#789

ah okay, good to know about this. thanks for the explanation! :pray:t4:

#790

Just to follow up for those who are having similar issues, problems disappeared when I swapped Pis so I suspect it was an issue with the old Pi’s SD slot.

I noticed on the 4b the screen will power off entirely, on 3b+ the screen remains on with “sleep” but dimmed.

#791

OK - can you check the device info with the following? (assuming the arc clone shows up on linux as /dev/ttyUSB0

udevadm info --query=all --name=/dev/ttyUSB0

Then you’re looking to see if “ID_MODEL” matches “monome arc” - which is what norns is looking for for enumerate as arc. (I think an underscore replaces a space, so that’s ok)

EDIT - I checked the clone sources and there it is: “monome arc clone” so it wont match.

change norns/lua/core/startup.lua line 52 to “monome arc clone” then restart norns and Bob’s yer uncle. (You will need to do this after each norns software update)

EDIT EDIT - ok strange - the norns code is using util.string_starts so “monome arc clone” should still work. Curious.

2 Likes
#793

I have a strange issue that has popped up on my Fates build last night after I attempted to update to the latest Norns Build via the update menu, I am currently running 191201. The issue that I am seeing is that All audio from scripts have stopped playing across the board. The Tape functions just fine and all the audio levels are at full but I am getting nothing from the output.
When I run Study1.lua from Maiden and go to the SC tab, I see the error message -

SC output

CroneEngine.free
FAILURE IN SERVER /n_free Node 5497 not found
free engine: an Engine_TestSine
CroneEngine.free
FAILURE IN SERVER /n_free Node 5497 not found
a CroneAudioContext
[ CroneEngine adding command, hz, f, a Function ]
[ CroneEngine adding command, amp, f, a Function ]

– crone: done loading engine, starting reports

engine: an Engine_TestSine
command entry: [ 0, hz, f ]
command entry: [ 1, amp, f ]
cpu_peak
cpu_avg
amp_in_l
amp_in_r
amp_out_l
amp_out_r
pitch_in_l
pitch_in_r
FAILURE IN SERVER /s_new Group 1001 not found
FAILURE IN SERVER /n_set Node 5498 not found

My audio issues seemed to crop up after I had installed a few scripts from the Project Manager in Maiden. Not sure if this is related or not. Trying to pair back to the minimum, I have rebuilt the Fates image and only have the We and Awake script directories present currently.
Has anyone else ran into this issue?

I just performed a clean re-etcher write of the SD card and the audio is now working as expected on build 191016. I’m not quite sure what happened but I appear to be back up an running again.

#796

Thought that could be it but yes, doesnt fix it.

When i connect an arc clone and a genuine grid as mentioned they both show up as grids as but with different descriptor formats
GRID

  1. m0000021
    2.monome 128 m0000605
    3.none
    4.none

There is a space before the arc serial number, it seems that the dev.name field is stripped leaving just the space and serial number. Ive attached a screengrab of maiden reporting the devices when they are plugged in

Also when turning an encoder, maiden reports no entry for arc 2, arc.lua[line 202]

There used to be a monome.lua file in the core folder but it doesnt appear to be included in the last update.

– monome device manager

local util = require ‘util’
local grid = require ‘core/grid’
local arc = require ‘core/arc’

norns.monome = {}

norns.monome.add = function(id, serial, name, dev)
if util.string_starts(name, “monome arc”) then
norns.arc.add(id, serial, name, dev)
else
norns.grid.add(id, serial, name, dev)
end
end

norns.monome.remove = function(id)
if arc.devices[id] then
norns.arc.remove(id)
else
norns.grid.remove(id)
end
end

Screenshot 2019-12-15 16.51.10
Screenshot 2019-12-15 16.51.101866×782 16.7 KB

#797

Got mine built up and am having an issue that may be a silly error on my part. Once I burn the disc image to sd card I’m left with the card being partitioned (one labeled “boot” and the other “rootfs” and most of the space unallocated (leaving only 256MB free space to use). Tried reformatting, tried a different sd card, tried moving that unaollcated memory back to the primary (boot) partition (I seem unable to modify the rootfs partition) but whenever I burn the new image I end up with the same result. I tried resizing after burning the image and still no dice. Any ideas? (and sorry of this is some basic IT helpdesk level stuff).

It boots up like normal, runs awake no problem, I’m able to pull up maiden, etc. but no memory to try to update or install anything from maiden library.

#798

Curious. I’ve got someone else with a similar issue so I’d love more debug on this.

If you can go through and install the same scripts again and narrow down if it’s script related that’d be awesome.

Otherwise it could be update related. There’s a little mod needed to get crone to re-compile right, but that hasn’t been an issue for anyone yet (I think)

Also - its required to do STSTEM>RESET after installing a script with an engine (which may or may not be clear from the script docs)

#799

Need to “expand filesystem” on the pi.

This should be on the disk image install doc.

If you’re unable to do the expand filesystem (it throws an error) then this is another issue and I’ll prob need you to DM me to troubleshoot.

1 Like
#800

I’ll see if I can repo, but I think that the issue arose when I switched my method of getting scripts from a manual copy via SSH over wifi over to the Maiden File Manager.
I used the maiden interface to uninstall all the scripts (probably about 50) and reinstalled them, only restarting through ‘sleep’ once they were all installed. I then booted back up and I had no sound on any script but everything else seemed to function just fine - along with tape providing audio.
Reflashing the SD back to a base image still did not provide any solutions until the third attempt or Reimaging was etched to the same sd card.
Super weird.

So I was able to reproduce the conditions when installing awake-rings through the file manager. all audio stopped with SC giving the same error " FAILURE IN SERVER /n_free Node 5497 not found".
After I removed the script and rebooted through Sleep the audio continued to function normally.
Is this a duplicate engine issue?

#801

Looks like that did it, thank you very much.

I’ve done lots of eurorack diy but this is my first time dipping my toes into pi, command line, ssh, etc. and that this is all so well conceived that a bonehead like myself can jump in is such an awesome service to the music making community. The dedication here is truly inspiring. :pray:

3 Likes