DSP Robotics Support

Further to a post over at Music-Society:

OB-2 - BEND - MOD mode.
Noise modulation on down bend: not implemented - or not connected?

Thanx for the tipps. I was able to remove those blue Vector knobs by your description.

Also be sure to delete the large, unused filter module inside the Filter - you may have to drag the window down to see it; be sure you have the Navigator strip showing at the top (check it in the 'View' tab on the toolbar).

I still cannot find that one, must be blind, I'm sorry. But their must lay the answer because the only unwanted parameters left, call "Filter-knob" now and that word is also there as some kind of a label in front of some correctly renamed parameters. Any chance for a screenshot?

The LFO2 rectangle is also back in place, oof

Updates here: https://drive.google.com/drive/folders/ ... sp=sharing

Too late for a screenshot - I already got rid of it.

Some OB-2 bugs pointed out at Music-Society (fixed) and I added a feature not on the Two Voice: Voice #1's oscs can be re-routed to Voice #2's filter, for processing big 4-osc sounds through a common filter.

Like the SEM Eurorack module, I added Saw to the LFOs.

Also tossed in the OB-1 manual.

https://www.dropbox.com/sh/94zkxdb9je9x ... IV5ja?dl=0
I'm sure we all appreciate you helping out with the automation fixes.

Working on the automation clean-up of tableBlend now, though I'm going to wait to do the oscs till Spogg's back from vacation in case he'd like to share his wave-sequencing for it so it works a bit more like Prophet 12.

k brown

OB-2 has been rather extensively up-dated with new features.

-OB-1 had env mod of VCO 2 only; OB-2 now has env mod (VCF or VCA) of all four ocs (like SEM Plus).
-Cross mod changed from switch to continuous control.
-Noise level changed from switch to continuous control.
-Saturation effect comes in when out levels go above 12:00.
-Feedback added to Filters.
-Voice #1's oscs can be routed to Voice #2's Filter.
-External input added to both Filters.
-Saw added to LFOs and Vibrato.

https://www.dropbox.com/sh/94zkxdb9je9x ... IV5ja?dl=0

k brown

tonus 2620 (ARP 2600) now should be Automation-friendly.

https://www.dropbox.com/sh/xt1xoykr2903 ... LkD0a?dl=0
Pretty proud of this one - beta-test away; this one deserves a good fine-tuning.

OK -

I don't have a clue about SM/FS (kudos Knob Twiddler for leaping in - brave, brave man! and Thank You!) but ...

... just launched the CM edition of SM (no, it doesn't open your .OSMs - I didn't expect for one moment that it would), and think I might have spotted something. (I won't take offence if anyone who actually has a clue points out that what I'm about to say is really dumb.)

The 2620 was probably the 'standout' of this outstanding bunch, for me, right from the start (so please, folks, test every last drop out of this one!).

It was also the only one (that I recall) that can only load patches, not banks.

I'm guessing this one lacks a module called 'Preset Manager'?

If so - can you please drop one in, give it a 'Total' count of 50 (like the others) or (even better!) 128 (the maximum number of programs for a VST bank - let's encourage all those talented sound designers out there to really go to town on this one!) and toggle 'Show In Parent' to off.

With any luck, this won't even 'break' any patches I try to make in the interim.

And if it turns out that what I've said isn't too dumb (beginner's luck!), I might even feel encouraged to dive in a bit deeper and see if it's worth getting FS (or at least the demo) so I can try to contribute in more practical ways (a la KT).

Oh - I almost forgot: Thank You!


** Edit **

In case anyone missed it: https://www.theguardian.com/music/2016/ ... es-aged-79

Thanks cakebox -

The Preset Manager was already in there; as I recall when I first started bashing about with SM (at first, the CM edition), exporting as vst isn't possible without the PM in there. I raised the max to 128. If you're using vstHost, I thought the internal PM wasn't being used. I know the saving and loading of .fxp doesn't use it, but maybe it's different with .fxb - I've never created any banks.

Intereseting that it wouldn't load the schematics, I thought the only limitation to the CM edition was that it wouldn't create schematics with more than a certain number of modules - didn't know it wouldn't open them either.

Will be curious to know if the change to 128 max allows you to do what you want.

https://www.dropbox.com/sh/xt1xoykr2903 ... LkD0a?dl=0


k brown

Amazingly - yes it does (imagine my surprise!).
Thank you.

SM-CM says your files were made with a newer version of SM. (Hardly surprising - the coverdisc version is dated 2007).

Perhaps one of the Buchlas next? Would be a fitting tribute.

**Edit**

What should the 2620's Parameters '#000' and #001' do?

Yes, I only started with Synthmaker CM.

I may do the Buchla called SystemOne D, but I'm inclined to wait on Music Weasel and the others till I can get some help from Spogg or someone with the sequencers and the random voltage modules. Anyone trying out a Music Easel emulation is going to expect a proper sequencer, and the step LFO isn't even close. I was praying that some Flowstoner had familiarity with the Buchla Source of Uncertainty and help out with a rough approximation of it; I know my attempt is a joke at this point, largely because there is so little info online regarding exactly what it does and how it sounds. The random sources in the Music Easel were much simpler and what I did in Weasel is probably somewhat close. SystemOne D doesn't have random voltage sources or a sequencer, so I'll do the automation fix on that.

I haven't been able to figure what's generating those #000, #001. Got the same thing in tableBlend which I just finished.

k brown

To Knob Twiddler:

I've freshened up the GUI a bit for b6, which I thought was a rather dreary-looking. This is the same color design as tableBlend. If you wouldn't mind replacing the back panel and module backgrounds with these, since I don't have FS and can't work on your automation fixed version. Just be sure they end up all the way in the bottom layer ('move to back') after they are pasted in; sometimes they don't always paste to the furthest back level and you have to 'send' them there.
Thanks,

k brown