Fates - a DIY norns DAC board for Raspberry Pi

[okyeron]

Cyberduck appears to hide dot-files/dot-folders and i’m not sue how to enable that.

But… you can go directly to that directory

Use the Go → Go to Folder… menu item and paste the path /home/we/.local/share/SuperCollider/Extensions

[toneburst]

@okyeron

Cyberduck appears to hide dot-files/dot-folders and i’m not sue how to enable that.

There’s a “Show hidden files” option in the View menu (in the macOS version, anyway).

[GATEDFUZZ]

okay, ive been trying to figure it out for a while and nothing ive attempted has worked. so i gotta ask, what are some functional uses for the UART connectors on the far side of the Fates pcb? to use them, do i need to change something in my configuration or is it for some form of remote control/file transfer thing. I just want to make sure im getting the most out of it and im totally stumped.

[jmsiener]

I could be wrong here but really it is just there if you wanted to serial into it instead ssh. Could be handy if you’re on a desert island without WiFi but have usb-serial cable around.

I suppose you could also make a breakout board with an optocoupler and use it for MIDI but I don’t know of anyone who’s done that. It’d require a bunch of mucking about to make it work.

[okyeron]

This is the correct answer.

[GATEDFUZZ]

okay cool, i snagged a random rpi screen that has a serial interface and i was hoping it might be possible to run some form of midi or control from it to fates (or vice versa) but in the end i think usb would just be easier. might make a cool combo in some kind of cyberdeck just to keep things tidy. but thanks for the confirmation, as i wasnt sure if i was missing out on some wild trick or something

[komicone]

Hey ya Fates community.
I’ve recently dusted off my Fates build from a while ago and I’m not able to get any Supercollider engine script to produce audio. Softcut is functioning just fine so when I play content back from tape everything is functioning as normal.
I have removed all of my scripts apart from Awake with the same behavior. I assumed that I had a duplicate engine somewhere but can’t seem to locate the root of the issue.
Does anyone have any ideas of where I should be looking?

In Maiden I get this as the output on the SC window -

a CroneAudioContext
FAILURE IN SERVER /p_new Group 1001 not found
[ CroneEngine adding command, hz, f, a Function ]
[ CroneEngine adding command, amp, f, a Function ]
[ CroneEngine adding command, pw, f, a Function ]
[ CroneEngine adding command, release, f, a Function ]
[ CroneEngine adding command, cutoff, f, a Function ]
[ CroneEngine adding command, gain, f, a Function ]
[ CroneEngine adding command, pan, f, a Function ]
-----------------------
-- crone: done loading engine, starting reports
--------
engine: an Engine_PolyPerc
command entry: [ 0, hz, f ]
command entry: [ 1, amp, f ]
command entry: [ 2, pw, f ]
command entry: [ 3, release, f ]
command entry: [ 4, cutoff, f ]
command entry: [ 5, gain, f ]
command entry: [ 6, pan, f ]
cpu_peak
cpu_avg
amp_in_l
amp_in_r
amp_out_l
amp_out_r
pitch_in_l
pitch_in_r
pan: -1.0
pan: -1.0
FAILURE IN SERVER /s_new Group 1012 not found
FAILURE IN SERVER /s_new Group 1012 not found
FAILURE IN SERVER /s_new Group 1012 not found
FAILURE IN SERVER /s_new Group 1012 not found
FAILURE IN SERVER /s_new Group 1012 not found
FAILURE IN SERVER /s_new Group 1012 not found
FAILURE IN SERVER /s_new Group 1012 not found

[edit]
So I bit the bullet and did a fresh install thinking that I should just start over from scratch. I went through all the steps outlined (on a 3 B+ and using 200218 norns 2.2.9 as the install source), expanded the file system and could hear the melody of Awake!
I thought I was out of the woods now, so I did a system update from the system menu, it went through the standard update process, and was ready for a reboot. I restarted through sleep twice to make sure everything was at a solid starting point, Selected Awake, and no sound
I opened up Maiden to see what was being output from SC and I am seeing the same type of error

