Of course, Thonk do genuine Rogan encoder knobs
https://www.thonk.co.uk/shop/make-noise-mutable-style-knobs/

I prefer the look of the unskirted ones from Modularaddict, but these skirted parts are much better made (and in stock, which is a bonus, obviously :wink: )

2 Likes

I found these on amazon in Germany.

3 Likes

Hi to everyone
i noticed that the OUTPUT of my Fates is very LOW. I tried to play a 48khz sample from TAPE but the volume is always very low. There is a way to solve this?

these are the measurements

48khz sample (measurement on mono out)
I wish the samples were played back at the original volume but it seems impossible.

You could take a look at raising the volume using the alsamixer command line tool. Look at the Master level. I believe the default image has that set to 86 so there’s a bit more you can get from it.

I don’t really understand what “original volume” or “very LOW” mean in this context. As compared to what?

Please see the codec data sheet for what to expect from the device.

Of course - be sure to check your tp TAPE levels on the Mixer page of norns. It’s also possible to change that value from script with audio:level_tape (level) so you might triple check some script isn’t changing that value somewhere

firstly - it’s a line-level audio device, not a eurorack device. so expect a maximum voltage range of something like +/- 1 V.

if you removed the DC offset, your 0.68 Vpp would translate to something like -9 or -10dB of headroom. i don’t know how much headroom your samples have, but that’s not an unreasonable amount.

however, the DC offset is problematic. assuming your scope setup allows accurate readings of external signals, i have to assume the -1v offset is a hardware issue. (i’m also assuming the samples don’t contain DC.)


on the software side, TAPE playback levels are influenced by the TAPE level setting on the mix page, as well as by master output level and reverb/compressor characteristics. with those levels at 0db and compressor/reverb disabled, TAPE will play exactly what is in the sound file. (just as if you used aplay from the command line.)

3 Likes

Beyond the oscilloscope measurements my test is very simple. I reproduce a 48khz sample from tape with Reverbero and Compressor disabled. All the levels in the mixing parameters are set to 0.0db, however the sample reproduced on Fates comes out much lower by comparing it with the playback through the player of the MAC finder.

to make you understand the problem better I uploaded the two audio tracks. One is the original sample, the other is recorded directly by the FATES with all the mixer settings at 0db

i’ll say it more simply: i don’t know why your fates is quiet, but 1) it seems like a hardware issue and not an issue with TAPE, 2) the oscillator image doesn’t tell us much without context. (even the soundfiles do not tell us much without knowing how you captured the signal under test.)

to decide this, one way or another, try things like aplay on the command line (testing ALSA and bypassing norns software), or running norns synthesis scripts like awake (bypassing the TAPE functionality.)

and of course, don’t measure or record it as you would a eurorack module, but i hope that goes without saying.

that’s all i’ve got.

1 Like

I made another test. It may be that this will tell you more.
This time I recorded the sample via TAPE / REC. In this way the sample is played at the same volume (i.e. the original volume). I left with 2 outs from ableton live towards FATES, I have attenuated the volume on the ableton mixer by about 6db as I use a Motu Ultralite (DC Coupled). This time the sample recorded via TAPE is played back at roughly the same volume.
This makes me think there was something wrong with the sampling rate or something else?
The only difference is that from FATES / TAPE the sample is recorded in 24 bits. While the sample that sounded low was 32bit. Both at 48khz.
I confirm that scripts like AWAKE sound and optimal volume.

Thanks for the support

1 Like

Hello there
Has anyone a sort of encoders strange behaviour? In the Levels page, if I turn encoders clockwise, the Levels falls down a little bit. I know it’s also a first batch Norns issue.
Mine is a Fates complete kit from January 2020.
Thank you :slight_smile:

3 Likes

my encoder 2 is really jumpy. i have to really try to lock it into a fluid ccw motion to turn any parameter down or else it jumps from like 100% cw back to 20% ccw at the slightest nudge. Someone else mentioned that i should just replace it. so im going to try that, maybe this morning. im a little hesitant because i lost a screw, so my case is like bulging and it feels fragile where the pin header connects to the pi. bought some replacement screws but they’re too small. picked the wrong length from the bom sheet. but i do have an extra fates board that i messed up on my first attempt so i’m just going to switch mine for one of those encoders.

2 Likes

Mmm yes. But it’s weird because mine are the “complete kit encoders”. Maybe are there better ones? Any suggestions?

I would like to treat another question: what about the latest Norns firmware?

Encoders will go bad more quickly than pots if your device is bumping around unprotected in the bottom of a bag. Replacement is a good bet, and then considered packing when transporting to extend the life of said encoders.

I’ve had this problem with encoders I bought new from Mouser when building my Fates. One of the four was jumping values unless i was turning it reaaaally slow, after a few month it became completely unusuable so I replaced it and now everything works as it should.
Be careful while desoldering, i lifted a pad accidently by heating it too much.

1 Like

Use the ones listed in the BOM. The ones in the kits are exactly the same part.

It’ll get updated when I have time (and I’m crazy busy the next couple days)

4 Likes

Update 200712 now available

If you are running a version prior to 200218, DO NOT USE SYSTEM > UPDATE .
You must update manually via SSH. Instructions are on the release page: https://github.com/fates-project/norns/releases/tag/2.4.2

If you are on 200218 or later
use SYSTEM > UPDATE while connected to the internet.
(please report back if you have problems with this)

General Norns update notes and info about this release are on the norns release post here Norns: update 200712

21 Likes

Thank you so much and 20ch of appreciation!

Update went smoothly as usual. Thank you for this!

1 Like

So reflowing seemed to work at first, but now the same situation occurred again. I will reflow again, but is there a chance the fault is within the encoder and I should try a different one?

Yeah… It’s possible the encoder is bad.

A good solder pump/sucker helps a bunch for removal.