To SynthEdit or not to SynthEdit

[do_androids_dream]

For me, the HG Fortune's AstralDreamer and Tiger consistently crash, UltraSwamp and DreamMachine3 crash inevitably. All come up with load errors at one time or another and can often lead to a crash also. I like the synths for their uniqueness, but don't use them any longer because of it.

Do what I do - get the synth to do what you want it to then bounce it to audio. I do this with most synthedit synths as they can be unreliable to say the least.

[fluffy_little_something]

one of my most used plugins is synthedit. It crashes at least once a day.

And which one would that be?

None of mine ever crash. Occasionally there is some odd behavior, but since that doesn't happen in all DAW's alike I can't even say with certainty that is a SE issue. And odd behavior is not limited to SE synths.

For me, the HG Fortune's AstralDreamer and Tiger consistently crash, UltraSwamp and DreamMachine3 crash inevitably. All come up with load errors at one time or another and can often lead to a crash also. I like the synths for their uniqueness, but don't use them any longer because of it.

I never liked HG Fortune stuff, tried a couple of those plugins, but they did not convince me.
I use almost exclusively SE plugins (except Noisemaker) because my computer is not the most powerful, Mostly old Superwave stuff and it never crashes. Maybe your problems are related to HG Fortune plugins in particular. They seem to have an excessive amount of parameters, maybe SE is not ideal for that. I remember that the Memorymoon emulation of the CS80 is also less reliable, feels heavy on my system, it is also a more complex synth with lots of parameters and the ribbon controller, which my DAW does not like somehow.
The Superwave Professional and P80 on the other hand have not shown any abnormal behavior, let alone crashed. I guess it might have to do with the way developers configure the modules, because, thinking about it, the P80 is also complex with lots of parameters. Maybe the developer is simply better at what he is doing.
The only odd thing is that whenever I use more than one Superwave plugin (regardless which ones) in the same project in Mixcraft, there is an ugly noise whenever I first load and play an existing project. Then I click stop and play, and the noise is gone. During mixdown there is no noise at all, even right after loading the project.
When I do the same in Mulab, however, there is never any noise. So it seems it is not a SE issue, but a Mixcraft issue.

[BBFG#]

You bring up multiple instances and that seems to be the problem with HGF also. Except that it extends to multiples of HGF as opposed to multiples of any single VST by them. Their older VIs seem to work better than their newer VIs, but my problems seem to start when installing too many of their 'NFG' freebies.
Errors in loading came up often since the libraries had seem to confuse the synth in finding the right ones. So I ended up making a separate folder for each one and then having to place their path in the DAW. This helped somewhat, but didn't completely solve it.
Tiger continued to have consistent problems and AstralDreamer problems were still frequent. So picking just a couple of them seems best. The Swamp synths, I decided the sound wasn't to my liking really, SerenityPro and Avatar are probably the most reliable and usable in a musical sense. Those and the two STS synths (26&33) are still my favorites of theirs but I have other 64bit VIs that do what they do without the inherent problems. So they've become effectively outdated. What I like best about HGF, and I am keeping an eye on them in case they do find a way to go 64 bit, is their 'soundscape synths' where the stuff seems more unique than others in that regard.
One thing I've learned lately with HGF though is, don't buy any of this current 32 bit offerings because there seems to be super price drop or give-away right around the corner.

Edit/add: I should add here that I am using a sound set from HGF in WusikStation now, but again, I bought it only to find them giving it away within a couple of weeks after.

[fluffy_little_something]

Strange. Same here, it does not matter whether I use several instances of the same Superwave synth or one instances of different Superwave synths each. One might think that each synth is clearly separate from the other, each has its own module folder and ID. Still there seems to be some overlapping between synths and instances Maybe a path issue as I noticed that with SE synths I never see the names of my patches in my DAW, but instead the names of some factory presets I am not using.
With Swierk there is no such overlapping, I tried several instances today, no problem. Unfortunately the sound is not as good, quite some noise on low and high octaves.

[bsl]

SynthEdit +1

[Yudaidhun]

I don't care how the software developed.
Only what I care is its stability and usability...... and price

[BBFG#]

I don't care how the software developed.
Only what I care is its stability and usability...... and price

Stability seems to be the main issue with SEdit.
Usability is of course, subjective.
But considering that, the price is usually comparable.

[xoxos]

i always figured the main issue with synthedit was what other people say about it.

[antto]

plugin racism? ;]

[kbaccki]

i always figured the main issue with synthedit was what other people say about it.

well played, sir...

RE: multiple SE instance... if not mentioned SE 1.0 suffered from well-known stability issues with multiple instances/multi-core systems. Supposedly addressed with SE 1.1: http://www.synthedit.com/members/version-1-1-faq/

Not sure if the original plugs needed to be recompiled/repackaged against 1.1, or if you can just drop SE 1.1 components directly into plug folder. Short of that, a known workaround was to create multiple copies of the plugin and rename each copy to a unique name.

[jack [psychicmodulation]]

Yes, I also have 1.4. The bug seems to affect only my own user patches, not the factory presets. I have tried saving my own patches again after opening them in the new version, but the bug is still there. As if the setting of the previously opened patch is simply not updated when opening a new patch.

I ran some tests with your patch and may have figured something out. I don't want to derail this thread, so I'm linking over to this one instead:
http://www.kvraudio.com/forum/viewtopic ... &start=120

[yessongs]

that brass patch is really cool. Are those stock presets in evol?

Nopes none of them are stock but modified versions from the included presets. The bad thing however is that i cant share them because i just discovered that presets are not saved correctly within Cubase VST Preset format What a bummer !

Dang it

what about if you open it up in another host and save them in something like vsthost which I seem to see a lot of people mention as having a way to work with fxb's and fxp's at kvr?

[MaxSynths]

I don't care how the software developed.
Only what I care is its stability and usability...... and price

Stability seems to be the main issue with SEdit.

Not true. The stability issues (the multicore bug) have been solved from a long time. Most SE plugins are rock solid.

[bailees7irish]

This discussion is actually pointless.
Either you use 64 bits PC´s... and renounce many good Freeware.
Or you use furthermore 32 bit Systems... and has a lot of fun

Agreed
32-bit for me 'til I die!

[Slarti]

.

I have never had anything NI on my computer and probably never will.

So you're saying "Ni" to NI then!

Sorry, couldn't resist!

(Ancient movie reference!)