DuosX VST Voice Doubler

VST, AU, AAX, CLAP, etc. Plugin Virtual Effects Discussion
Post Reply New Topic
RELATED
PRODUCTS

Post

fritzman wrote: Hi Midiworks,

nice try. But unfortunately not well done. Your SynthEdit plugin doesn't even look goo, but hey that's just my taste. Is it still not possible with SynthEdit to compile all additional modules into one dll?
It sounds poor. It's buggy. It does not sound as good as Antares Duo and it doesn't even mimic all of it's functionality so how can it be an Antares clone?
Sorry man, but obviously it's you who didn't do his R&D. If you would have done so you would have recognized that Antares is using a completely different DSP technique than you. It's way more complicated than your delay gimmick. A little delay feedback is far from the vocal timbre in Antares Duo. It doesn't even remotely sound similar.
But you wanted me to compare it, so I did.
In the end your plugin is a chorus with a random LFO plus a short delay with a feedback knob which you call Vocal timbre.

Do you wanna know why I'm so upset? Because I hate it when people fake stuff and then have a big mouth full of wannabe marketing. Do you remember all the kids in the music shop playing smoke on the water? Ain't talking bout love? Everybody played it but only a few played it convincingly. That's my point.
YOU imply that your plugin is at least as good as Antares Duo if not better, it doesn't have this and that prob, etc. After comparing I found out that your plugin is a buggy alpha version of a wannabe Antares clone. Alpha means: All functionality is implemented. In your plugin is NOT all of the Antares functionality implemented, your vocal timbre knob is a joke. A beta version is feature complete bus is not fully tested. Your plugin is not fully tested as it's really buggy.

OK, that's it for now. And yes, I'm with Hink. I would be VERY surprised if your amp plugin will be as good as you would like it to be. Learn some DSP stuff. This would help in many ways.


Best wishes, FRitz

P.S. This is not personally against you. Please see this as constructive critizism. I simply don't like it to get taken for a ride.

OOOOHhh Fritzi! :-o
Why did you take my manner of ranting about the dudes?

:hihi:

.
Last edited by ;-) on Sat Sep 17, 2005 9:16 pm, edited 1 time in total.

Post

No crackles, no strange phase shifting like the original AVOX DUO.
And your delay based pitch shifter don't modyfy the phases badly anyhow ???
That's ridiculous.

But hey! Why not simply "clone" that throat modeling thingy from Antares with some oscillator and reverb modules in SE ??? Can be easiely toped ... :hihi:

.

Post

He distributes 3rd Party SE modules (renamed - which is already a copyright injury) with his (commecial!) SE stuff.

I guess, he also did not credit those 3rd parties in his plugin, nor donate ...

I'd really like to know, whether he is a legal user of those modules. :roll:

Otherwise there would no need to modyfy them, right? :roll:

Bad, really.

.
Last edited by ;-) on Sat Sep 17, 2005 9:51 pm, edited 1 time in total.

Post

I would suggest that you re-think your wording. You've made an unfounded accusation full of guesswork and assumptions about rights and usage for 3rd party modules, but not everyone is able to see that. Some people may take you at face value.

One of the key words in your post was "guess".

Not trying to get in your face, but really now...
Image

Post

It's easy to change the name without cracking the modules. You just have to rename them. I'd guess he's changed the names so he doesn't have to share the glory of credit. Rene's pretty active at the SE users list, I'd be surprised if he was doing anything bad.

It is slightly unfriendly not to credit the module developers. Judging from the parameters exposed for automation, at least one is an EVM module.

Post

Ok there is no pronlem with EVM modules, but probably with Chris Kerry modules? :roll:

.
Last edited by ;-) on Sat Sep 17, 2005 10:04 pm, edited 1 time in total.

Post

Lunch Money wrote:I would suggest that you re-think your wording. You've made an unfounded accusation full of guesswork and assumptions about rights and usage for 3rd party modules, but not everyone is able to see that. Some people may take you at face value.

One of the key words in your post was "guess".

Not trying to get in your face, but really now...
Not exactly. Because I actually did see the strange renamed modules and made a binary readout of them therefore.

That is what I got:

Code: Select all

By using this module you agree to abide by all aspects of the license

License Agreement:
This module is provided as is with no warranty of any kind
The use of this module is entirely at your own risk
You may not distribute this module in any way or by whatever means
You may not View,Modify or Copy any of the code in this module
This module is only for use in SynthEdit and VST/i's created by SynthEdit,
the use of this module elsewhere is strictly forbidden

