Page 1 of 2

VST's

Posted: Fri Mar 04, 2016 6:31 pm
by BobF
Hello gang,

I was wondering, can we get a list of what Daw's or other programs that are sub post to accept vst's, like Audacity for example that you made with Flowstone.

What daw's and other programs have you found to work 100% with your vst and what ones maybe not so good. Did you have to modify your fsm in any way to get it to work?

If you have learned anything at all making vst's PLEASE share. I think any information here could help many of us.

*** The reason I am asking for this is I am having a terrible time getting my DFP Combo Flanger to work as a vst in Audacity that is sub post to support vst's. I have tried removing all inputs and outputs, just leaving one mono in and one mono out with no luck, then tried deleting the preset manager, also no luck. Spogg tested it in Reaper for me and says it works very well and sounds good. I am stumped.

Ok, that's it. Thanks!
Later then, BobF.....

Re: VST's

Posted: Fri Mar 04, 2016 8:58 pm
by tulamide
A few things worth mentioning:
- 32-bit VSTs only with 32-bit Audacity. Make sure you have not installed the 64-bit version of Audacity.
- Plugins are not supported 100%. On their support wiki they write: "The overwhelming majority of VST effect plug-ins should display and process correctly. If an incompatible VST plug-in does cause a problem, click the Manage button in the effect's dialog then choose "Options...". In the dialog that appears, try reducing Buffer Size, disabling Latency Compensation or disabling graphical display. See VST Effect Options in the Manual for more information on these choices."
- In case of issues with VSTs the developers ask to contact them via feedback@audacityteam.org, here's more info: http://wiki.audacityteam.org/wiki/VST_P ... n_Audacity

Re: VST's

Posted: Sat Mar 05, 2016 5:17 am
by noisenerd
I've only tried a couple so far, but I haven't yet had any trouble with any of my FlowStone VST's in either Bidule or Reaper. I can't remember any specific ones offhand, but I know a few of the other plugins I use occasionally came from SM.

Also, fwiw, I've had trouble with several plugins from multiple sources in Audacity, many of which I know were not made in FS or SynthMaker. Some of them work fine everywhere else, and some have trouble with one or multiple other hosts... but Audacity definitely seems particularly "picky" about plugins.

Re: VST's

Posted: Sat Mar 05, 2016 6:01 am
by RJHollins
I use Reaper and Bidule as main applications for my work.

I've had minimal issues with FS VST in either.

There has been an issue with REAPER, and involved a particular FS VST being added to the MASTER BUS. This VST had a 'TIMER' function, and the TIMER would NOT run until I added a blank track. Then everything worked, including pull-down menus and such.

This was something I only experienced on Reaper's MASTER BUS. I believe this must be something specific that the MASTER BUS is not totally active until a TRACK is added. It may involve things like 'sample rate', or clocking.

Another app, WaveLAB, does not like 4 channel audio [side-chain]. Stereo works fine.

Re: VST's

Posted: Sat Mar 05, 2016 9:23 am
by Spogg
One thing I found out the hard way with VSTs, in Reaper anyway, is never to open a blue signal path, that is to mute a path by using a selector to switch to a dummy input. It works fine in the VST if you do this in a poly signal path. It's ok to select between blue paths so that, for example, to bypass a reverb works fine or to choose one effect or another with a selector in blue.
Opening a blue path in the FS edit environment always works fine, just not in the exported VST. I only test in Reaper so this may not be an issue in other hosts.

Cheers

Spogg

Re: VST's

Posted: Sat Mar 05, 2016 2:51 pm
by RJHollins
Hi Spogg,

... is never to open a blue signal path, that is to mute a path by using a selector to switch to a dummy input.

This caught my attention. Do you have more details about the issue you experienced ? Also ... what might be a replacement technique to substitute?

thanks

Re: VST's

Posted: Sat Mar 05, 2016 3:28 pm
by Spogg
RJHollins wrote:Hi Spogg,

... is never to open a blue signal path, that is to mute a path by using a selector to switch to a dummy input.

This caught my attention. Do you have more details about the issue you experienced ? Also ... what might be a replacement technique to substitute?

thanks


Yes, if your schematic has blue stream opening, for muting, everything is fine with the VST(i) until you mute or unmute. Then the VST may hang and stop responding to some or all mouse clicks. This is in Reaper don't forget, may be different in other DAWs.
I originally wanted to save CPU by muting blue streams by opening them but it's not reliable.
To repeat, I can open poly streams without problem.

I've attached a quick illustration of what I found is a much more reliable method for muting a blue stream.

It would be interesting to hear if anyone else has found this.

Cheers

Spogg

Re: VST's

Posted: Sat Mar 05, 2016 3:49 pm
by RJHollins
Interesting technique Spogg ... I'll test this out in Reaper.

additional question ... on the De-Zip prim, I don't see a value setting the 'duration' parameter.
Is this by design ? not needed ?

Re: VST's

Posted: Sat Mar 05, 2016 4:18 pm
by Spogg
RJHollins wrote:Interesting technique Spogg ... I'll test this out in Reaper.

additional question ... on the De-Zip prim, I don't see a value setting the 'duration' parameter.
Is this by design ? not needed ?


The default is 40mS with no input. This is ideal just for removing clicks when muting or un-muting. If you hover over the prim there is a help popup that explains.

Cheers

Spogg

Re: VST's

Posted: Sat Mar 05, 2016 4:47 pm
by RJHollins
got it .... Thanks 8-)