#646

likely cause - your overlays might have been overwritten?

Also - a quick note about wifi. If you were previously connecting with wpa_supplicant and then switched over to Network Manager, you need to do 2 things:

  • reset /etc/network/interfaces to what norns expects*.
  • delete or rename /etc/wpa_supplicant/wpa_supplicant.conf

* /etc/network/interfaces should be this:

# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
1 Like
#647

Is the wpa_supplicant in the boot directory(not in front of the pi right now).

Another question: is it possible to make the inputs stay centered in the monitor? Right now my inputs are panned left and right.

#648

system -> audio -> monitor mode = MONO ? is that what you want?

1 Like
#649

this starts out in the boot dir, but gets moved to the path /etc/wpa_supplicant/wpa_supplicant.conf on first use. That’s where you want to look for it.

1 Like
#650

That fixed it. Thanks!

:pensive: of course…

#651

It just hit me that the input/output of my USB soundcard is very low. I need to crank my Audient iD4 to get a good headphone output. What settings in jack (I’ve tried alsamixer, but due to the Soundcard type there are no settings I can change) or else can I change to fix this? I’ve cranked the settings in the system menu of norns but with no help.

#652

Alsamixer should be the way to adjust levels. Confused as why that wouldn’t work.

Is this for a headphone output separate from main outputs?

Obvious troubleshooting here: https://raspberrypi.stackexchange.com/questions/80072/how-can-i-use-an-external-usb-sound-card-and-set-it-as-default/80075#80075

#653

No adjustment options in alsamixer, just “internal clock validity”. Will do some research.

#654

just ordered a rpi 3 b+. gonna maybe attempt to run norns on it, as well as try out orac and some pd stuff. i have zero programming knowledge and no linux experience, so we’ll see how this goes! i love to tinker and learn new stuff, so i’m real excited! what dacs are y’all using? i have a focusrite scarlett 2i4 that would be nice to use, but i understand there have been some compatibility issues. guess we shall see!

#655

hi, I’m using a focusrite 6i6 and a behringer uca202 (also usb) on a rpi3b+ without issues. the only part I’ve found somehow tricky was to setup the encoders.

1 Like
#657

this is good to know, thank you!

#658

I’ve got a weird issue that I cannot seem to identify why is happening.

Only error I can seem to find is the following in matron:

# script clear

pset >> read: /home/we/dust/data/system.pset

ERROR (i2c/hp) failed to write

ERROR (i2c/hp) failed to write

### SCRIPT ERROR: NO SCRIPT

Seems like an issue with system.pset, is there a way to fix this?

Edit:
I sFTPed and deleted the system.pset file. and that seemed to help(took a backup of course).

#659

It’s normal and I’ve ignored it for the longest time.

Basically I think something in the official norns hardware is trying to set the headphone volume which is handled by a i2c chip separate from the main DAC. Thus on the Raspi - this error gets thrown because that i2c chip does not exist.

#660

but that should not lead to any bugs right? What happened was that I got unresponsive encoders, until I removed the .pset file.

#661

Hello—I’ve been following this thread for a while and I’m working on building a norns with a 3B+, a PiSound and an HDMI screen. I’m struggling with making sclang find the JACK server, but I might be able to resolve that with resources I have.

My question is: since the Cairo screen.c code has changed, what is the way to properly scale the Matron display to my screen? I’ve got the 2 tiny screens at the top thing going on at the moment.

#662

Look at line 162 in screen.c

Change that and recompile norns with ./waf

#663

I’m scaling it now—as recommended higher up in the thread—right after line 163. I’m still getting the cairo surface only covering the top half of the screen and appearing twice.

#664

I just remembered where else I saw this:

/boot/config.txt

# uncomment to force a console size. By default it will be display's size minus
# overscan.
#framebuffer_width=1280
#framebuffer_height=720
1 Like
#665

The framebuffer changes how the console (and cairo surface/surfaces) renders within the space provided by the screen, so scaling that up doesn’t do much beyond making the text appear smaller. It seems like people are mostly using SPI displays—not sure what I’m missing in order to make it properly render on my HDMI display here.

#666

Hi,

on line 62 you need to set the resolution of your screen, mine is

surface = cairo_image_surface_create(CAIRO_FORMAT_ARGB32,640,480);

Then the scale line should be something similar to:

cairo_scale(cr, 5, 7.5);

where 5 = 640/128
(x = device res width/original cairo surface width)

and 7.5 = 480/64
(x = device res height/original cairo surface height)