#758

Which heatsinks did you order? The ones on the Rasp Pi shop? I saw them and wondered if they fit into the case when installed. I am looking forward to receive the case and build it but I cannot estimate how everything will fit together by now.

#759

Trying to add these to yesterdays order of the Raspberry Pi. Will see if everything fits together.

#760

I am having sound trouble with my build (from kit) I’m a diy noob so bear with me
Solder points seem all ok with no bridges, but the Fates USB C port isn’t working either with my power adapter (I’ve ordered another one to be sure) - the Pi 4 power port works just fine with the adapter though. Screen and menus work fine, Voltages are accurate, but sound is very patchy. Depending how I hold the unit the sound will distort and cut out, and it can provide a clean signal if place the unit very carefully and “just right”. Buttons and knobs give off some feedback when I touch them. Do you think I need to clean my solder joins / any remaining flux and reflow again?

IMG_20191210_074230 (1)
IMG_20191210_074230 (1)3024×4032 4.17 MB
IMG_20191210_074243
IMG_20191210_0742433024×4032 4.2 MB

#761

I can’t spot a “smoking gun” in your pics, but

sounds a lot like a short (or near-short; is there even such a thing?), or at least a ground loop.
friendly critique: use less solder. If you examine Adafruit’s example, counting from the left, quite a few of your joints look like #6 and #8, i.e. valid electrically, but not best practice. it’s something which comes with experience, and your work overall is obviously sound :slight_smile:

1 Like
#762

Best guess is your pi header connections are not good. (Cold solder joints maybe)

Reflow all of the 2x20 header pins. Give each one a good 4 count with the iron touching, and maybe check your iron temp.

Also - make sure you contact both the pin and the pad hole with your iron so both parts are equally heated.

1 Like
#763

Thank you @ground_state I had a feeling there was too much solder on points. I’ll clean it up reflow again this evening, including the 2x20 header pins, cheers @okyeron

#764

(hopefully) helpful tip: if you have to do a lot of re-flow, one of these
Google Photos
is like a flippin’ magic wand (not Mr. Man, though :slight_smile: )

1 Like
#765

yep I have a similar pen :slightly_smiling_face:

1 Like
#766

Question about bluetooth

I’ve managed to get my Bose BT headset connected and working (!)

it requires compiling bluez-alsa from source[1], then setting up an ‘.asoundrc’ as shown in bluez-alsa issue #176, 1st post.

well, that and using bluetoothctl to connect/pair/trust the headphones.

check this:

aplay --list-pcm 
~ $ aplay --list-pcm
null
    Discard all samples (playback) or generate zero samples (capture)
default
btheadset
    BT Headset
sysdefault:CARD=sndrpiproto
    snd_rpi_proto, 
    Default Audio Device
dmix:CARD=sndrpiproto,DEV=0
    snd_rpi_proto, 
    Direct sample mixing device
hw:CARD=sndrpiproto,DEV=0
    snd_rpi_proto, 
    Direct hardware device without any conversions
plughw:CARD=sndrpiproto,DEV=0
    snd_rpi_proto, 
    Hardware device with all software conversions

btheadset yo

aplay -D btheadset ./Pd/externals/else/voice.wav does the needful.

hardware headphone out still works as expected for norns and orac, at least.

the question now is; how do I get ‘jack’ (in the case of norns), and/or ‘alsa’ (in the case of ORAC/Pd) to use the btheadset device?

I’ve tried @TheTechnobear’s VNC trick to look at e.g. PolyPd - the Audio dropdowns still only show the RPi audio interface…

[1] although maybe not. there are packages in the default Buster repos, but I wanted to make sure I had the latest and greatest.

#767

Wow! This is SO COOL! Now, this is a wild question, but, one use case I’ve desired for a bit is the ability use a Bluetooth keyboard with the norns (get them keyboard wires out of here!).

Now, I understand that this takes a BIT more work than headphones, since folks would need to find a way for the ‘usb’ section of the norns to read Bluetooth (or for Bluetooth in the language of the Pi to be registered as a usb device).

Is this something you’d have the know how to begin working on? Between ORCA and now Nisp both using keyboard abilities, it would rad to have a wireless keyboard as part of a setup…

#768

@kasselvania not my area of expertise, but I would imagine that seeing if you can get bluetoothctl to connect/pair to your keyboard would be the place to start.

keep in mind that, for BT, connect/pairing is more-or-less equivalent to plugging in a USB (or other kind of hard connection) device - the OS still (in most cases) needs a device driver and software stack on top of it in order to do anything with the new device. keyboards should be pretty easy, tho :slight_smile:

#769

Bluetooth input won’t work on norns (yet). Input devices are limited to USB right now. Might be doable for Orca-C or pd tho.

I’ve tried hacking this (wiimote anyone? :slight_smile: ), but it’s a bit beyond my limited C coding knowledge. (something in the norns stack crashes when I try to recognize a bluetooth device).

1 Like
#770

Patchage maybe ?

#771

interesting, but I really want to stick to CLI/norns interface… mostly because once I start down the path of using X/VNC, I probably won’t be able to stop myself :stuck_out_tongue:

EDIT: I think the answer lies in the fact that the working alsa profile is in the ‘we’ user’s profile, and in order for norns/Pd/et al. to see and use it, it would have to be system-wide

#772

I assume the FATES and DIY norns using traditional Bluetooth will eventually open up the floodgates (yes, wiimpte AND JoyCon accelerometer input sounds like a ton of fun; maybe a recreation of some sort of theremin sending CV data to a Mangrove or ii JF through crow bends the mind).

Hoping soon someone will crack that code on the ‘Bluetooth as usb’ in the norns stack

#773

4GB might be overkill but it’s what I used. 2GB would be more than reasonable.

#774

second reply :stuck_out_tongue:

@okyeron, you were right, at least for norns (haven’t tried messing with Pd yet)

the non-gui option:
alsa_out -j btout -d btheadset -p 1066 -n 9 -c 2
and then
EDIT: If you want volume etc. control, then use the ‘crone’ device:
jack_connect crone:output_1 btout:playback_1;

jack_connect crone:output_2 btout:playback_2

The audio quality seems fine, and there’s no latency that I can notice, at least not with “AWAKE” - something more demanding could impose a delay, and I certainly wouldn’t want to do any mastering with this setup :joy:

note that:

  • -j option to ‘alsa_out’ names the port
  • you may have to play with -p and -n to silence/even make ‘alsa_out’ work
1 Like
#775

So I reflowed everything and it’s super clean, thanks for you help there… I have nice audio coming out now, except with incoming audio I get digital noise and whiney hiss at about 90 - 100% vol. With IN turned up MON also introduces additional noise. If I bring IN and MOM down to about 75% the noise is gone. Is that normal?

IMG_20191210_225049
IMG_20191210_2250493024×4032 3.79 MB

#776

What’s your test situation? Your picture does not show anything plugged into the inputs. What script is running?

Please compare the output noise you’re hearing between the headphone out and the main outs - same or different?.

FWIW - As you have it in that picture, the HP level is totally maxed out. I’d think that’d be punishing thru actual headphones.

Also FWIW - Turn MON down unless you actually want to monitor the input signal.

#777

Sorry, I was running my phone audio into the input to test. With audio coming into input the HP out out is a little better sounding than Outputs, but both were not great at mid level… compared to Awake or Scales which sound perfect.
I’ll do some more testing.