Found 0 LADSPA plugins
JackDriver: client name is 'SuperCollider'
SC_AudioDriver: sample rate = 48000.000000, driver's block size = 128
SuperCollider 3 server ready.
Requested notification messages from server 'localhost'
localhost: server process's maxLogins (1) matches with my options.
localhost: keeping clientID (0) as confirmed by server process.
Requested notification messages from server 'localhost'
/notify : already registered
localhost - already registered with clientID 0.
localhost - handling login request though already registered - 
This seems to be a login after a loss of network contact - 
- reconnected with the same clientID as before, so probably all is well.
Shared memory server interface initialized
JackDriver: max output latency 8.0 ms
CroneDefs: sending defs
play_fade
patch_mono
patch_mono_fb
patch_stereo
patch_pan
rec_smooth
adc
amp_env
pitch
polySub
patch_mono_gate_pause
patch_mono_gate_pause_fb
AudioContext: in_b[0] index: 4
AudioContext: in_b[1] index: 5
AudioContext: out_b index (stereo): 0
AudioContext: initPolls
FAILURE IN SERVER /g_new Group 1 not found
FAILURE IN SERVER /g_new target Node 1000 not found
FAILURE IN SERVER /g_new target Node 1001 not found
FAILURE IN SERVER /s_new Group 1000 not found
FAILURE IN SERVER /s_new Group 1000 not found
FAILURE IN SERVER /s_new Node 1000 not found
FAILURE IN SERVER /s_new Node 1000 not found
FAILURE IN SERVER /s_new Node 1002 not found
FAILURE IN SERVER /s_new Node 1002 not found
FAILURE IN SERVER /s_new Node 1000 not found
FAILURE IN SERVER /s_new Node 1000 not found
>>> /crone/ready
>>> /crone/ready
>>> /crone/ready
FAILURE IN SERVER /s_new Group 1 not found
engines: [ Glut, PolySub, KarplusRings, Ack, SimplePassThru, MollyThePoly, PolyPerc, Passersby, TestSine, None ]

has anyone seen this before or know how to get sorted out?
(not sure if it is relevant but found this similar behavior in a SuperCollider post - https://scsynth.org/t/failure-in-server-s-new-group-1-not-found/929 )
thanks much!

[claasp]

heyy all, wondering if anyone’s experienced their fates not turning on?

it seems the red and green lights turn on on the rpi but instead of the green light flickering and turning off it just remains illuminated.

does anyone know what could be causing this?

power source seems to be fine as it powers my second fates without issue.

[static]

Do you have sidekick installed? Maybe try the Vulcan grip?

[claasp]

no, i don’t. hmm can’t i’ve heard of vulcan grip before

[zebra]

a lllllllll idiom, thanks to @SPIKE.

referring to the soft-reset key combo: hold K3, then hold K2, then hold K1, then hold all three for 10 seconds.

help

[claasp]

ahhh i see vulcan grip is the 3k combo… i’ve tried it several times but in this case, it doesn’t seem to help at all

occasionally a few mins will pass with it plugged in and it works but that’s rare.

as of right now, both lights remain illuminated but that’s about it for functionality

[static]

could it be a corrupt file system from removing the power too soon? maybe try imaging a spare sd card if one’s available to see if that boots?

[claasp]

ok, i went as far as to swap both rpi’s and nothing. it does look like it could be a corrupt file system as the sd card from the other fates works. how do i go about fixing the corrupt file system?

[static]

since I’m not sure that it can be repaired, I would re-image at this point. If it happened again, I would try to make sure that the power cable is suitable and not damaged. maybe consider using a different micro sd card too.

I’m really not sure though, it might be repairable…

[okyeron]

You could try plugging in an HDMI cable to get console on that screen and see if any obvious errors pop up.

Could try to SSH and recover any data but sounds like boot is not finishing perhaps.

Green led on all the time is a weird state though. Does not match regular led error patterns (usually those are flashing for a set number of times)

Reflashing the sd with the Fates disk image is likely the solution. Perhaps to a new sd card if one is available.

[claasp]

thank you i’ll give this a try and see how what happens…if i can recover everything from the sd card then i’ll just port most of what’s on there onto a more efficient sd card

[alley_cam]

Got my fates back in working order and gave it a nice refurb. Running current updated image.

Everything is working nice but E2 is behaving strangely during script selection. It jumps huge distances on that menu but is totally fine on volume or while inside a script.

Thought it was a bum encoder initially, switched it out with a new one, popped little dejumper caps on, tried with caps off the pins, still no dice. Only this encoder is being weird.

any party people experienced something like this?

Edit

Crappy wifi in my studio was the culprit during update. It’s all groovy now!

[taxhaven]

I have experienced that a couple times but it’s not a regular thing. Could it have to do with the currently running script?

[Doom]

So many things I’d like to say, mainly thanks for letting me know, i immediately ordered😁