Samplitude ProX and Waves Element synth - just unstable and crashes...

[lfm]

Evaluating ProX and try to get Element to work.

Every other type of VST instrument runs without any issues.

But the special thing about Element is that all hosts list it as FX - so you have to load like an FX.

If I can get it load run - it doesn't sound right at all. Very bitcrushed kind of. And when closing gui it crashes.

But most of the time it just crashes within a few secs after loading.

If I load on audiotrack it loads, but when pressing midi button - it crashes within 2s.

Have had contact with Magix support all week and we are not through debugging their debugging tools yet - they cannot read the output of a testprogram of theirs that I was to run.

So should I just leave the idea of Samplitude - or is there a solution?

Element is brand new, and listed as supported at Waves compatibility chart.

I get very much the feeling as when I left Cakewalk Sonar that has random crashes - that Samplitude is in the same untrusted realm.

And I should mention Element runs without any problems in Reaper or Sonar. So nothing wrong with my system as far as I can tell.

Latest RME drivers, latest NVIDIA drivers, latest ProX, latest Waves v9r11.

Any ideas what to try?

Thanks.

[siriusbliss]

I think someone over at the main Samplitude forum got this to work, so you should post over there.
Samplitude.com

Good luck

G

[lfm]

Thanks.

I got a new email from support this afternoon, saying they will look at dumps and logs and eventually come with an update.

If they were able to reproduce they did not say.

If there is a workaround, why not provide that to users until it's fixed. If on their forum they should know too.

How did they ever get a 'supported' on Waves compatibility chart one wonders.

What I'm evaluating is much more about a reliable system and vendor, than this particular synth.

So I thought I did something wrong, really, since Waves chart said 'supported'.

They have been thorough enough to say Waves Tune is not supported. I was dead sure anything listed supported really was darn well tested.

So what I think about Magix - don't go there, it's looking for trouble.

[Hink]

thread on it on the samp forums...

http://support2.magix.net/boards/sampli ... %2Belement

seems to me if kraznet can duplicate it they are working on it but here's a video he made on how to use elements in samp

[Kraznet]

I actually made that video to show someone how to get it to work in Samplitude.
However not long after I discovered it was prone to crashing Samplitude more times than not. I made 2 videos which I sent to waves and they said they would work on it but as yet nothing has happened.


Regards
Kraznet

[Skorpius]

But the special thing about Element is that all hosts list it as FX - so you have to load like an FX.

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.

So should I just leave the idea of Samplitude - or is there a solution?

As I said, I presume it's a bug in Element. However, you might want to try different sampling rates (44/48/96) and see if Samp reacts identically with each sampling rate.

Otherwise, I would definitely not recommend leaving the idea of Samplitude. You won't get any other DAW with such mighty object editing features. They make ProX unique.

[lfm]

thread on it on the samp forums...

http://support2.magix.net/boards/sampli ... %2Belement

seems to me if kraznet can duplicate it they are working on it but here's a video he made on how to use elements in samp

Many thanks.

What beats me is - how did Element end up on the supported list at Waves?

It's really better to say 'not supported' there until it really is.

[lfm]

Otherwise, I would definitely not recommend leaving the idea of Samplitude. You won't get any other DAW with such mighty object editing features. They make ProX unique.

I really had a bad start - but kept on working on it since I feel there might be something to what you are saying.

But it's just not very intuitive.

What is a breeze in Reaper is such a struggle. But many things you do once possibly to reuse in all kinds of projects.

Made a track folder for Superior Drummer with outputs, then a submix track to go with it - try making this a drums stem in the end.

But I fail to route this submix to master. It won't allow me?
It's really uphill just getting routing done....

And bunch of simple things like, how do you add multiple VST folders?

They have different naming of outputs in track dialog and inspector on the side. The final target is listed as output in track dialog - even though going through master, but side inspector says StMast. Very confusing.

They clutter gui with "DirectX/Vst" everywhere - who the hell is using DX stuff anymore - in x64?
It's really back to 2005 when I used Sonar that still had DX as main interface.

And I'm looking for some plugin manager to get things sorted into categories, and remove stuff I will never use from gui.


But I will try to at least get what objects are about - it might be worth it - if I ever get the routing done.

[ATS]

I tried to demo Element in FL Studio but could not get it to come up as a synth. I emailed support but they still don't support FL Studio so they would not help. I love Waves plugins but it frustrates me to no end how they don't support one of the most used hosts out there. So I just deleted it off my computer and will save some money.

