#516

The problem is that it’s a separate headphones codec within the original Norns (per my understanding) to power the headphones jack.

1 Like
#517

Yeah, but the wm8731 has a headphone amp module controlled over i2c, so functionally I cant see what the difference is… not sure what I’m missing…

#518

I didn’t design it, I’m imparting what I remember being told by the designer of the FATES. I might have misremember red or misunderstood the reasoning for that. My guess is, everything has been done to not alter the Norns core architecture.

What I’m wondering is, if the output volume alters the headphones level, what is essentially the difference? I understand that you don’t have a third, dedicated pot with a volume control, but you have essentially the same device.

#519

You are correct. The dac has a digitally controlled HP level (over i2c). I only just recently got the right commands sorted out with help from @TheTechnobear.

By default the hp level and main outs level are tied together in the norns level mix page.

The only issue here is how to handle controlling just the hp level since it’s got a different address from the norns hardware hp amp.

You could modify the norns code to map the correct i2c commands to the HP menu thing, but this would require a re-do after each Norns update. Or a custom norns branch (and thus maintenance of the branch, etc)

Alt approach - You could do a quick one liner script in the maiden REPL to set HP volume. I’ll need to fire up my gear to figure that out tho

1 Like
#520

This is probably a really dumb comment (not being familiar with norns code) but arent there abstractions at the driver level in raspbian that would cater to both? eg snd_soc_wm8731
Again, sorry if this is a really stupid obvious comment…

#521

Nah… it’s just a norns code thing. (I believe) The hp level on Norns hardware is sending an i2cset command and they use a custom driver (snd_monome I think)

So you can do the following from maiden to change the hp volume on fates (use at your own risk :grin:)

os.execute("i2cset -f -y 1 0x1a 0x05 0x0")

Will set it to zero - last parameter there is a hex value for volume. 0x70 is a good medium value.

2 Likes
#522

Hi fellow nerds,

I’ll most likely build Fates soon enough, i have not been that excited about a project for a long time.

Looking at the Orac software makes me wonder though. Has anyone thought about modding the PCB in a way that 3 stereo output could be a thing? Since Orac can run 3 parallel chains, it could be somehow possible to output them separately? Would that even be possible?

Thanks! :slight_smile:

1 Like
#523

Question regarding soldering the usb-c jack.

When I insert the part the internal 14 pins don’t protrude through the pcb, but appear to sit flush with the top of it. Is this normal? In the build pictures they look like they’re protruding.

#524

I haven’t used Orac yet but I think that as-is it is “limited” to stereo output, you could certainly alter this though since it’s all based on pure data, but that’d need some work on the patches.
Regarding hardware you’d need more DAC outputs (fates, like original norns has 2 ins an 2 outs) so not possible by modding the PCB, but you could use an external class compliant sound card.

#525

Yes, of course some pure data sorcery would have to be made but wouldnt it be great? hehehe

#526

orac is not really limited to stereo output.
you just define your own router with the chains you want, and then send them to output using the standard dac~ object.

I do this with an organelle/fates using an ES-8 to send audio and CV out to my eurorack.

4 Likes
#527

They are almost flush… as long as you are careful about bridges and the flux floweth, you should be fine :wink:

1 Like
#528

That’s great news, Orac seems so flexible. I had forgotten about the CV Tools, we recently bought an ES-8 at work (inside a MN shared system) can’t wait to explore this!
Building my fates tomorrow :slight_smile:

1 Like
#529

Update to what I wrote below: I got it to work. I guess there’s issues with Catalina and Etcher. Launching Etcher with the sudo command from Terminal did the trick:

sudo /Applications/balenaEtcher.app/Contents/MacOS/balenaEtcher

Here’s what I initially wrote: I’m sure I’m doing something incorrectly, but I don’t know what. I’m trying to flash the img file to the SD card that came with my Pi. I am doing this on a Mac. I installed balenaEtcher, and it runs properly (had to turn off the security on the Mac to get it to install and run), and then I popped the SD card into the Mac, where it was recognized. I selected the img file in Etcher, and then I selected the SD card. I hit Flash, and I was asked to re-enter my account password. I did this. I immediately got an error message that reads “Something went wrong. If it is a compressed image, please check that the archive is not corrupted.” I did this with the 2.2.0 img and the 2.2.1 img in the Fates GitHub, and got the same error with both. If anyone has a suggestion, that’d be super. Thanks.

#530

Update to the update: It worked. My Fates/Norns is alive and Awake.

3 Likes
#531

They might only protrude a tiny bit (I can usually feel them with my iron better than I can see them)

Just be sure you see pins in each of the holes (before you solder). I had one (out of many so far) where the pins bent - was quite vexing until I removed the thing with hot air and saw the bent pins.

#532

Follow-up question: I installed 2.2.0. When I tried to use the Norns update command, I got a “disk full” error. Any advice on what to do? Thanks.

#533

Did you expand the file system (and RTFM :stuck_out_tongue_winking_eye:)? (sudo raspi-config)

2 Likes
#534

Ha! No, I will read up. I clearly forgot something from when I previously had a Norns.

#542

any luck? After reading your post I went back to my Fates and…no sound. The GUI and encoders and scripts all seem to be loading fine though.