Very useful indeed, thanks ! :slight_smile: I will also run more tests tomorrow morning

I will do that, thanks :slight_smile:

Edit:

Unfortunately I didn’t have time to do many tests today. Tomorrow I will try to install a previous version and see if the error happens again

Here’s the output of journalctl

MIO connected
Linux norns 4.14.91-rt49-v7+ #1 SMP PREEMPT RT Sun Jun 16 15:56:26 BST 2019 armv7l
 ___ ___ ___ ___ ___
|   | . |  _|   |_ -|
|_|_|___|_| |_|_|___| monome.org/norns

Last login: Thu Oct 17 18:18:08 2019 from 2a01:cb18:8e2:7c00:4ec:9513:680a:c7b8
192.168.1.18 ~ $ journalctl -u norns-jack
-- Logs begin at Thu 2016-11-03 17:16:43 GMT, end at Fri 2019-10-18 19:08:31 BST. --
Oct 18 18:56:47 norns systemd[1]: Starting norns-jack.service...
Oct 18 18:56:48 norns jack_wait[348]: Cannot connect to server socket err = No such file or directory
Oct 18 18:56:48 norns jack_wait[348]: Cannot connect to server request channel
Oct 18 18:56:48 norns jack_wait[348]: jack server is not running or cannot be started
Oct 18 18:56:48 norns jack_wait[348]: JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
Oct 18 18:56:48 norns jackd[347]: jackdmp 1.9.12
Oct 18 18:56:48 norns jackd[347]: Copyright 2001-2005 Paul Davis and others.
Oct 18 18:56:48 norns jackd[347]: Copyright 2004-2016 Grame.
Oct 18 18:56:48 norns jackd[347]: Copyright 2016-2017 Filipe Coelho.
Oct 18 18:56:48 norns jackd[347]: jackdmp comes with ABSOLUTELY NO WARRANTY
Oct 18 18:56:48 norns jackd[347]: This is free software, and you are welcome to redistribute it
Oct 18 18:56:48 norns jackd[347]: under certain conditions; see the file COPYING for details
Oct 18 18:56:48 norns jackd[347]: JACK server starting in realtime mode with priority 95
Oct 18 18:56:48 norns jackd[347]: self-connect-mode is "Don't restrict self connect requests"
Oct 18 18:56:49 norns jack_wait[348]: Cannot connect to server socket err = No such file or directory
Oct 18 18:56:49 norns jack_wait[348]: Cannot connect to server request channel
Oct 18 18:56:49 norns jack_wait[348]: jack server is not running or cannot be started
Oct 18 18:56:49 norns jack_wait[348]: JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
Oct 18 18:56:49 norns jackd[347]: creating alsa driver ... hw:0|hw:0|128|3|48000|0|0|nomon|swmeter|soft-mode|16bit
Oct 18 18:56:49 norns jackd[347]: ALSA: Cannot open PCM device alsa_pcm for playback. Falling back to capture-only mode
Oct 18 18:56:49 norns jackd[347]: Cannot initialize driver
Oct 18 18:56:49 norns jackd[347]: JackServer::Open failed with -1
Oct 18 18:56:49 norns jackd[347]: Failed to open server
Oct 18 18:56:49 norns systemd[1]: norns-jack.service: Main process exited, code=exited, status=255/n/a
Oct 18 18:56:50 norns jack_wait[348]: Cannot connect to server socket err = No such file or directory
Oct 18 18:56:50 norns jack_wait[348]: Cannot connect to server request channel
Oct 18 18:56:50 norns jack_wait[348]: jack server is not running or cannot be started
Oct 18 18:56:50 norns jack_wait[348]: JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
Oct 18 18:56:51 norns jack_wait[348]: Cannot connect to server socket err = No such file or directory
Oct 18 18:56:51 norns jack_wait[348]: Cannot connect to server request channel
Oct 18 18:56:51 norns jack_wait[348]: jack server is not running or cannot be started
Oct 18 18:56:51 norns jack_wait[348]: JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
Oct 18 18:56:52 norns jack_wait[348]: Cannot connect to server socket err = No such file or directory
Oct 18 18:56:52 norns jack_wait[348]: Cannot connect to server request channel
Oct 18 18:56:52 norns jack_wait[348]: jack server is not running or cannot be started
Oct 18 18:56:52 norns jack_wait[348]: JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
Oct 18 18:56:53 norns jack_wait[348]: Cannot connect to server socket err = No such file or directory
Oct 18 18:56:53 norns jack_wait[348]: Cannot connect to server request channel
Oct 18 18:56:53 norns jack_wait[348]: jack server is not running or cannot be started
Oct 18 18:56:53 norns jack_wait[348]: JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
Oct 18 18:56:54 norns jack_wait[348]: Cannot connect to server socket err = No such file or directory
Oct 18 18:56:54 norns jack_wait[348]: Cannot connect to server request channel
Oct 18 18:56:54 norns jack_wait[348]: jack server is not running or cannot be started
Oct 18 18:56:54 norns jack_wait[348]: JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
Oct 18 18:56:55 norns jack_wait[348]: Cannot connect to server socket err = No such file or directory
Oct 18 18:56:55 norns jack_wait[348]: Cannot connect to server request channel
Oct 18 18:56:55 norns jack_wait[348]: jack server is not running or cannot be started
Oct 18 18:56:55 norns jack_wait[348]: JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
Oct 18 18:56:56 norns jack_wait[348]: Cannot connect to server socket err = No such file or directory
Oct 18 18:56:56 norns jack_wait[348]: Cannot connect to server request channel
Oct 18 18:56:56 norns jack_wait[348]: jack server is not running or cannot be started
Oct 18 18:56:56 norns jack_wait[348]: JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
Oct 18 18:56:57 norns jack_wait[348]: Cannot connect to server socket err = No such file or directory
Oct 18 18:56:57 norns jack_wait[348]: Cannot connect to server request channel
Oct 18 18:56:57 norns jack_wait[348]: jack server is not running or cannot be started
Oct 18 18:56:57 norns jack_wait[348]: JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
Oct 18 18:56:58 norns jack_wait[348]: Cannot connect to server socket err = No such file or directory
Oct 18 18:56:58 norns jack_wait[348]: Cannot connect to server request channel
Oct 18 18:56:58 norns jack_wait[348]: jack server is not running or cannot be started
Oct 18 18:56:58 norns jack_wait[348]: JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
Oct 18 18:56:59 norns jack_wait[348]: Cannot connect to server socket err = No such file or directory
Oct 18 18:56:59 norns jack_wait[348]: Cannot connect to server request channel
Oct 18 18:56:59 norns systemd[1]: norns-jack.service: Control process exited, code=exited status=1
Oct 18 18:56:59 norns systemd[1]: Failed to start norns-jack.service.
Oct 18 18:56:59 norns systemd[1]: norns-jack.service: Unit entered failed state.
Oct 18 18:56:59 norns systemd[1]: norns-jack.service: Failed with result 'exit-code'.
lines 46-67/67 (END)
Mio disconnected