[lfm]

I tried to demo Element in FL Studio but could not get it to come up as a synth. I emailed support but they still don't support FL Studio so they would not help. I love Waves plugins but it frustrates me to no end how they don't support one of the most used hosts out there. So I just deleted it off my computer and will save some money.

Element is a really lovely sounding synth - that's why I tried it first when testing Samplitude. I ditched all the Arturia stuff for it.

In both Reaper and Sonar I manage to load it as normal FX without issues at all. I guess it depends on the host how it's built and handle instruments.

Samplitude obviously handle it very differently.

And Reaper allow you to change it listed as VST instrument as well. But it worked just as well, listed as FX, just looking in another place.

I don't know how it works with Waves - if vendor itself is to be big enough to take responsibility or if Waves really put their own people testing everything. I really believe the former - and Magix did a sloppy job doing it.

[Skorpius]

But it's just not very intuitive.

It's certainly not as intuitive as, e. g. Studio One, but it's so much more powerful.

I can't follow you with everything you're complaining about. But Samplitude definitely requires a look in the manual from time to time. So, if you don't bother to look certain things up in there, you may not understand some of the basic functions.

I've been using ProX for a couple of years now, and there are still loads of functions I haven't even used or don't know anything about yet.

Consider ProX as a very powerful tool which does require some efforts to really get to know it. It's definitely not a tool for someone who's just started to work with sequencers or DAWs.

What is a breeze in Reaper is such a struggle. But many things you do once possibly to reuse in all kinds of projects.

You can save just about anything you do or create with ProX as a user preset: projects of any kind (e. g. 8 Track Mono in/out ADAT transfer), FX settings, Mixer settings, the workspace - you name it. Work things out the way you need them, save them as a user preset, and don't forget to make backups. Then you can keep loading those presets into ProX until Judgement Day.

But I fail to route this submix to master. It won't allow me?
It's really uphill just getting routing done....

Not sure what you're talking about there. Have you tried the "Track" menu, where you can define the Track Type and, e. g. add a Submix Buss to which you route individual tracks? Also, have you checked the various managers, like the Routing Manager or the VST Instrument Manager?

Be sure to check those settings or consult the manual. I don't think there are a lot of things you cannot do with ProX.

And bunch of simple things like, how do you add multiple VST folders?

What on earth do you need multiple VST folders for? You choose one main VST folder and put everything in there, FX and Instruments. ProX distinguishes them automatically, even if they are in countless sub-folders of the main VST folder.

They clutter gui with "DirectX/Vst" everywhere - who the hell is using DX stuff anymore - in x64?

I don't know what you mean by "everywhere". The only place where I ever encounter DirectX is in the settings (VST/DirectX/Rewire). Just ignore it if you don't use it. And don't forget that some people might still need it, so it's a case of backward compatibility.

But I will try to at least get what objects are about - it might be worth it - if I ever get the routing done.

An object is everything you put in a track or record to a track. It can be a complete track (unsliced) or just a sliced portion of Midi or audio. Each and every object can be handled individually. And that's what I call flexibility.

OK, I hope I could help. Make sure to consult the manual for further information, because Magix doesn't pay me for promoting their great DAW.

One thing I should also mention is the great support of Magix. With some companies, it takes several days before they bother to answer your question. Magix usually answer the same day and are usually very supportive. I don't know if that's also the case with Reaper.

[lfm]

OK, I hope I could help. Make sure to consult the manual for further information, because Magix doesn't pay me for promoting their great DAW.

One thing I should also mention is the great support of Magix. With some companies, it takes several days before they bother to answer your question. Magix usually answer the same day and are usually very supportive. I don't know if that's also the case with Reaper.

You certainly helped, thank you.

Not that I think I really will need any of the object nitty-gritty most advanced stuff. Just working like a tapemachine like most daws works for me.

But I will try to grasp the greatness of it all.

I do agree support is fairly quick, and they really try to help.
That's a good start.

Even though we struggled to debug their debugtool this week, they could not read the format created from syscheck or whatever it was called.

But still cannot digest that they put Waves stuff to be supported - that isn't.

It would be good to have at least two daws I can trust fully. Planning to quit my dayjob and do music fulltime - and don't want daws to stop the show - something must work at all times.