#978

Dumb question - why did you get a USB wifi nub? The raspberryPI 3B and 3B+ (recommended) have wifi built in.

For your update issue - it sounds like the update did not properly finish something.

I’d suggest re-flashing the SD card then trying the update again.

#979

Thank you so much for your response and advice to re-flash and try again. That’s what I was thinking but I’m so new to this stuff I had the classic fear response of making things worse.

Re using the USB wifi nub – I am using a Raspberry P3 B+, and thought it had built in wifi, but when I tried to connect to wifi it wouldn’t scan or show any networks. Without knowing how to troubleshoot the Raspberry Pi side of the wifi, I decided to try a nub since they’re pretty cheap. With the nub it saw my network right away, so I’m not sure what I did wrong with the initial setup. I will try to connect without the nub again once I re-flash and get going…

#980

OK, so I re-flashed and that got it going again. This time the wifi worked fine without the nub, so I probably did something wrong the first time. Anyhow, I ran the update again and everything seems to have worked!

Thanks again!

8 Likes
#982

Still trying to figure this out and wondering if anyone can offer any insight.

With audio going in, I can pick it up at the INA and INB test points. If I SSH in and start alsamixer and then unmute Digital Sidetone I can hear the input in headphones plugged into the shield. Is Digital Sidetone just sending the input straight to the output in the chip without it going to the Raspberry Pi?

I also don’t see a capture bar in alsamixer. Is this normal?
alsamixer

Is there anything else I can look out for on the software side?

Thanks!

#983

Just got my norns-shield working last night. Hooked up my mk128 grid monome and it registers and can input data to the norns-shield but I get no led feedback (nothing lights up other than at first boot of the monome so I know there is power). Other videos I’ve seen with a monome plugged into Awake have buttons lit for indication. Any reasons the mk128 wouldn’t light up at all? I know it is a single brightness but then I’d expect the leds to just be on.

#984

Mono-bright grids may not be 100% compatible with some scripts. Most/Many scripts assume vari-bright, so your mileage may vary from script to script.

You could try my Grid Test script and see if you get anything from it. I’ve not tested it with a mono-bright, but you should get some lights from it.

1 Like
#985

Hi, could you share the corrected image for ssd 1325, I will be grateful to you!

#986

Hi…sometimes after starting up my Norns Shield the output level is very low. It doesn’t seem to be related to the main mixer settings (output levels are normal). Loading different scripts doesn’t seem to change anything either. Usually a sleep cycle will resolve it but sometimes that doesn’t work either and I’ll need to try it a few times. I’ve been trying to identify a pattern but don’t see any at this point.

It isn’t happening frequently enough that I’m terribly worried about it, but I was wondering if anyone else has encountered this behaviour and might have any suggestions.

#987

I see the same sometimes, but mine isn’t fully working anyway so maybe not the best comparison. Levels look normal on the mixer page. Do you see the volume return to normal when Reverb is enabled but then low again if its turned off?

Don’t have a fix to suggest unfortunately.

1 Like
#988

I haven’t tried enabling the reverb when it happens but I’ll keep that in mind for next time. Thank you!

#989

I have the same issue. I did some reflowing of connections and it went away, so I thought that was the fix. It wasn’t though, as I have the same problem recurring occasionally. Good to hear it’s not just me! The next time it happens I’ll take note of what I was doing and we can compare notes. Last time a reboot fixed it for me.

1 Like
#990

Okay it just happened again - low audio output after booting up. Tried adjusting the reverb…no luck. Tried a reset, no luck. Did a sleep cycle and switched to Awake - output is back to normal, but input level is still really low. Switched back to the script I was working on (modified version of Cranes) and the input was still really low. Cycled again and it was back to normal.

#991

Has anyone modified the Norns Shield to add a 4th encoder like Fates for use with Orac?

I was looking at adding one in KiCad, but was curious if there is a recommendation to which set of gpio pins to use and also, how to enable it in the system.

Thanks!

#992

does orac have midi mapping for the controls?

someone should do a midi controller with 4 knobs and a wooden nub keyboard…

6 Likes
#993

That would be sick. C&G should team up with Monome and make an Organelle style controller.

#994

You’d have to look at what gpios are available.

Also itd require system level changes which will be incompatible with future updates so your need to maintain a separate fork of the the whole
Linux system and norns stack. (Not for the faint of heart)

#995

That’d be easy enough…

The Keys: The 24 keys (not including the Aux button on the far left) transmit “note on” messages. The leftmost key uses note number 60 (“middle C,” or “C3” in most MIDI systems), and the rightmost key uses note number 83 (“B4”), with all keys in between following this scheme. When a key is pressed down, a “velocity” of 100 is transmitted. When a key is released, a “velocity” of 0 (zero) is sent.

The Knobs: Knobs 1, 2, 3, and 4 transmit “control change” messages using controller numbers 21 , 22 , 23 , and 24 , respectively. The full range of controller values (from 0 to 127 ) is utilized.

The Aux Button: The Aux button transmits momentary “control change” messages using controller number 25 . When the button is pressed down, a controller value of 100 is transmitted. When the button is released, a controller value of 0 (zero) is sent.

The Pedal Port: A pedal connected to the Organelle’s Pedal port transmits two sets of “control change” messages.

Controller number 64 transmits a controller value of 0 (zero) for any received signal below 64 , and a controller value of 127 is sent for any received signal of 64 or above. This discrete, threshold behavior is particularly good for sustain-/damper-style pedals.

Controller number 26 transmits continuous values. While the general range would be from 0 (zero) to 127 , the exact range of values may vary based on the pedal connected. This continuous behavior is ideal for an expression-type pedal.

#996

One more update (sorry if this isn’t the thread to be posting this kind of stuff). I think I’ve identified the pattern to my low audio output on startup issue:

I have a MIDI Fighter Twister connected to the Norns Shield. If I power up with the MFT connected and get a low audio output (which doesn’t always happen), disconnecting the MFT and then doing a sleep cycle consistently corrects the problem. After restarting and then connecting the MFT, everything is fine.

Curious to know if anyone else who encountered a similar issue had a MIDI controller connected when starting up.

#997

my guess would be too much current draw at boot…

1 Like
#998

Hi Unicity!
Yes, but not your exact situation. When starting mine up my (200323 Shield) with a iconnect midi 2 (which is self powered) I’m getting the very low volume output (I haven’t checked the ins yet). I did 3 sleep cycles (each time having to unplug/replug in the power) and it went back to normal. I’ve only had the shield built for 2 days so I still have lots more testing to do. I will try with my MF Twister soon as well.

1 Like