From the original SynthMaker forum (2004–2014), with its members’ names and dates.
tester ·
It would be a great idea to open (and stick) a list of VST capable software (DAWs and synth loaders) - compatible with SM generated VSTs, plus a short list of known (vital) and comfirmed issues. That should help to develop SM in right directions too or just to monitor software changes (how they work with SM plugs).
What do you think?
Dell ·
99% of the most popular DAWs have no problem with Synthmaker's VST. Any minor issues (if any) can be corrected by the developer.
tester ·
Not all of them seem to see the SM made VST effects. For example Audacity did not, at least on my computer. I had the opportunity to check the adobe audition 1.5 - also is not compatible (shows as not compatible). I saw in search mode, that there were some issues with Cubase and multiple plugin windows. That's why my proposal. People who are not programmers and don't know compatibility details - are checking if SM will work for them, and such list will give them a cue. If you start to argue, that everyone is familiar with VST engine versions adopted in these applications, then my answer is - "well - not everyone". I'm attracted to a software if I know that it will work with specific apps and if I have some initial confirmations. Best way is to gather them together, and not speculate. It works also as a good marketing strategy for promoting such stuff like SM. Awakes trust. The more I need to click, the less time I have to click further. For example - I became anti-fan of apple i-devices, because there was and is a lot of confusions between various i-devices and various hardware extensions for them. Wider perspective.
Dell ·
If the VST is not working, then it is an error on your part. I have no issues with 99% of DAWs (The ones you mentioned included with my designs).
I have videos to back it up in the rare occassion a user that tries my design states the plug-in does not work. User error is pretty common with first time users of Synthmaker. It has happen to all of us. So, if you want to solve the problem, offer the OSM so one of the members can help you.
tester ·
Dell - if you re-make my simple VST effect to work in adobe audition ver. 1.5 and audacity, then I agree with you. You can use "test-mixing-revisited.osm" from this thread:
vst effect problem (initial values vs my values)
I'm sure that working design would be also a good example for other beginners like me.
cyto ·
I can't comment on Audition, but I downloaded Audacity just to test this. I can report positively that the little plugin from the other thread works perfectly fine in it. One thing that I think may be confusing you, when you export a vst, you need to remove the "direct sound ins" and "direct sound outs" etc. Did you remember to do this? The only thing you need to export is the module with the actual effect or instrument in it. To see an example, search the toolbar for "VST". There is a little module in there that I think just has the echo inside. That should provide a template for how to format your module for export.
-cyto
Dell ·
Hi.
There is nothing to repair for the VST is fine. Possibly your version of Adobe Audition is the root of the problem for, 1.5 is a very old version. Adobe Audition is now on version 5 and, the oldest I have is 3. The video shown below is Adobe Audition 3 operating on Windows 7 using your plug-in.
http://www.zshare.net/video/98931604fa54916d/
If the stock effects (Compressor, flanger, etc.) does not work, there is a chance that your processor may be a Celeron which, is the only Intel chip I've encountered that does not work with Synthmaker plug-ins.
Some Celeron chips do not include SSE which, is needed in order for Synthmaker plug-ins to run. Older Pentiums and current flagship processors offer SSE.
It may be best to download the current version of Adobe Audition (It offers a 20 or 30-day trial) so you can determine if it is indeed your older version of Adobe Audition or hardware related problems.
Cheers!
tester ·
Pentium Core 2 Duo, XP pro sp2/3.
Exported only a test module (by clicking on a module), not ins/outs (remove them from schematic completely? I assume you saw the schematic); it works in wavelab; audacity scans for it but does not detects; old audition shows in the 'not compatible' list.
Not intersted in new adobe audition; they removed core elements, that defined cool edit as cool; now it is "yet another DAW" with rather unpleasant interface (3.0 has nasty interface too).
Almost 4 a.m., time for some sleep. 😉
Dell ·
Then you are out of luck unless someone is willing to troubleshoot an 8 year old DAW muchless have access to Adobe Audition 1.5/Cool Edit version 2. Many of us need to focus on what's current in the market.
tester ·
What I'm trying to tell here Dell - is that there are various people and various habits. Also - not everyone will pay for newer audition, not everyone lives in a Country where you earn thousands of dollars, euros, pounds, not everyone will change his DAW (or whatever software) each time when something does not works (first - will seek for solutions, how to make it works). There are even more aspects; wider perspective so to speak. What I'm also saying is, that when people begin to search for vital informations, there is a cross-mixture of multi-level data, not only up-to-date but also outdated and you must make independent check which info is outdated and which not. I have that luck, that I know how to navigate through such informational chaos (100 000 of cables in CERN? Phew! 😉 Trifle!), but I also do understand - how it works with others in real world. Besides - you see our discussion. If everything would be so clear and obvious, then it would be no such talk here.
We live in speeding times, thus vital informations directly under your hand (sticky lists that in simple terms calm you down) are more valuable than searching engines which produce dozens of ambiguous results.
To show the mechanism - now, when someone (who stuck in some troubble) types in seach engine word "compatibility" - will find this thread, judging according to the on-top keywords. Clear stated doubts, clear stated explanations; thats good. Two years from now on - this person would also need to make some checkups which SM version was covering this period of time. 🙂
Dell ·
All I here is excuses.
cyto wrote: I can't comment on Audition, but I downloaded Audacity just to test this.
-cyto
Your reply to cyto...
tester wrote: Pentium Core 2 Duo, XP pro sp2/3.
Exported only a test module (by clicking on a module), not ins/outs (remove them from schematic completely? I assume you saw the schematic); it works in wavelab; audacity scans for it but does not detects; old audition shows in the 'not compatible' list.
Your reply to Dell...
tester wrote: Not intersted in new adobe audition; they removed core elements, that defined cool edit as cool; now it is "yet another DAW" with rather unpleasant interface (3.0 has nasty interface too).
Almost 4 a.m., time for some sleep. 😉
Not only did you not thank Cyto for taking the time to download and installing Audacity on his computer trying to help you, You won't even try to install the latest version of Adobe Audition 5 demonstration to find out if indeed your old version of Adobe Audition is the root of the problem or something else.
Yet, you offer a barrage of excuses. With an attitude like that, I bid you good luck.
tester ·
@Dell - if you have something personal to me, move it to PM; we should not confuse the conversation board. Okay?
Wrote something here? To have a post removed or your name hidden, write to [email protected].
SynthMaker