Linux norns 4.14.91-rt49-v7+ #1 SMP PREEMPT RT Sun Jun 16 15:56:26 BST 2019 armv7l


| | . | | | -|
||||| |||___| monome.org/norns

Last login: Fri Oct 18 19:19:36 2019 from 2a01:cb18:8e2:7c00:8d1:5eb3:bfa7:b13a
192.168.1.18 ~ $ journalctl -u norns-jack
– Logs begin at Thu 2016-11-03 17:16:43 GMT, end at Fri 2019-10-18 19:23:08 BST. –
Oct 18 19:13:58 norns systemd[1]: Starting norns-jack.service…
Oct 18 19:13:58 norns jack_wait[348]: Cannot connect to server socket err = No such file or directory
Oct 18 19:13:58 norns jack_wait[348]: Cannot connect to server request channel
Oct 18 19:13:58 norns jack_wait[348]: jack server is not running or cannot be started
Oct 18 19:13:58 norns jack_wait[348]: JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
Oct 18 19:13:59 norns jackd[347]: jackdmp 1.9.12
Oct 18 19:13:59 norns jackd[347]: Copyright 2001-2005 Paul Davis and others.
Oct 18 19:13:59 norns jackd[347]: Copyright 2004-2016 Grame.
Oct 18 19:13:59 norns jackd[347]: Copyright 2016-2017 Filipe Coelho.
Oct 18 19:13:59 norns jackd[347]: jackdmp comes with ABSOLUTELY NO WARRANTY
Oct 18 19:13:59 norns jackd[347]: This is free software, and you are welcome to redistribute it
Oct 18 19:13:59 norns jackd[347]: under certain conditions; see the file COPYING for details
Oct 18 19:13:59 norns jackd[347]: JACK server starting in realtime mode with priority 95
Oct 18 19:13:59 norns jackd[347]: self-connect-mode is “Don’t restrict self connect requests”
Oct 18 19:13:59 norns jack_wait[348]: Cannot connect to server socket err = No such file or directory
Oct 18 19:13:59 norns jack_wait[348]: Cannot connect to server request channel
Oct 18 19:13:59 norns jack_wait[348]: jack server is not running or cannot be started
Oct 18 19:13:59 norns jack_wait[348]: JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
Oct 18 19:14:00 norns jackd[347]: creating alsa driver … hw:0|hw:0|128|3|48000|0|0|nomon|swmeter|soft-mode|16bit
Oct 18 19:14:00 norns jackd[347]: configuring for 48000Hz, period = 128 frames (2.7 ms), buffer = 3 periods
Oct 18 19:14:00 norns jackd[347]: ALSA: final selected sample format for capture: 16bit little-endian
lines 1-22…skipping…
– Logs begin at Thu 2016-11-03 17:16:43 GMT, end at Fri 2019-10-18 19:23:08 BST. –
Oct 18 19:13:58 norns systemd[1]: Starting norns-jack.service…
Oct 18 19:13:58 norns jack_wait[348]: Cannot connect to server socket err = No such file or directory
Oct 18 19:13:58 norns jack_wait[348]: Cannot connect to server request channel
Oct 18 19:13:58 norns jack_wait[348]: jack server is not running or cannot be started
Oct 18 19:13:58 norns jack_wait[348]: JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
Oct 18 19:13:59 norns jackd[347]: jackdmp 1.9.12
Oct 18 19:13:59 norns jackd[347]: Copyright 2001-2005 Paul Davis and others.
Oct 18 19:13:59 norns jackd[347]: Copyright 2004-2016 Grame.
Oct 18 19:13:59 norns jackd[347]: Copyright 2016-2017 Filipe Coelho.
Oct 18 19:13:59 norns jackd[347]: jackdmp comes with ABSOLUTELY NO WARRANTY
Oct 18 19:13:59 norns jackd[347]: This is free software, and you are welcome to redistribute it
Oct 18 19:13:59 norns jackd[347]: under certain conditions; see the file COPYING for details
Oct 18 19:13:59 norns jackd[347]: JACK server starting in realtime mode with priority 95
Oct 18 19:13:59 norns jackd[347]: self-connect-mode is “Don’t restrict self connect requests”
Oct 18 19:13:59 norns jack_wait[348]: Cannot connect to server socket err = No such file or directory
Oct 18 19:13:59 norns jack_wait[348]: Cannot connect to server request channel
Oct 18 19:13:59 norns jack_wait[348]: jack server is not running or cannot be started
Oct 18 19:13:59 norns jack_wait[348]: JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
Oct 18 19:14:00 norns jackd[347]: creating alsa driver … hw:0|hw:0|128|3|48000|0|0|nomon|swmeter|soft-mode|16bit
Oct 18 19:14:00 norns jackd[347]: configuring for 48000Hz, period = 128 frames (2.7 ms), buffer = 3 periods
Oct 18 19:14:00 norns jackd[347]: ALSA: final selected sample format for capture: 16bit little-endian
Oct 18 19:14:00 norns jackd[347]: ALSA: use 3 periods for capture
Oct 18 19:14:00 norns jackd[347]: ALSA: final selected sample format for playback: 16bit little-endian
Oct 18 19:14:00 norns jackd[347]: ALSA: use 3 periods for playback
Oct 18 19:14:01 norns jack_wait[348]: server is available
Oct 18 19:14:01 norns systemd[1]: Started norns-jack.service.
Oct 18 19:14:12 norns jackd[347]: JackEngine::XRun: client = SuperCollider was not finished, state = Running
Oct 18 19:14:12 norns jackd[347]: JackAudioDriver::ProcessGraphAsyncMaster: Process error
Oct 18 19:14:12 norns jackd[347]: JackEngine::XRun: client = SuperCollider was not finished, state = Triggered
Oct 18 19:14:12 norns jackd[347]: JackAudioDriver::ProcessGraphAsyncMaster: Process error
Oct 18 19:14:12 norns jackd[347]: JackEngine::XRun: client = SuperCollider was not finished, state = Triggered
Oct 18 19:14:12 norns jackd[347]: JackAudioDriver::ProcessGraphAsyncMaster: Process error
~
~
~
~
~
~
~
~
~
~
~
~
192.168.1.18 ~ $

