Synthedit

Synthedit-modulesOpen-source SynthEdit Modules (SEMs) for SynthEdit 1.3 and higher.Notes on LicensingThe original source code provided here (all folders EXCEPT se_sdk3) is offered under the terms of the BSD 2-Clause License (see file LICENSE in this folder), which permits permits use in open-source, closed-source, and commercial projects under very liberal terms. However, the complete programs provided here depend on the SynthEdit SDK, and hence are subject to its license--see the README for the SDK.The SynthEdit SDK License is a modified version of the BSD 2-Clause License, which adds a third clause stating "Neither the name SEM, nor 'Music Plugin Interface' nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission." This does not prohibit or even restrict distribution of compiled SEMs; it only addresses how they may be endorsed or promoted.Notes on Distribution of VST plug-insSynthEdit itself is most commonly used to create audio plug-ins which adhere to the Virtual Studio Technology (VST) standard. "VST" is a registered trade mark of Steinberg Media Technologies GmbH, which imposes much more rigorous licensing terms on distribution of VST plug-ins. Refer to the Developer section of the Steinberg web site for details.Finally, note that Steinberg will no longer be issuing licenses for distribution of plug-ins according the older VST version 2 ("VST2"). See this important page on the SynthEdit site for details.

Plugins The SynthEdit Music Plugin Standard (SEM for short) is an advanced API for MIDI and Audio plugins. SEM Version 3 is a clean modern API designed for power and simplicity. SEM is easy to use yet more powerful than other plugin standards. SEM V3 is supported in SynthEdit Version 1.1. Download SynthEdit 1.1Currently in beta testing. Download SEM V3 SDK SDK Version 3 Documentation Getting a Compiler 3 Compilers have been tested with the SDK: Microsoft Visual C++ The SDK was written using this compiler. The Visual C++ Express version is free, but requires you to download Windows Platform SDK yourself. Also cheap for Students is the Academic version. Shop around to get the best price. Gnu C++ Code::Blocks integrated development environment. This is good, free, modern compiler. See Using Code::Blocks with SynthEdit tutorial. Borland free compiler This compiler is too old now, it does not work with this SDK. Code generator To help convert your modules to the new SDK, SE includes a simple code generator. On your existing module... Right-click->Build Code Skeleton. This creates the template code for your module in the folder "C:\SE\My Projects\modules_source" - you need to create that folder first. The template doesn't do any processing, it's just a non-functioning module with the pins and module-name etc. setup for you, to save you typing the boring bits. NOTE - SE SDK3 does not yet support GUI DT_ENUM pins. Avoid upgrading any modules with those. Processing // Process audio.void Gain::subProcess( int bufferOffset, int sampleFrames ){

With the RangeMinimum/Maximum settings. Except this flag goes on the Sliders output pin. It indicates to SynthEdit that when you connect the Slider's output pin, the slider should be initialised to the destination pin's default value, and the Minimum and maximum range should be set to suit the destination pin. parameterId parameterField{ Value, writeable only in SynthEdit environment -ShortName , MenuItems,MenuSelection,RangeMinimum,RangeMaximum,EnumList,FileExtension IgnoreProgramChange,Private,Automation,Automation Sysex,Default,Grab,Normalized } metadata - For audio pins the format is ",,40,0". When user connects a slider, the sliders minimum and maximum travel is automatically set. In this example min=0, max=40. SynthEdit does not enforce these limits, the user can override them. Only valid on input pins. The first two blank values are depreciated and ignored. notes notes hostConnect{ PatchCommands, MidiChannelIn, ProgramNamesList, Program, ProgramName, Voice/Trigger, Voice/Gate, Voice/Pitch, Voice/VelocityKeyOn, Voice/VelocityKeyOff, Voice/Aftertouch, Voice/VirtualVoiceId, Voice/Active, VoiceAllocationMode, Bender, HoldPedal, Channel Pressure, Time/BPM, Time/SongPosition, Time/TransportPlaying } Voice/Active To save CPU SynthEdit suspends processing on unused voices. This can lead to a problem when the module is 'woken' to play a new note - it's inputs may have changed while the module was suspended. This can be due to the user changing patch, or because an LFO or envelope feeding the module has changed while the module was inactive. From the module's point of view, it's input has 'spiked' or 'stepped' suddenly, any kind of filter in this situation will ring for a short time before it settles. This is quite noticeable in SE synths with resonant filters as a click on the next few

The 'hostConnect' part. When the keyboard2 wants to set a voice's pitch, it transmits the new pitch out that pin. The host receives that signal and acts on it. Another example - loading a fxb bank: - Put an DT_INT pin on your GUI Module. - specify - hostConnect="PatchCommands". - Valid commands are: 0 null 1 CopyPatch 2 LoadPatch 3 SavePatch 4 LoadBank 5 SaveBank To initiate a bank load. Set your pin to 4, then back to zero (ready for the next command). SynthEdit will display the Bank-Load dialog box, then load whatever bank the user selects. Windows 2000 users To enable runtime support for Visual Studio V8, you may need to download these dlls: MFC80U.DLL MSVCR80.DLL MSVCP80.DLL. Put them in C:\Program Files\SynthEdit\ DEV C++ Compiler Notes Install DEV C++, Install gcc V4.1 (or better) from Tools menu. 3.4 don't support templates very well. File, New Project, DLL, Add module files (Gain.cpp, Gain.h) Project-Project Options - Directories - Include Directories - Add se_sdk3 folder Release updates to your module You may need to release an updated version of your module with more features. Your users will have SynthEdit projects created with the older version. Changes to your module can cause those existing projects to crash. There are some guidelines you need to follow when adding or removing pins from an existing module. RULE 1 - The worst thing you can do is: Remove a pin. Add a new pin using the same ID, but a different type or direction.