Real-Time Touch Controller for the Yamaha DX7 Synthesizer
spectralplex.com
spectralplex.com
I've always suspected this actually influenced the electronic music styles of the time. The 90s were the start of the analogue resurgence. Sure, an 808 or a 303 is a fabulous-sounding beast in itself. But twiddling knobs is just so much more rewarding and responsive than spending hours squinting at a two-line LCD.
I believe bringing that flexibility to a digital synth is a good thing. I imagine that there could be ways to create a modular 'control panel' and with the help of an embedded compute (as suggested in the article) provide rapid mirroring to the synth. I am a bit surprised that isn't an 'addon' already :-)
I agree that modular are much more rewarding as you really can just tweak knobs (or have the machine tweak its own knobs in stragne ways)... that's really what I prefer.
To my ear, it never quite had the smooth richness of sound that, for example, the SH-101 had (manually tweaking the cutoff always seemed to generate some aliasing clicks), but it still gave great tweakability.
The DX7 was designed to be a gig-able synth that anyone could throw in a car and set up on their own. It was a brilliant success because you had good-enough epiano and other stock sounds in a package that was far more portable than a real epiano, clav, basic poly, etc.
This was purely a cost/weight issue. The hardware required for one-knob-per-function would have doubled the weight and probably tripled the cost.
E.g. a company called Jellinghaus made a full-sized analog-style programmer and it was bigger than the DX7.
https://www.matrixsynth.com/2008/01/jellinghaus-dx-programme...
People like analog synths because they have a very simple programming model that only makes a relatively small range of sounds, most of which sound good more or less by default. You trade immediacy against sophistication.
The DX7 etc went the other way, which infuriated musicians used to those analog sounds, but created an entire support industry of sound designers and libraries.
If you want a tactile UI now you can create one on an iPad. The surprising thing in 2019 is that synth designers still haven't fully explored touch screen interfaces, and are mostly just recycling ideas from 30 years ago.
Obviously your meaning was toward "customisable UI", which tablets are. I use one as a daw.
If you want a tactile UI, get a Yamaha Reface DX[1]!
It's amazing how much fun you can have with an FM synth with a couple of sliders that allow you to change the sound as you play it.
I can write love odes to that machine.
[1]https://usa.yamaha.com/products/music_production/synthesizer...
However, DX7 works as both – it was both used as a source of very innovative sounds, as well as a simple preset-driven keyboard for many, many pop musicians who seemed to never have used anything but built-in presets.
Well and they sound completely different.
The UI differences don't come down to number of controls but the fact that most analog designs have a 1:1 relationship with the sound, every knob you turn has a very distinct impact on the sound and usually, applying that to any input generates more or less the same impact on the output. It's extremely intuitive to learn how changing a knob changes the sound.
FM is completely different, where altering simple things like the operator ratios and modulation index have massive changes on the sound and don't create the same effect on different sounds - it's naturally non-intuitive. Most FM wizards get there through tons of experimentation, not through established fundamentals.
Imagine playing a wind instrument and changing your embouchure alters the pitch of the differently depending on what note you finger. That's what programming an FM synth is like.
iPad synths are a dime a dozen these days. Lack of a physical interface is as big a problem on them as with larger synths. They are hardly tactile.
A corollary here is the success of wavetable synths compared to granular, additive, and FM in the softsynth space. Wavetables have the same subtractive model as traditional analogs, and incorporate many of the same features as semi-modular synths. But they are extremely versatile because of how their interface is intuitive even for first time users - it's stupid easy to change the sound, the only additional dimension is the wavetable but that's quick to pick up. Compared to say, granular synths which are possibly the most versatile paradigm, but whose controls are extremely divorced from the timbre of the sound you design.
I buy broken DX7's and restore them back to 'as good as possible', I've seen some DX7's that still worked but didn't have a lick of paint on them from all the throwing around. They're built like tanks.
There were monstrosities like the PG-1000. Basically, 56 sliders in a separate box which you could plug in to the D-50 (or D-550) to program all of the parameters at once with a physical interface. I think it sucks. I still have my D-550 and I’ve seen the PG-1000s go past at the stores for good prices.
In a short time, synths went from having a handful of parameters to being complete monsters and it took a while for the UI to catch up. The Korg Poly6 from 1981 has 22 knobs, Oberheims aren’t far off, but the DX7 has something on the order of 100 parameters. I think it has 7 envelope generators and each EG is about twice as complicated as an ADSR.
There’s basically two viewpoints on the DX7 on forums, from what I can tell. One viewpoint is that you would do your programming for the DX7 on a computer over MIDI, and with such a setup you could unlock the true potential of the device—or at least tap into the thousands of presets available online. The other viewpoint is that most of the presets online are garbage or duplicates, and you only want a DX7 for the handful of classic presets it had like Full Tines.
I recently dived in a bit deeper. For the JS13K demo competition last month, I wrote an audio synthesis engine in JavaScript that let me write audio programs in Lisp, and this engine could replicate some of the DX7 sounds. I also own a Yamaha TX-802 (basically rack-mount DX7mkII), so the techniques were familiar. I went through the TX-802 library and various presets I found online and dissected them to try and build my own sounds for my JS13K game.
(Skip to here if you only care about UI.)
My conclusion is that the DX7 UI is only part of the problem. FM synth programming is not remotely user-friendly and it won’t be. The problem I found was that it was often very narrow ranges of parameters that would sound good or meet your needs in a particular patch. I spent hours tweaking modulation levels. I would mute one operator chain, tweak modulation and envelopes on the other one, then switch and continue. Changing frequency ratios had an even bigger effect.
This is in contrast to subtractive synthesis, where it’s fairly easy to dial in a frequency cutoff for your filter.
I think the problem here is that once the modulation level gets too high, the level of the fundamental starts dropping, and it happens very quickly. FM modulation levels have a very narrow range from “enough modulation that it sounds interesting” to “too much modulation and it sounds like garbage”.
So my personal opinion is that the DX7 is still gonna be a pain to program even with more knobs. YMMV. I happen to own a TX-802 and programmed my own FM softsynth.
Yes, FM programming is surprising in that way.
On some patches, the range of "sounds different, but good" values is larger. On others, a small change, and your glorious soundscape descends into early 90s videogame sound or to metallic screeches crazy fast.
Still, the Reface DX does an admirable job of making FM programming enjoyable and fun. As you said: there's no point in change all of the parameters at once, you end up going operator-by-operator. I think the Reface DX offers a great balance UX-wise.
If it weren't for the DX7 I would have stayed in the classical instrument stream and done a music degree. I wouldn't be on HN today.
So, it's great that people are still applying new tech and gizmos to the DX7. It's got a special place in my heart.
It's the new life of a DX7. Still FM, but something you can bring to a campfire. Or a party. Or to the office. Always at your fingertips.
I never leave this thing at home; it's either in my car, or my backpack.
https://usa.yamaha.com/products/music_production/synthesizer...
The reason FM synths need to be digital is that very precise pitch ratios between oscillators are important in order to get good sounds. For example you may want to modulate the pitch of one oscillator with another exactly a fifth up (3 to 2 frequency ratio). It can easily sound terrible if the fifth up oscillator goes slightly out of tune.
These sort of precision and nonlinearity in output are also one thing that makes FM synthesis a lot harder to use.
That was my first thought. And actually, I kept trying to understand (from the article) how exactly this UI makes FM programming easier. Does it? Or is that not the point?
Because one of my "sound designer dreams" is being able to get the sound in my head coming out of the machine using FM. I can do that with regular subtractive synthesis (more or less) but with FM, I feel like I'm twiddling knobs until I like the way it sounds. And that's with a really good interface!
However part of the challenge of this would be in covering numerous combinations and identifying places where two or more parameters need to be changed simultaneously. Still basically a problem governed by combinatorial constraints.
It didn’t help that in the 90s when I had that keyboard they’re weren’t many online sources of info about it..
The dx7 was neat but couldn’t make very realistic instrument sounds. Very popular though.
But there are some exceptions, e.g. Autechre are well known for using the similarly flexible MaxMSP. As Sean Booth said in an interview with Resident Advisor[0] when asked about new equipment:
"I just use MaxMSP now, because in Max I can generally build the thing I need, and if I don't know how to do that it'll generally be worthwhile learning. Intellectual capital or whatever. So rather than spend me money on equipment, I spend me money—as time—in learning how to build stuff."
Because there are a ton of alternatives to CSound.
I use Max/MSP. But you could also use PureData, SuperCollider, Chuck, JUCE, etc.
Compare a CSound IDE to something like the Ableton Operator interface or even PureData as someone else mentioned. Very different (and both great for different approaches and people!). A lot of folks want flexibility in the sound by exploring an interface/instrument without having to come up with that interface/instrument themselves.
I mean, I can put stuff into WordPress with SQL directly, but it's much nicer to do it with an interface.
Similarly, I can program a snare sound using a noise generation, an envelope, and a filter, but it's sometimes nice to grap a box and it a button even if I'm constrained by whatever filter and parameters are already in the box... because the interface will dictate a lot of how I use the tool, and that is a feature not a bug :D
Simple example - Chebyshev polynomials. How many Csound users even understand that these will alias if they cross Nyquist?
So Csound does a lot badly. It's not quite unusable in a commercial setting, but the sound quality is a long way behind even basic VSTs - which means the steep learning curve and 1960s-style programming system don't justify the benefits.
Supercollider has similar issues. The control language is more interesting, but the synthesis and processing code are similarly unrefined.
https://asb2m10.github.io/dexed/
Personally, I'm a synth nut and Dexed is my go-to when I'm in the mood for FM, but I prefer good old subtractive synths over FM most of the time.
The fact that it's running a DX7 series synth is simply because I wanted to see how much easier it would make a synth to operate, so why not try it out on the one with the scariest reputation, a DX7. The result was much more than I had bargained for, it actually made it a fun instrument to play with. Of course, it could operate about anything that can be digitally controlled.
I wanted to use capacitive-type touch sensors, but the problem with touch technology is it's sensitivity to ambient electrical noise, which can wreak havoc with the sensing signals. So I designed a variation that ignores electrical interference. This lets it be responsive & reliable; no lag, ever, giving it a more natural feel in use than you'd expect.
In other words, you start with a recording of the sound you're after and then just start brute-force iterating through the parameter choices until an analysis of the output looks close enough to the input?
I mean, fftw3 takes about a full minute on my Chromebook to measure the quickest algo. So I'd hope that generating output analyses would be fairly snappy...
An Aphex Twin collaboration, naturally
As an added bonus you get a very capable sequencer and it can act as a groovebox on its own for quick sketches.
The DX7 is one of my favorite synthesizers in history, and its software successor, FM8 [2] by Native Instruments is my favorite synthesizer that I regularly use. As with many of the 61-key workhorse keyboards of the 80s, the DX7 is extremely solidly built and has excellent synth key action which makes it a joy to play. It's not weighted, but it also doesn't feel like a toy, and the velocity range (while oddly bound to 0-100, one of its few unnecessary flaws) is very playable throughout the entire range. Beyond that, the DX7 as a synthesizer is technologically a legendary synthesizer that contributed heavily to 80s and 90s music [3][4]. It had great presets, the most recognizable of which is the default patch which is it's rendition of a Rhodes piano. Many folks bought it for that purpose, and you'll that patch in many songs that you may recognize.
The DX7 uses a type of synthesis called FM synthesis, which (sort of like FM radio encoding) allows any of its 6 operator oscillators to be used additively or as an operator which feeds its signal to one or many other oscillators, potentially in a cyclical manner. Operators can use frequency multipliers and dividers with base oscillators (I believe only sine waves for the DX7 although there's a fair amount more in FM8) so that you can have operators sound harmonically many octaves above a base oscillator, or vice versa. In FM8, you can use multipliers anywhere from 0-64 with a 0.001 resolution. Through careful usage of envelopes and oscillator feedback structures, you can go quite a bit beyond your usual virtual analog style subtractive synthesis. but you can do quite a bit of semi-realistic physical modeling and beyond, whether it be orchestral instruments, drums, or punchy cartoonish caricatures of either. It's easily the most versatile form of non-sample based synthesis I've ever found.
The wonderful thing about FM8 is how intuitive and flexible the synth gets once you begin to get used to it. The envelope editor makes it straightforward to create arbitrary stage envelopes with the curvature of each stage customizable and really straightforward to visualize. I personally lean on FM synthesis so heavily for a variety of reasons. It's a taste thing, but it's also a matter of practicality. If you're judicious about patches you use, it's easier to tune FM instruments to make them take up less spectral space, and clash with other elements in a mix without extra post-processing. Additionally that they tend to be quite CPU light, so the number of distinct instances you can run in realtime without maxing out your CPU is a fair amount higher than hefty virtual analog synths like Massive (it may potentially be the same for Spire). Finally, when it comes to soundscape design possibilities, long envelopes and frequency modulation open the door to ambient shape design that is borderline impossible to do otherwise. I believe this is why the DX7 became Brian Eno's favorite synth [4].
FM8 is not free (although it and Komplete were some of the best investments I ever made in my music) but there are a variety of free DX7 synths out there that you can use, some of which are compatible as editors for DX7 SysEx patches. The one I'd recommend is Dexed [5], which is open source and pretty nice, because you can use it with the giant free DX7 patch ecosystem that's built up over decades. Give that a go with REAPER (trialware), LMMS (open source but a little hard to use with VST/AU plugins), Live (evolving and likely the best for professional musicians to create on), or a DAW of your choice and you're in business. Which reminds me, I have a track I need to finish...and based on my commentary, you can probably accurate guess whether there's at least 1 instance of DX7 on it.
[1] https://www.youtube.com/watch?v=O3PGO_DiuYU
[2] https://www.youtube.com/watch?v=lx_L9dPIa78
[3] https://reverbmachine.com/blog/exploring-the-yamaha-dx7
Frist, it is a DX. While the architecture is not identical to the DX7, it is a 4-OP FM synth with feedback on each operator, which gives it a huge tonal range.
Second, the UI is great. And yes, there are 4 realtime controls that make it easy to change the timbre of the sound as you play it.
But the most important part is its compact size and built-in speakers. I've brought the Reface DX to campfires, into the desert, on an airplane, to the top of a mountain, on hikes, to the beach, to the office. I jammed with strangers in the streets of Madrid. With me, I bring cheesy 80s music (FM was all the rage back then), jazz (the e-piano sound on the DX just cuts it), and whatever else I want.
The main question I think about is whether I want to grab it or one of the volcas. When it comes to live jamming, it's likely that a groovebox is closer to my cup of tea.
My next-size-down setup is an Akai LPK25 controller running into the cellphone (running an FM synth, for example).
I wonder how much those touch sensors cost, because I'm sure it could quite easily be used as generic MIDI controller.
A very early prototype got hooked into a theatrical lighting system, just because. I only had it wired in for a few minutes, the guy that did the lighting design for that theater really, really, wanted me to leave it. The ability to be able to be so interactive with the lighting appealed to him.
As to cost, the sensors themselves would be dirt cheap to mass-produce, the most expensive part would be the display. This one uses discrete LEDs, but I think an old-style, low-res, low cost monochrome LCD would be plausible, allowing more sensors in the same space, and a alphanumeric for labels & such. Most of the circuitry could be replaced by a simple microcontroller, it doesn't require any high-power math or signal processing.