Seems like your MIO device is also a soundcard and it apparently receives soundcard ID 0 which is the one JACK tries to use, which going by the logs isn’t really working (no reason shown though, but doesn’t really matter).

Just to be sure: What hardware are you running this on and which distro are you using? Did you change any system config for your primary soundcard (which one?) to work?

Could you post the output from cat /proc/asound/modules as well as the output from aplay -l
with the MIO plugged in?
[edit] Or cat /proc/asound/cards if there’s no /proc/asound/modules.

[edit2] I’ve created an issue for this https://github.com/monome/norns-image/issues/78

1 Like

thanks for the report! good to know. sounds addressable.

also sounds like a separate issue.

  • 1st issue is older than multiport support
  • 1st issue: no problem plugging in after launch

still unclear if 1st issue is seen without running matron or not. woop, nvm i see last 2 posts now.

anyways some other issues with the multiport change, needs work

@simonvanderveldt should we be using the monome soundcard name explicitly instead of hw0? (or whatever)

Yeah, I’d like to check the asound modules output first but we should indeed look into ensuring we use the correct soundcard a bit more, either via JACK config or by making sure it’s always device 0 (not sure yet if we can guarantee that, seems like most distro’s do the opposite: force all USB soundcards to not be 0, wondering why that is).

1 Like

