Classic Synth Patches

[Siri]

ILIOand Reverb Machine have partnered to introduce a new patch collection series for the Spectrasonics flagship synthesizer Omnisphere. The Fame Series pays homage to famous synth sounds used in classic songs. The Fame Series shines the spotlight on hidden hits with stellar synth sounds, and makes them ready for use in your latest tracks. And since these tones are replicated from famous songs, they are designed to sit perfectly in your mix.

Reverb Machine is the work of Dan Carr, a London based electronic music producer, sound-designer and musician. After working predominantly as a live musician, he started exploring the world of synthesizers, sharing presets and sound design tips on reverbmachine.com. Topics include the synth sounds of popular artists, the generative music techniques of Brian Eno, and music theory. He also produces content for Reverb.com and is tentatively working on a debut album.

Spectrasonics Omnisphere is required for use and will need to be updated to at least version 2.6 prior to installation of this patch library. Registered users can update for free by logging into their Spectrasonics User Account.

I am going to roll out updates over the week so please play with them for like maybe an hour before posting that something does not work yet. but i have found several issues that are going to be fixed

1.) All synths will mute for 1.5 seconds while switching soundfonts

2.) Bug in SVF resonance squashed

3.) Scaling for SVF fixed

4.) Classic ADSR page replaces un-needed LFO/MODS generators page

5.) Reverb on/off and reverb [0-44] selectors exchanged, pan parameter will replace Preset selector for synths w/o multibanks

And as for a manual I will try to keep a running list of things you need to do. Most issues seem to be (when not a bug) that Organelle likes values to be initialized or else things are silent. Like turning on filters/ effects and it seems like when you load a new soundfont by pressing Aux button on page 1 or with a foot switch for the multi bank patches you need to select a preset before Sound will begin. Other than that I think most things are traditional Synthesis behaviors like filters and envelopes i am going to ask my friend Joe and see if he might like to make the online manual for the Vintage FLuidsynth Synths

So, I set page one to the preset # I want to save and then navigate to the menu to save the current setting in that preset spot? If so, how to I recall that preset? I tried simply setting the preset encoder to the same number, but nothing happened. Am I doing something wrong?

play with this one to tide you over

Dropbox Dropbox - Link not foundDropbox is a free service that lets you bring your photos, docs, and videos anywhere and share them easily. Never email yourself a file again!

Which iOS synth(s) would you say best emulate the sounds of certain "other" Classic Synths. (But not sample based player apps. They have to be actual synths with controls that work like the real thing.)

Now... learning to re-create classic synths from the great apps Zeeon, SunRizer, RippleMaker, the Moog, PPG and Korg is a great skill to have but me... I'd rather be playing because turning knobs is a different use of time.

Probably the best use of time is simply picking one synth and really learning what it can do:

program and play. I think all the Yonac's are also on sale right now and they are low cost powerful Apps.

My understanding is that it has a library of high quality samples for each synth and that it has some filters and modulators but that the filters are the same for all the synths.more ROMpler than synth.

I do have the free version of Syntronik and I think it's cool. But it frustrates me to look at the Syntronik interface showing all the classic synths, without the complete layout of the original controls for each particular synth. It just makes me want emulator versions even more.

Part of my interest in classic synths is nostalgia. The unique sound character those classic synths could create, and also all the "what ifs" involved of having the potential to "nuance" the sounds using the controls.

I wish I understood more about how iOS synths use code to model analog circuits. I've read in the past that what gave the OB-X its unique sound (in part) was a unique type of filter design. What I don't understand is how difficult it is to actually code the particular elements into an iOS synth to emulate those classic circuit designs.

I know the Moog Model 15 App, and a few other iOS apps, emulate a modular interface. I find this interesting because it means an iOS synth can have different sections that emulate particular types of circuit functions. But in the case of a modular interface, not all modules need to be used to emulate a sound. This must mean it's possible for the software to have capabilities that can either be included or bypassed.

If I could wish for an iOS synth. It would be one that contained the "capacity" for variety sections for emulating particular types of circuit functions. So in essence, all the sections required to emulate an OB-X, a Jupiter 8, or a Juno 60 are all included in the software. But the key element for this hypothetical synth's design, would be the ability to select different interfaces, containing the different sets of controls that you want to work with.

In other words, one iOS synth with a lot of capability like that of a modular synth. But instead of the all the modules being up front and visible on one interface. You can instead choose different interfaces that only include the set of controls that you want to work with.

So imagine you're after a basic Juno 60 type range of sounds. You open this hypothetical synth app, and tap on a tab that is labeled "basic synth". Up pops an interface that offers you a set of controls, and one oscillator like that of a Juno 60. Then in the same app, if you next want to work the a set of controls like that of a Jupiter 8. Tap the tab for that synth layout and then you are looking at two oscillators, and all the controls familiar to a Jupiter 8. Another tab can bring up a layout for an OB-X. As well as a bunch of other layouts as well. Not all have to be emulations of classic synths. They can be completely modern as well.

The idea is that all the functionality of a very complex synth is in there, but you can control how much of it is reveled and used in a particular interface, by selecting how much of it you want to work with.

But I think the idea of treating level of interface complexity similarly to that of selecting a patch. Might be a really good design, especially for those who are just learning about programing synths. or those who only want as many controls in view as they need for the particular kinds of sounds they want to work with.

This hypothetical synth ought to be particular useful if each interface used a similar layout in each of the complexity levels. Switching from the one oscillator synth interface, to a two oscillator interface, would keep all the controls arranged in similar sections. That way it's intuitive when changing layouts, as the controls you're looking for will be located where you'd expect them to be.

3a8082e126