Samplitude Pro X opinions

[Kraznet]

I sent in various bug reports plus videos to Waves and they said they would look into it but nothing has happened yet. All the other Waves plug-ins work in Samplitude no problem.

Regards
Kraznet

[lfm]

I do wonder why you keep repeating your personal problems with Samplitude here. They are not representative at all, and as you know have been intensively discussed in another thread:

http://www.kvraudio.com/forum/viewtopic ... 76#5336876

Let me quote something I already told you there, regarding the probability that Element causes your problem, not Samplitude:

"Then the probability is high that the fault is on the part of Waves. Normally, Samp ProX is really precise about differentiating VSTs and VSTis. I've loaded tons of both into ProX and never had a VSTi that was recognized as an FX."

BTW: KVR member Kraznet confirmed that Element is the cause of the problem, not Samplitude.

If you don't like Samplitude, or if it's too complicated for you, that's just fine. Leave it and ignore it. But for the future, please spare us with unqualified statements like "cumbersome to work with" or "they have not fixed it yet" - when the fault lies on the side of Waves.

I was really trying to help you in that other thread, taking my time to write comprehensive answers. While it seemed like you had finally realized what your problems with Samplitude are, you're starting all over again with the same stuff in this thread.

Write to the Waves support, but leave Samplitude to those who like and understand it.

Well, I can tell you - I will put comments about what I feel is relevant. And I could not think of a better thread than "your opinion about ProX".

The very idea of forums is to exchange information - pros and cons about anything. And readers are smart enough to decide for themselves - what is the final outcome!!!!

If somebody started a fanboi thread "What you like about ProX" - I will stay away, I promise.

My overall concern is that my tools work - and Element is listed as "supported". How the heck did that happend?

Are Magix the ones that did the testing - and finally are responsible for putting 'supported' in the Waves compatibility charts?

Or do Waves have their own employees that go through and test everything for the chart for every single supported product and plugin of theirs.

My guess is the former - and my question again - How did it appear as 'suported'?

It is an odd thing to have a synth listed as fx, I know - but both my old Sonar 8.x and Reaper handle it nicely anyway - and Reaper has a simple checkbox to have it listed among instruments anyway - sooooooo simple and clever.

Anybody that does not like pros and cons for things should not spend their valuable time browsing KVR at all - is my view.

And thank for your effort to help out in the former thread - again. I did thank you there as well - I always do appreciate people making an effort.


p.s. A tip for Magix - remove the "supported" tag on Waves charts for Element until it's actually supported. You remove all credability to Magix and products by saying things that are not true.

[lfm]

I sent in various bug reports plus videos to Waves and they said they would look into it but nothing has happened yet. All the other Waves plug-ins work in Samplitude no problem.

Regards
Kraznet

Thanks.

How does it work - does Waves take responsibility for putting "supported" on Element?

Or is that your doing?

I would not react with such a strong response against ProX if Element was listed as "not supported". That would be sufficient and I don't have to worry about the rest of my plugins listed as 'supported' causing the same kind of instability that Element did.

I cannot enforce this enough - that chart must correspond to reality!!!!

[w1awb]

I'm sorry that your experience with Samplitude wasn't a better one. But I'm curious as to what you meant by this... that those of us who recently tried the Samplitude demo, LIKED it, then bought it (like me) have NO BRAINS?? Really??

But it's a no-brainer for sure - NOT TO BUY.

[Kraznet]

I sent in various bug reports plus videos to Waves and they said they would look into it but nothing has happened yet. All the other Waves plug-ins work in Samplitude no problem.

Regards
Kraznet

Thanks.

How does it work - does Waves take responsibility for putting "supported" on Element?

Its Waves who decide whether something is supported or not and from my testing the only plug-in that isn't working is Element.

Or is that your doing?

I have no say in the matter is I don't work for MAGIX or Waves. Although I do beta test for both companies.

Regards
Kraznet

[Jim Roseberry]

Fair enough...

Take a look at this...



It's a VST 3 Editor/librarian for a Yamaha MOX Keyboard which allows for total hardware/software intergration. All edits to the hardware are saved within the project when used as a VST. Although there is a standalone version, it's not as convenient and can become confusing when dealing with many projects. As far as I know, this can't be done with VST 2.

That type of "full-remote" Editor can and has been done via VST2.x spec.
The Korg M3 Editor...

[koolkeys]

Fair enough...

Take a look at this...



