my first synth

RunBeerRun2 · 14 Apr 2012

Hi, I noticed when I turn on polyphony, the cpu goes way up. I suggest checking out the WIKI page here, it basically shows how the end of the circuit goes with clipper and poly to mono, it took my synths of 30% cpu on a dual core down to 6%.

richyspitz · 15 Apr 2012

thanks ill look into it,i started off making it as a mono synth but added the poly option in after, there's still a few things i need to learn about this software, i only started using it this week. one thing i couldnt work out is how i can automate the synth when im in a daw, is there a module i need for that?

trogluddite · 15 Apr 2012

richyspitz wrote: automate the synth when im in a daw, is there a module i need for that?

Hi there, To get VST automation your schematic will need a "Preset Manager" module from the toolbox. This handles all communication with the host, including automation as well as preset handling (so that your DAW can remember the settings in your song/project files). Most knobs/switches etc. from the toolbox are already set-up to make use of the Preset Manager - but there is one important thing that you must do... Open up the "properties" for each control, and edit the "Preset" box to give each one a unique name (these are the names that your DAW will use for automation control tracks etc.). If any two controls have the same name, it will confuse the host, and presets/automation will be "buggy". There are "preset" and "auto" boxes in the properties so you can choose which controls are rememebered (preset), and which can be automated (auto) - and you can also tick the "MIDI cc" box and enter a controller number if you want your controls to respond to MIDI from knobs/sliders on a control surface or keyboard.

richyspitz · 15 Apr 2012

thanks thats helped me out alot

DigiBot · 18 Apr 2012

trogluddite wrote: richyspitz wrote: automate the synth when im in a daw, is there a module i need for that?

Hi there, To get VST automation your schematic will need a "Preset Manager" module from the toolbox. This handles all communication with the host, including automation as well as preset handling (so that your DAW can remember the settings in your song/project files). Most knobs/switches etc. from the toolbox are already set-up to make use of the Preset Manager - but there is one important thing that you must do... Open up the "properties" for each control, and edit the "Preset" box to give each one a unique name (these are the names that your DAW will use for automation control tracks etc.). If any two controls have the same name, it will confuse the host, and presets/automation will be "buggy". There are "preset" and "auto" boxes in the properties so you can choose which controls are rememebered (preset), and which can be automated (auto) - and you can also tick the "MIDI cc" box and enter a controller number if you want your controls to respond to MIDI from knobs/sliders on a control surface or keyboard.

[[But there is one important thing that you must do... Open up the "properties" for each control, and edit the "Preset" box to give each one a unique name]] arrrhhhh Super dupa Mr Trog 😉