Latest Builds: Rev 2242 April 13

[Urs]

Hi,

will the "unit" issue during the display automation parameters be addressed in the near future? emoving this string would amke editing Diva, ACE et al even better on hardware controllers

Thanks!

Cheers

Well, it has been "unit" since 2004 and a few days ago was to my best knowledge the first time it came up. I have been thinking about this, and we can certainly use better terms for a lot of parameters. It does require us to implement an appropriate model and to go through the parameters of every module in each of 30+ plug-ins. I think we have about 100 different modules with an average of, hmmm, 20? parameters.

We might rather start doing this gradually, once our new staff is up to speed.

[Urs]

Hi, your edit display.

sorry I meant loading older projects not older presets.
that is I open a project that I used a preset in in one of your plugins, or Cubendo allows you to choose a default setting or preset..... I usually have one of your presets saved as the default for that plugin in Nuendo.....loading a new instance of that plugin in fresh project doesn't show you the preset name.

rsp

Interesting. I presume that this is a side effect of us trying to "remember" and display the preset name in VST3. We'll look into it.

Unfortunately every fix we did last year came with a bag of bad surprises :-/

[zvenx]

My repro is very simple by the way.
New Project in Cubendo
load an instance of either Zebra/Diva (I didn't try ace but I assume it does the same)
choose a preset.
as an insert use Saturn, choose a preset.
Save the project.
Close the project
Re-open the project
Parameters are recalled properly, but in the header instead of seeing the preset name I see my name, and version number.

rsp

[asseca]

This version crashes eXTv1.4, eXTv2.7

Also fails to load in BiaB2014

VST scanning fails in Chainer (Demo)

[Urs]

This version crashes eXTv1.4, eXTv2.7

No problem on Mac and PC here, 1.4, 2.6, 2.7beta

VST scanning fails in Chainer (Demo)

Hmmm... what processor do you have?

[asseca]

Intel i3 3225, Win 8.0 64-bit, 16GB RAM, ASIO4ALL
Problems tested with different latencies + settings to no avail.

Summary: (32-bit hosts)
This works fine in:
ReaperV3.78
Cantabile Light v2.0.0.2067
Presonus Studio One v2.6.2
VstHost v1.5.4
NI Kore v2.1.4
BloXpander v1.5
MUX v5.5.1

Problems in:
Crashes eXTv1.4, eXTv2.7, asHost
Fails to load in BiaB2014, RealBand 2014
VST scanning fails in Chainer (Demo)
Crashes Wavosaur v1.0.8

[Urs]

Hmmm, I wonder why it fails to work in eXT elsewhere (we had similar reports before), but on our machines they always work... strange stuff...

[asseca]

So far problems in 6 32-bit hosts ...

[Urs]

So far problems in 6 32-bit hosts ...

Hmmm, some of those might not be compatible with VST2.4. Or multithreaded plug-ins.

Do you have any crash logs?

If you place an empty text file called, say, ACE.log on your desktop and let any of those scan ACE, is there anything logged? Because if not, then ACE isn't even loaded and thus not recognized as a plug-in.

[asseca]

Zebra.log has the following entry after a crash:
AM_MemoryRecord closing down with 0 allocations vs 0 freed

Some of these 32-bit hosts may not be v2.4 compatible, but worked fine with Zebra2 rev2157.

[EvilDragon]

Some of these 32-bit hosts may not be v2.4 compatible, but worked fine with Zevra2 rev2157.

rev2157 was VST2.4...

[Urs]

Zebra.log has the following entry after a crash:
AM_MemoryRecord closing down with 0 allocations vs 0 freed

Some of these 32-bit hosts may not be v2.4 compatible, but worked fine with Zebra2 rev2157.

Cool thanks. That's rather interesting indeed. I'll look into that possibility. It either means that these hosts opena nd close the dll without actually doing anything and maybe we haven't caught that case, or it could also mean that they can't "find" the plug-ins and thus close the dll.

That said, I'm the memory management routine that prints this has been in there since early 2129. So it wouldn't be the cause if 2157 doesn't crash.

I just hope I can reproduce it tomorrow.

[fuse]

Latest build of Satin (and the two before) 64bit VST3 crashes Sonar X3e 64bit, Windows 7 64bit.
VST2 works fine.

[Urs]

Latest build of Satin (and the two before) 64bit VST3 crashes Sonar X3e 64bit, Windows 7 64bit.
VST2 works fine.

Good to know, thanks.

We're officially taking VST3 out of the default installation options, making them optional installs. We're adding a ReadMe to the downloads pointing out the known issues and a recommendation to stick to VST2.

This may sound extreme, but really, VST3 has become a nightmare for us, and with every new VST3 host popping up came more crashes. The "full VST3" as opposed to "simplified VST3" is not a plug-in format we can afford to put further work in.

We'll re-evaluate our commitment to VST3 once we find the months to rewrite things for the "simplified VST3" API, but we really can't hold these updates off for another quarter or two until this has happened. Hence the decision to set VST3 aside.

[Urs]

Problems in:
Crashes eXTv1.4, eXTv2.7, asHost
Fails to load in BiaB2014, RealBand 2014
VST scanning fails in Chainer (Demo)

I just tried with Chainer demo: All plug-ins work, just like in all versions of energyXT. This is with Win 7 SP 1

Maybe there is a problem with Windows 8? I think we have one around, we'll give it another try.