Just an idea of sorts
This is a rough front panel layout for a new 12 voice bi-timbral polysynth using elements of my “A Bit More” design and a pair of self contained voice cards.
Each card has dual DCOs, multi pole filters like the Matrix 12, 3 envelopes (1 software/2 hardware) and 3 LFOs (2 software/1 hardware). A pink/white noise source and a multi effects processor for each board.
1 voice card is built and tested. So it’s time to build the assigner and panel which is encoder based.
I’m only using black keys because they are easier to play.
7 Likes
Ready for software
Finished wiring up this front panel, now to start some programming. Teensy based assigner and front panel controller with 14 MCP23017 port expanders to control the encoders, buttons and LEDs. Simplest wiring there is.
Parameter screens will be added later.
8 Likes
As allways, your creations are “from a different dimension” (<= as in WOW, F…in’ cool). I can only imagine how you do it while the word around you goes down the drain… probably the only way to stay sane in these times (AND especially at your location)… 
keep it up, yu are an inspiration (to me).
5 Likes
Here’s the latest update, most of the front panel is working, I have a bug around the effects, but that’s just pin assignments that I’ve not got right yet, so I know the effects work, they are just disabled at the moment.
8 Likes
Thanks, I appreciate it and yes, building synths keeps me sane in the current times.
4 Likes
I’ve started in the second board to make it up to 12 notes poly.
7 Likes
Second voice board on test.
1. 74HC595 clk and latch pins swapped
2. All 74HC595 chips dead?
3. Gate pins of voices 1,3 and 5 on wrong pin
4. Some idiot installed 6 4053 chips instead of 4051.
5. Fault on voice 1 in high pass mode.
6. Two TL074 inserted the wrong way around, poof.
Other than that I can carry on to complete the LFO, noise, effects and output section.
6 Likes
Trying to decide between superb electronics or alchemy I settled on witchcraft. Superb as always.
2 Likes
Thanks, I’m making the most of things whilst I can still see the components.
1 Like
Latest update, finished the second board and fixed the filter issue with the first.
6 Likes
I see your crazy projects (crazy = 
) and have a serious question as I am struggling with that same question:
When you start a project like this one, have you like an idea what (sonic) effects you want to get and start your design from there, or have you like a diagram, the idea what components to put together and see what sounds you can create?
I have an idea what I want to achieve but struggling with a design (w(o using a computer).
I usually start with an idea for a VCO or DCO and develop that as a standalone project. It’s either another design such as the Hagiwo $9 DCO or my own from scratch. I think about it’s control, modulation, outputs etc and if it of any use in a synth build. Obviously when testing I’m listening for the tone and looking with the scope at the waveforms produced and how to improve functionality if possible.
There are many many core ideas out there that are far from useful as a module or synth core. For example the poly kit DCO was great, but missing FM and had other bugs, but after building one and modding it the core was suitable for use in a synth or as a module and the updates were fed back into the community. But this allowed me to go on and build the poly kit DUO, a 6 note dual DCO version with patch memory etc. For example the Hagiwo dco selected waveforms by pushing a button and cycling through them. I modified that to be 3 select lines to select 1 of the 8 available, later I made that a CC midi message for even less wiring
This current build came about after frustration of building what I thought to be a reasonable core by marcel-license of a super saw oscillator only to find it missing essential components like modulation and a bad library that made compilation impossible. Some of this has been fixed now but I just sat down with Claude and said let’s build a super saw DCO and expanded the features once I got the core running.
I tend not to document which is my biggest downfall, I find myself struggling to remember the schematics sometimes when finally putting things down on paper, but I manage.
2 Likes
A colleague had a great motto: A good engineer is a lazy engineer. I never invent stuff my self if stuff is available already, but I am into sequencers and here’s my challenge. I want a sequencer that circles through a reasonable long sequence but that little by little changes that sequence.
Also some kind of controller that slowly pans from one sequencers to another …
(Listening too much to Helen Vogelsinger)
Starting to add the parameter displays in, I don’t have one created for the arp so this is just a test one. It’s a copy of DCO1.
5 Likes
New display format
I’ve been working on new display layouts, encoders are great but don’t tell you anything until you move them, so I’m replicating the 12 possible encoders I can have for each section of the synth. These update over MIDI from the front panel editor and change colour depending if I’m on the lower or upper layers over the synth.
7 Likes
Pretty much completed the new parameter menus.
3 Likes
Your energy and fantasy makes me uncomfortable numb.
3 Likes
You know it’s getting serious when you do the artwork.
Creating the front panel design so I can chomp out huge chunks of aluminium in the front panel. This one’s a pain because front panel designer has a limit of around 1100 and this panel is 1158mm
7 Likes
This looks like an amazing project.
3 Likes
Lots of drilling and routing today and the front panel is finally fitted to the synth case. New panels printed out and laminated to reduce the glare. Starting to look like a real synth now.
9 Likes