If this module is used in a VST/i please donate at www.chriskerry.f9.co.uk
If no donation is made for the use of this module in each VST/i,
the following credit must be displayed:-

This VST/i features modules by Chris Kerry
www.chriskerry.f9.co.uk

Post

;-) wrote:but probably with Cris Kerry modules?
Chris has a complicated licensing arrangement, so as long as Rene donated specifically to hide credit on this plugin, I think he doesn't have to give credit.

Chris's licensing has changed over the years, so that may be different now. I can't keep track (why I rarely ever use 3rd party modules any more, too much software to to keep straight).

Post

shamann wrote:It's easy to change the name without cracking the modules. You just have to rename them. I'd guess he's changed the names so he doesn't have to share the glory of credit. Rene's pretty active at the SE users list, I'd be surprised if he was doing anything bad.

It is slightly unfriendly not to credit the module developers. Judging from the parameters exposed for automation, at least one is an EVM module.
SE modules are redistributables, right?
I think it *is* an copyright injury to rename them intentionally in most cases, because that is modification in fact.

.
Last edited by ;-) on Sat Sep 17, 2005 10:03 pm, edited 1 time in total.

Post

shamann wrote:
;-) wrote:but probably with Cris Kerry modules?
Chris has a complicated licensing arrangement, so as long as Rene donated specifically to hide credit on this plugin, I think he doesn't have to give credit.

Chris's licensing has changed over the years, so that may be different now. I can't keep track (why I rarely ever use 3rd party modules any more, too much software to to keep straight).
Why does he rename all SE modules to appear DAT20.SEP, DAT21.SEM, DAT22.SEM, DAT23.SEM then ? :roll:

.

Post

;-) wrote:SE modules are redistributables, right?
I think it *is* an copyright injury to rename them intentionally.
Possibly. I'm not sure copyright extends that far, since changing a filename is a trivial matter, and the module libraries that distribute with a plugin are crippled, so it is only a matter of obfuscation, rather than infringing on anyone's rights.

Post

;-) wrote:Why does he rename all SE modules to appear DAT20.SEP, DAT21.SEM, DAT22.SEM, DAT23.SEM then ?
I guess so that no one knows he's using Chris and Etric's modules. He wouldn't be the first SE user to do so. Some SE users seem to find it aggravating to share their glory with the module coders.

Post

hmmmnnn ... a quick look at chriss license forbids modification of the CODE ...
You may not View, Modify or Copy any of the code in this module
... but doesnt mention renaming etc ... so this would be within the LETTER or such a license but not within the SPIRIT of it certainly ...

slainte :? rob

Post

shamann wrote:
;-) wrote:Why does he rename all SE modules to appear DAT20.SEP, DAT21.SEM, DAT22.SEM, DAT23.SEM then ?
I guess so that no one knows he's using Chris and Etric's modules. He wouldn't be the first SE user to do so. Some SE users seem to find it aggravating to share their glory with the module coders.
Well.
I think that too, because there is no need to rename SE modules.
This also would tend to confuse you with the content of your SE module folder quite a bit.
:wink:


But if he really payed a donation PRIOR distributing his plugin, then I am ready to excuse me for my guessing. :wink:

But in the "Chris Kerry case" he had to do a donation FOR EACH new plugin he redistributes. Otherwise a credit must be displayed.

.

Post

I mean on the other side he writes that in his license:
2. RESTRICTIONS.

The SOFTWARE is confidential and copyrighted and is owned by the author.
Title to the SOFTWARE and all associated intellectual property
rights is retained by the author. You may not make
copies of the SOFTWARE. You may not modify, decompile,
or reverse engineer the SOFTWARE.

You may not distribute the SOFTWARE in any form or in any way.

In particular, you may not sell, hire or lease the SOFTWARE.
Quite strict. :?


I always did see such things coming. SE creations are (mostly) merely done like usual documents. Not much different like a Word document or an Excel sheet...

I mean he did not develop a software program at all. He merely did track virtual patch cables arround and saved a document.

The plugin dll itselfes is actually only a precompiled copy, where the resources are patched with SE on the fly ...

There is not even a "compiling" (in the sense of native software compilers) made at all.

But the fact, that they are distributed in binary (native executable) form is quite a problem for the software copyright. Especially in the case of the used external modules.

It should have a reason too, that the modules will dumped out to disk permanently on first plugin start.


I wished it would be more clear all here.

.
Last edited by ;-) on Sat Sep 17, 2005 10:37 pm, edited 1 time in total.

Post Reply

Return to “Effects”