jack ruby

Why not "blush and bashful"? https://www.youtube.com/watch?v=gyerYQ6n3hA

Your helpers are adorable! The oven looks great too :D I was thinking of trying teracotta tiles for my next pizza oven floor. I'm glad you've disabused from that idea :)

Great 'ible! Couple Qs . 1) above you have a + input and - input. Is the chip actually balanced, or do you just mean 'hot' and 'cold' as most audio signals. 2) can you change the bias of the chip further into class A or is it fixed? Thanks!

Great 'ible! I've been on that headfi thread since about 10 pages in, now it's 480! I had to stop subscribing to it :) Thanks for putting everything into one convenient instructible. I would love it if you put a list of your materials/suppliers so we can copy your great work. Thanks!

It's the standard pi/raspberry login for raspbian

Yep. Still my main audio system :)

This is a fantastic project. You have my vote! One question: could you not just feed the cotton thread through the extruder with the PLA/Nylon filament? I mean, do you really need a second hole in the extruder nozzle?

Muhackl,I'm so glad you've got your system working now :) To understand the controls, take a look at the readme in the claub ladspa plugin folder. Charlie has pretty good documentation there. To understand how to use these even more, look at Charlie's ACD (active crossover designer) software. In there he has documentation on the different filters and how to calibrate them. There are a lot to choose from :) ACD will also model the system response for you after applying different filters. It's quite powerful.http://www.audio.claub.net/software.html

Hey Muhackl, I posted something yesterday, did you try it? I think you are calling squeezelite improperly, with the -o option. You don't want to specify the card to output, because it will bypass the ALSA configuration. Also, check your squeezelite config against mine that's attached to the 'ible somewhere. Cheers,James

I think you shouldn't be starting squeezelite with all the options. Particularly -o is sending output to the card directly. You want the output to go to "default" which will run it through your alsa based EQ. I run mine with "sudo /etc/init.d/squeezelite start". You may want t make sure your squeezelite settings are fully tuned as well. I think mine are attached on this 'ible somewhere :)

I'm not sure what you mean exactly, wangyinx. Do you mean will the sound output work over HDMI? Yes, if you follow the directions, change the settings in boot and so on, it will work quite well :)

Hey muhackl, don't feel bad! I missed your earlier comment. Let me take a look and I'll get back to you :)

Alright, got home and after an hour of fiddling came up with thishttp://pastebin.com/JXmyq68XThat should take care of what you need, any additional tweaking is up to you :)

I'm on the train so I can't try it myself, but maybe Try this:pcm.!default { type plug slave.pcm t-table}ctl.!default { type hw card 0}pcm.t-table { type route slave.pcm filtercross ttable { 0.0 0.5 # 0=left 1= right 1.0 0.5 # 0.5 mixes the two together }}pcm.filtercross { type ladspa slave.pcm "plughw:0,0" path "/usr/lib/ladspa" channels 8 plugins { 0 { label ACDf #lowpass for woofer output to channel0- left policy none input.bindings.0 "Input" output.bindings.0 "Output" input { controls [21 1 0 330 0.5 1 1] } # [filter type polarity dbgain frequency q] } 1 { label ACDf ...

I'm on the train so I can't try it myself, but maybe Try this:pcm.!default { type plug slave.pcm t-table}ctl.!default { type hw card 0}pcm.t-table { type route slave.pcm filtercross ttable { 0.0 0.5 # 0=left 1= right 1.0 0.5 # 0.5 mixes the two together }}pcm.filtercross { type ladspa slave.pcm "plughw:0,0" path "/usr/lib/ladspa" channels 8 plugins { 0 { label ACDf #lowpass for woofer output to channel0- left policy none input.bindings.0 "Input" output.bindings.0 "Output" input { controls [21 1 0 330 0.5 1 1] } # [filter type polarity dbgain frequency q] } 1 { label ACDf #lowpass for woofer output to channel3 policy none input.bindings.0 "Input" output.bindings.1 "Output" input { controls [22 1 0 330 0.5 1 1] } # 2nd order highpass at 300 hz } }}pcm.plughw.slave.rate = "unchanged";

Oh! Also make sure you've removed your .asoundrc file, because that could be messing things up. You'll know if it's a problem if you get different results running `speaker-test` and `sudo speaker-test`

More complete documentation of asoundrc/asound.conf :http://alsa.opensrc.org/Asoundrc

Muhackl, I got my hifiberry in today, so I can play along at home :) Couple things I noticed in your asound.conf file:1) you are still telling ladspa that you have 8 channels, that should be 2 channels. 2) you need to have a mixer somewhere to mix the left and right channels together - presumably before the crossover3) you need to then send the output of the highs to one channel and the lows to the otherthe flow should be like sound comes in-> sound gets mixed from 2 channels to 1 channel -> sound gets split by high and low -> sound output is routed highs=left and lows=rightthe other thing I noticed is that you are calling hw:0,0 with speaker test. Don't. Call speaker-test -c2. Specifying the hardware will make the sound go straight to the hardware, bypassing ALSA and your LADS...

