From the original SynthMaker forum (2004–2014), with its members’ names and dates.
Nu Audio Science ·
[old link]
See that thread
Create a bunch of tracks and put the plugin on them
Then put the same plugin on the master
Now in some hosts it wont even play properly in others it wont render properly
The LFO is way out of sync and in some instances just creates random noise
The weird thing is that in the test project and plugin we have been using the track fx have nothing turned on whatsoever
Just the master fx has an LFO filter on it and it is all over the place
Easiest host to check to find a broken one is Reaper
I spoke to the Reaper dev about this and he says it is the plugin using shared static data causing this
Malc let me know if you need a .rpp reaper prioject to show you this isuue 😉
NAS
Eska ·
My plugin did not pass the multiple-instances test of Christian C. Buddes plugin analyzer. There seems to be an issue.
aliasant ·
Eska wrote: My plugin did not pass the multiple-instances test of Christian C. Buddes plugin analyzer. There seems to be an issue.
About that.... Does anyone have the latest VST Plugin Analyzer? It cant be downloaded from Buddes website. Tried googling it but all I ended up with was dead links =(
Is this problem new with the beta or is it an old problem?
Disco_Steve ·
I've had this problem too, and its been driving me nuts.
only some of my pluggins do it in my host. I managed to stop one of mine causing a problem, by getting a selector to recompile properly, by removing it completely, and then putting it back in again. now for that plug all works well (with all simple tests done so far), I must try out that vst tester app sounds very usefull 🙂
this is a serious issue, that must be addressed.
theun ·
aliasant wrote: Does anyone have the latest VST Plugin Analyzer? It cant be downloaded from Buddes website. Tried googling it but all I ended up with was dead links =(
The right link is here
http://www.savioursofsoul.de/Christian/Programs/VST%20Plugin%20Analyser.zip
Last week or so Christian issued a new tool, "VST Plugin Unit Test". Probably Eska is referring to that one, as it includes also a multiple instances test, among many other tests.
Christian started a topic at kvr about this tool : http://www.kvraudio.com/forum/viewtopic.php?t=246971
The tool itself can be DLd here http://www.savioursofsoul.de/Christian/Programs/VUnit.zip
aliasant ·
Sweet theun 🙂
aliasant ·
Been testing different plugs with the "VST-Plugin Unit Test" and none of my plugs can pass the first 2 tests.
Then I made a VST from the Example Synth in the toolbox and that one has the same problems.
Would be nice if Malc could use this tool and make sure that plugs created with SM at least pass all the important tests.
I did also test some of my other commercial plugs and none passed all tests but they did pass most.
MichaelBenjamin ·
hey, nice tool. the simple sine passes all but the testprocessdoublereplacing which seems to be a vst 2.4 thing.
it would be good if one could nail down the things that cause an error with multiple instances.
MichaelBenjamin ·
aliasant wrote: Then I made a VST from the Example Synth in the toolbox and that one has the same problems.
do you mean the small "vsti" one? i just tested it, it passes all but the processdoublereplacing.
aliasant ·
MichaelBenjamin wrote:
aliasant wrote: Then I made a VST from the Example Synth in the toolbox and that one has the same problems.
do you mean the small "vsti" one? i just tested it, it passes all but the processdoublereplacing.
No the bigger Example Synth. Its a .osm in your SM folder I think. Not in the toolbox.
Interesting though that you say the smaller VSTi passes. Gonna try that here too.
Update: I realized that the Example Synth I first tested was modified by me. If I open the "example.osm" from the SM folder and make a VST from that it passes all but the multiples and the TestProcessDoubleReplacing.
That should then give some clues for me as to what went wrong in the other one.
I had the same result with the small VSTi.
Update2:
The only thing I had modified in the example synth was that I removed the original VST PresetsManager and replaced it with Exos PresetManager. When I removed the PM all together it passed all tests( except the multi wich I didnt even try)
Nu Audio Science ·
Such an horrendous issue that makes pretty much any plugin from SM unusable if you want to have more than one instance that i am going to keep bumping this
SE has been slated really badly in recent times for these issues and when this gets out that SM is the same then i fear for the public perception of it and any plugins made in it
Really
SE has it fixed already in latest betas 🙁
NAS
Disco_Steve ·
also bump, although the inconsistancy will make it darn hard to fix 🙁
I know the list of things to do is getting so long that you could make it into many socks, but this one MUST be fixed.
Nu Audio Science ·
Been doing a bunch more tests with the beta testers of my plugins and we have found some other rather bad anomolies too
On certain plugins after 4 instances have been loaded each new instance takes twice as long as the previous instance to load (You can imagine how quickly that builds up) Oh by the way no fonts used at all in the plugin
Also after 6 instances of certain plugins parts of the system get clogged up with something, I say something because using host built in performance meter and windows own native performance meter doesnt show anything but the system defiantly slows down heavily
Will keep testing and bumping this thread with all the info
NAS
EDIT*
Some figures
4 instances load time 8 seconds
6 instances load time 18 seconds
8 instances load time 45 seconds
Nothing else but the plugins in the project
Now even though the 8 seconds for the 4 instances isnt really acceptable (Its terrible lets be honest) doubling the instances to 8 and getting load times of 45 seconds is a very bad
This is not good at all
NAS
Disco_Steve ·
I use sonar (old) which ahs to wrap each of its vst's to be able to use them. and I just noticed than the SM vst's take much longer to wrap than 'other' vst's.
basicly another excuse to BUMP this page 🙂
malc ·
The LFO sync is a relatively easy fix. Sorry about that - I'm surprised this wasn't spotted until now.
Not sure why the load time in increasing. Are you using the 1.1.3 beta? Does it happen with 1.1.2?
I'll certainly check out Christian's test app, thanks.
Nu Audio Science ·
1.1.3 beta 1 Malc
That LFO sync issue is the biggest issue here
Load times are acceptable if the plugins actually work hehehehehe
But i will carry on doing tests because the load time thing is puzzling
Cheers
NAS
Disco_Steve ·
I agree. slow but working is better than broken 🙂
Nu Audio Science ·
OK the original bug i posted has been quashed
So if there are no other multi instance issues i am going to tag this thread as fixed 😉
Cheers
NAS
Disco_Steve ·
I just found a subtle one
on loading the third instance of a plug, the plug-in works in general but the graphics don't update, and some of the selectors don't switch, in fact I think its just the selectors not switching (not tested will do)
but on reloading sonar the third instance works properly. looks like this bug is very nearly sorted. SO VERY PLEASED 🙂 Thankyou Devs
Steve
Wrote something here? To have a post removed or your name hidden, write to [email protected].
SynthMaker