LinuxMusicians

Yes, that works, rghvdberg. Thank you!

tl/dr : windows plugins on LM forum is a good thing.

Bit off topic:
I 'compete' in the One Synth Challenge on kvraudio.com.

Mac users : I can't use this, it's Windows only!

Windows users : 32 bit? I'm on 64 bit ... (buys jBridge $15) ... This makes my system unstable / crash etc

Me: I use Linux. Windows plugin? No problem. 32 bit? No problem. 64 bit? No problem. Runs just about everything
Oh, and for free...

Cannot say Linux is better, but I can say it's waaaay more flexible / diverse.
And I think that's the best way to promote it. Show the world that it just about can do anything you want.

One of my fellow OSCers has installed Qiana Studio and after I helped him set it up spent hours just tying apps together with Jack. He said a whole new world had opened up.

I wasn't saying windows plugins here is a bad thing, I use some myself. It's just very rare to see such a long thread dedicated to them, I'm not even sure native u-he plugins got this many posts. I was just curious as to why these ones, why not melda, fabfilter, VOS, etc.

sysrqer wrote:I wasn't saying windows plugins here is a bad thing, I use some myself. It's just very rare to see such a long thread dedicated to them, I'm not even sure native u-he plugins got this many posts. I was just curious as to why these ones, why not melda, fabfilter, VOS, etc.

Because the actual dev or maintainer or just someone involved with the project actually came to our community and has been posting. I understand why most devs wouldn't bother but its great to have somebody participating here. I'm sure any company could generate a similar stir should they show up.

ssj71 wrote:

sysrqer wrote:I wasn't saying windows plugins here is a bad thing, I use some myself. It's just very rare to see such a long thread dedicated to them, I'm not even sure native u-he plugins got this many posts. I was just curious as to why these ones, why not melda, fabfilter, VOS, etc.

Because the actual dev or maintainer or just someone involved with the project actually came to our community and has been posting. I understand why most devs wouldn't bother but its great to have somebody participating here. I'm sure any company could generate a similar stir should they show up.

It's nice to see devs on the forum
Also, would be cool if k.brown setup a git repo for his plugins.
git pull .. new plugins yay!

Also, if we keep pulling him in here on the forum, he might one day release native linux versions. You never know

Also, also
Just learned about https://www.darlinghq.org/ i.e. wine for mac
so maybe one day we'll run au plugins

also, aslo, also

linux is cool

