#1954

@zebra - following up here on SUPERCOLLIDER FAIL errors from the Norns Shield thread.

I have someone with a couple of my dac boards running into some funky startup issues and reporting frequent SUPERCOLLIDER FAIL's

To compare, I checked for jack errors in journalctl and get the following (this is on my pi4 which runs pretty normally without any SC Fails).

journalctl -r | grep jack output

10.0.1.20 ~ $ journalctl -r | grep jack
Oct 11 14:42:25 norns jackd[330]: JackAudioDriver::ProcessGraphAsyncMaster: Process error
Oct 11 14:42:25 norns jackd[330]: JackEngine::XRun: client = SuperCollider was not finished, state = Running
Oct 11 14:42:25 norns jackd[330]: JackEngine::XRun: client = softcut was not finished, state = Triggered
Oct 11 14:42:25 norns jackd[330]: JackEngine::XRun: client = crone was not finished, state = Running
Oct 11 14:42:25 norns jackd[330]: JackAudioDriver::ProcessGraphAsyncMaster: Process error
Oct 11 14:42:25 norns jackd[330]: JackEngine::XRun: client = SuperCollider was not finished, state = Triggered
Oct 11 14:42:25 norns jackd[330]: JackEngine::XRun: client softcut finished after current callback
Oct 11 14:42:25 norns jackd[330]: JackEngine::XRun: client = crone was not finished, state = Running
Oct 11 14:42:25 norns jackd[330]: JackAudioDriver::ProcessGraphAsyncMaster: Process error
Oct 11 14:42:25 norns jackd[330]: JackEngine::XRun: client = SuperCollider was not finished, state = Running
Oct 11 14:42:25 norns jackd[330]: JackEngine::XRun: client = softcut was not finished, state = Triggered
Oct 11 14:42:25 norns jackd[330]: JackEngine::XRun: client = crone was not finished, state = Running
Oct 10 22:25:20 norns jackd[330]: JackAudioDriver::ProcessGraphAsyncMaster: Process error
Oct 10 22:25:20 norns jackd[330]: JackEngine::XRun: client = SuperCollider was not finished, state = Running
Oct 10 22:25:14 norns crone[425]: starting jack clients…
Oct 10 22:25:14 norns crone[425]: setting up jack clients…
Oct 10 22:25:13 norns systemd[1]: Started norns-jack.service.
Oct 10 22:25:13 norns jack_wait[331]: server is available
Oct 10 22:25:13 norns jackd[330]: ALSA: use 3 periods for playback
Oct 10 22:25:13 norns jackd[330]: ALSA: final selected sample format for playback: 16bit little-endian
Oct 10 22:25:13 norns jackd[330]: ALSA: use 3 periods for capture
Oct 10 22:25:13 norns jackd[330]: ALSA: final selected sample format for capture: 16bit little-endian
Oct 10 22:25:13 norns jackd[330]: configuring for 48000Hz, period = 128 frames (2.7 ms), buffer = 3 periods
Oct 10 22:25:13 norns jackd[330]: creating alsa driver … hw:0|hw:0|128|3|48000|0|0|nomon|swmeter|soft-mode|16bit
Oct 10 22:25:13 norns jackd[330]: self-connect-mode is “Don’t restrict self connect requests”
Oct 10 22:25:13 norns jackd[330]: JACK server starting in realtime mode with priority 95
Oct 10 22:25:13 norns jackd[330]: under certain conditions; see the file COPYING for details
Oct 10 22:25:13 norns jackd[330]: This is free software, and you are welcome to redistribute it
Oct 10 22:25:13 norns jackd[330]: jackdmp comes with ABSOLUTELY NO WARRANTY
Oct 10 22:25:13 norns jackd[330]: Copyright 2016-2017 Filipe Coelho.
Oct 10 22:25:13 norns jackd[330]: Copyright 2004-2016 Grame.
Oct 10 22:25:13 norns jackd[330]: Copyright 2001-2005 Paul Davis and others.
Oct 10 22:25:13 norns jackd[330]: jackdmp 1.9.12
Oct 10 22:25:12 norns jack_wait[331]: JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
Oct 10 22:25:12 norns jack_wait[331]: jack server is not running or cannot be started
Oct 10 22:25:12 norns jack_wait[331]: Cannot connect to server request channel
Oct 10 22:25:12 norns jack_wait[331]: Cannot connect to server socket err = No such file or directory
Oct 10 22:25:12 norns systemd[1]: Starting norns-jack.service…