It's a VST 3 Editor/librarian for a Yamaha MOX Keyboard which allows for total hardware/software intergration. All edits to the hardware are saved within the project when used as a VST. Although there is a standalone version, it's not as convenient and can become confusing when dealing with many projects. As far as I know, this can't be done with VST 2.

That type of "full-remote" Editor can and has been done via VST2.x spec.
The Korg M3 Editor...

I think the point was that the editor he showed, which is the editor for his specific keyboard, is only in VST3. So for him, VST3 has more value.

Brent

[Hink]

I'm sorry that your experience with Samplitude wasn't a better one. But I'm curious as to what you meant by this... that those of us who recently tried the Samplitude demo, LIKED it, then bought it (like me) have NO BRAINS?? Really??

But it's a no-brainer for sure - NOT TO BUY.

nantucket? my late sister owned a large real estate company on the vineyard, my mother is on the vineyard as we speak...sorry for the ot

[w1awb]

Yes Hink! I'm on the next island over from the vinyard.

nantucket? my late sister owned a large real estate company on the vineyard, my mother is on the vineyard as we speak...sorry for the ot [/quote]

[Hink]

Yes Hink! I'm on the next island over from the vinyard.

nantucket? my late sister owned a large real estate company on the vineyard, my mother is on the vineyard as we speak...sorry for the ot

I'm in Mass 5 miles from Nashua NH...I've never been to Nantucket but spent a lot of time on the vineyard, more than I cared to tbh. My family comes from the Bar Harbor area of Maine and we had a place up there.

[lfm]

I'm sorry that your experience with Samplitude wasn't a better one. But I'm curious as to what you meant by this... that those of us who recently tried the Samplitude demo, LIKED it, then bought it (like me) have NO BRAINS?? Really??

But it's a no-brainer for sure - NOT TO BUY.

Sorry you are offended, I should have added "no-brainer for me".

[lfm]

I sent in various bug reports plus videos to Waves and they said they would look into it but nothing has happened yet. All the other Waves plug-ins work in Samplitude no problem.

Regards
Kraznet

Thanks.

How does it work - does Waves take responsibility for putting "supported" on Element?

Its Waves who decide whether something is supported or not and from my testing the only plug-in that isn't working is Element.

Or is that your doing?

I have no say in the matter is I don't work for MAGIX or Waves. Although I do beta test for both companies.

Regards
Kraznet

Thanks for taking the time.
Your tutorials are excellent and helped a lot too.

I have been taking more space here than intended, I will leave it at this.

[Jim Roseberry]

I think the point was that the editor he showed, which is the editor for his specific keyboard, is only in VST3. So for him, VST3 has more value.

Brent

Hi Brent,
I was addressing the last point ("I don't think this can be done via VST 2.x")
I was giving an example of the exact same type of "full-remote" editor... that WAS done as a VST 2.x plugin.

It's obvious why Yamaha is making the editors for the MOTIF series VST3.
They were first to the VST3 table (having changed the spec)... and they want you to run Cubase.

Note that I've got nothing against Yamaha or Cubase.
I own a license for version 7... and I own a MOTIF XS.

[koolkeys]

Don't get me wrong, I know what you were addressing. I just think he was being very specific in that he couldn't run the editor he uses in a VST2.4 host, because it's not made for VST2.4. Hence it not being possible.

I agree that they want you to use Cubase, and while the actual features are possible elsewhere, that particular editor isn't possible to run without VST3.

I wish I had a Motif.

Brent

[Andywanders]

Jim, thanks for the info. I really didn't know if it could be done with VST 2 or not.

Brent, that's exactly what I meant. It's unfortunate (for me) that my editor isn't available as a VST 2, but that's life I guess.

In the meantime (and being the eternal optimist that I am), I'll just stick with Cubase and Studio One until Magix get on board with VST 3.

I'm sure they will eventually. Even Imageline support it now, and more plugin devs are into it these days (SSL, U-He and others).


______________________________________________________

Off Topic...

I wish I had a Motif.

Get one..! You won't regret it. I've had loads of hardware over the years - Prophets, Korgs, Rolands, EMUs, and a gorgeous Kurzweil K2500 - but in a lot of ways, the Motif beats them all. Take a good look at the MOX next time you're in a music store. It's incredible bang for the buck. You get Motif sounds at a budget price - no sampling though - and if you're a keyboard player, the 88 note is a joy to play.

Anyway... Back to Samplitude