Muhackl, I got my hifiberry in today, so I can play along at home :) Couple things I noticed in your asound.conf file:1) you are still telling ladspa that you have 8 channels, that should be 2 channels. 2) you need to have a mixer somewhere to mix the left and right channels together - presumably before the crossover3) you need to then send the output of the highs to one channel and the lows to the otherthe flow should be like sound comes in-> sound gets mixed from 2 channels to 1 channel -> sound gets split by high and low -> sound output is routed highs=left and lows=rightthe other thing I noticed is that you are calling hw:0,0 with speaker test. Don't. Call speaker-test -c2. Specifying the hardware will make the sound go straight to the hardware, bypassing ALSA and your LADSPA plugins. Also, make sure whenever you change asound.conf that you run `sudo alsactl kill rescan` just to make sure the new conf changes have been picked up.

Muhackl,You shouldn't need to hack the kernel because you are using 2 channel hardware, but only if your kernel is 4+ . I don't know anything about the hifiberry soundcard, because I don't have one... though I do have one on the way. :)Have you looked at the hifiberry docs? https://support.hifiberry.com/hc/en-us/articles/20... Which give a basic asoundrc conf file layout, which seems to suggest you'd use hw:0,0 which is the same as my asoundrc file. If it's different, just point alsa to output to hw:0,1 or 1,1 or 2,2 or whatever works. You can test which device that output is by running ```pi@raspberrypi ~ $ aplay -l ``` if you get device 0, subdevice 0, then you're golden. The ALSA project has a nice overview on asoundrc file designhttp://www.alsa-project.org/main/index.php/Asoundr...I...

Muhackl,You shouldn't need to hack the kernel because you are using 2 channel hardware, but only if your kernel is 4+ . I don't know anything about the hifiberry soundcard, because I don't have one... though I do have one on the way. :)Have you looked at the hifiberry docs? https://support.hifiberry.com/hc/en-us/articles/20... Which give a basic asoundrc conf file layout, which seems to suggest you'd use hw:0,0 which is the same as my asoundrc file. If it's different, just point alsa to output to hw:0,1 or 1,1 or 2,2 or whatever works. You can test which device that output is by running ```pi@raspberrypi ~ $ aplay -l ``` if you get device 0, subdevice 0, then you're golden. The ALSA project has a nice overview on asoundrc file designhttp://www.alsa-project.org/main/index.php/Asoundr...In your asoundrc file, you'll only need two channels, so you'll need to mix channels 0 and 1, then run them through a crossover plugin to make 0 be bass and 1 be treble (or whatever). Make sure you test with the woofer and not the tweeter. It's easy to blow out a tweeter if you get it wired up backwards (ask me how I know)!

'iblers,Sorry that the formatting on the code is all screwy. The instructables editor doesn't respect formatting in the <code> blocks, and has inserted all sorts of html nonsense. You can use the .txt files attached to run the necessary scripts. Let me know if you run into any other problems. Thanks,JR