by bassybeats | May 17, 2020 | FX Pedals
As with a lot of my projects they seem to be long running and never get done. Well with the 2020 lockdown I had plenty of time to get through some projects, probably obvious by the volume of things I have been posting lately. Well this one was an idea I have had for a long time, it was based on the high volume of germanium transistors I ended up with from all my builds. Lots that were uncommon, out of ‘spec’ or not usually used in fuzz pedals.
What I wanted was a way to load up 4 different options for Q1 and Q2 and be able switch between them all and bias them up externally by ear. The base of the project was a Fulltone 69 fuzz circuit as it sounded good and was easy to wire up. Initially, I wanted to have it negative ground so it can be used with normal power supplies from other pedals. I had a good crack at doing it in Eagle and making a PCB and never made progress or got it right, this was the part that delayed the project the most, holding onto the idea of a custom PCB.
The alternative plan
I eventually gave in hand wired a unit using 3 layouts from Tagboardeffects.com. The Fulltone 69 Fuzz, The Dallas Rangemaster and the Negative Voltage Inverter. These 3 circuits gave the options to wire it all by hand during the lockdown and get a working prototype working. If it works out and my friends want one as well I can then look at a PCB, but there was no point if it sounded like crap.
I actually already had a 69 Fuzz so it was just a matter of breaking out the trim pots and transistors onto a daughter board and the wire up some 4P3T rotary switches to change between each transistor for both Q1 and Q2. To test it out, I had to find a selection of PNP transistors that were roughly the right values to put in each spot, which I used my handmade transistor tester ( arduino based ). I actually left the sockets and patch wires on the fuzz board which meant I could still put transistors directly into it to verify issues if something didn’t work or stopped working.
Next came figuring out how to box this whole thing up. It was going to be big, but I did have some old 1590DD cases that needed to be used, they aren’t good for foot pedals but are perfect for these testing units. Originally, I was going to do a voltage sag knob but after testing it out I instead changed to an input cap selector for the rangemaster.
When it came to wiring it all together, it was a nightmare. The worst part of was getting the grounds all working fine and it is easy to get the LED’s and case grounds wrong. In the end I dropped my own versions and found the dual effect wiring diagram from MadBeanPedals.com. Once I got the switching working I only had some minor issues which ended up being a dead 7660S voltage inverter. Once that was solved it was just a matter of getting it all in the case together.
It all turned out pretty well and i’m surprised it actually works. I don’t think it will be worth making a PCB but I guess thats what vero/tagboard is for. It matches up well next to my other fuzz experiment box that has 3 different fuzzes + an LBP1 in it.
by bassybeats | May 17, 2020 | Computing
After needing getting to a point of upgrading my main rigs to a ultrawide screen and going between PC and Mac I came into the strange need to have a way to switch the 3.5mm audio out to run into my desktop speakers. I tried using the speaker/audio out from my monitor as the displayport signal carries audio as well but it was incredibly noisy and introduced a lot of hum.
So this is just a short post on how I made a small box to handle the switching. It’s just housed in a small black plastic box from Jaycar with a ground loop isolation unit inside, a couple of 3.5mm jacks and a DPDT toggle switch. The isolation box helps remove any hum introduced by the power of each device in the chain as the MacbookPro power supply tends to introduce ground loops for some reason. For wiring, I just used the cable from the isolator itself as there was plenty left over.
Materials
by bassybeats | May 16, 2020 | Computing
This was one of the longest running projects that I have had running. Since forever I have tried to get a proper media storage solution working. It first started with when I had the 4 bay DroboProFS. It was good for years but always had some gotcha’s. It was tethered to my MacbookPro permanently and my mac was running Plex Media center, so to watch anything from around the house my laptop had to be on and connected. This worked for years but slowly the drives started getting very full and then started dying.
I actually managed to pickup a much bigger Drobo 12 bay rack mount unit, but the networking was too slow and I couldn’t install plex to it, meaning I would have to run plex off it over the network from my laptop still, so not ideal. I sold the Drobo and made some money, which was enough to look at building a proper home media server. I got a good deal on a 6th Gen i5 rig with 16gb ram and an empty case. At the same time, I picked up a bunch of 1tb drives from my old work for $10ea and loaded the machine with drives.
The basic idea was simple, build a machine that could run plex, store all my media and project files, act as a download server, FTP server and have built in redundancy. Due to my machine not having enough sata ports or raid capability, I opted for getting a couple of 4 port SATA cards and running a software raid on Linux Mint using MDADM. For over a year this worked great, but then as usual I had drive failures.
The Final Form
I finally got sick of space limits and drive issues, so I did a case swap and a full re-build. I ended up with 4x2tb drives + 3x4tb drives with two MDADM arrays in RAID5 giving my two arrays with 2 drive failures, surely I would be fine from here on out right? Wrong. I persisted to have issues with drives dropping out of the arrays seemingly at random, and not always the same drives or the same sata ports. After a lot of debugging ( including getting a new 8 port sata board ), it became obvious that the drive failure noise was actually a Seagate HDD “feature”. The little chirping/clicking was actually the drive telling me there was an issue with the power. I so a quick power supply swap with a project that I wasn’t using and it came alive. All drives rebuilt their raid arrays and not drives dropped out anymore.
I still had some minor performance issues with the software arrays and I think it is down to using a 8 port sata controller instead of a proper raid card. But because this is mostly a read-only system the write performance wasn’t too much of any issue. I opted for Webmin for my remote management solution as it then meant I could run my server headless downstairs plugged into the network. It gives you all the control to monitor the system, manage the file shares and FTP servers as well as other stuff.
Something to look at doing is upgrading MDADM to 4.1 by source as it is much better at detecting broken arrays and rebuilding them. Some useful MDADM commands and fstab lines are below. You need to force build broken arrays and mount the filesystem with the correct parameters on boot to be able to write to it. If you have a failed array on boot, you will need to comment out that fstab line to be able to boot and rebuild the array, a process I was very familiar with by this point.
- sudo mdadm –verbose –assemble –force –run /dev/md0 /dev/sdf /dev/sdg /dev/sdh /dev/sdi /dev/sdj
- /dev/md1 /mnt/archive ext4 rw,user,exec,x-gvfs-show,x-gvfs-name=Archive 0 0
The final build has the following setup on it:
- i5 6500 CPU
- 16GB DDR4 ram
- 4x 2TB Seagate Drives
- 3x 4TB Seagate Drives
- 1x 8 port PCI-E Sata expansion board
- Fractal Design R2 case
- 3x Fractal design case fans
- CryoRig CPU cooler
- Zalman GV Series 600w Power Supply ( this will get replaced with a quieter unit one day
A slight update
So I got sick of drives falling out of the raid and the cheap SATA controllers dying so I finally invested in a good LSI card to get it sorted once and for all. Its an LSI SAS 9217-8i controller custom flashed to IT mode. This is a PCIe 4x card as well so I know I wont run into issues with bottle necks ( not that my raid5 would bottle neck ).
Open Media Vault 5
As well as the new LSI card I also was getting sick of managing the MDADM array manually through Webmin and its Linux Raid interface. I did some digging and noticed that Open Media Vault also using MDADM for its raid arrays and flashed a USB with it and saw that it recognised the array. So it was time to abandon Linux Mint and move over to a proper NAS distro. It wasn’t without its learning curve though as there is no desktop at all, so its all command line and web based. I had an issue getting it to display the IPv4 address on first boot and had to change over its network interface as well as set a reserved IP on the router to get to it.
For most of the setup I just followed DB Tech’s tutorials to get it setup. I ended up with the following setup:
- Open Media Vault 5
- 2x Raid 5 arrays
- Docker and Portainer installed
- QBitTorrent + PIA VPN
- Plex
- Nginx + MariaDB + PHPMyAdmin
Transcoding
My last hurdle was getting hardware transcoding working. AMD has no hardware acceleration under Linux for Plex so you are stuck with Nvidia. I opted for the GTX1050ti as it supports 3 streams at 1080p at the same time, needs no PCIe power and was affordable. Getting the Nvidia driver installed under Open Media Vault 5 was no easy task and involved getting the driver loaded into Docker to be able to use it in Plex. I also loaded up NVTop in the command line so I could verify that it was using the GPU for transcoding when I was streaming and that it was indeed allowing it to do multiple streams at the same time.
Recent Comments