Well, the best list lives inside the package manager in a norns.

Meanwhile, thumbing through the “norns” tag in the “Library” category on this site should get you off to a start.

1 Like

The first you said - It works !! Many Thanks !!

1 Like

a good starting point :slight_smile: : https://monome.org/docs/norns/app/

3 Likes

Really like the case over the screen, if Im seeing that correctly! The exposed oled can be a pain to keep clean…

reminds me of one of those sit-down pac-man machines.

5 Likes

I’ve replaced codec and crystal and it works :smiling_face_with_three_hearts:

1 Like

I had forgot to expand disk space, so I had little space left in my diy norns.
If anyone else forgot to do it, go to the Terminal and type:

ssh we@norns.local
(password: sleep)
sudo raspi-config

then select > Advanced > Expand disk
and reboot.
it went from 2Gb free to 28Gb on my 32Gb SD.

16 Likes

Does anybody have an alternative part for the encoders? Those I can find on mouser have different shaft lenght (for D-shaft) or the same lenght but knurled shaft.

2 posts were merged into an existing topic: Potential group buys

You can always buy knurled knobs instead.

Does anyone have an idea of approximately the cost of duty and import tax on shipping the norns shield kit to the UK? :slight_smile:

I bought just the populated PCB and didn’t pay any import duty or tax.
It may well be different for the full kit, and it’s often quite random as to whether the Royal Mail decide to take the tax from you or not.

I imported mine with a Crow and the VAT was around £20 + the handling fee of £12.
I get caught 99% of the time. The handling fee is a flat charge no matter the cost.
The PCB alone may get around them bothering to charge it though.

Thanks. I’ve looked at gov.uk guidelines and I think it should be £0 but I will report back after payday.

heads up everyone. i’m moving commerce discussion to Trade, per the CoC.

2 Likes

can somebody suggest how I alter the JACK config? I don’t know JACK, or where it is, but am finding the L/R funkiness confusing…

i don’t know of any jack configuration option that will reverse the order of the DAC ports.

i see two options.

option 1, change the behavior of the mixer client (c++)

there are three JACK clients involved. one is scsynth (2x2 I/O), one is softcut (2x2) and finally the main mixer client called crone (6x6.) only crone is connected to the ADC and DAC ports. (NB that softcut is owned by the same parent process as crone.)

each of the crone clients inherits from Client, which is a template class specialized by the I/O count and given a JACK name at construction.

the function Client::connectDacPorts() programatically connects the client outputs to hardware outputs. so you could hack that function.

looking now i notice that (1) this is already hacky - must have been a stereo client originally, (2) it should really just be a MixerClient method. so i should clean this up, such that the hack doesn’t involve the parent class methods.

if you use this option, it would be helpful to do it as an optional runtime flag for crone. that way other people can easily enable it.

option 2, re-route the JACK connections after launch (bash)

after all the clients are running, you can use the jack_connect and jack_disconnect utilities to re-route the connections. specifically i think it would be something like

jack_disconnect "crone:output_1" "system:playback_1"
jack_disconnect "crone:output_2" "system:playback_2"
jack_connect "crone:output_1" "system:playback_2"
jack_connect "crone:output_2" "system:playback_1"

but i am kinda guessing the exact port names at the moment. you can use jack_lsp to list them.

if you do use this option, i think the best place to execute it would be when the lua stack starts up - perhaps in your version of norns/lua/core/config.lua. this would ensure the crone process is already running.

and for completness,

option 3 - caveman

switch cables or rewire the PCB.

4 Likes

option 4 - put your headphones on backwards (…kidding)

i apologize for the confusion… what i was originally suggesting was @zebra’s option 2. i’ll test and make a howto.

3 Likes

Option 3 is not stupid - I’m building quarter inch breakouts, and those are easily used reversed. It’s mainly a headphones issue, being honest.

Of course, modifying that script means it will be overwritten on every update?

My instinct would be to somehow add something like an environment variable to flag the board as a DIY one pre-revision (reversed), which then branches code in the official script. I presume Supercollider can access environment variables, of course. But that would have minimal affect on everybody else, and be a change that persists over updates.

I appreciate this affects a small amount of the norns ecosystem, but right now it’s not insignificant imho, and it’s a feature of an officially released thing, hence trying to work out how to solve this with minimal alteration but in a relatively robust way.

I’m just about to order shield pcbs. It wouldnt be much hassle to change the L/R ins/outs on the board before ordering but I dont want to do that if there is going to be a software revision that detects the diy shields and swaps them in sw!

Is there a consensus as to which way this is likely to go? (From a personal point of view it would be nicer in hw so that eg orac would be supported as well !) I’m also guessing that from a sw maintenance point of view it would be easier to use a custom adapter cable on the existing shields and keep norns and diy shield in sync with no branches.

I’m using a shield. If I want something on the right, I put it on the right…
The visual feedback we generaly have is just a number.