#2199

Thanks for getting back to me, and sorry for the late reply. I will try that later.

a|x

#2200

will this work for the encoder stability hack?

image
image828×798 79.5 KB

#2201

Probably.

I need to go eyeball it, but 0603 may fit between the pins better

I’ll check and report back here later.

#2202

there’s also this option which is what i ended up going with…from what i understand it should wrk

image
image828×983 46.2 KB

#2203

just to clarify is it anything 100n and below that will work ?

RE: ended up using the 0.01uf cer caps and all went well:) @jamisnemo brilliant hack, makes a big difference in the response, thanks!

2 Likes
#2205

Hello there,
Thank you for all the work in making this a reality, my year with Fates has been great and it’s really given my old 256 a new life.

I’ve been enjoying livestreaming lately (mostly with Arcologies) and wondered if anyone could point me in the right direction in getting the contents of the OLED screen to pass out of the on-board hdmi socket please? Would be great fun to cut to it as another feed!

Thanks in advance.

1 Like
#2206

You can look for information about mirroring the framebuffer -perhaps using raspi2fb

See this article and look for the section on mirroring

#2207

Thanks for the heads up (pun kind of intended), I’ll dive in!

#2208

Has anybody made a patch that would enable the fourth encoder to function as a MIDI encoder for script parameters (using MIDI learn)? Any thoughts, would it require a virtual MIDI device, or could it be achieved by modifying params.lua?

1 Like
#2209

Why midi?

Just add some code for enc(4) to change the param you want.

Or maybe I’m misunderstanding your goal.

EDIT to add some pseudo code

function enc(n, delta)
  if n == 4 then
     params:set(n, param[n])
  end
end
3 Likes
#2211

Thanks, I might start with modifying individual scripts like that.

But actually I meant something different. “Patch” was perhaps a poor choice of words, sorry about that. I meant a fork of the norns (or actually fates) codebase that would allow the fourth encoder to be used in all the scripts, mapped and remapped to various parameters, without further code modifications.

1 Like
#2213

EDIT: Fixed now, just needed to run the onboard update after the latest install

Hey new Norns/Fates User here

Just set-up my fates last night with a fresh install of the latest. The onboard scripts like awakw are working but I can seem to get any community scripts to work. I keep getting init error and maiden reports attempting to add a nil value.

Error is slightly different for each script but here is the one for oooooo as an example

SCRIPT ERROR: init

/home/we/dust/code/oooooo/oooooo.lua:88: attempt to call a nil value (method ‘add_group’)
stack traceback:
/home/we/norns/lua/core/norns.lua:126: in method ‘add_group’
/home/we/dust/code/oooooo/oooooo.lua:88: in global ‘init’
/home/we/norns/lua/core/script.lua:93: in function ‘core/script.init’
[C]: in function ‘xpcall’
/home/we/norns/lua/core/norns.lua:127: in field ‘try’
/home/we/norns/lua/core/engine.lua:91: in function </home/we/norns/lua/core/engine.lua:89>

reading PMAP /home/we/dust/data/oooooo/oooooo.pmap

Did I miss something in the set-up?

#2214

This is doable and a very good idea. I was thinking about a fork too since there more things to be added, like the headphone volume control.

2 Likes
#2215

Anyone run the 201202 update yet?

I’ve not had a chance to announce it yet, but put it up the other day.

Would love to get feedback from anyone running on a pi3b+. I added a change that affects how the screen works when HDMI is plugged in, so I’m curious if that works properly for others - @TanSaturn maybe?

2 Likes
#2216

Updated fine on rpi3. I’ll have to get back home to test the hdmi.

#2218

I’m still getting the same behavior. Tiny, illegible norns UI in the upper left and upper center of the TV set. Same for either hdmi port. Fates screen shows a zoomed in shell.

image
image4032×3024 2.16 MB
image
image4032×3024 1.35 MB
image
image4032×3024 2.12 MB

Sorry for the blurry photos.

#2219

Just ran the update, and tested it out with Awake to my (new) Minirig 3. Worked fine.

#2220

I haven’t tried to change the line in the lua code (I will, thanks!), but I also wanted to report that encoders on my fates seem to be a lot jumpier than before the update last month or so.

UPDATE: Changing the line 70 in the encoders.lua seems to make the trick, more or less. Encoders are still jumpy, but not as much as after the recent update (and I have updated to very latest firmware too).

#2221

Pi3 or pi4?

I may need to walk you thru a change to /boot/cmdline.txt

#2222

Pi4. I’m game for guidance. Thank you!