My notes from getting a USB sound card working sometime last year:

Comment out options snd-usb-audio so usb can load first (or set it to zero)

sudo nano /lib/modprobe.d/aliases.conf  
# options snd-usb-audio index=-2

So perhaps that could be configured so USB does not take hw:0

I’m not sure this is involved, but I have this configured for fates (and I believe @Nordseele would have the same config) :

/etc/asound.conf

pcm.!default  {  
       type hw card 0  
     }  

    ctl.!default {  
      type hw card 0  
    }  

Also - onboard audio is blacklisted in /etc/modprobe.d/raspi-blacklist.conf
with blacklist snd_bcm2835

3 Likes

The CM3 doesn’t omit the HDMI interface correct?
Usually the onboard device is given 0th index.

If the HDMI interface is indeed being picked up first by ALSA, one should be able to edit /etc/modprobe.d/alsa-base.conf and add options
snd-usb-audio index=0
options snd_bcm2835 index=1

EDIT: oops, saw @okyeron 's post only after i submitted this

1 Like

just to be super clear, the original issue seems to be with using a midi device that does in fact enumerate as an audio device, and appears to be grabbing hw:0 - maybe as a result of those very same changes. (i dunno, just throwing it out there.) in this case that’s not desirable and it will bork jack and supercollider. (it’s not the use case where you do want to use a USB soundcard instead of a monome/fates soundcard.)

(i looked up the MIO thing briefly and it seems to advertise some kind of “audio pass-through” feature.)

2 Likes

Reproduced issue with my fates pi4 + Waldorf Blofeld + Livid Block + Teensy midi dingus (2host). (none of those are audio interfaces). Running 191016

