Audio Weaver has synthesizer capabilities, as well as audio effect capabilities. Our current version of the tool doesn't have a VST Wrapper, but there is a workaround that will work with most DAW platforms, given that you have some sort of Audio Routing capability (such as the asio4all (http://www.asio4all.com/) driver for windows. Using this free driver, along with Virtual Audio Cables ($30? http://software.muzychenko.net/eng/vac.htm), you can set the output of AudioWeaver (in server settings) to go to Virtual Audio Cables. In your DAW, set your audio device to asio4all. From there, you should be able to stream the AudioWeaver output to your DAW by enabling this Virtual Audio Cable input device. This is the routing necessary for having an AudioWeaver "instrument".
To have an AudioWeaver "effect", you must run 2 virtual audio cables (adjustable inside the VAC Control Panel). They will be named Virtual Audio Cable 1 and 2. You will have to use the same Asio4all driver inside your daw, but this time, enable an output device "Virtual Audio Cables 2" to send audio into AudioWeaver. The Server will have to have its input device set to Virtual Audio Cables 2, and output to Virtual Audio Cables 1. The DAW should still have Virtual Audio Cables 1 as input. This allows you to stream some channel in your daw into AudioWeaver for effect processing, and back into your Daw as a "wet" signal. This will have to be recorded in your daw to capture it (or you can use AudioWeaver to write processed data to a .wav file).
If any of this doesn't work, I can provide links to documentation on these third party tools, but third party support may have slower feedback from this forum.
The above setup is assuming that you want realtime processing. If realtime is not needed, there is the old-school trick of exporting .wav files to and from different software. This technique is referred to as "printing" and was used when pcs were more compute-limited. This would be done one effect at a time and took a long time. For this reason, AudioWeaver also comes with a very fast "process files" function found in Tools->Process Files. The downside to this technique is that in order to tweak settings, a new file must be "printed".
11:28am
I am wondering if Audio Weaver works together or similar with SynthEdit/FlowStone and JUCE
2:48pm
Hi uer,
Audio Weaver has synthesizer capabilities, as well as audio effect capabilities. Our current version of the tool doesn't have a VST Wrapper, but there is a workaround that will work with most DAW platforms, given that you have some sort of Audio Routing capability (such as the asio4all (http://www.asio4all.com/) driver for windows. Using this free driver, along with Virtual Audio Cables ($30? http://software.muzychenko.net/eng/vac.htm), you can set the output of AudioWeaver (in server settings) to go to Virtual Audio Cables. In your DAW, set your audio device to asio4all. From there, you should be able to stream the AudioWeaver output to your DAW by enabling this Virtual Audio Cable input device. This is the routing necessary for having an AudioWeaver "instrument".
To have an AudioWeaver "effect", you must run 2 virtual audio cables (adjustable inside the VAC Control Panel). They will be named Virtual Audio Cable 1 and 2. You will have to use the same Asio4all driver inside your daw, but this time, enable an output device "Virtual Audio Cables 2" to send audio into AudioWeaver. The Server will have to have its input device set to Virtual Audio Cables 2, and output to Virtual Audio Cables 1. The DAW should still have Virtual Audio Cables 1 as input. This allows you to stream some channel in your daw into AudioWeaver for effect processing, and back into your Daw as a "wet" signal. This will have to be recorded in your daw to capture it (or you can use AudioWeaver to write processed data to a .wav file).
If any of this doesn't work, I can provide links to documentation on these third party tools, but third party support may have slower feedback from this forum.
The above setup is assuming that you want realtime processing. If realtime is not needed, there is the old-school trick of exporting .wav files to and from different software. This technique is referred to as "printing" and was used when pcs were more compute-limited. This would be done one effect at a time and took a long time. For this reason, AudioWeaver also comes with a very fast "process files" function found in Tools->Process Files. The downside to this technique is that in order to tweak settings, a new file must be "printed".
Good Luck!
6:51pm
Thanks for the reply. My query is actually about VST development, not audio processing, although I can see the process you explain being useful.