alpha

This is the unfinished development version of SynthEdit. It is somewhat unstable and may crash. Please back up your SynthEdit projects before trying the preview. . The new GUI is far more demanding of your graphics card as it uses gradients, curves and drop-shadows. I would appreciate your feedback especially regarding the performance of the new GUI.

Important: First un-install any existing Preview (alpha) version using the Windows Control Panel Add/Remove Programs screen.

Download SynthEdit 1.2 Online install (6.5 MB)

Notes:

- With SynthEdit 1.2 modules (SEMs) are stored in two locations:

  • C:\Program Files (x86)\SynthEdit 1.2 Alpha\modules - Modules shipped with SynthEdit only.
  • C:\Program Files (x86)\Common Files\SynthEdit\Modules - 3rd-party add-on modules from other vendors. Please copy your 3rd-party modules here.

Don't copy SynthEdit's own SEMs to the common folder (the ones already in C:\Program Files (x86)\SynthEdit 1.2 Alpha\modules. If you are using SynthEdit 1.1 alongside Version 1.2, leave your existing module folder as-is. Version 1.2 will not access these.

- This version does not scan for new modules at startup. This makes SynthEdit start much faster, but you will need to "Re-Scan Modules" from the preferences screen whenever you add new modules to your collection.

- If you are using an earlier version of the Alpha you may experience a crash on start-up. The fix is to delete the module cache file. This is a hidden file.

  • Vista/Win7 - C:\Documents and Settings\All Users\Application Data\SynthEdit\Plugin-Cache
  • XP - C:\ProgramData\SynthEdit\Plugin-Cache

3 - If you still experience crashes at start-up this may be caused by a problematic module. Temporarily move your modules folder elsewhere. Then try starting SynthEdit again.

Know Issues:

  • Tooltip Hints do not work on controls within the Structure Window. They do work in your saved VST Plugin.
  • Clicking within text boxes within the Structure Window does not highlight the text correctly.
  • On screen MIDI Keyboard don't respond to key presses.

Oversampling

Known Issue: Some 3rd-party Oscillators share common data. So If you load two instances of your synth, oversample one but not the other - then one of the Oscs will play the wrong pitch. Solution: Oversample ALL Oscs.

Known issue: Control signals going into an oversampler can devlope a 'ripple'.  This is due to the upsampling process, you can minimise it by using stronger oversampling filters (more poles).