Sorry to crush anyone's hopes, but if anything native Linux is even possible with these it will have to be done by someone else. I'm not a developer (I hope I didn't give that erroneous impression) - just a hobbyist dunce who's spend way too much time dorking around with Synthmaker. I don't know code from nuclear fusion. I included the raw Synthmaker schematics in all these folders so someone more awesome than I can do something more with them. Beyond finishing the parameter-naming to make them compatible with DAW automation, I don't plan on doing anything further with them. My initial hope when casting the whole lot out to net, was that some Flowstone master might find something worth developing further. So far that hasn't happened, so it's unlikely it will.

I just hope someone's having some fun with them as they are.

Your plugins are fine, k brown. I like several of them.

I don't think it's reasonable that we demand from developers that they make native Linux plugins. It's not where they get most of their money and/or recognition. The Linux community has built a pretty nice bridge with Wine and Airwave, so I really think we should just shut up and enjoy the privilege.

If I were to ask anything from a developer, it would be that they test it with Wine and Airwave, and perhaps whatever DAW they can get their hands on. Let's say, Ardour at the least. And of course fix it in case it doesn't run. But even that is usually a tall order.

Lots of good suggestions here that I agree with 100%. :thumbs:


brian

k brown wrote:Sorry to crush anyone's hopes, but if anything native Linux is even possible with these it will have to be done by someone else. I'm not a developer (I hope I didn't give that erroneous impression) - just a hobbyist dunce who's spend way too much time dorking around with Synthmaker. I don't know code from nuclear fusion. I included the raw Synthmaker schematics in all these folders so someone more awesome than I can do something more with them. Beyond finishing the parameter-naming to make them compatible with DAW automation, I don't plan on doing anything further with them. My initial hope when casting the whole lot out to net, was that some Flowstone master might find something worth developing further. So far that hasn't happened, so it's unlikely it will.

I just hope someone's having some fun with them as they are.

Nah man, I was just trolling a bit.
Keep up the good work!

Well, though jbuonacc over at KVR certainly could have gone about it in a less nasty and more specifically helpful way, in going back over his remarks and listening to the examples he posted it seems the big issue is how these act at too-high filter resonance settings and/or with feedback applied (I kept thinking to myself - well just turn the damn resonance down!) - I suppose it's a reasonable expectation that a synth shouldn't choke like that under any conditions. It never struck me as a big issue because I personally don't care for the sound of high filter resonance - that quacking duck sound; so since I don't use the synths that way (and I built these initially only for my own use) I never labored over how to prevent that behaviour.

The feedback issue I was more aware of, but I just thought the thickening of the sound one can achieve with it was worth having to 'baby' it to keep the filter from choking. But I guess for general public consumption, people expect a more 'bullet-proof' behaviour; fair enough.

I think my big initial mistake was not being more clear that these were not polished, fine-tuned products of an expert synth-coder, but just some stuff I knocked together in my spare time over the years and I just thought others might get some use out of them. My fervent hope when initially posting them at DSPR, was that one of the Flowstone gurus over there might find one or more of them interesting enough to take it further with their additional expertise and 'finish it up' for all to benefit from. Aside from some initial cleanup by Spogg over there (thanks), so far that `has not happened. The whole reason the .osm Synthmaker schematics are included in the folders is so someone might say "hmm, this one's interesting; needs some fixing - let's see what I can do", then share the result with everyone.

The other thing jbuonacc was experiencing was internal clipping, and I'm guilty as charged there - I didn't pay enough attention to gain structure. As a long time audio engineer, It's just second nature when I hear something clip, I turn down the thing in front of it. Again for general public, that should be less necessary.

So - I've gone back into a bunch of them and hopefully addressed some of these issues. My applogies to anyone whose made a bunch of presets for any of them - the changes may make them unusable in some of the new versions (most should be OK).

So far I've done:

80-vox
Atticus
Cassini
Chorg 770DV
cutOats
CyRinx
eXpando
Joker
Kroma Duette
Luge
M
minimodular
mOdyCat
Multipoly
Mx-Jr
Nebula
OatsFM
OB-2
Rolend Block-8
Rolend Cronus
Rolend JP-680
Rolend PG-238
Rolend SH-12
Rolend SH-57
Rolend SH-75
Rolend 101M
Syntha-kon
Synthegrated 12A
Synthegrated 15A
System One D
System One E
tableBlend
The Dodeca 258c
The Putnie

Personally, I don't think any apologies are in order here. There are other synths out there that are pretty "untame" and as long as it doesn't cause the speakers to blow out, it's all part of the fun. There is a dose of responsability required when using instruments like that though. They can be quite powerful!


brian

Finally got Synthy P (based on the very rare EMS Synthi Professional) param-named (and a visible Preset Manager), in the process did a major re-vamp (mostly error-corrections ;-] ) and an alternate version that has a single ADSR, like the hardware. Oscillator three can toggle to a step LFO.
The alternate version is now called Synthy P; the earlier one with seperate VCF and VCA EGs now called Synthy P_2eg.

The Preset Manager appears at the bottom; I just didn't include it in the screenshot.

Here's one that wasn't in the original Bundle because it wasn't finished yet. Inspired initially by the DIY hardware synth, Goom. It had an interesting signal path, but no LFO! So I expanded it to three oscillators and gave it two freely assignable LFOs (one through the mod wheel) and two freely assignable Mod EGs. I implemented the oscillators as my favorite three-control multiwave (blendable Sine/Tri/Peak/Saw/Pulse). The filter is CS-80-style HP in series with LP (2 or 4-pole), with dedicated IL/AL/A/D/R envelope. I call it TriGoom.

Since the name Goom was clearly a wink at Moog, I did this up in minimoog-style livery (no, it doesn't SOUND like a minimoog!!, OK?

Spogg over at DSPR asked a while back about have I done a 'dream synth' - the closest I've come I suppose is this one I just finished tidying up. It's based on a daydream of a Yamaha that combined most of the features of several CS-series synths. The mighty CS-80 was mighty because of it's truly polyphonic touch response and plethora of performance controls; it's basic synthesis abilities were surpassed by most of the other CS synths, especially the monophonic ones like CS-15 and CS-30.
So, the idea was to do a plugin that combined many features of CS-30, CS-15 and CS-80 in a CS-80-style panel layout.

Therefore CS-358 :

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!