#416

i got a SUPERCOLLIDER FAIL message the first time i used fates. i just went to system -> update and it was gone after the update installed and the system rebooted.

1 Like
#417

unfortunately ‘supercollider fail’ is a catch all error message.
as there are many reason supercollider might not start, anything for hardware issues (dac cannot be initialised) to software configuration.

really what you need to do is to logon on to norns, and type ‘sclang’
this will try to start supercollider (scsynth), and if it fails you will see a load of errors messages which can be used to determine the underlying cause.

whats the build error?

2 Likes
#418

I’ve seen this happen 1 out of 3 times I do an update. If it’s just a glitch in the matrix, a reboot will usually clear the problem.

If it happens everytime, then it may be a sign of the dac not initializing (as mentioned above). I’ve had a couple people get this error because pins on the DAC were bridged.

1 Like
#419

restarted illustrator. works fine now…:face_with_hand_over_mouth:

1 Like
#420

thank you for this! i didn’t realize that the “supercollider fail” message was a catch all error message. that should be helpful going forward.

#421

yeah I’m pretty sure it’s a config or card issue because the initial flashing of the (16gb) card work fine and I get some sound out of the awake app (but not with my 64gb sandisk extreme)

As soon as I expand the file directory, change my localisation and reboot I get the SUPERCOLLIDER FAIL message then I go and try the ./waf thing get a build error at the very last step (matron) then no sound for the app requiring supercollider.

the apps using softcut like MLR/GLUT are working fine. I’ll try again tonight

#422

So to clarify a bit…

  • if you expand the filesystem, reboot and get that error - Just reboot once more and see if the error clears.

  • Be sure your SD card is formatted FAT32 and not ExFAT or something else.

  • “the ./waf thing” is recompiling the norns source code on the device. This is ONLY needed if there has been a change to the norns C code and you have manually pulled a new version from github (git pull). This should not be considered a first thing to try for troubleshooting. (you will also need to RESET or reboot the device after doing this).

  • if you do get build errors from matron - post all of the errors here and we can help troubleshoot.

1 Like
#423

Just Finished my build eveything works until i expand the memory then the audio stops working. I’ve rebooted a couple of time but the doesn’t seem to fix the issue and now gives the super collider fail message. I’ve applied the two fixes above and the soldering work on the dac looks correct.

#424

As much detail as possible is needed to try help to debug.

  • which pi?
  • what size sd card?
  • Can you clarify what you mean by “everything works”?
  • which “2 fixes above” - and when did you apply them?
  • does reflashing the sd card get you working again?
#425

Pi3+, 64GB, the volume level and multiple midi devices fixes (output volume is definitely turned up) and reflashing does get it working again but it’s inconsistent 50/50 chance of it working. I have used diffrent buttons but they work as does the screen and encoders the only things i have plugged in are the headphone jack and the power.

#426

To me this points to some issue with the DAC soldering. I’d suggest touching all the dac pins with an iron once more and get a good look at it with a magnifying loupe. Even better - Post a picture here. Sometimes lifted pins are hard to spot.

I’d also suggest starting from the known disk image and following through the instructions to expand the file system and then test it awhile before applying any changes/updates/etc. (just to be sure there’s not any errors being introduced along the way).

(shot in the dark) It may also be worth trying a smaller SD card as @madeinspace reported above that he was having issues with a 64GB card (although I have no idea why that would cause an error with the audio system). I’ve only used 16GB/32GB cards so…?

1 Like
#427

Fresh image on a 32gb has the same issue weirdly it seesm to work more often when not expanded here’s a pic i did spy somthing that looked like a bridge but fixing it doesn not seem to have help. Oh aditional detail i forgot to meantion i haven’t soldered the 4 mono jacks on yet as they’re still in the mail but given it does actully work sometimes i don’t think that’s the issue.

DSC_0054
DSC_0054.jpg1003×1144 231 KB

#428

That bottom 220R looks a bit off to me (although it could be the light/angle). Since that’s the i2s control stuff (bottom one is I2S_CLK), it could explain the dac being wonky

Yeah - Missing jacks should not make any difference.

#429

which kind of Power Suppy do you use. what does the red LED of you Pi saying? (off, blinkin, permananet)
I posted it already somewhere above. If you use an supply which delivers not enough juice (in terms of mA),
The I2c connection is not stable and leads to an 50/50 chance of a working fates

In my case it was Orac which was working pretty fine and as soon as I switched to regular norns the audio was broken.

2 Likes
#430

Thanks @koerby that may have solved it i’ll track down a better supply to test

I’m using a 2.4A supply but the pi never seems to draw more than 0.6A amps out of it. The red light is blinking which i guess does mean the power supply is the issue makes sense as i just built my second board and had the exact same issue. Not sure why it’s complaing though i’ve got a little usb votage monitor and it hovers around 4.98V and 0.490A while running norns.

#431

I have one of those USB voltage monitors as well and it never seems to go above 0.5A-0.6A as well. ¯_(ツ)_/¯

I think dmesg should give you some idea of how many undervoltage warnings are happening.

Also just found this nugget which might be helpful

You can minimize the voltage drop by using a lower resistance power cable

#432

Scrach that it’s the power supply switched to a lower rated one and that worked because raspberry pi’s are weird???

Thank for the help guys and thanks Okyeron for all your hard work on this project

2 Likes
#434

Ok so after all that, I powered the raspi with the shortest micro usb possible instead of the USB-C port and it started working normaly again. So be aware ppl it might be an inadequate power issue.

micro SD cards tested:

ScanDisc 32GB and 64GB Ultra
ScanDisc 64GB Xtreme

Thanks guys and @okyeron for your help troubleshooting

1 Like
#435

sidenote:
Have anyone ever tried laser cutting their own encoder knobs? Thought I would give it a try while I make my case.

09

2 Likes
#436

Quick update for people who’ve asked about heat when using RPi 4-based Fates and a 3D printed case – I have little rubber feet under mine and no problems when using on a hard surface, but I had it resting on a bed while using it for an hour or so and the bottom got hot enough to warp the PLA a bit. No performance problems however.

3 Likes