Posted by Ludichristos666 on Tue, 08/06/2002 - 01:56.
Quote:
"The plug-ins are available as DirectX plug-ins and as native Cubase VST plug-ins ( PC ). The DirectX plug-ins are compatible with Soundforge 4.0d, Cakewalk Pro Audio 7, WaveLab 2.01 and Cubase VST PC 3.7. The Cubase VST plug-ins are compatible with Cubase VST PC 3.7 and WaveLab 2.01. The plug-ins can be used with any DirectX or VST-compatible application, they have only been tested with the above-mentioned software."
First thing you guys need to do is test
these with current versions of the host progs everyone is using.
Get yourselves Fruity Loops 3.5,
Wavelab 4.0e, Cubase SX 1.2, SonarXL 2, Soundforge 6 and Cool Edit Pro 2
Its an understatement to say it looks unprofessional that you are testing your product with software hosts that are literally years out of date.
More and more people are using Fruity Loops, Plugin developers need to test their product with Fruity
Readme
Quote:
"The plug-ins are available as DirectX plug-ins and as native Cubase VST plug-ins ( PC ). The DirectX plug-ins are compatible with Soundforge 4.0d, Cakewalk Pro Audio 7, WaveLab 2.01 and Cubase VST PC 3.7. The Cubase VST plug-ins are compatible with Cubase VST PC 3.7 and WaveLab 2.01. The plug-ins can be used with any DirectX or VST-compatible application, they have only been tested with the above-mentioned software."
First thing you guys need to do is test
these with current versions of the host progs everyone is using.
Get yourselves Fruity Loops 3.5,
Wavelab 4.0e, Cubase SX 1.2, SonarXL 2, Soundforge 6 and Cool Edit Pro 2
Its an understatement to say it looks unprofessional that you are testing your product with software hosts that are literally years out of date.
More and more people are using Fruity Loops, Plugin developers need to test their product with Fruity
Wavelab 2 ???? Cubase 3???
I am laughing my ass off here
Ludichristos666