Updated to v1.2: Integrate — Subtractive Synthesizer [CLAP, FL Studio]

[ThomasHelzle]

Also let me know which CPU you are using.

I'm using an intel core i7 3930K CPU. 64GB RAM, Focusrite Scarlett 18i20 gen1 audio interface with latest drivers, Geforce GTX 2080 TI.

Cheers,

Tom

[emef]

i installed the demo, instant crash in bitwig every time i try to play a note
i want to delete the demo, but can't find where integrate is stored and it doesn't show up in the apps and features section
can you help me find them, i'm using windows 10

Sorry to hear that's it's not working for you.
The 64-bit version is installed into

Code: Select all

C:\Program Files\Common Files\CLAP\

and the 32-bit version is in

Code: Select all

C:\Program Files (x86)\Common Files\CLAP\

cheers

[nakst]

Small update to Version 1.0.1. Changes:

• Added "Uninstall" option to the installer
• Improved diagnostics information for crash reports
• Minor bugfixes

[ThomasHelzle]

I'll give that a try.

Would also be good if you would offer to only install the 64Bit version - I no longer have any 32Bit hosts (although Bitwig can load it of course).

Cheers,

Tom

[nakst]

Small update to Version 1.0.2. Changes:

• Allow only installing the 64-bit or 32-bit CLAP plugin at a time
• Preview installation folder path
• More detailed diagnostics reporting
• Support diagnostics in the FL Studio plugin

[Lbdunequest]

This is surprisingly damn good sounding vst.

But i woulsdnt say its a low cpu usage synth. With unison on its demanding like uhe diva with digital oscillators on.

Im using i7 4790k

I dont think that auto code select feature is great idea if it might select wrong algorhytm.

[ThomasHelzle]

Small update to Version 1.0.2. Changes:

• Allow only installing the 64-bit or 32-bit CLAP plugin at a time
• Preview installation folder path
• More detailed diagnostics reporting
• Support diagnostics in the FL Studio plugin

So did you find the cause of the crashes already?

[nakst]

So did you find the cause of the crashes already?

I am still working on it. Another person with the same CPU as you has reported the same issue -- it seems to be a tricky one to find. This new version 1.0.2 contains more diagnostics information in the crash reports, so if you're able to send me a crash report made with this new version that would be greatly appreciated.

[ThomasHelzle]

Do you use any SIMD/AVX stuff the CPU doesn't support?

Also: When I throw Integrate.clap onto "Dependency Walker" it shows a ton of errors.
Does it need a specific ms-runtime maybe?

Cheers,

Tom

[nakst]

This is surprisingly damn good sounding vst.

Thank you! A lot of people I've talked to seem to be enjoying it.

But i woulsdnt say its a low cpu usage synth. With unison on its demanding like uhe diva with digital oscillators on.

Ah, it's possible I might have written that during development when there were less features running in the signal path, and since then CPU increased as I added more features. I'll have a look around at my promotional materials to double check if any information is out of date.

[nakst]

Do you use any SIMD/AVX stuff the CPU doesn't support?

The v1.0.2 update includes details in the crash report about which CPU features it is trying to use. If you're able to send me a new report, I'll compare this with your CPU to see if that's the issue.

Also: When I throw Integrate.clap onto "Dependency Walker" it shows a ton of errors.
Does it need a specific ms-runtime maybe?

If the plugin is missing dependencies then the DAW will refuse to load it -- that is a Windows feature. You should not worry about what Dependency Walker says, it does not show information correctly since around Windows 7, IIRC.

[mystran]

Also: When I throw Integrate.clap onto "Dependency Walker" it shows a ton of errors.
Does it need a specific ms-runtime maybe?

If the plugin is missing dependencies then the DAW will refuse to load it -- that is a Windows feature. You should not worry about what Dependency Walker says, it does not show information correctly since around Windows 7, IIRC.

I think technically depends.exe still works "correctly" yet the problem is that there are some "delay loaded" (ie. actually only needed in certain situations) dependencies in some system libraries that depends.exe complains are missing and I think all the common ones that it likes to complain about are stuff that won't actually ever be loaded on a system where they aren't installed... or some such nonsense like that.

It's still a useful tool, but you have to be careful in how you intepret the results and not everything in red is an actual problem.

[ThomasHelzle]

Ok, thanks for the explanation, just thought that may be an issue since it happened to me in the past when a plugin needed a specific runtime.
Will give it another try later.

My 9 year old CPU, overclocked to 4.1GHz does very well otherwise, even for my 3D work it's pretty good.
I think I only had one other application that didn't work.

Cheers,

Tom

[nakst]

Small update to Version 1.0.3. Changes:

• Fix detection of some older CPUs which previously caused a crash in the reverb DSP code.

[ThomasHelzle]

So I ran 1.0.3 and it still crashes the same as before - after a plugin restart I see the demo screen.
Do you still need the crash data or did you figure it out in the meantime?

Cheers,

Tom