So then… The user sent me a log from the device with the errors - and they have like 200 lines of these process error/xrun errors:

Oct 12 15:31:04 norns jackd[309]: JackAudioDriver::ProcessGraphAsyncMaster: Process error
Oct 12 15:31:04 norns jackd[309]: JackEngine::XRun: client = SuperCollider was not finished, state = Triggered

that user’s full journalctl log: 118-full-bad.txt (127.6 KB)

Any thoughts or suggestions on what’s up with these ProcessGraphAsyncMaster: Process error's?

#1955

I completely boneheaded my norns in 36 hours
I attempted to run maiden and start the Norns study’s and my day went down the tubes
I have no apps to select from now
All I can do now is audio recordings
How can I save my weekend fast?
I see it slipping away
Thanks

#1956

hi there! did you delete the whole dust folder or just the code folder? if you deleted the dust folder, you can use this post to get back to normal

then just download the scripts you want from the library

4 Likes
#1957

I think I deleted it all
Thanks
I’ll try right now

1 Like
#1958

!!!WOW!!!
That was a voyage
Thank you for your help
I’m up and running better than before
Atleast now I know

1 Like
#1959

Has anyone tried powering norns with a USB module (like this) in the same case/power-source as the crow it hosts? This seems convenient, but I wonder if this would have e.g. ground loop issues.

Here: crow
#1960

you will likely have ground loop issues, but worth a try!

definitely recommend the USB battery bank for easy isolated extra power.

1 Like
#1961

I would like to have an extra WiFi nub for my norns, for backup reasons. Would you happen to be able to recommend one that is compact in size like the original one… and is also verified to be compatible as well as high quality? Thanks!

1 Like
#1962

I’m sure the answer must be in here somewhere but I just can’t find it.

I had to replace my router and now Norns doesn’t find the new network anymore. The ‘add’ screen shows 15 other networks but not the one from the router that is standing right next to the unit.

I just want to update the firmware, add a few scripts and get on with my life.

Can this maybe be done via USB? Any help would be appreciated, I have to admit that this is incredibly frustrating.

#1963

Is your network 2.4 ghz or 5? When I first got Norns, it also couldn’t detect my (sole) 5 ghz network at all. Once I re-configured my router and added a 2.4 network, all was good. Hopefully that’s true in your case too!

5 Likes
#1964

That solved it. Thank you so much! I would have never thought of that. Such a relief. <3

1 Like
#1965

Not sure if maybe this has been answered somewhere that I didn’t find in searching but:

Is there currently any sort of place where one can check out some norns scripts? Or is it just around various git repos at the moment?

#1966

Have you seen the Library? There is a norns tag :slight_smile:

#1967

Click on the norns tag next to the title of this thread and you’ll see all norns related stuff. I believe most scripts are in there.

#1968

ahaaaa… perfect. Thanks to both of you!

#1969

apologies for the delay, didn’t see this till now.

you may either purchase a new WiFi nub here or just email help@monome.org for a $10 (shipping incl.) replacement

1 Like
#1970

Hi! simple question here that I bet I could find myself but…
Okay so I want to update to the newest version of norns (this is the easy part). After I do so, if I want/need to update my scripts (it seems like some needed some tweaks after the new norns update), what is the best way to do so?
Thanks!

#1971

if you mean scripts written by others: hopefully addressed in the norns FAQ, but let us know if you run into something not covered :rainbow:

if you mean your own scripts, I believe softcut and crow were the only things that might require changes in your code. softcut changes documented here

1 Like
#1972

Ah, so as I thought I’d need to overwrite the current code with the new code :slight_smile:

I wish it was my own scripts, hopefully soon!

Thanks so much Dan :v:

1 Like
#1973

If you’re comfortable with the command line, I find it can also be faster to ssh into norns and run “git pull” in the script directory. for example:

ssh we@norns.local
cd dust/code/otis
git pull
7 Likes