I’m testing right now and can do some back and forth in private message if anyone likes.

10.0.1.20 ~ $ cat /proc/asound/modules
 0 snd_usb_audio
 1 snd_usb_audio
 2 snd_usb_audio
 3 snd_soc_rpi_proto

Which is pretty weird

1 Like

i’m not really gonna comment on this anymore, (i’m not using remotely the same HW setup as yall) but lastly just to make sure people are talking about the same issue(s), might wanna roll back or revert this PR https://github.com/monome/norns/pull/886, where multiport was added.

1 Like

I’ll try rolling back to that release here shortly.

Additional testing shows just one device attached does not cause the SC fail, but with 2 devices it fails.

This is purely kernel/ALSA level, so I don’t expect any changes to the norns software stack to be at fault.

I’m not so sure this is true (as this problem had not come up for me prior to this last release), but I am testing now to see if that’s the case

i just said i was shutting up, and i already said this, but an alternative test would be, yknow, not running matron (where the changes are) and just running jack/sc

if I reboot, stop all norns services and just run jack, no problems.
/usr/bin/jackd -R -P 95 -d alsa -d hw:0 -r 48000 -n 3 -p 128 -S -s

But can’t test from a clean boot since the norns systemd stuff starts even if I disable them. What else do I need to change to keep these from starting at boot?

sudo systemctl disable norns-jack.service
sudo systemctl disable norns-crone.service
sudo systemctl disable norns-matron.service
sudo systemctl disable norns-maiden.service
sudo systemctl disable norns-sclang.service

sudo systemctl mask norns-matron ?

1 Like

OK - can confirm this is happening at the kernel/ALSA level. (I checked with a buster install without norns installed at all.)

Thank you for bearing with me while I tested this to confirm.

Fix

for (@Nordseele)
(taken from here)

You can reorder the load order of audio devices in alsa-base.conf

sudo nano /etc/modprobe.d/alsa-base.conf 

then add


# This sets the index value of the cards but doesn't reorder.
options snd_usb_audio index=-2
options snd_soc_rpi_proto index=0

# Does the reordering.
options snd slots=snd_soc_rpi_proto, snd_usb_audio

As for why these midi devices are showing up as snd_usb_audio devices? No idea yet.

5 Likes

Is this the metric halo MIO? If so which one and are you using the 3d card?

You don’t need to disable the individual services.
You should instead disable the target.
Eg

sudo systemctl disable norns.target
1 Like

Thank you all for your replies ! Really appreciated. The good news is that the issue seems to be fixed now (see below)

To clear up confusion about the Midi device, the Iconnectivity MIO is just a 30€ USB Midi to Din converter and doesn’t have any audio pass-thru feature unlike the IconnectMIDI2+ or 4+ made by the same manufacturer. It’s not a Metric Halo either, only a simple converter :slight_smile:

These are the result of cat /proc/asound/modules in two different scenarios:

A . Norns booted without the MIO already connected and connected after
0 snd_soc_rpi_proto
1 snd_usb_audio

B. Norns booted with the MIO already connected. (causing the error)
0 snd_usb_audio
1 snd_soc_rpi_proto

I’m running this on a RPI3B+, Raspbian Stretch and the soundcard is not an external USB card but a WM8731 like Fates. The onboard RPI soundcard is blacklisted. The system configuration and install process is almost identical as Fates. (It’s mostly the config and install process based on the work of @okyeron @TheTechnobear and others :slight_smile: )

Yes, the MIO enumerates as a USB audio interface, therefore causing a problem with the main soundcard (not the onboard RPI audio but a WM8731 like Fates) It seems to be the case with other Midi devices as @okyeron mentioned. Yes, we share the same configuration.

Modifying alsa-base.conf as you’ve suggested above has fixed the issue, thanks a lot. I think I remember we used to do something similar from the very first « Norns on Raspi install instructions », then this step became optional. I’ll update the install scripts.

And today I will test the new multiport devices functionality with an IconnectMIDI2 this time, it’s great to have this feature ! :wink:

Thanks again :wink:

1 Like