DSP Robotics Support

Hi K Brown

just a heads up, I was playing around with a few of your synths, very nice! run into a little problem with the Goom! the knobs gui are not updating in realtime, while the knobs work they don't update and move to the position you set them to until one clicks the workspace outside the plugins window! some sort of redraw issue!

nice collection though

Regards!

Must be an iissue with your host - i can't duplicate the behaviour with vstHost or Tracktion.

Hi K Brown,

it is in Flowstone itself i was getting this, i haven't tried the plugin yet!

I only have Synthmaker, so someone else here will have to help.

In other news - updates to TriGoom, CS-358 and 80-vox. In all three, each oscillator now has the ability to FM itself (no jokes, please). Specifically, the Tri wave can phase modulate the Sine wave.

I realized TriGoom has a pretty heavy CPU load, so I did an alternate version (TriGoom b, in same folder) that has about 1/3 the hit. Had to sacrifice a couple of features: the oscs' self-FM (has nasty artifacts with the wavetable oscs used) and Waveform Modulation (zippers badly when done with WT oscs).

Martin Vicanek has made some great very low CPU oscillators but in Flowstone of course.

Another reason to get FS Mr Brown, so speak to your wife, speak to her of the importance to you to satisfy your many fans...

I'm away for 2 days now but soon I can try to copy his code into SM ASM boxes and see if they work in OSM format.

Cheers

Spogg

During my brief Flowstone trial period, I did copy over Martin's Saw and Sine oscillators, but two problems - two of the Saws can't be used to make a Pulse osc, and neither of them has Sync inputs.

To Spogg or anyone else who may be able to help - it's come up at Music Society that the Step LFOs' controls cannot be mapped to a midi controller. My assumption is that this has to do with the fact that the 'sliders' are not actual individual controls but part of a single module. Does anyone know if someone ever built a Step LFO whose controls can be midi controller mapped?

Also, to all: in general, if something appears to be not be working right your first step should be to re-download it from the master folder because I often go through these and find errors or make improvements, but don't litter the forums about every single 'fix' - your issue may have already been addressed!

Another Yammy - this one based on a pretty obscure model, I believe the last analog Yamaha put out just before the DX7, the CS-70M. Personally I think these last CS polysynths were pretty unattractive, so did it up in CS-80 livery.

Yumaha CS-75M :




I added the ability of each Channel's Sine to FM the other; the depth being controlled by the Filter EGs. Also more waveforms, extended 'Footage' ranges and filter keytrack which the CS-70M inexplicably lacked.
Probably it's most interesting feature was it's dedicated Wheel/Aftertouch LFO in addition to the main LFO. The main LFO's controls are a bit unusual, so be sure to read the 'Info' box and maybe refer to the included CS-70M manual.

k brown wrote:To Spogg or anyone else who may be able to help - it's come up at Music Society that the Step LFOs' controls cannot be mapped to a midi controller. My assumption is that this has to do with the fact that the 'sliders' are not actual individual controls but part of a single module.

I looked into this, using Reaper DAW.
Your CS-358 has correctly named preset parameters for each of the 16 sLFO sliders. These happen to be stored in an array but show up correctly in Reaper when you turn off the plugin's GUI. You get 16 parameter sliders, one for each step. The next thing to do would be to use Reaper to assign a MIDI cc value to each step-slider. In Reaper you can even create an alias for each parameter. Then the external MIDI controller can be mapped onto each or any step you wish. In addition you can create automation for any named parameter, including the 16 sLFO sliders. Naturally the GUI won't show the sliders moving but the parameters will be modulated. The plugin's Preset Manager handles all the dialogue.

I only use Reaper (it's brilliant, well supported, frequently updated and cheap!) so I can't answer for other DAWs.
For Reaper you can find instructions and info on their forum, via Google, regarding mapping and automation.

Cheers

Spogg