Hi @okyeron. Do you mean Processing won’t work on Fates, or that you’ve not tried it?
Eyesy looks cool. So you managed to get OF working in it?
Based on this thread on the Eyesy forum EYESY disk image for openFrameworks / openGL / Lua (beta) - EYESY - Critter & Guitari it didn’t look like the official OF beta was very functional (no MIDI support, for example).
Just have not tried processing on the pi.
For the OF stuff maybe hit me up on discord and I could walk you thru it (I’d need to take a bit to remember how to set it up). I also did a custom build of eyesy which added midi etc.
My fates doesn’t boot occasionally. When this happens only the red led lights up.
I have to plug off and in the power cable for a second time to get it boot up. I don’t see a regularity or the reason for this behavior. any idea?!
Remove and re-insert the sd card?
(Otherwise, no clue)
I’m going to do my best here to explain this but I’m admittedly a little clueless.
While updating my disk image and expanding the directory via SHH as I was getting the insufficient disk space error message I managed to do something, no idea what. Now my Fates will power on but there’s nothing on the screen.
Any troubleshooting suggestions?
If you’re early in the process and it’s a fresh install just wipe the SD card and start again.
I’m assuming this is the update which requires a full reflashing of the SD card anyway.
For subsequent updates it can be done through the system menu without all the extra steps.
If however you have files (presets, audio) you want to get off this SD card you can connect the card to a computer and copy them across before wiping.
Unfortunately it was pretty late in the process and I’ve since tried reflashing the SD card a number of times. Maybe a new card would help?
It could be that you need to fully repartition and reformat the SD card with a disk utility on another computer.
Or yes trying a different card.
Update: I noticed the green light flashes on and off in groups of 5 very consistently. Any ideas?
You can check the full reference for Raspberry Pi LED error codes (note the slightly different codes for Pi 4), but most of them mean there’s a filesystem error or fault with the SD card.
Hey everyone,
Looks my screen just broke up. Bad soldering it seems.
So for the meantime i would like to use a screen via hdmi.
Is it possible and if so, how can I achieve this ?
Wasn’t there a post here on lines about mirroring the display over wifi?
Did you solder your display directly to the board or use a socket+pin header? If you used the socket and header it should be easy to replace but maybe it just came unseated from the header. You could also just flash another SD card and see if that boots to rule out data corruption.
Norns has the HDMI deliberately disabled (and I assume likewise Fates) so this isn’t possible. See below for HDMI on Fates.
However, ndi-mod can share your norns screen contents remotely via a network connection.
I knew there was something over network!
HDMI is not disabled on Fates. So yeah - you could change the framebuffer to whatever the HDMI is using - this is dynamic on Pi4 so I can’t really give suggestions on how to do that
The matron.rc file will let you change the framebuffer assignment.
Is the Fates version of the latest Norns firmware (230405 I believe) incoming soon, @okyeron?
Or did I miss the announcement?
Sorry, Not updated yet
I’m using this thread instead of opening a new one as the subject is the same.
My Fates connects to the wifi network and is able to find and load updates, it is also able to create a hotspot. I’ve been able to connect to it and work with Maiden on my Mac.
This all seems impossible now.
Its hotspot is not seen by my Mac and there’s no way to connect to Maiden’s project manager being both connected to the same wifi network (dBm -52).
Fates has been put asleep a couple of time with no positive result.
Any advice?
Thank you!
Are you using the numeric ip address to find dates in maiden?